Software Architect

About us

AB InBev is the leading global brewer and one of the world’s top 5 consumer product companies. With over 500 beer brands, we’re number one or two in many of the world’s top beer markets, including North America, Latin America, Europe, Asia, and Africa.

About AB InBev Growth Group

Created in 2022, the Growth Group unifies our business-to-business (B2B), direct-to-consumer (DTC), Sales & Distribution, and Marketing teams. By bringing together global tech and commercial functions, the Growth Group allows us to fully leverage data and drive digital transformation and organic growth for AB InBev around the world.

In addition to supporting well known global beer brands like Corona, Budweiser and Michelob Ultra, the Growth Group is home to a robust suite of digital products including our B2B digital commerce platform BEES, on-demand delivery services Ze Delivery and TaDa Delivery, and table top beer keg PerfectDraft.

We are an exceptional team, focused on understanding and supporting consumer and customer needs, harnessing new technology, and scaling growth opportunities.

What you'll do:

• Lead the system design and hands-on delivery of a data-intensive web product on Microsoft Azure. You own how the application is shaped end to end — services, APIs, the Next.js layer, integrations, security, and how it behaves under load.
• This role is defined by two things: designing the system and shipping a performant application. You write the code for the most critical paths and own them from design through production. Architecture without implementation, or features that do not hold latency, throughput, and cost targets, is not the job.
• Design how the product queries, processes, and presents large volumes of data — modeling, SQL performance, caching, pagination, aggregation, search, and asynchronous processing — and ship dashboards, reports, and data exploration on top of existing data platforms. Every design choice is judged by whether the product stays fast, correct, and operable as data volume and concurrency grow.
• Choose and document the system shape (modular monolith, microservices, synchronous, or event-driven) against performance, consistency, security, cost, and operational complexity. You make the trade-offs explicit, including when a simpler design is enough.
• Set standards for authentication and authorization, observability, automated testing, code review, and continuous delivery, using AI-assisted engineering as part of how the team builds. Partner with the teams that own ingestion, pipelines, and the data platform. You own how the application queries, secures, and serves that data at production performance.