About the role

ContactVerse runs its build and deploy pipelines on self-hosted GitHub runners in AWS. You own the estate, you write down how it works, and you make it recoverable by somebody who was not there when it was built.

What you will do

• Own the AWS estate. Accounts, networking, IAM, compute, and the cost of all of it.
• Own the pipelines. GitHub Actions on self-hosted runners, across every product repository, including the gated migration repositories.
• Make deployment boring. A repeatable path from merged to running is the single most valuable thing you could build.
• Own secrets and access. Who holds what, where it is stored, and what happens when somebody leaves.
• Write the runbooks. If you are unavailable, the next person should be able to follow a document rather than guess.
• Own monitoring and the alerting that goes with it, so a failure is noticed by us before it is noticed by a customer.
• Work with the developers rather than behind them. Unblocking an engineer waiting on an environment is the job, not an interruption to it.

Your first year

First 90 days. The estate documented, access inventoried, and at least one service deploying through a repeatable pipeline.

By six months. Deployment routine rather than an event, with monitoring that tells us first.

By twelve months. Infrastructure that is predictable, documented and recoverable without you in the room.

What you will bring

• Four years or more running AWS in production, not only in a lab.
• GitHub Actions, including self-hosted runners and why they go wrong.
• Comfortable with Linux, networking and IAM at the level where you can explain a decision rather than recite it.
• Infrastructure as code, and the discipline to use it when a console click would be quicker.
• Has inherited an undocumented estate and made it legible. This is the closest thing to the actual job.
• Python well enough to read the services you are deploying.
• Calm when production is not.

Nice to have

• MySQL operations, backups and restores you have actually tested.
• Alembic or similar migration tooling against shared databases.
• Cost optimisation where somebody checked the bill afterwards.
• Container orchestration.
• Security hardening or a compliance exercise.

What you will work with

A Python and FastAPI estate on AWS, GitHub with branch protection and required pull requests into main, GitHub Actions on self-hosted runners, Alembic migrations in dedicated repositories, and MySQL.

What this role is not

Not a ticket queue. You will be asked what should change, not only to action what somebody else decided.

How we work

Everything is remote and nobody is in an office. The team spans the UK and India, with the main working overlap in the evening IST. The precise pattern is agreed with you rather than imposed.

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

• 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 three 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 60 to 90 minutes. Not a whiteboard exercise and not a take-home test you do unpaid in your evenings.

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-021, 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.