Senior Backend Engineer: Machine Learning Infrastructure

Acerca de

UsLaunched in 2019, Constructor is an AI-first e-commerce search and discovery platform that helps shoppers find the right products at the right time and enables leading global e-commerce brands to drive meaningful revenue and conversion gains.About The RoleThe ML Infrastructure team builds and operates the shared backend services and platform capabilities that Constructor's ML and product teams rely on to develop, deploy, and run machine learning at scale - from model serving (including LLMs) to the specialized storages and data pipelines behind it.We are a service team by nature: our roadmap is shaped by the needs of product teams, and we succeed when they can move faster with less friction

We're looking for a Senior Backend Engineer who is comfortable with, and motivated by this dynamic, and who will take end-to-end ownership of core services.

In the near and mid-term, our focus areas include:Making ML workloads easy to run, scale, and operate for every teamProviding self-service, configurable infrastructure components to ML and product teamsOwning and evolving core ML services and related pipelines with a high bar for reliability and performanceChallenges you will tackleDesign, build, and operate high-load distributed backend services that power the company's ML infrastructureTake end-to-end ownership of core ML services and related data pipelines: from design and implementation to deployment, observability, and continuous improvementPartner with ML and product teams to understand their needs and turn them into reliable, reusable platform capabilitiesMake and defend technical decisions: evaluate trade-offs, design first, and own the outcomeBe responsible for what you and your team doRequirements5+ years of professional experience in backend or platform engineeringExtensive Python knowledge (our primary language)Hands-on experience developing on a public cloud (AWS, GCP, or Azure) or with self-managed Kubernetes - AWS is our primary platform, but we're n.