---
title: Working Remotely
description: "How Langfuse works remotely across its San Francisco and Berlin hubs, and what we expect around overlap, async communication, and travel."
---

# Working Remotely

We work across two hubs — San Francisco and Berlin — with team members spread across Europe. The [Working Mode section of our Principles page](/handbook/how-we-work/principles#working-mode) describes the full setup: the Berlin week cadence, onboarding expectations, and why we work this way.

This page is about the practices that make remote work well in day-to-day reality.

## Async by Default

The default is remote-first. That means communicating async wherever possible:

- **Write things down.** RFCs, decision logs, and project specs are how we stay aligned across locations and time zones. If it's not written, it didn't happen.
- **Use `#team-async` for updates** that don't need an immediate response. Save `#team` (notifying) for things that actually can't wait.
- **Don't create a meeting for something that can be a short doc or a Slack message.**

## Stay Unblocked

If you're stuck, don't sit quietly in a DM thread waiting. Post in Slack, start a quick call, or — when in Berlin — tap someone on the shoulder. Blockers should surface within hours, not days.

## Video Calls

Mixed remote/in-person calls need a few explicit norms to work well:

- **Raise your hand** when you want to speak. People in the room naturally talk over each other; remote participants need to be actively called on.
- **Turn your camera on** by default. It makes a real difference for remote participants to feel present.
- **Join from a quiet space.** If you're in the office, use a meeting room or call from your desk with headphones. If you're remote, take calls from your desk.

## Calendar

Mark your working location in Google Calendar using the location feature — your home city, and when you're traveling to Berlin. This helps everyone know when there's time-zone or in-person overlap, and avoids confusion about availability.

## Home Office Setup

We expect everyone to have a setup that lets them do their best work from home. A reliable internet connection, decent webcam, and microphone are the baseline.

## Make sure to join the all-company offsites

While we are remote-first, we do have two all-company offsites per year. Joining them is highly encouraged to get to know your direct colleagues in person and other team members.

<!-- agent-instructions -->

---

## 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/how-we-work/remote.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**: <https://langfuse.com/llms.txt>, 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 <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.