About the role

This role owns the platform every ContactVerse product runs on: the cloud estate, the build and deploy pipelines, access and on-call. You would own all of it, and the first job is to make sure no single person is ever the only one who can get in.

What you will do

• Own the AWS estate. Accounts by application and environment, networking, identity and cost.
• Own the runner fleet and CI/CD. Self-hosted runners, workflow reliability, and the build and deploy path for every service.
• Own the migration pipelines. Database migrations are the highest-risk routine operation any service estate runs, and they need automated guardrails and a tested rollback rather than care alone.
• Own secrets and credentials. In AWS Secrets Manager, with rotation, and with automation running under app-only least-privilege identities rather than a person's account.
• Own the access inventory. So that when someone leaves, revocation is a checklist rather than an archaeology exercise.
• Own incident response and on-call. Including the rota, the escalation path and genuine overnight cover.
• Own branch protection and repository governance. Across the repository estate, consistently, by ruleset rather than by hand.
• Own observability. Logging, metrics and alerting that tell you something is wrong before a customer does.
• Document the estate. Properly, so the next person does not start where you started.

Your first year

First 90 days. A complete picture of the estate and who can reach what, with the access inventory current.

By six months. CI/CD and migration pipelines reliable, and an on-call arrangement that does not rest on one person.

By twelve months. Infrastructure that is boring, which is the highest compliment it can be paid.

What you will bring

• Eight years or more in platform, infrastructure, DevOps or SRE, including being the escalation point.
• Deep AWS: IAM, networking, EC2, Secrets Manager, and cost control.
• Strong CI/CD, including self-hosted runners and the security considerations they bring.
• Has owned database migration pipelines against shared or live databases.
• Has taken over an estate from someone who had left, and made it understood.
• Infrastructure as code: Terraform or equivalent.
• Has designed an on-call rota that did not depend on one person.
• Available for a working overlap into the evening IST.

Nice to have

• Kubernetes or container orchestration at small scale.
• GitHub organisation administration, rulesets and GitHub Apps.
• Security certification experience. You will work closely with Trust and Security.
• Cost optimisation where model and compute spend is the largest variable cost.
• Experience supporting an engineering team across a time difference.

What you will work with

AWS, GitHub Actions and GitHub organisation rulesets, Terraform, AWS Secrets Manager, Alembic migrations, and a Python and FastAPI service estate.

What this role is not

Not a ticket queue. You own whether the platform runs, including at three in the morning.

How we work

The team works to a UK-aligned pattern, with the main working overlap in the evening IST. These hours are indicative and may change as the business changes; any change would be discussed rather than imposed. Development happens on company-provided remote machines. Everything is remote and nobody is in an office.

We are a small company and we write things down. Decisions are recorded, corrections are made to the source rather than to the output, and status is expected to be honest even when it is unwelcome.

Compensation and what we offer

• A long-term incentive, discussed at offer stage for senior appointments.
• Fully remote working, with company-provided equipment where the role requires it.
• A role with unusual scope for its level, because the organisation is being built rather than joined.
• Direct access to the founders. There are no layers between this role and the people making the decisions.

How we will assess you

We assess against three or four weighted signals agreed before we read a single CV, rather than against years of experience or a list of tools. Expect four stages:

• Introductory conversation with our People team. About 30 minutes, covering the role, your background and what you are looking for. This first conversation may be with an AI assistant; you will be told at the time and may ask to speak to a person instead.
• Conversation with the hiring manager. About 60 minutes, going deep on what you have done and how you think.
• A working session on a real ContactVerse problem. About 90 minutes. Not a whiteboard exercise and not a take-home test you do unpaid in your evenings.
• Final conversation with the founders. Covering fit, expectations and how we would work together.

We aim to complete the process within three weeks and to give you a decision, with reasons, within three working days of the final stage.

Equal opportunity

ContactVerse is an equal opportunity employer. We welcome applications regardless of age, disability, gender identity or expression, marital or civil partnership status, pregnancy or maternity, race, religion or belief, sex or sexual orientation. We select against the published signals for the role and nothing else. If you need an adjustment at any stage of the process, tell us and we will make it. It will not count against you.

Research consistently shows that some candidates apply only when they meet every criterion. If this role interests you and you meet most of what is listed, please apply.

How to apply

Write to career@contactverse.ai quoting reference POS-014, with your CV and a short note (a few paragraphs is plenty) on the part of this role you would most want to get your hands on, and why.