Join a team that builds the experiences every AWS customer uses to understand, monitor, and optimize what they spend, from individual developers to enterprise FinOps teams managing tens of millions of dollars in monthly spend. The AWS Billing Console Platform team owns the console's hosting platform, on which around thirty AWS engineering teams build their console pages; over fifty customer-facing billing and cost pages of its own; and the rendering engine that turns an AI agent's cost data into the charts, tables and reports customers see. Two AWS agents answer cost questions today, a FinOps agent and Amazon Q in the console, and chatbots and console pages form one ecosystem customers navigate between to get problems solved and questions answered. Today each renders its answers its own way, and a cost figure has to be right the first time. This team is building the rendering layer both agents will draw on: an engine that checks every plotted value against the data the agent gathered, an open artifact format any agent host can render, and the component catalog that makes a cost chart look the same wherever it appears. We are hiring a Software Development Engineer to extend this rendering platform to provide effective visualization for any problem that our web pages handle, especially for risky mutative actions. You'll use only the latest genAI, open source and proprietary technologies to directly enhance agents to give them the power of our AWS management console pages for problems that can only be solved visually or that require supervision by users. Key job responsibilities - Design, build, test, and operate the rendering engine behind AWS's cost agents: the components, the emit path, and the checks that verify every number before a customer sees it. - Bring generated cost visualizations into agent conversations against the accuracy and customer-outcome bars the team sets, and keep two agent hosts rendering the same artifact from the same data. - Define and publish a rendering format for cost artifacts and adopt the open protocol the console ecosystem is converging on. - Build and operate customer-facing console pages on the team's page-building platform and component library. - Help scale a platform that absorbed the work of three teams in a 2026 reorganization: drive down operational load through automation, observability, and legacy-service decommissioning so the team can invest in new customer experiences. - Own services end to end, including participation in the team's on-call rotation for production support. - Raise engineering quality through design reviews, code reviews, automated evaluation, and operational excellence, and partner with product managers, applied scientists, designers, and the agent teams across AWS. A day in the life You start by checking the health of the services you own and clearing anything handed off from on-call, then pick up your current project: maybe a new artifact type, where you run the agent's answers through the team's fidelity scorecard, read where a figure drifted from its source, and fix the emit path. Midday you review a teammate's component, then join a design review where the team and the agent teams weigh how one artifact renders in two hosts. In the afternoon you pair with an applied scientist on the evaluation set for the next release and sketch the components a new chart needs. Across the week you balance net-new rendering and platform work against the operational excellence that billing customers depend on, and rotate through on-call. The problems are open-ended, the customer scale is large, and the design space is new, so there is room to set technical direction and take on new scope. You will have the support of an experienced team and a manager invested in your growth. About the team The AWS Billing Console Platform team owns the platform, the customer-facing pages, and the rendering engine that AWS customers and AWS's cost agents use to manage cloud spend. We operate at scale. Around thirty AWS engineering teams build their console pages on our hosting platform, which gains two to three new console pages every year, and we own over fifty customer-facing pages ourselves, with a production footprint consolidated from three teams in a 2026 reorganization and driven toward lower operational load through automation and legacy-service decommissioning. We own generative UI for billing and cost management, the rendering engine the FinOps agent runs in production and the cost-visualization skill Amazon Q is launching, and we are extending that ownership into a platform: the agent interfaces, the generated experiences, and the open format customers will see across AWS's cost agents. That combination, a large operational platform plus a green-field AI mandate, means an engineer here can take on scope quickly and see a clear path to the next level. We operate what we build, hold a high bar for operational excellence, and care about inclusion, mentorship, and work-life harmony, so engineers at every level can do their best work and grow their careers.