TL;DR

We are hiring an engineer who wants to explain Langfuse in person.

This is the events and community side of DevRel. You will organize, attend, and speak at conferences, meetups, workshops, customer events, and community gatherings. Your job is to put Langfuse in the right AI engineering rooms, make the product clear to technical audiences, and turn in-person conversations into durable marketing momentum.

This is not primarily a tabletop or booth-staffing role. You should be excited to travel, give talks, run demos, host events, talk to developers and technical leaders, and bring what you learn back into the company.

What you'll do

• Represent Langfuse at conferences, meetups, workshops, customer events, partner events, and community gatherings across Europe and the US.
• Speak about Langfuse and AI engineering topics in ways that experienced developers and technical leaders find useful.
• Run live demos and technical sessions on tracing, evals, prompt management, datasets, metrics, and related LLM engineering workflows.
• Build and maintain field-ready material: demo flows, workshop runbooks, talk abstracts, event landing pages, follow-up emails, signup flows, and conference-in-a-box assets.
• Identify which events are worth attending, sponsoring, speaking at, or skipping.
• Organize Langfuse-hosted meetups, workshops, dinners, and smaller technical gatherings around the highest-quality audiences.
• Partner with ClickHouse field marketing, sales, solutions, product marketing, and engineering teams where it helps Langfuse show up well.
• Turn event learnings into useful artifacts: better messaging, better demos, better docs, better talks, better customer stories, and sharper product feedback.
• Own the event loop from plan to follow-up: audience, goals, run-of-show, technical content, onsite execution, post-event notes, and next actions.
• Help create a repeatable Langfuse field motion so every event does not start from scratch.

What we're looking for

Must

• You are an engineer, former engineer, or deeply technical operator who can credibly explain software to experienced developers.
• You are excited to travel significantly and spend a meaningful part of your time in the field.
• You can give a good technical talk, run a live demo, and handle unscripted questions from strong engineers.
• You can organize practical details without losing sight of the technical story.
• You care about developer experience, open source, AI engineering, and the quality of the rooms you spend time in.
• You are comfortable with ambiguity and can independently decide what to do before there is a mature playbook.
• You have strong written and spoken English.

Extras

• You have worked in DevRel, product marketing engineering, solutions engineering, field engineering, developer advocacy, or technical community roles.
• You have spoken at developer conferences, meetups, workshops, webinars, or technical customer events.
• You already create technical content, demos, videos, talks, open source projects, or educational material.
• You are deep in AI engineering, LLM observability, evals, agents, or developer tools.
• You have experience working with sales, field marketing, partner teams, or startup GTM teams.
• You have original opinions that experienced developers value.
• You can write code well enough to build, debug, and maintain demos or workshop material.

What this role is not

• It is not a generic event marketing role where success is mainly booth scans and swag distribution.
• It is not a pure DevRel content role where most of the work happens behind a laptop.
• It is not a sales role, though you will spend time with prospects, customers, partners, and the ClickHouse GTM team.

Location and travel

This role can be based in Europe or the United States. We expect significant travel across the US and Europe, with occasional travel to other regions when the audience quality justifies it.

This role is intentionally travel-heavy. The exact cadence will change with the event calendar, but you should expect travel to be a meaningful part of the job.

Why Langfuse?

• You will work on one of the core problems in AI engineering: helping teams understand, evaluate, and improve production LLM applications.
• You will represent an open source developer tool used by some of the most sophisticated AI teams in the world.
• Your work will have a visible impact on how Langfuse shows up in technical communities and in-person AI engineering rooms.
• You will work closely with a small, engineering-heavy team that ships quickly and talks to users constantly.
• You will get the leverage of ClickHouse while still working in the focused Langfuse team.
• You will help define what events-led developer relations looks like for a technical, open source, AI-native company.

Our Process

We can run this process quickly when calendars line up.

1. Fill out application
2. We screen your application
3. Screening Call: Quick intro and logistics, remote
4. Founder Call: Marketing deep dive, 40 min, remote
5. Deep Dive: Technical demo, event strategy, and community deep dive, 60 min, remote
6. Super Day: half or full day with the team, in office when possible, remote in some cases
7. Meet the other founders, short calls
8. Decision and offer

Links

• All repos: https://github.com/langfuse
• Company handbook: https://langfuse.com/handbook
• Team: https://langfuse.com/handbook/chapters/team
• How we hire: https://langfuse.com/handbook/how-we-hire
• Blog: https://langfuse.com/blog
• Docs: https://langfuse.com/docs
• Changelog: https://langfuse.com/changelog
• Careers: https://langfuse.com/careers/careers

Some DevRel and community work we like

• Vercel: developer-first launches, technical demos, and high-trust DevRel work
• Hugging Face: community-led education, workshops, courses, and technical ecosystem building
• ClickHouse: practitioner-led technical talks, field events, and infrastructure category building
• Swyx / Latent Space: original market framing, technical taste, and public point of view
• Simon Willison: technical writing and demos with a clear point of view

Process

We can run the full process to your offer letter in less than 7 days (hiring process).

Tech Stack

We run a TypeScript monorepo: Next.js on the frontend, Express workers for background jobs, PostgreSQL for transactional data, ClickHouse for tracing at scale, S3 for file storage, and Redis for queues and caching. You should be familiar with a good chunk of this, but we trust you'll pick up the rest quickly (Stack, Architecture).

How we ship

Link to handbook

• We trust you to take ownership (ownership overview) for your area. You identify what to build, propose solutions (RFCs), and ship them. Everyone here thinks about the user experience and the technical implementation at the same time. Everyone manages their own Linear.
• You're never alone. Anyone from the team is happy to go into a whiteboard session with you. 15 minutes of shared discussion can very much improve the overall output.
• We implement maker schedule and communication. There are two recurring meetings a week: Monday check-in on priorities (15 min) and a demo session on Fridays (60 min).
• Code reviews are mentorship. New joiners get all PRs reviewed to learn the codebase, patterns, and how the systems work (onboarding guide).
• We use AI as much as possible in our workflows to make our users happy. We encourage everyone to experiment with new tooling and AI workflows.