Still hiring?
13 checksNo red flags
Browse
All Tech JobsThe whole board, newest first.Roles That Fit MeAnswer a few questions, see your matches.Early WindowFound before the big boards.Direct ApplyStraight to the manager, past the ATS.By specialty
Your materials
CV AnalyzerWhat an ATS sees, and what to fix.Tailor CVBrought in line with one posting.Cover LetterWritten from your CV and the role.You and the process
Hey, I’m Wayjo. I find roles before the big boards.
Free to browse. An account unlocks the rest.
Jobs
All Tech JobsThe whole board, newest first.Roles That Fit MeAnswer a few questions, see your matches.Early WindowFound before the big boards.Direct ApplyStraight to the manager, past the ATS.Not stated
Similar roles pay £120K - 155K a year · our estimate
The whole posting in a few lines. Sign up to read it here and on every role you open.
Sign Up to ReadAircall is a unicorn AI-powered communications platform transforming how teams win with customers.
For over a decade, we’ve believed voice builds the strongest business relationships. We bring voice, SMS, WhatsApp, and 250+ integrations together on one seamless workspace—so every customer conversation drives revenue, resolves issues faster, and builds trust. Our AI Voice Agents handle routine interactions while your team leads the conversations that matter most. Used by 24,000+ businesses worldwide.
We’re 600+ people from 40+ nationalities across Paris, London, Madrid, Berlin, New York, San Francisco, Seattle, Sydney, and Mexico City. We’re ambitious, product-driven, and execution-focused—built for visible impact, fast decisions, and real growth.
Come join us!
About the role
We're building a new platform team and are looking for its manager to lead it. You'll bootstrap a team that owns the shared services our engineering teams rely on to deliver features to customers: workflow orchestration, feature flagging, real-time messaging and the API layer.
The team's job is to run this layer properly and offer it back to engineering as a service: reliable, documented, and easy enough to adopt that nobody has to raise a ticket to get started. These services operate at scale (Aircall has over 20,000 customers) and are critical to the smooth operation of our product.
Team shape: we're planning a team of 4 engineers, starting with [first domain to move across, e.g. Temporal]. Planned hiring mix: full-stack and backend engineers with large-scale distributed systems experience.
What success looks like in your first 6 to 12 months
You’ve hired the team.
First domain taken over from the team running it today, with a documented handover and on-call in place, with a roadmap for the others.
Service expectations (for example, OLAs and support levels) published for each owned service.
Quarterly roadmap agreed with the other engineering leads, with protected capacity so support work doesn't crowd out everything else.
What this team will own
This is shared application infrastructure, not AI infrastructure.
Workflow and async execution: Temporal, and the patterns teams use to build on it.
Progressive delivery: feature flagging service, rollout conventions and flag hygiene.
Real-time connectivity: WebSocket infrastructure, connection fan-out, channel authorisation and scaling.
API and graph layer: schema registry, supergraph composition and schema checks in CI.
The team owns these domains rather than any particular product. If we change a tool, the team still owns the job and runs the migration.
Our stack: Python, Go, TypeScript/Node.js / AWS services - EKS , RDS / GitLab CI/CD / Backstage IDP .
Boundaries with other teams
Infrastructure: Infrastructure operates the clusters and core AWS platform; this team runs the shared services on top of it.
Security: Security sets policy and reviews; this team owns the security posture of its services.
Observability: Service-level alerting and dashboards owned by this team.
What you'll be doing
Building the team. You'll hire most of it, set the bar for who joins, and grow the people you hire through coaching, career development and performance reviews.
Taking systems on properly. Each domain moves across from the team running it today. You'll agree what a clean handover looks like, make sure the knowledge comes with it, and take on on-call once the team is ready. Handovers will follow the pace of hiring.
Running a service. Availability, capacity, upgrades, cost, compliance and incident response. You'll publish what teams can expect from you (for example, OLAs and CSAT targets).
Setting the roadmap each quarter or half-year with the other engineering leads, and protecting enough capacity for support work.
Working with our suppliers: cost, contracts, roadmap pressure, and the occasional build-or-buy decision.
Making the supported path the easy path, so teams adopt it because it's the least effort, not because they were told to. You'll use the tools and processes we already have to drive standardisation.
Hands-on expectations: You’ll be hands-on with coding (AI first), design review, and on-call participation, and how this changes as the team grows.
From the office
Aircall.io, Inc.
Office in London, United Kingdom
Also hiring in Madrid, Spain, San Francisco, United States, Paris, France and 2 more places
We've checked whether it's still hiring and how crowded it is.
Still hiring?
13 checksNo red flags
How crowded?
6 checksNo red flags
How well does this role fit you?
Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.
Something wrong with this vacancy?
$300,000 - 405,000 / year