Senior Software Engineer in a team of 8 on the Platform DevFlow team, distributed across EMEA, NASA and APJ, under the Engineering Productivity organisation within Elastic's Platform organisation. Delivering and supporting tooling that is "left of the main branch" to improve the developer productivity of teams. Working in a globally distributed team of 8 on the Platform DevFlow team in the Engineering Productivity organisation

• Working to support + improve services owned by the team, around how we use Buildkite (CI/CD platform), development environments for Elastic Cloud and Elastic Cloud Serverless, Supply Chain Security, and more to support internal customers' expeirence to ship more easily
• Defining and leading a cross-engineering effort to provide a "golden path" for dependency updates via Renovate, providing a batteries-included setup for teams to keep on top of internal and external dependency updates
• Working with stakeholders across the organisation from Engineering, Infosec and IT
• Working with stakeholders across the organisation
• Providing an in-depth on-call handover + runbook, as well as at-a-glance views of the operational health, as well as a mix of (internal) customer-facing and operator docs
• Delivered on time, on budget, and worked with Stakeholders to carefully avoid scope creep
• Working through a revamped new design doc process and was the first IC to receive approval
• Implemented novel solutions to be able to better test + maintain complex Renovate rules
• Forseeing a lack of central visibility into usage of Renovate, implemented a novel solution to be able to regularly scan teams' configurations
• Active member of Platform EngProd's follow-the-sun "Host of the Week" + on-call rota (for in-hours and out-of-hours support) and active driver of feedback around improving our processes, ownership and improving the experience for Operators and Customers
• Active member + driver of improvement around our process for in-hours and out-of-hours support
• Active driver of team and organisational process improvements
• Working to support + improve services owned by the team, around how we use Buildkite (CI/CD platform), development environments for Elastic Cloud and Elastic Cloud Serverless, and to empower engineers across the Platform org to ship more effectively
• Introducing areas of focus to improve developer experience and resolve papercuts
• As DevFlow owns Supply Chain Security, working with IT, Infosec and senior stakeholders to highligh and address a number of gaps in controls, or to look at possible risks in our Open Source supply chain
• Involved in working towards "0 CVEs" initiative at Elastic, with the rollout of Chainguard Images (based on Wolfi) across the organisation
• Providing novel insights into the End-of-Life status of Chainguard images in use, using dependency-management-data
• Speaker at the internal Engineering Productivity Lightning Talks
• Building and maintaining tooling for deploying development environments for Elastic Cloud and Elastic Cloud Serverless
• Building and maintaining tooling for cleaning up unused cloud resources
• Building and maintaining tooling for cleaning up unused cloud resources and deploying development environments for Elastic Cloud (Serverless)
• Invited to join the Open Source Working Group (not yet an Open Source Program Office) at Elastic, working to improve Elastic's consumption of Open Source, giving back to the community + improving outbound Open Source contributions.
• As part of the Open Source Working Group, using dependency-management-data to gain insights into our use of Open Source and internal dependencies that we didn't have before
• Improving usage of Renovate across the organisation to better manage keeping on top of dependency updates, by rolling out shared configurations and managing common Elastic-specific dependencies
• Supporting improvement of teams' usage of OpenAPI, including changes required within the oapi-codegen OpenAPI-to-Go code generator I maintain, which Elastic has been using since before I joined
• Supporting improvement of teams' usage of OpenAPI, including supporting upstreaming of changes required within oapi-codegen
• Contributing to conversations around OpenAPI governance + spec visualisation tooling
• Invited to join as an (internal facing) Elastic Security Champion, due to my continued focus on security of internal software, our software supply chain, and reducing risk of issues earlier in the Software Development Lifecycle
• Co-organiser of the Go community at Elastic, with twice-monthly meetings of alternating discussions and lightning talks, and improving Go adoption + experience
• Working asynchronously with a distributed team and company

Senior Software Engineer in a team of 12 across the UK and India, working on software that connects consumers, riders, restaurants and agents, making sure everyone has a great experience with Deliveroo

• Led work to build a new Go API, with a heavy focus on design-first OpenAPI, with integration into a TypeScript consumer codebase, as well as retrofitting OpenAPI into a Rails codebase to improve speed of integration as well as improving the documentation around the service. The pattern for design-first OpenAPI has been adopted across several other projects in the org. Involved working with the Open Source project to upstream changes to allow it to work with different functional requirements, and through continued development on the library, I am now a maintainer on the project
• Working across a team of 12 engineers, leading on features and supporting engineers on a mix of Go, Ruby on Rails, (Full Stack) Typescript codebases
• Working to raise the bar on quality, consistency and maintainability of shared libraries across the organisation, including working on internal developer tools for better automation and code generation for Go projects, as well as tooling around OpenAPI.
• Single-handedly driving the rollout of Renovate across the ~2100 repositories across the organisation as a better fit for keeping our dependencies up-to-date as an Enterprise
• Champion of supporting Open Source projects we use, through understanding how we use our projects (through the dependency-management-data project mentioned below, initially for Hacktoberfest but also for cross-organisation capabilities, including heavily enabling the Product Security and Release Engineering teams to more effectively target changes.
• Improving the community around Open Source at Deliveroo, through events such as Hacktoberfest and running several team discussions around Open Source sustainability
• Championing Open Source sustainability and building internal community around contributing to Open Source, partly through Hacktoberfest
• Built a set of tooling, in an Open Source first approach, under dependency-management-data for providing a queryable database of how your projects use Open Source and internal dependencies, allowing for querying of software using end-of-life versions or packages that have been deprecated.
• Built an event-driven set of services in AWS Lambda with AWS EventBridge to provide real-time data updates for dependency-management-data
• Took ownership of an unmaintained, but heavily used, developer tool ("Marvin the paranoid staging android") for ensuring deployments to staging environments were performed, building up domain knowledge and implementing features to improve the developer experience, as well as ongoing maintainence and onboarding.
• Led improvements in the team's ways of working to improve team effectiveness, increasing predictability of sprint delivery by a minimum of 25% in the first 6 months of following these practices.
• Building internal tooling for improving efficiency and developer experience with various internal and external tools
• Regularly contributing to the internal libraries and tooling, with a particular focus on the Go ecosystem
• Member of the Go team to help guide and improve usage of Go across Deliveroo
• Editor of and regular contributor to the Deliveroo Engineering blog (writing, editing and finding opportunities for new posts) and the Deliveroo Engineering Twitter account.
• Building and supporting infrastructure in AWS, using Terraform and Datadog
• Making changes to existing (monolithic) Ruby on Rails codebases, with a focus on decomposing as scaling limits are hit, or as considerable performance benefits could be achieved
• Led internal investigations around the archiving of gorilla/mux and the Gorilla toolkit, and its impact on Deliveroo's usage of the library, aided by the dependency-management-data project, and encouraging important conversations about the sustainability of our Open Source dependencies
• Rebuilt internal (RESTful) API documentation site with a tactical solution using Hugo and Stoplight Elements to replace the existing service, as well as writing a design document to plan for the target state of API documentation at Deliveroo.