🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Come and join a team of builders creating the next generation of AI-powered developer tools for Amazon. We're part of Builder Operations, and our mission is to put intelligent, agentic tooling directly into the hands of every Amazon builder — accelerating how they write, ship, and operate software. This is a unique opportunity to join an early-stage team with a greenfield product, where you'll own features end-to-end, ship fast, and see your work adopted by hundreds of thousands of engineers across the company. Work/Life Balance Our team puts a high value on work-life balance. It isn't about how many hours you spend at home or at work; it's about the flow you establish that brings energy to both parts of your life. We believe striking the right balance between your personal and professional life is critical to life-long happiness and fulfillment. We offer flexibility in working hours and encourage you to find your own balance between your work and personal lives. Mentorship & Career Growth Our team is dedicated to supporting new members. We have a broad mix of experience levels and tenures, and we're building an environment that celebrates knowledge sharing and mentorship. We care about your career growth and strive to assign projects based on what will help each team member develop into a better-rounded professional and enable them to take on more complex tasks in the future. #asbx Key job responsibilities - Design and build client-side AI coordination systems that orchestrate multiple agentic coding tools into a unified developer experience - Own features end-to-end — from design through implementation, testing, and production rollout to Amazon builders - Develop in TypeScript/Node.js, with contributions to systems-level components in Rust or Go where performance and isolation demand it - Build secure integration layers including process sandboxing, credential isolation, and shell access controls - Design and implement agent orchestration patterns — prompt routing, tool coordination, memory and context management across AI sessions - Collaborate with security, platform, and partner teams to ensure tools meet Amazon's security bar while preserving developer velocity - Instrument and monitor tool adoption, driving improvements based on usage data from hundreds of thousands of builders - Contribute to an open-source-style internal community — reviewing contributions, shaping extensibility patterns, and supporting adopters A day in the life You start your morning reviewing a pull request from an internal contributor who's extended one of your tool's integration points — the community is active and you're helping shape how others build on top of the platform. After merging, you pick up your current feature: a new coordination layer that lets multiple AI agents share context seamlessly during a coding session. You prototype in TypeScript, test locally against Kiro CLI and Claude Code, and push a working iteration before lunch. In the afternoon, you pair with a teammate on a tricky orchestration problem — how to gracefully hand off context between tools when a builder switches tasks mid-session. You spike two approaches, benchmark them, and land on the simpler one. Before wrapping up, you check adoption dashboards to see how last week's release is landing across teams and jot down a couple of ideas for reducing friction you're seeing in the usage patterns. Your days are a mix of deep building, fast shipping, and lightweight collaboration. You own your features from design through production, and you see real builders using your work within days, not quarters. About the team This role sits on Builder Operations, a team within the Amazon Software Builder Experience (ASBX) organization. We help builders ship and resolve faster without trading safety for speed. Our team owns operational work end to end. We shape how that work gets prioritized and coordinated, how code moves safely through release pipelines, and how production issues get detected, resolved, and prevented from recurring. Success looks like builders spending their time architecting resilience rather than firefighting failures. AI agents already operate in production across Amazon's builder ecosystem, reviewing code, resolving operational issues, and supporting oncall teams at scale. You would join at an inflection point. Agents deliver measurable results today, and the next phase shifts operations from a human-in-the-loop model toward safe, context-aware, agent-first execution. You would help build the systems that let agents act safely, understand the context they operate in, and coordinate their work so that every Amazon builder can rely on them daily.
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.
