🎁 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 →
We're building the platform that powers the Amazon Ads Console — the framework layer that drives development velocity, latency, and availability improvements for tens of product teams building advertising experiences. As the console transitions toward agentic, AI-driven workflows, we need a Senior SDE to lead the technical evolution of our platform and the new systems that will underpin this shift. The Ads Console Frameworks team owns Pantheon (the app framework powering the console's architecture), Argus (an agentic quality evaluation platform that autonomously walks advertiser workflows to detect regressions), Compass (a self-serve product analytics platform for the console), and the shared services and components that every Ads Console page depends on. Our systems serve as the foundation dozens of teams build on. This is not a heads-down coding role. You'll drive architectural decisions with broad ambiguity — designing how the console's frameworkS evolve to support agentic development patterns, defining how product analytics should work across 141 pages, and shaping platform contracts that other teams adopt. You'll need strong product instincts to understand advertiser workflows and form a point of view on where framework-level solutions unlock the most leverage, and either bring knowledge of the advertising business or the curiosity to develop it quickly. The role spans technically complex domains — from front-end framework architecture and module systems, through platform services targeting 99.99% availability under peak load, to AI agent orchestration, evaluation systems, and governed data pipelines. You'll also be expected to embrace and advance AI-native development practices, using AI tools and agentic coding techniques to accelerate how the team builds software. This is a horizontal team role: you set technical direction that other teams build on, define API contracts and integration patterns across organizational boundaries, and maintain platform quality as adoption scales rapidly. The right candidate has designed and built platform systems at scale, can operate independently in highly ambiguous problem spaces, has recent hands-on experience with AI-powered or agent-oriented systems, and brings product thinking to every technical decision. Key job responsibilities - Lead technical architecture and hands-on delivery across the full AI application stack — UI, services, agent infrastructure, orchestration, and evaluation — for the Ads Agent experience and integration framework used by dozens of partner teams. - Bring product thinking to every technical decision: develop deep understanding of advertiser workflows so architecture choices reflect how advertisers actually use the product. - Set architectural direction on a horizontal platform team: define integration patterns and API contracts that dozens of teams build on, lead design reviews, and maintain quality as adoption scales. - Establish and exemplify best practices for building AI applications (evaluation methodologies, quality guardrails, prompt engineering, orchestration patterns) and for AI-native development (using AI tools and agentic coding to accelerate the team's delivery). - Drive operational excellence and mentor engineers across the team. A day in the life You start the day reviewing agent quality metrics and system health across the stack. Mid-morning you're leading a design review for a new framework capability — asking sharp questions that blend technical depth with product thinking about advertiser workflows. After lunch you're writing high-leverage code: the interface for a new extension point that partner teams will build on. Later you join a cross-team architecture discussion on whether a new capability should be a skill or a separate agent, driving alignment by making tradeoffs concrete. You close the day refactoring a service that grew complex during prototyping — because on a horizontal team, accumulated complexity compounds with every partner. About the team We are a team of ~50 engineers building the experience layer for the Amazon Ads Agent and Console. We own the chat interface, advertiser-facing communications, and the frameworks that enable dozens of partner teams to integrate agent capabilities across the Ads Console. This is a horizontal team — our APIs, patterns, and quality bar ripple across the organization. We're at an inflection point on two fronts: the product we build is an AI agent, and our development workflow is shifting to AI-native practices using agentic coding. Both are core to how we operate. We value technical depth, product-minded engineering, fast iteration, and building over theorizing.
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.