Engineering
ContactVerse has several hundred API endpoints defined across NEXXOS Core and the industry verticals, a large number already built, and a standard of completeness that has not always been met: endpoints returning mock data, responses that do not match the published spec, roles not enforced.

About the role
ContactVerse has several hundred API endpoints defined across NEXXOS Core and the industry verticals, a large number already built, and a standard of completeness that has not always been met: endpoints returning mock data, responses that do not match the published spec, roles not enforced. This role is for somebody senior enough to raise that standard by example rather than by memo.
What you will do
- Build endpoints that are actually complete: real data, the published request and response shape, roles enforced, tests that run against a real database.
- Own services end to end rather than tickets, including the migrations they depend on.
- Review other people's code, and make the review the moment the standard is set.
- Keep the schedule and the code in agreement, and fix the record when they are not.
- Work to the requirement documents rather than around them, and raise a change request when the requirement is wrong.
- Mentor the early-career developers, who are most of the pod.
- Take part in the architecture conversations. Every AI request routes through Core against a region-scoped provider registry, and that only holds if people understand why.
Your first year
First 90 days. Shipping complete endpoints and visibly raising what complete means.
By six months. Owning a service, and trusted to review anything in it.
By twelve months. The person others check a design with before building it.
What you will bring
- Six years or more building backend services that real users depended on.
- Python, and ideally FastAPI. Close enough to be credible in week one if not.
- Relational databases done properly: schema design, migrations, and why a shared database makes both harder.
- Has worked to an API specification and cared when the implementation drifted from it.
- Testing that you actually write, against real infrastructure rather than mocks of it.
- Can explain a technical decision to somebody more junior without making them feel small.
- Available for a working overlap into the evening IST, which is when the team operates.
Nice to have
- AWS.
- Alembic.
- Multi-tenant SaaS and the tenancy mistakes that follow.
- Telephony, contact centre or conversational systems.
- Has introduced a testing or review standard to a team that had none.
What you will work with
Python and FastAPI on AWS, MySQL, Alembic migrations in dedicated repositories, GitHub with required pull requests into main, and a documentation site carrying the functional requirement, technical design and data model for every endpoint.
What this role is not
Not a role where the specification is somebody else's problem. If it is wrong, you are expected to say so.
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-026, 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.


