BackEnd Engineer: Experiments

The Experiments team at Constructor builds an experimentation platform: traffic allocation, exposure logging, metric computation, statistical analysis, and a UI for launching experiments and interpreting results. It’s used both internally and by customers running experiments on production traffic.

We’re scaling customer experimentation usage and investing in making experiments faster, more reliable, and easier to interpret. Unlike boxed experimentation tools, our platform has to support a wide range of customer integrations, traffic patterns, and industry constraints — which makes the engineering problems unusually real-world and high-leverage.

Team: 3 Software Engineers, 1 Data Analyst, an Engineering Manager, and a Product Manager.

THE ROLE

This is primarily a backend role (Python services + data-heavy systems). You’ll occasionally work in the Dash UI and contribute to Spark jobs, but those are not the main focus. We care about correctness, observability, and product usability more than complex infrastructure.

Tech: Python, FastAPI, PostgreSQL, Plotly Dash, PySpark/Databricks, AWS, CloudWatch, Sentry

(Spark work is ~5–10% — we don’t expect you to be a data engineer or own the data platform.)

- Build and maintain backend services for experiment assignment, logging, and report generation

- Improve scalability, performance, and reliability of experiment reporting pipelines

- Add product-facing features to the UI to help users launch experiments and interpret results

- Take technical ownership of projects: shape solutions, break down work, and drive execution with the team

- Participate in a weekly on-call rotation (investigating occasional issues and answering internal questions)

You’ll collaborate closely with Search/Recommendations engineers, ML/DS partners, and customer-facing teams when needed. This role does not require frequent direct customer calls.

- Strong experience building and owning production backend services in Python