Staff Software Engineer

Engine is an all-in-one travel and spend management platform for businesses and travelers. The Staff Software Engineer will drive system design and build scalable, secure, high-performing software systems and APIs, while collaborating cross-functionally, mentoring engineers, and leading key engineering initiatives. The role also emphasizes daily use and deep understanding of agentic coding tools and AI-first development practices.

Responsibilities:

• Design and Implement: Drive System Design output across the team, craft innovative software systems and APIs that contribute to the success of Engine’s mission, focusing on scalability, security, and performance
• AI First Mindset: Deep agentic experience (Claude Code, Cursor, or comparable) tools; not just daily use, but in depth understanding of agentic workflows, how to build a harness, how to structure a codebase for agents, etc
• Collaboration: Collaborate with cross-functional teams, including Product and Data Science, to unlock new opportunities and deliver seamless experiences for our customers
• Leadership: Mentor mid-to-senior level engineers, and lead efforts to ensure the quality, scalability, and robustness of our software
• Ownership: Lead key initiatives that improve efficiency, enhance system performance, and drive customer satisfaction

Requirements:

• 8+ years of hands-on experience in designing, implementing, and maintaining highly available and high-performing distributed systems. You have a proven track record of building public-facing (consumer-grade) APIs and managing the complexities of versioning, deprecation, and consumption-based rate limiting
• Node.js, TypeScript, Kotlin (or similar modern backend languages), React, and AWS
• You're a problem-solver with a strong grasp of software design principles, scalability, and system architecture. You thrive in fast-paced, innovative environments and prioritize Domain-Driven Design
• AI-first as a daily practice, not a talking point. You are actively using agentic coding tools (Claude Code, Cursor, or comparable) and you have a point of view on where they help, where they hurt, and how to set the team's defaults