About the role

ContactVerse has an analytics estate in code with nobody above it, and an AI programme that depends on data nobody owns. This role builds the data platform properly: the warehouse, the pipelines, the analytics tables that belong to NEXXOS, the reporting customers see, and the internal dashboards leadership actually runs on. It is a build role before it is a reporting role.

What you will do

• Own the data platform. Warehouse, pipelines and the analytics tables, with a model that is designed rather than accumulated.
• Own customer-facing reporting. The metrics the product promises, accurate and explainable, per tenant.
• Own internal analytics. The dashboards leadership uses to run the company, and the definitions behind each number.
• Own data quality and lineage. So that any number can be traced to its source and defended.
• Support the AI programme. Evaluation data, usage data and the feedback loops that make models better.
• Own retention and privacy in the data layer. What is kept, for how long, and what is anonymised, in a business processing customer conversations.
• Work within the data model governance. Tables originate in the requirement sheet; the analytics tables belong to NEXXOS and are not modelled into other products.
• Make self-service possible. So that a question does not require you to answer it.
• Instrument the product. Deliberately, so that the data we need later exists now.

Your first year

First 90 days. A data platform plan, and the analytics tables under proper ownership.

By six months. Customer-facing reporting that is accurate, and internal dashboards leadership can act on.

By twelve months. A number anyone can trace back to its source.

What you will bring

• Eight years or more in data engineering or analytics, including a leadership role.
• Has built a data platform rather than only reported from one.
• Strong SQL and Python, and modern pipeline tooling.
• Has modelled a warehouse for multi-tenant SaaS, including per-tenant isolation.
• Has owned data quality and can describe a time a number was wrong and what they changed.
• Understands privacy obligations around personal data in analytics.
• Comfortable being the first data hire.
• Available for a working overlap into the evening IST.

Nice to have

• AWS data services.
• Experience supporting ML or LLM evaluation with data infrastructure.
• Product analytics instrumentation from scratch.
• Customer-facing embedded analytics.
• Experience of a company where analytics tables had grown organically and needed rationalising.

What you will work with

AWS, Python, a Postgres-based service estate, analytics tables currently held within a service repository, and a documentation site generated from the requirement sheet. There is no warehouse yet. That is part of the job.

What this role is not

Not a reporting analyst. You build the platform, not only the charts.

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