Senior Software Engineer, Instacart

• 5+ years of software development experience
• A strong sense of ownership, self-motivated and enjoy the fast pace of a startup environment
• Previous experience building and maintaining a robust build system using Jenkins, BuildKite, Gitlab or CircleCI
• Strong knowledge of Go, Ruby, or Python and experience with AWS Infrastructure
• Ability to balance a sense of urgency with shipping high quality and pragmatic solutions

Desirable

• Our backend systems power the clients used by millions of customers every year to buy their groceries online. These systems must also support tight integration with the largest retailers in the US and Canada. Engineering at Instacart provides the opportunity to work on challenging scaling problems while also designing the features that will define our industry. You will learn how to build in an open collaborative environment serving millions of requests daily
• As a Senior Software Engineer in our Infrastructure team, you will be the technical force that shapes our infrastructure. You will design, develop, and maintain comprehensive access controls and governance frameworks to safeguard the integrity and privacy of our infrastructure. Your work will elevate the data utilization across several departments, enabling valuable insights, informed decision-making, and driving business value
• We are leveraging AI to automate and simplify the development lifecycle. Our new features focus on:
• Owning and Enhancing the Build System: Develop and maintain robust build systems within Bento (our local development CLI tool) to support scalable and efficient software deployment
• Incorporating AI Tools: Integrate AI technologies to streamline workflows, enhance code quality through automated reviews and testing, and reduce the manual burden on developers
• Collaborate with team members to enhance Bento, focusing on scalability, usability, and the integration of AI tools
• Work on the orchestration of on-demand and ephemeral CI environments that allow for integration and E2E tests before merging PRs. This proactive approach shifts quality assurance earlier in the development process (“shift left”), ensuring that only the most stable, well-tested changes are merged into the master branch
• Continuously engage with metrics to drive improvements in our processes and outcomes, directly enhancing developer productivity and satisfaction
• Maintain and improve the build systems to allow for 1000+ developers to get changes tested, built and deployed faster