• Learn everything there is to know about aviation maintenance planning through our on-boarding process (so don't worry if you do not have any experience in this industry!) • Analyze tough customer problems and come up with great designs that you will turn into efficient backend solutions • Design, develop, and maintain scalable systems and well-tested features • Design and implement services that are reliable, high-quality, performant, and sustainable • Work with our business team to build great user stories and designs from (sometimes) ambiguous requirements or problems • Occasionally wear many hats due to our smaller team size, with opportunities to work on everything from design to deployments, or meeting with our customers to build integrations for them

• Proactively increase the code quality of our Exporter apps by checking & improving the code quality with LLMs (e.g. Claude) • Extending the end-to-end test coverage and automated test runs, including performance tests • Delivering 3rd level support, which includes analyzing bugs with the help of Atlassian Intelligence • Fixing found bugs and automating these processes with Jira Service Management Premium

• You will own the optimization of our discovery and checkout journeys, rapidly shipping customer experience improvements that directly lift onboarding success and booking conversion rates. • You will drive fast-paced product iterations by taking feature briefs from early concepts to live production environments, keeping technical implementations simple and impactful. • You will run continuous experiments and A/B tests to validate new initiatives, such as building configuration comparison features that help customers evaluate their vehicle options. • You will champion a "build it, run it" mindset, taking full ownership of testing, deploying, and monitoring clean, reliable frontend and serverless systems. • You will leverage modern AI workflows and orchestrate agents to accelerate your development pace while maintaining exceptional code quality and user experience standards.

• Products end-to-end. You pick up a problem from product or a founder, write the spec yourself, decide what's in and out of scope, build it, ship it, and watch the metric. If the metric doesn't move, you figure out why and try again. • A direct line to product. No PM in the middle. You talk to product directly, push back when you should, and decide together what's worth building this week. • A team of agents. Claude (or whatever ships next month) handles code review, test generation, and boilerplate. You set the rules, review the reviews, and keep the bar for agent-produced code in your project above the company average. • Production health in your area. Bug count, incidents, test coverage, the long-term shape of the codebase agents are touching. You own the number, and we measure it. • Speed, measured. Lead time, throughput, agent cycle time. You'll have a personal baseline in week 2 and an improvement target by month 2. We don't count tickets closed. • Saying no. Roughly a third of what lands on your plate shouldn't get built. The right answer is often "let's run a 2-day experiment first" or "this doesn't move a metric we care about". Push back with reasoning, not instinct.