--- title: Onboarding description: New hire onboarding guide. --- # Onboarding at Langfuse Welcome to Langfuse! This document outlines how onboarding works for every new team member — what to expect on your first day, first week, first month, and beyond. Our goal is to help you quickly gain context, feel confident contributing, and become an owner of your area of the product. At Langfuse, we lead with context, not control. We share the "why" and "what's important right now," so you can make the best decisions for our users. You'll get support, feedback, and guidance along the way — but you'll also have the space to take ownership early. ## Timeline Overview | Milestone | Focus | Key Outcome | | -------------- | ------------------------------ | -------------------------------------------------- | | **Day 1** | Getting oriented | Understand company priorities and get set up | | **Week 1** | Making your first contribution | Deploy your first change to production | | **Months 1-3** | Taking ownership | Complete your first independent project end-to-end | | **Month 6** | Becoming a go-to person | Own a product area and be a trusted domain expert | --- ## Day 1 — Getting Oriented **Goal:** Understand company priorities and get set up for work. - **Welcome meeting with Max (CTO)** — Context on company status, top priorities, challenges, and decision-making - **Setup and access** — GitHub, Slack, a local development environment, and AI tooling: Codex, Claude and Cursor, all via ClickHouse ConductorOne - **Connect the integrations** — Linear, Datadog, AWS SSO, incident.io, PostHog, Sentry, Pylon, Hex. Your coding agent's skills depend on these, and an unauthorized one does not produce an error: the agent simply cannot answer. Connect them on day one rather than discovering a gap mid-task - **Clone both repositories** — `langfuse/langfuse` and `langfuse/langfuse-docs`. The docs repo carries the documentation, the changelog and this handbook, and shipped work regularly needs a change in it - **Meet the repo's agent** — in a `langfuse/langfuse` checkout, ask your coding agent to "onboard me". It works out what access you have, records it, and walks you through the pages here - **First task** — Small starter task to explore codebase and workflows. Goal: merge something within the first few days ## Week 1 — Making Your First Contribution **Goal:** Deploy your first change to production and understand our systems. By the end of Week 1: - Fully working development setup - Merged and deployed your first change - Understand high-level architecture, CI/CD process, and monitoring - Read and acknowledge policies (security, compliance, data handling) - Engage in team communication _We don't expect speed — we expect curiosity. Take the time to explore and ask "why."_ ## Months 1-3 — Taking Ownership **Goal:** Deliver your first independent project end-to-end. By the end of Month 3, you should have: - **Shipped an independent project** — Led a small feature or improvement from start to finish (technical planning, product thinking, implementation, documentation, user research) - **Joined support rotation** — Started handling support tickets, seeing product through users' eyes, and maintaining your improvement backlog - **Learned through reviews** — Received feedback on every PR from the team during your first ~2 months - **Balanced priorities** — Demonstrated ability to align your backlog (support, fixes, improvements) with company priorities - **Contributed to planning** — Participated in planning discussions ## Month 6 — Becoming a Go-To Person **Goal:** Own a product area and be a trusted domain expert. By six months: - **Domain expertise** — Be the go-to person for a specific area (e.g., evals, datasets, integrations, infrastructure) - **Shipped projects** — Multiple projects delivered from idea to production - **Mentorship** — Able to mentor new joiners and review PRs in your area - **Self-sufficient** — Fully independent in planning, building, and deploying - **Impact-driven** — Clear sense of how to prioritize for maximum impact _You're not just contributing — you're shaping how we build and make product decisions._ ## Ongoing Support Throughout your onboarding and beyond, you'll have support from: - **Max and the team**: Available for prioritization help and technical guidance - **Pull request reviews**: Continuous feedback on your code - **Support rotation**: Learn from real user problems and needs - **Context sharing**: Regular updates on company priorities and strategic direction Welcome to the team! --- ## Agent Instructions This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/handbook/product-engineering/how-we-work/onboarding.md`. ### Querying these docs If the answer is not on this page, query the documentation instead of guessing: - **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question: ```bash curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?" ``` - **Index of every page**: , with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt). ### Before writing Langfuse code - **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results. - **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application. - **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples. - **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api `) to read or write traces, prompts, datasets, and scores from the terminal. Found an error in these docs? Please open an issue at .