Plausible Analytics

Plausible is a small, fully remote team building an open-source, privacy-focused web analytics product. Work is organised to minimise synchronous meetings and to favour asynchronous, written collaboration.

Day-to-day communication is written-first and happens on platforms such as GitHub threads, Basecamp, HEY email threads and internal chat. Email is generally used for external communication and customer support. The team values clear, concise written communication and keeping public or documented discussion where possible.

People at Plausible handle a wide range of tasks rather than narrow, siloed roles. Examples of typical work include adding new metrics to the dashboard and API (with matching docs), improving onboarding flows, investigating and troubleshooting customers’ data issues, optimizing dashboard loading performance, automating manual back-office tasks, creating or improving documentation, and helping customers directly.

The technical environment includes Elixir + Phoenix on the backend, HTML/CSS/JS + React on the frontend, PostgreSQL for relational data and ClickHouse for analytics. CI and builds use GitHub Actions and Docker; deployments use Terraform and Ansible. Production currently runs on Hetzner Cloud with Docker and self-hosted ClickHouse (with plans toward self-hosting PostgreSQL and considering container orchestrators such as Nomad or Kubernetes to enable horizontal scaling).

Because the team is small, individuals have broad ownership and direct impact. Participating in the on-call rotation is part of the role (the rotation is paid), and the company supports flexible arrangements around hours and vacation.

To apply, send an email with your previous work experience, relevant skills and the technologies you’ve worked with to jobs@plausible.io. For customer-facing roles they ask applicants to describe what they’ve done in the past and what they can bring to Plausible.

Typical interview steps vary by role but follow a common pattern: a short introductory interview (often with Uku or Marko), a technical assessment (for example a pair-programming session for product engineering or a technical interview for infrastructure), and a final interview with Uku & Marko where practical working arrangements and compensation are discussed.

They evaluate candidates for self-management (a “manager of one”), thoughtful and kind communication, and role-specific skills. Engineers are expected to write well-tested, readable code and be comfortable with—or able to quickly learn—the listed technologies. Customer-facing candidates should be strong, concise writers who can explain technical topics clearly and troubleshoot in browser developer tools.

The company suggests following their social channels (Twitter or Mastodon) to hear about new openings. Final offers and practical working arrangements (hours, vacation, compensation) are negotiated during the final interview; onboarding follows once terms are agreed.