Senior Implementation Engineer

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!

These three roles own a partner implementation together. Implementation Management owns the plan from kickoff to Hypercare exit. Product Consulting translates the partner’s operating model into BEES capabilities. Implementation Engineering configures and lands the technical delivery so integrations run in production. One owner per decision: plan, fit, and system.

You configure and land the technical delivery, making integrations run in production. You own mapping, integration and go-live readiness. You partner with MIS when the BEES Connector is in scope. You do not own the project plan or the commercial fit-gap.

• →Own technical configuration: mapping, integration and delivery until it runs in production.
• →Partner with MIS when the BEES Connector is in scope.
• →Drive engineering capabilities into MIS tooling and go-live readiness.
• →Activate BEES product features per partner; leave runbooks and monitoring behind.
• →Automate manual steps that would otherwise sit with TCS after Hypercare.
• →Leading KPI: no SEV1 after Hypercare. Supporting: tooling adoption — manual steps automated.

• 5+ years in platform, integration or implementation engineering, with work that reached production — not only PoCs.
• Working knowledge of APIs, data mapping, middleware and enterprise integration.
• Comfort writing runbooks and standing up monitoring, not only shipping a config.
• Able to work with a partner’s IT team and with MIS on connector scope.
• Strong English (written and spoken). Spanish also preferred. 

• Prior BEES Connector, ERP/WMS integration, or distributor systems.
• Python or SQL sufficient to own mappings and challenge bad data.
• Experience reducing post-go-live severity through tooling, not heroics.

• Production is the definition of done — a mapped file that never ran is not done.
• You leave the run team able to operate without you.
• A SEV1 after Hypercare is a design failure, not an operations surprise.