Engineering Manager - Shared Application Infrastructure

Aircall
London Office
Posted 4 days ago
Posted 17 November 2026
full-time

About the Role

Aircall 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 <span class="_0nmozVaHVx _2V7sgO2M4S _3BoeIDwZ7G _30zrXRyxdf _0ReiIH7zJH" data-testi