Subphonic
Senior DevOps Engineer
Get notified of more jobs like this · No spam, ever
How your CV stacks up
Upload your CV to see how well it fits this job role
?%
About Subphonic
Subphonic is a voice technology and AI company. We turn conversation data into structured, usable insight, combining deep voice and telephony expertise with AI that does something practical rather than something demonstrable.
AI isn't a layer we bolted on later. It was designed into the stack from the start, which is why it behaves like part of the platform rather than a feature hanging off the side of it.
Our customers are enterprise and Tier 1 telecoms operators, so we run voice at real scale and under real scrutiny, including to PCI DSS standards. That shapes the engineering more than most compliance regimes do. PCI DSS doesn't simply ask you to document your controls; it dictates how you segment networks, handle keys, and prove it on a schedule. Designing for those constraints and for real-time AI at the same time is a different problem from retrofitting either one later.
About the role
This role owns the cloud infrastructure and delivery pipelines our engineering teams ship through. Day to day that means infrastructure as code across Azure and AWS, CI/CD that people trust, observability that catches problems before customers do, and access and network controls that hold up under audit.
Voice AI makes that more interesting than average. Audio arrives in real time and won't wait for you, and because AI is part of the platform rather than a bolt-on, the infrastructure decisions you make shape what the product itself can do. If you like problems where the constraints are real, there are plenty of them here.
It's a hands-on role with real scope. You'll be one of a small number of people who understand how the whole platform fits together, working directly with engineering and security rather than through tickets.
What you'll do
- Build and maintain cloud infrastructure across Azure and AWS, defined as code (Terraform, Bicep, or similar); not clicked together in a portal, with the odd exception.
- Own and improve CI/CD pipelines end to end: build, test, deploy, and rollback, used daily by other engineers.
- Build and run the infrastructure our AI and real-time voice workloads depend on, including what it costs and how quickly it recovers.
- Implement and tune monitoring, alerting, and logging so incidents surface before customers notice them.
- Take part in incident response, including root cause analysis and the follow-up work that stops repeats.
- Manage secrets, identity, access, certificates, and network segmentation to a standard that holds up under PCI DSS audit.
- Improve deployment frequency and lead time without weakening the compliance posture.
- Lead infrastructure design decisions, mentor other engineers, and act as a point of escalation for platform issues.
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.
What we're looking for
- 5+ years in a DevOps, SRE, or platform engineering role, with hands-on ownership of infrastructure other engineers depend on.
- Production experience with both Azure and AWS. Depth in one and solid working knowledge of the other is fine; we're not expecting equal mastery of both.
- Infrastructure as code in a team setting (Terraform, Bicep, or similar), including how you handle state, reviews, and drift.
- Building and maintaining CI/CD pipelines (Azure DevOps, GitHub Actions, or equivalent).
- Containers and orchestration in production (Docker, Kubernetes).
- Networking fundamentals you can reason about under pressure: application gateways, firewalls, DNS, and segmentation.
- Secrets, certificates, and access management, and a working understanding of why audit trails matter.
- Able to explain technical trade-offs clearly to people who aren't infrastructure specialists.
Nice to have
- Managed Kubernetes at scale (AKS or EKS).
- Grafana, Prometheus, or comparable observability tooling.
- Azure Application Gateway and Azure Firewall.
- Windows and Linux server administration.
- Experience working in a PCI DSS environment, ISO 27001.
- Telecoms, payments, or voice technology background.
- Familiarity with SIP, VoIP, or real-time voice infrastructure.
If you can tick every single one of these, we should probably be having a conversation about a more senior job title. If you've got the essentials above and a couple from this list, apply anyway and let us be the judge.
Get help with your application
Your very own career expert that helps elevate your application to the next level.
What success looks like
First 3 months
- You understand our infrastructure and compliance controls well enough to make changes confidently, and you've shipped improvements to at least one pipeline or alerting gap.
First 6–12 months
- You own significant areas of the platform outright and other engineers come to you on infrastructure decisions.
- Deployment lead time is down, alert noise is down, and audit evidence is easier to produce than it was when you joined.
Why this role
Every organisation is sitting on thousands of hours of conversations that say exactly what its customers want, what keeps going wrong, and where money is leaking out. Almost none of them can read any of it. That's the problem we work on, and AI is the first technology that's made it tractable at the scale our customers operate at.
You'd own the infrastructure that makes that work: the pipelines, the platform, the controls. Your decisions stick, because the team is small enough that they're visibly yours. And you're not rebuilding from zero every quarter, because the business is established enough to have real customers with real expectations.
The team you'll join
We're a small team that got into this because voice AI is one of the few places the technology is useful right now, not just eventually. Three things we care about, in roughly this order.
- AI that earns its place. We're interested in what these models actually do in production, under load, for a customer who will notice if they're wrong. That's a harder bar than a demo, and a more satisfying one to clear.
- Automating our way out of toil. If something is manual twice, somebody here is already irritated about it. You'd have a lot of freedom to go and fix that.
- Culture you build rather than print. We explain our reasoning instead of handing down decisions, we write things down, we disagree in the open, and nobody is expected to be a hero at 2am covering a gap we could have closed in daylight.
“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
Location