BEES · posted · checked
Engineering Coordinator
JavaKubernetesPostgresSpringHybrid · São Paulo
Who can apply
Hybrid · São Paulo
Location: Campinas, São Paulo, Brazil
About BEES
Join us to build the future of B2B commerce!
BEES is AB InBev’s B2B platform. Through our ecosystem, merchants and retailers across 29 countries can stock their businesses quickly, easily, and securely.
At BEES, we dream big, lead with purpose, and develop technology that transforms the way retailers and sellers grow.
Every line of code and every partnership is built in service of a single mission: to make commerce better for retailers and sellers around the world. Here, your work is not just important. It makes a difference!
What you'll do:
Lead two engineering teams as their people manager — formal reporting line for the engineers in both teams — while owning delivery, priorities, and operational discipline.
Run engineering management practices: regular 1:1s, continuous feedback, performance conversations, goal-setting, and participation in performance review and calibration cycles; support career growth and partner with leadership on hiring and onboarding.
Coordinate delivery across both teams — flow, dependencies, quality, and predictable status — as the senior delivery anchor alongside team technical leads.
Partner with technical leads so choices stay aligned with platform architecture while engineers ship partner integrations on the Java / Spring data-adapter platform — from discovery and build through UAT, production cutover, hypercare, and steady-state operation.
Keep both teams healthy and predictable in a high-agility portfolio where partner priorities, launch windows, and operational incidents shift quickly.
Act as the engineering diplomat for your teams: unblock cross-team dependencies with Program Management, TPM, QA, and partner technical teams during parallel onboardings and cutovers.
Work with MIS leadership (Engineering Manager, Architect, Program Manager) on people and delivery risks — capacity, performance, deployments, on-call load, quality gaps — and translate priorities into actionable team plans.
Own coordination of quality and operational discipline — UAT readiness with QA, regression alignment, observability and runbook expectations, L3 on-call rotation handoffs when teams are on Maintenance allocation, and closure on post-incident follow-ups.