Engineering Super Day

Preparation for the Super Day

We expect everyone participating in a Super Day to be genuinely interested in joining Langfuse and to have prepared for the day:

Everyone:

• Read the handbook from top to bottom
• Read the documentation to understand the product and how it works
• Review our data models in Postgres and Clickhouse how we persist data. We have dedicated data model docs in our product documentation as well:
  • Observability data model
  • Scores data model
  • Experiments data model
  • Prompt management data model

Product & Backend Engineers:

• Be proficient in SQL — many of our onsite challenges rely on SQL logic
• Local dev setup:
  • Typescript: set up our repository by following the Contributing Guide
  • Other languages: set up a scaffold project beforehand and prepare to connect to the spawned and seeded Clickhouse database (see the Contributing Guide for database setup)

Frontend/Design Engineers:

• Set up our repository by following the Contributing Guide

Take-home Design Discussion Preparation

You’ll receive a technical challenge in PDF format describing a feature to plan for implementation.

30 minutes after receiving the challenge, we’ll have a 15-minute call where you can ask any questions about the challenge, the product context, or clarify requirements.

After the call, you should take some time to prepare for the discussion during the Super Day. More on that below. No formal document is required to be submitted.

Super Day: Design Discussion Session

We’ll discuss the feature that we sent you in advance. Imagine you’re already working at Langfuse and you want to clarify your approach and trade-offs before building the feature. This means: you are in the driver’s seat, you are responsible for understanding product requirements and deriving technical specifications. You are also required to make educated technical trade-offs. We are there to help you and answer any questions you have.

We start the session with a 15 minutes presentation by you on the preparation and your thoughts on how to build it. From there, we will dive into the technical details and discuss trade-offs. By the end of the session, all of us should have a clear understanding of how to build this feature. You should have clarified all product and engineering specifications needed to move forward with implementation.

Super Day: Feedback

After the morning session, Marc and Max will take a few minutes to discuss the session and provide you with feedback. We believe this is fair given the investment you’re making. In the interest of time and fairness for everyone, we may decide not to continue with the afternoon session if we don’t think we’re a good fit for each other.

Super Day: Lunch

Meet the team for lunch, learn what they work on, and observe how they collaborate. Ask any questions you have.

Super Day: Implementation Session

We’ll scope down something from the morning discussion to code during the afternoon session.

Process:

1. Pre-discussion (~30 minutes). You sit in the driver’s seat and lead the scoping conversation.
2. Implementation by yourself (~2 hours)
3. Check-in and review (~30 minutes)