No open roles today.
This page is still worth reading.

The honest state of things

Claudphic has no open positions today. One person builds and operates both products, and the company is not yet at the point where adding a second person is the right use of money.

Most companies at this stage either hide the careers page or fill it with aspirational language about a team that does not exist. We would rather tell you the truth and keep the page useful, because the people worth hiring later are often reading now — and because a company whose entire argument is about honest signals cannot fake its own headcount.

Open applications are read. Not filed automatically, not answered by a template. Strong ones are kept, and when a role opens, those people are contacted before anything is published.

What working here would actually be like

Some of this is appealing and some of it is not. Both halves are true, and you should have both before spending time on an application.

You would own things completely. Not a ticket queue. A surface — a product area, a vertical, a customer segment — with the decisions attached to it. In a company this size there is no layer between deciding and shipping.

You would talk to customers. Everyone does, whatever their job title. The distance between building attribution logic and hearing a business owner describe the lead they lost is the most valuable distance in this company, and we intend to keep it short.

The scope would be uncomfortably wide. A product engineer here would touch infrastructure, data pipelines, interface work and the occasional support conversation. If you want deep specialisation in one layer, this is genuinely the wrong company, and we would rather say that now than discover it in month three.

There is no established process to inherit. Some people find that liberating and some find it exhausting. Both reactions are reasonable. If you need a defined ladder, quarterly calibration and a written promotion framework, we do not have those and will not for some time.

The work has a stated position attached. Claudphic refuses categories of revenue — client services, paid rankings, sponsored editorial — that would make the numbers easier. That means slower growth than the alternative, and it means occasionally watching a competitor do the thing we will not do. If that sounds like unnecessary purity rather than the point, this will be a frustrating place to work.

The roles that open first

These are not listings. They are the honest order in which the company will need people, so you can judge whether writing now is worthwhile.

Full-stack product engineer — Claudphic Ads

The first hire, most likely. Someone comfortable across a PHP or Node backend, a modern front end, and the API integrations that make attribution work — Google Ads API, Meta Conversions API, webhook plumbing, queue processing and the unglamorous reliability work that decides whether conversion uploads actually arrive. Experience with advertising platforms is a genuine advantage; the ability to learn them quickly is close to equivalent.

Editorial researcher — Unfiltered Choice

Someone who can read a business banking fee schedule properly and find the thing the marketing page omits. This is research work with a strong writing component, applying a published rubric consistently across providers and documenting the reasoning so a reader can audit it. Financial-services literacy matters more than journalism credentials. Intolerance for vague claims matters most of all.

Customer success and onboarding — India

Attribution is a technical subject that most vendors explain badly. This role is about getting Indian businesses from signup to a working conversion loop and making sure the numbers they see are numbers they trust. Comfort explaining a technical mechanism to a non-technical owner, in English and Hindi, is the core of the job.

How we would hire

1. A real conversation, not a screen. What you have built, what you would want to own here, and what you think is wrong with our approach. The last part is not a trap.
2. A paid piece of real work. Small, scoped to a few hours, drawn from something actually on the roadmap. Paid at a fair rate regardless of outcome.
3. A conversation about the work — the decisions and trade-offs, which tells us more than the artefact does.
4. A decision, quickly. Days, not weeks. Silence is not an answer and we will not use it as one.

Compensation, stated as clearly as we can

We will not publish a salary band before a role exists, because an invented number is worse than no number. What we can commit to now: compensation will be at or above market for the role and location, stated in the first conversation rather than extracted through negotiation, and never structured to depend on someone not knowing what they are worth.

Equity is likely for early hires and will be explained honestly — including what it is probably worth, which for a company at this stage is a real number multiplied by a low probability. Anyone who presents startup equity without that caveat is selling something.

Writing to us before a role exists

Open applications are welcome and are read by the founder. To make yours useful, three things help more than a CV:

• What you would want to own here. Specific to Claudphic, not a general statement of interest. It tells us more than any employment history.
• Something you have made. Code, writing, a product, an analysis. Shipped work beats described work every time.
• One thing you think we have wrong. This site states a position in some detail. Disagreeing with part of it, specifically, is the strongest possible signal that you actually read it.

Send it through the contact page. You will get a reply within two working days, including when the answer is that there is nothing right now — which is currently the honest answer for every role above.

Before you apply, read these

Working somewhere is easier to judge from what a company refuses than from what it promises. The services page lists the revenue we turn down. The independence policy sets out rules that cost us money. The operating principles state what each principle costs rather than only what it sounds like.

If those pages read as unnecessarily rigid, that is genuinely useful information — for both of us.