Build the risk-intelligence layer for regulated finance.
We are early. Today the team is its two founders, and the honest description of the company is a platform that is built and running in our own non-production environments, a company registered in England and Wales, and no customers yet.
That is the job, stated accurately, and it is the whole offer. If you want a product with traction and a playbook, this is not it. What is on offer is the chance to decide what a compliance platform should be before a customer, an auditor or a regulator has told us.
Today
- No open roles. The areas we expect to open first are set out below.
- Pre-revenue, with no customers and no client traffic on the platform.
- Open applications go to careers@regnovaiq.com.
Where the company actually stands
- Pre-revenue. No customers.
- Nothing is deployed for a client and no client traffic runs through the platform.
- Company of record
- RegNovaIQ is the product. NOVAIQ LIMITED is the company of record: company number 16948483, incorporated 7 January 2026 in England and Wales. The full record is on the company page, which links to Companies House.
- NVIDIA Inception
- Member since 3 September 2026.
- Security certification
- We hold no SOC 2 report. No SOC 2 examination has been completed. We hold no ISO 27001 and no other third-party security certification today, and we do not claim one.
- Founders
- William Davis (Co-Founder).
How we work
Nothing is done until something proves it.
A change is not complete when the code is written. It is complete when a test has run against a running system and produced evidence that can be read back later. Status is bound to that evidence, not to anyone's opinion of the work.
Refusing is an acceptable answer.
If a requirement is unclear, a contract unknown, or a claim unverifiable, the correct move is to stop and say so. That is written into our engineering rules, not merely tolerated in practice.
We write down what is not true yet.
We say on this page, and on the security page, that we hold no certifications. The product pages separate what ships from what is planned. We will not win a deal on a claim we cannot evidence: for a financial-crime vendor, an unevidenced claim is a liability, not marketing.
Changes are small, reviewed, and gated.
Every change goes through review and an automated gate on the way to a protected branch. Bypassing that gate is not something an engineer can do to save an afternoon: it requires explicit, documented authorisation and it is recorded. In practice we fix the failure instead.
The platform is broad and unevenly finished.
The platform spans screening, monitoring, investigation, governance and an operator console. Those areas are not at the same level of maturity, and we say so on the product pages. Part of any early role here is deciding what to finish and what to cut.
Where we are based
The registered office is in Croydon, England.
The rest of the working arrangement is not published yet, and we would rather leave it blank than guess at it. None of the following is settled on this page today:
- Whether the work is remote, hybrid or in person.
- Which time zones we can hire across.
- Whether there is an office.
- Whether we can sponsor a UK work visa.
- Whether an engagement is employment or contract.
- Salary and equity, and what we will disclose about them.
Each of these will be stated here alongside the first role we open.
Roles we expect to hire first
There are no open roles right now. These are the areas we expect to open first. Sequence and timing depend on funding, so treat this as direction, not a queue.
| Area | What it owns | Why it comes early |
|---|---|---|
| Founding engineer, platform | The service layer, tenant isolation, the evidence trail, and the path from a commit to a running environment. The stack is described on the technology page. | The platform is wide and held by two people. Depth here is the constraint on everything else. |
| Applied machine learning | The model lifecycle, training, evaluation and monitoring, and the explanation and governance that have to sit around any model output shown to a regulated user. | An output has to stand up to a regulator's question, not only to a benchmark. |
| Financial-crime subject-matter lead | Whether what we build matches what an MLRO, sanctions analyst or investigator actually has to do at 9am. | With no customers, domain judgement is the only check we have on whether the product is right. It is the highest-leverage non-engineering hire. |
| Security engineer | The platform's security controls and the evidence behind them. | No bank's vendor-risk review will shorten this path for us, and it gates the first serious enterprise conversation. |
| Founding commercial and design partners | The first design partners, and the discipline of selling a product described exactly as it is, including the parts that are unfinished. | May come before some of the above. Pre-revenue is a commercial problem as much as an engineering one. |
Open roles
None right now.
We would rather publish nothing than publish a role we are not funded to fill. When that changes, roles will be listed on this page.
Open applications
What happens to your application: we hold what you send us for as long as we are considering it and for six months afterwards, then delete it. We do not share it outside the company. Ask us to delete it sooner at contact@regnovaiq.com and we will. The general privacy notice does not yet cover applicants, so this paragraph is the commitment.
Send a short note and a CV, a portfolio, or a link to something you built to:
Useful in that note: which of the areas above you would take, one thing you have built or run that resembles it, and one thing on this site you think is wrong. The last one is not a test. We want to know.
For recruiters and agencies
We are not working with agencies and we do not accept unsolicited candidate submissions. Unsolicited CVs do not create a fee obligation.