Chief Technology Officer

Our mission is to give every website owner the understanding a company with an analyst has. The first step is building the best analytics tool for AI founders: one that reads the data and writes the conclusion, so nobody has to decode a chart. We are small, flat and self-funded, and the people who answer support email write the code. We like people who are direct, curious and happy to ship, and we spend our days reading customers' data and building what it tells us to.

About the role

As Chief Technology Officer at Clerion, you will own how the product is built: the script tag running on customers' sites, the ingest behind it, the pipeline that turns numbers into a written briefing, and the EU infrastructure it all runs on. You will decide what we build, what we buy and what we leave out, and you will carry those decisions through to shipped code.

This is a hands-on role in a small company. You will write code most days, work directly with the founder on what comes next, talk to customers about what their data is telling them, and hire the first engineers as the team grows. The bar you set becomes the way the company works.

What you will do

• Own the technical direction of Clerion and make the trade-offs plain: what we build, what we buy, what we say no to.
• Keep the SDK small and the ingest fast and correct at every level of traffic, from a personal blog to a launch-day spike.
• Own the briefing pipeline: how Clerion reads the data, ranks what changed, and writes it without ever inventing a figure.
• Run the infrastructure: EU hosting, reliability, cost, backups, and every promise on the security page.
• Design the data model and the APIs so that the next five features are easy and the wrong ones are hard.
• Work with customers directly when their data does something strange, and fix the cause rather than the symptom.
• Hire the first engineers, set how the team reviews, ships and is on call, and lead it day to day.
• Write down how the system works so a new engineer is productive in their first week.
• Be the voice of what is technically possible in every product decision.

You may be a fit if

• You have built and run a production web product end to end, and you still want to write code.
• You have worked on analytics, event pipelines or other data-heavy systems, and you know where they break under load and under bad input.
• You have shipped features built on large language models, and you are sceptical about them in the right places.
• You have run infrastructure in production and been paged for it, and you design so that happens less.
• You can explain a hard technical decision in plain words to an engineer, a founder or a customer.
• You have hired and led engineers before, or you have been the person everyone learned from and you are ready to.
• You want a small company where your calls shape the product, not a large one where they get reviewed.
• You have used analytics tools on your own projects and have strong views on what they get wrong.

How to apply

Using the product first is required.

1. Use Clerion on a real site for at least a week. Start the 14-day trial, install the script tag, read your briefings. This is required, not optional: we only hire people who have used the product.
2. Write down one idea. Something Clerion should do, stop doing, or do differently, based on what you saw. A paragraph is enough.
3. Email hello@getclerion.com with the role in the subject, your idea, and links to your work: GitHub, a product you shipped, or writing.