Orchestra
Backend Engineer
How your CV stacks up
Upload your CV to see how well it fits this job role
?%
by product
DATA ORCHESTRATION
Build, Run and Monitor Data Pipelines easily
ai and mcp
AI and mCP that makes engineers 10x productive
lineage
Quickly debug errors with End-to-end Data lineage
Data Quality
Easily Monitor and Run Data Quality Tests
By Technology
- Snowflake Easiest way to build data and AI on Snowflake
- Databricks Easiest way to build data and AI on Databricks
- Fivetran Trigger Fivetran jobs, reduce cost, improve flexibility
- dbt State-aware orchestration for dbt core
- COALESCE Trigger Coalesce as soon as data lands
- Iceberg Declarative AI and Data Pipelines on Apache Iceberg
- Estuary Real-time and batch managed pipelines
By Use-case
- Private Equity Cost-effective solution for pe-backed portcos
- DBT CORE Ultimate solution for data teams running dbt Core
IntegrationsPricing
Resources
- Blog
- Guides
- Partners
- Architecture
- Product Demos
- Documentation
- Case studies
- Careers
Login
Try it now
GET ON THE JOURNEY
Backend Engineer
Join our core backend team building the most powerful orchestration, monitoring, and agentic SAAS product in Data
TABLE OF CONTENTS
Frontend Product Engineer
Our Culture
Our culture is defined by six characteristics:
- High Ownership and Accountability: Turn great ideas into reality and own the outcome. No red tape here, and plenty of tokens
- Ambition and High Achievement: An exceptionally high bar combined with humility
- Openness: A flat structure where the best ideas win
- Transparency: Everyone sees the goals, the plan and the numbers.
- Teamwork: it takes a village - this is a collaborative, high comms team environment
- Trust: Responsibility, flexibility and tools in exchange for high standards.
Engineering at Orchestra
- We care deeply about our users, their pain points and experience
- We're a small team of generalists who embrace new challenges regularly
- We're united by our mission, focused execution, and speed
- We deploy to production multiple times a day, every change goes through peer code review and automated CI before it ships, and we verify it in a live environment before release
- We run a genuine continuous-improvement loop, not just a slogan: monthly retros, and we actively track our own lead time and deployment frequency, constantly asking whether the way we build could be faster or better
- Tech debt isn't an afterthought, every planning cycle guarantees at least one tech debt item gets worked
Reasons to use Rodeo
Start with a chat, not a search bar
Grad scheme, placement, apprenticeship? Not sure what you want yet — that's fine. Your agent talks it through with you and turns "I have no idea" into a shortlist.
It searches the market for you
Every day your agent scans the market matching roles against what actually matters to you, not just keywords on a CV.
Only hits
No noise. No "maybe this fits." Just roles with a clear explanation of why they're right — and where to focus when applying.
Tech Stack
- Backend: Python (FastAPI) + Typescript (express)
- Infrastructure: AWS (serverless!), terraform
- Containerisation: Docker
- Database: PostgreSQL + DynamoDB
- CI/CD: GitHub actions + Blacksmith runners
- Frontend: React + Typescript
- Storybook for our component library
Role Mission
Engineers at Orchestra are not just building endpoints, you will own the orchestration engine end-to-end, and you're expected to write code wherever it is needed to ensure the feature reaches production quickly.
You will be working alongside the best engineers in the world to solve real problems on a day-to-day basis. You will ship systems that go directly into Orchestra, the control plane data and platform teams at companies like Octopus Energy and Experian run in production.
This is a role for engineers who want to work alongside the best people they've ever worked with, who can move fast in production, and who want to own the problem most people don't think about until it breaks: making sure the thing underneath never does.
What You'll Accomplish
- Own the orchestration engine: scheduling, execution, state, retries, concurrency and cancellation, the machinery that decides what runs, when, and what happens when it doesn't. Python and FastAPI on AWS, shipped to production multiple times a day
- Design for load that isn't smooth: capacity, back-pressure and isolation for a system whose busiest minute looks nothing like its average one
- Build the AI-native layer: agents are where our hardest and least-solved problems are right now, and where a lot of the next year of the product gets built
- Own your infrastructure: there's no separate platform team to hand things to. You'll write the terraform, watch what you ship, and fix it when it's wrong
- Ship end-to-end: you'll drive features from idea through to production, not hand off design or QA to someone else
- Work directly with customers: you'll sit close to the people running real workloads on the platform, debugging the genuinely interesting failures with them rather than reading a ticket
- Influence product direction: your read on what's fragile, what's missing, and what customers actually need will shape what we build next
- Help shape how we build: as a small engineering team, you'll have a real say in our culture, our standards, and how we work, not just the code you ship
Get help with your application
Your very own career expert that helps elevate your application to the next level.
Exceptional Candidates Have Demonstrated
- Real depth in Python: you've run production services in it, not just scripts. You've hit its edges, made real architecture calls, and know why certain patterns exist rather than just following them
- Judgment about distributed systems: retries, idempotency, at-least-once delivery, state machines, queues, race conditions that only show up under load. You've debugged the sort of failure that only happens in production, and you design for it now
- Comfort owning infrastructure: you've worked in a cloud environment and you treat infrastructure as part of the job rather than someone else's. Experience with IaC and serverless architectures is a real advantage
- Data modelling instinct: you can explain why a piece of state belongs in Postgres rather than DynamoDB, and you've been on the wrong side of that call at least once
- A bias to shipping: you know the difference between a fix that takes five minutes and a problem worth pausing on, and you don't gold-plate the former chasing an elegant solution nobody asked for
- A hunger to keep growing: backend is where you're strongest today, not where you plan to stay forever. We're generalists, and the interesting problems don't respect the boundary
- A commercial instinct: you understand that what you ship affects real customers, and you've built relationships with the people who use your work, not just shipped into a void
Compensation & Benefits
- Base Salary: £100,000-£120,000 + Equity
- Team perks: Annual Offsite, bi-weekly socials, monthly team lunches
- Choice of laptop
- Access to latest and greatest AI tooling
- Work from home budget
- Referral bonuses
Apply by sending your CV and cover letter to careers@getorchestra.io
Company
- Home
- Orchestra dbt
- Product
- Orchestra Case Studies
- Orchestra Pricing
- Orchestra Integrations
- Careers - we're hiring!
Compare
- Orchestra vs. Airflow
- Orchestra vs. dbt CloudTM
- Orchestra vs. Astronomer
- Orchestra vs. Dagster
- Orchestra vs. Prefect
- Cost Calculator
Connect
- Github
- Substack
- YouTube
- Contact Us
- Orchestra Labs
Resources
- Blog
- Docs
- Press Kit
- Live Demo
- Feedback
- What type of engineer are you?
2026 Orchestra Technologies Limited
- Privacy Policy
- Terms of Service
- Continuity Plan
- Incident Response
- Cookie Policy
- T&C’s
“It took my CV and asked me questions relevant to understanding what kind of jobs to suggest for me. Suggestions were almost perfect. Jobs were exactly what I’ve been looking for.”
Jessica, London
Skills
Location