Building Langfuse
Join the team building the leading open-source AI engineering platform, now part of ClickHouse

Teams building AI applications need to monitor and evaluate them continuously to get them into production and keep improving them. Langfuse is the open-source platform for that workflow. Read about our mission.
In January 2026, we joined ClickHouse. We still run as our own team.
If you want to build great developer tools, or get developers to love them, we'd love to hear from you.
– Marc, Clemens, Max and the Langfuse team
Why join Langfuse
We're winning the category through open source
Langfuse is the most used open-source AI engineering platform, with the largest distribution in our space. See the public metrics.
Langfuse is the most widely adopted LLM Engineering platform, used by 50,000+ companies, with 37,123 GitHub stars, 65M+ SDK installs per month, and 38M+ Docker pulls. Trusted by 21 of the Fortune 50 and 129 of the Fortune 500 companies.
AI-native companies and large enterprises
AI-native companies like Ramp run on Langfuse, and so do very large enterprises. See more companies building with Langfuse.
You own an area, and your work is public
Engineers own a feature area and stay with it as the team grows. Marketers own launches, events, or a program like Langfuse Academy. The people who build a feature answer users in GitHub Discussions themselves. Because the work is open source, your track record stays public.
You own it from the customer call to the launch. Here is how that looked for one real feature, the evals revamp:
- Customer. It starts with users telling us in GitHub Discussions that mapping data into evaluators was painful. (How we work with customers)
- RFC. You write the RFC. The team reviews it async, then we settle the hard questions in one intense session. (Roadmapping)
- Build. Then you build. A lot. The main PR touched 600 files. (How we ship)
- Ship. You launch it with the GTM team: changelog, docs and marketing. (Releases)
- Offsite. Then you meet everyone in person at an offsite in Tokyo or Berlin. (Remote at Langfuse)
ClickHouse backs us and stays out of the way
We set our own roadmap. ClickHouse gives us a global sales team that sells Langfuse and a much larger audience for our launches. The engineers who build the database are one message away.
Our bet is that ClickHouse will be one of the great infrastructure companies of the AI era, and that joining Langfuse now means being part of that. The database already runs real-time analytics, observability, and AI workloads. Langfuse is how that platform sees what agents do in production. For more background, see below.
AI-pilled and remote
Everyone gets a very high AI budget. We build slides with AI, maintain our own coding harness, and almost everyone runs a small army of agents. We have three scheduled meetings a week. Everything else happens in writing (see our principles).
What you'll work on
Each of these projects was usually executed by one person.
Product engineering
You own your projects end to end and the product outcome, building whatever it takes, putting the user and the product first, and making smart technical choices.

Code evaluators
Deterministic Python or TypeScript checks on observations and experiments.

Halo
The assistant inside Langfuse that works across thousands of observations.

Responsive Timeline
The trace timeline fits any trace on one screen and zooms like a map.
Data platform
You own ingestion, ClickHouse query performance, and the infrastructure behind Langfuse Cloud and self-hosting, at petabyte scale.

Langfuse v4
Query every agent step directly, with faster tables and dashboards.

Full-text search
ClickHouse search across observation inputs, outputs, and metadata.

Langfuse Cloud Japan
A Tokyo region so traces, prompts, and evaluations stay in Japan.
Marketing and growth
Our audience is AI engineers, so most of our marketing is material they'd bookmark:
- Developer content, like the changelog, Langfuse Academy, and the docs
- Launches with one owner each, which also go out through ClickHouse's much larger audience
- Product marketing, events and community, and growth
Open roles
We are remote-first and hire engineers across Europe and in US-East time zones. Engineering teams are mixed EU/US. Marketing and all other roles hire in Europe and all of the United States. All roles are listed on the ClickHouse careers site. See how we think about pay and perks.
Team
| Name | Role | Social Links |
|---|---|---|
| Marc Klingen | Co-Founder & CEO | X, LinkedIn, GitHub |
| Max Deichmann | Co-Founder & CTO | X, LinkedIn, GitHub |
| Clemens Rawert | Co-Founder | X, LinkedIn, GitHub |
| Marlies Mayerhofer | Founding Engineer | X, LinkedIn, GitHub |
| Hassieb Pakzad | Founding Engineer | X, LinkedIn, GitHub |
| Steffen Reuther | Backend Engineer | LinkedIn, GitHub |
| Jannik Maierhöfer | Growth Engineer | X, LinkedIn, GitHub |
| Akio Nuernberger | Enterprise & Partnerships | X, LinkedIn |
| Nimar Blume | Product Engineer | X, LinkedIn, GitHub |
| Valeriy Meleshkin | Backend Engineer | LinkedIn, GitHub |
| Lotte Verheyden | Product Marketing Engineer | X, LinkedIn, GitHub |
| Leonard Wolters | Operations | LinkedIn, GitHub |
| Annabell Schäfer | Product Marketing Engineer | X, LinkedIn, GitHub |
| Tobias Wochinger | Product Engineer | LinkedIn, GitHub |
| Ben Bachem | Product Engineer | LinkedIn, GitHub |
| Mark Salpeter | Product Engineer | X, LinkedIn, GitHub |
| Niklas Semmler | Backend Engineer | LinkedIn, GitHub |
| Nikita Kabardin | Frontend Engineer | X, LinkedIn, GitHub |
| Vera Yap | Recruiting | LinkedIn, GitHub |
| Milana Gurbanova | Integrations Engineer | LinkedIn, GitHub |
| Lysander Kiesel | Product Engineer | X, LinkedIn, GitHub |
| Hande Kafkas | Growth Engineer | X, LinkedIn, GitHub |
| Doneyli De Jesus | Solution Architect | X, LinkedIn, GitHub |
| Muhammad Ali | Solution Architect | X, LinkedIn, GitHub |
| Boris Michel | Solution Architect | LinkedIn, GitHub |
| Tobias Klesel | Product Engineer | LinkedIn, GitHub |
| Trang Nguyen | Product Designer | LinkedIn, GitHub |
| Jordi Bosch | Backend Engineer | LinkedIn, GitHub |
| Abdallah Othman | Growth Engineer | X, LinkedIn, GitHub |
| You? | Your life's work | Open Positions |

Langfuse was born

Canal boat ride

Dinner on the canal

Team dinner

Exploring the city

Working from the AMS office

Team dinner

First billboard campaign in SF

First onsite week

CDTM event

Shibuya crossing

At ClickHouse offsite

Night out in Tokyo

Last night at ClickHouse offsite

ClickHouse AI team dinner

Christmas dinner

Langfuse offsite

Team photo

Picnic

Exploring SF

Founders at YC
Further reading
ClickHouse

AI is redrawing the database market
Tanya Bragin on how AI is changing analytics, warehousing, and observability.
ClickHouse blog

Why I joined ClickHouse at a $15B valuation
Jon Natkins on making that career bet.
Substack

ClickHouse raises a $400M Series D
Led by Dragoneer. The same round acquired Langfuse.
ClickHouse blog

Langfuse joins ClickHouse
What stays the same, and why the teams are building together.
Langfuse blog

Aaron Katz on 20VC
ClickHouse's CEO on AI, product, and building the company.
20VC
Videos and podcasts
A Day in the Life of a Technical Support Engineer at Langfuse

Typescript AI Conf: AI Observability Panel

Launch Week 4: Demos of new features

Startup Insider Podcast (🇩🇪 only): our story, how we work, what's next

Max (CTO) on ClickHouse data model optimizations to make Langfuse work

Handbook
We document our principles and processes in public, so you can decide whether you'd enjoy working here.
1
Why does Langfuse exist?
2
Who are our customers?
3
How did we get here?
4
Why do customers choose Langfuse?
5
Why is Langfuse Open Source?
6
How does Langfuse make money?
7
Who are we?
Open source
Almost everything we do is public:
