🎁 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 →
Build the full-stack experiences that help millions of AWS customers understand and optimize their cloud spending. We own the console surfaces and services behind AWS Cost Explorer, BCM Dashboards, and AWS Budgets — and we're evolving them fast. As an SDE 2, you'll own features end-to-end — from frontend React components to backend Java services to the operational health of what you ship. You'll design solutions to difficult problems: making cost data intuitive at massive scale, building managed dashboard experiences, and migrating millions of customers to modernized console architectures. You won't just implement specs — you'll work directly with product and UX to understand customer pain, propose approaches, and ship iteratively. What makes this role compelling: · You'll work across the full stack — React/TypeScript frontends, Java/AWS backend services, CDK infrastructure — with real ownership, not ticket work · The problems are genuinely hard: multi-partition deployments, cost allocation at scale, and UX for data that is inherently complex · Our team uses AI tools daily as development partners · You'll mentor others, lead design reviews, and influence the team's technical direction — this is a role where your voice shapes the architecture This isn't a maintenance role. We're actively rebuilding and modernizing core billing console experiences while launching net-new dashboard and AI-driven cost insight products. You're joining while the hard decisions are still being made. Key job responsibilities · Design and build full-stack features across AWS Cost Explorer, BCM Dashboards, and AWS Budgets — React/TypeScript frontends and Java backend services serving millions of AWS customers. · Own features through the full software lifecycle — from customer problem discovery and technical design through implementation, testing, deployment, and production operations. · Solve difficult problems at scale — cost data visualization, managed dashboard experiences, and console migration for millions of existing customers across multi-partition deployments. · Author technical design documents, lead design reviews, and provide meaningful code reviews that raise the team's code bar. · Drive operational excellence — own alarms, monitoring, runbooks, and on-call rotations for live production services; resolve root causes of systemic issues. · Mentor engineers, onboard new team members, and foster an inclusive environment where diverse perspectives shape technical decisions. · Collaborate with product management and UX to deeply understand customer pain points and translate them into incremental, shippable solutions. · Contribute to team technical strategy and roadmap — help decide where to invest, what to modernize, and what to deprecate. · Write clean, testable, production-ready code using AI-native development practices — leveraging GenAI tools as daily development partners. A day in the life You start the morning reviewing a PR from a teammate who's building a new budget threshold visualization — you leave feedback on the API contract and suggest a simpler state management approach on the frontend. After standup, you spend an hour pairing with a junior engineer who's stuck on a CDK deployment issue across partitions. Mid-morning, you dive into your main project: designing the backend service changes needed to support a new managed dashboard feature. You sketch out the API, think through edge cases (what happens when a customer has hundreds of linked accounts with different dashboard configurations?), and draft a design doc to share with the team. After lunch, you notice an alarm firing for elevated latency on one of your team's Cost Explorer APIs. You pull up the dashboards, identify a query pattern that's inefficient for a new customer segment, and open a ticket to fix it — writing a quick runbook entry so the next on-call engineer won't have to re-investigate. Late afternoon, you join a brainstorm with the team about where AI could improve the customer experience — could we use GenAI to help customers interpret cost trends, surface optimization recommendations, or simplify dashboard creation? You prototype a quick proof-of-concept using the same AI tools you've been coding with all day. You end the day pushing code for a React component you've been building — a widget that makes multi-account cost trends scannable at a glance. It's behind a feature flag, shipping incrementally. No two days are identical, but most combine: hands-on coding across the stack, mentoring, design thinking, operational awareness, and exploring how AI can make both our development and our customers' experience better. About the team We own the console experiences that millions of AWS customers use daily to understand and manage their cloud costs — Cost Explorer, BCM Dashboards, and AWS Budgets. We're not just maintaining these products; we're actively modernizing them while building net-new managed dashboard experiences and exploring how AI can fundamentally change how customers interact with cost data. We think about where GenAI fits — in how we build (AI-assisted development is part of our daily workflow) and in what we build (surfacing insights, simplifying complex data, making cost management conversational rather than dashboard-heavy). The culture is direct, collaborative, and low-ego. We ship iteratively, own what we build end-to-end, and invest in each other's growth. If you want a team where your ideas shape the product direction and your code ships to millions, this is it.
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.