Plausible Careers: Is Plausible Analytics a Calm Company to Work For?

Most "plausible careers", "plausible analytics careers", and "plausible jobs" results are either a company page or a board copying one. That is the right door when a role exists. It is the wrong place to decide whether a normal Tuesday will be calm. A careers page is a listing. A calm-score is a reading of how the week is supposed to work: hours you can plan around, meetings that do not eat the day, remote or async norms that are real, time off people actually take, and enough autonomy that you are not managed by chat.

This article is the next company deep dive in our careers series, after Buffer, 37signals, and Beehiiv. It is not a Plausible jobs portal, and it does not invent openings, salary figures, or survey scores. It scores the live Plausible Analytics directory profile the same way we scored named employers in best work-life balance companies to work for in 2026. When a practice is named on that profile, we say so. When it is not, we tell you to ask. Then we send you to the email address where Plausible actually hires.

This page is a calm-score, not a jobs board

Calm Companies does not post Plausible requisitions, collect applications, or promise that a role is open. The directory snapshot behind this article says "No open roles yet." The directory exists so you can read operating habits before you spend an evening on a message. If you already know you want the privacy-friendly analytics product, bookmark the official email below and write when there is a role to write about. If you are still deciding whether Plausible Analytics is a calm company to work for, stay here and score the week first.

Email jobs@plausible.io when you are actually applying. Decide with a scorecard. Do not confuse those two jobs.

The Plausible culture scorecard

Use the same five dimensions we use across the directory: hours, meetings, remote / async, PTO, and autonomy. Mark each as documented (the profile names a practice), partial (a related practice is named but the dimension itself is not), or unstated (you will have to ask). Documented is not automatically "good." It only means you can stop guessing.

• Hours: documented. Listings describe flexible hours, with part-time and full-time options in a 20–40 hour week. One universal day length, shared by every person, is not a separate number. The range is the named practice.
• Meetings: documented. The team minimizes synchronous meetings and typically holds no more than one internal meeting per week. Asynchronous, written collaboration is the preferred default.
• Remote / async: documented. Work is remote (worldwide), remote-first, and flexible. Written-first is named, not implied: GitHub threads, Basecamp, HEY email threads, and internal chat. External and customer support runs on email.
• PTO: partial. The profile says the company can accommodate a wide range of vacation, and varied vacation is listed with the perks. No fixed policy number is on the snapshot. Ask what people took.
• Autonomy: documented. Broad ownership, a wide range of tasks rather than silos, and a hiring bar that includes being a manager-of-one. On a team of 2–10, ownership and coverage are the same coin.

If you want the role-shape side of the same search, pair this scorecard with jobs with better work-life balance and the structural predictors in what actually predicts work-life balance at companies. A wide-ownership title on a two-to-ten-person team is still a wide job.

What the Plausible directory profile actually says

Plausible Analytics is listed as software development, with a 2–10 person team. The directory snapshot behind this article says "No open roles yet." The mission line on the card is "Easy to use and privacy-friendly Google Analytics alternative." Product category and a mission sentence are not a calm-score. They tell you what the company says it is for. They do not tell you how Tuesday works.

The profile describes an open-source, privacy-focused alternative to Google Analytics. It calls the product lightweight, and it describes the point as avoiding corporate surveillance. Funding is subscribers rather than venture capital. That is the directory's company description. It is not a study we ran, and it is not a meeting cap. A subscriber-funded week can be sane or loud. The operating notes are what you score.

How they work is specific, and it is small on purpose. The team is fully remote. They minimize synchronous meetings and favor asynchronous, written collaboration. Day-to-day writing happens on GitHub threads, Basecamp, HEY email threads, and internal chat. Email is the channel for external and customer support. People handle a wide range of tasks rather than staying in a silo. The example work named on the card is metrics and the API plus docs, onboarding, customer data issues, dashboard performance, automating back-office work, documentation, and helping customers.

The technical context is just as specific, and it belongs in the email if you are writing as an engineer. The profile names Elixir and Phoenix; HTML, CSS, JavaScript, and React; PostgreSQL and ClickHouse. Continuous integration is GitHub Actions and Docker. Deploys use Terraform and Ansible. Production is Hetzner Cloud and Docker, with ClickHouse self-hosted. That list is how the product runs. It is not a calm signal. It is the vocabulary of a technical note to jobs@plausible.io.

Two more operating facts sit on the same card, and both belong in the score. Broad ownership is named. So is a paid on-call rotation, next to flexible hours and vacation. Read the ownership line next to the rotation, not instead of it.

• Work location: remote (worldwide). Remote-first and flexible.
• Hours in listings: part-time and full-time options, 20–40 hours a week.
• Meetings: typically no more than one internal meeting per week. Async written work is preferred.
• Arrangements: the profile says they can accommodate a wide range of hours, vacation, and arrangements.
• Perks named on the card: remote worldwide; flexible hours in that 20–40 range; varied vacation; paid on-call; part-time and full-time. Salary and compensation ranges are published in job ads. This page does not reprint figures.
• Open roles on this snapshot: "No open roles yet." No titles to list.
• Hiring, when they hire: email jobs@plausible.io. The steps are on the profile, and they are spelled out below. Interview stages on a closed snapshot are still a description of the last process, not proof a seat is open.

Hours: flexible 20–40 in listings

A named week is the loudest calm signal on a directory card. Buffer names a four-day week. 37signals names a standard 40-hour week, reduced to 32 hours in summer. Plausible names a range. The directory documents flexible hours, with part-time and full-time options, and listings are written as 20–40 hours a week. That is documented. The word flexible is attached to a range, not left as an empty adjective. You still have to ask which end of 20–40 the role you want actually uses.

The snapshot we scored has no open role to quote, so there is no live ad sitting next to this sentence. The range is still the practice the profile names. Treat it as the boundary of the question, not as your future calendar. Part-time and full-time are both real options in that sentence. A 20-hour listing and a 40-hour listing are different jobs. Ask which one you are discussing before you score the week.

Paid on-call is documented beside that range. A rotation can sit outside the hours in a listing. The profile does not say how often the rotation comes around, how long a shift lasts, or what the pay is. On a team of 2–10, fewer people share it. Ask for the rotation as it ran recently, in a form you can repeat, before you decide the listing is the whole job.

The same card says the company can accommodate a wide range of hours and arrangements. That is stronger than a slogan and weaker than a personal schedule. Ask what last month looked like for someone on the arrangement you want, part-time or full-time, including on-call.

The 20–40 hour range is documented. The on-call calendar is named and uncounted. Ask for both.

Meetings, remote, PTO, and autonomy

Meetings are documented, and the sentence is more specific than most cards. The team minimizes synchronous meetings. A typical week has no more than one internal meeting. Asynchronous written work is the preference, and the channels are named: GitHub threads, Basecamp, HEY email threads, and internal chat. External and customer support runs on email, which is a different stream from that internal meeting. "Internal" and "typically" are doing real work in that sentence. A cap on internal meetings is not a cap on every customer conversation, and "typically" means the exception can exist. Ask what last week's internal meeting was, who had to attend it, and which customer conversations were live rather than email. A written cap you can check against last week is a practice. A cap nobody can find on a calendar is a slogan. This one is written down. Confirm it survived contact with the week.

Remote and async are documented together. Work location is remote (worldwide). The profile calls the company remote-first and flexible. Written-first is not an inference from the time zones. It is the named default, on the tools above. That is the same kind of sentence the 37signals card writes down, and the same kind of default Doist names. Screen the failure mode anyway. Our remote work policy red flags are the hidden-exception version: remote on the card, office hours in the chat. Ask what you must attend live if you are many time zones from the rest of the team, and whether any response-time expectation is written down. If the answer is a shrug, the written-first line did not survive the interview.

PTO is partial, and that mark is the honest one. Varied vacation is named as a perk. Flexible vacation is how the work section describes time off. The profile says the company can accommodate a wide range of vacation and arrangements. No fixed policy number is on the snapshot. You know time off is something they say they will design around. You do not know how many days that was last year, or whether people logged off. Ask both. On a team of 2–10, also ask who covers the product and the paid on-call rotation while someone is away. Accommodation language is not a day count. Paid on-call is a separate named perk. It is not a vacation policy. Salary and compensation ranges are published in job ads when ads exist. This page does not reprint figures, and the snapshot has no open role attached to one.

Autonomy is documented, and the profile holds the calm half and the heavy half in the same place. Broad ownership is named. People handle a wide range of tasks instead of a silo. The hiring notes look for a manager-of-one, kind communication, and the skills of the role. Manager-of-one on a team of 2–10 is a calm signal and a load signal. The example work on the card is the load: metrics and the API plus docs, onboarding, customer data issues, dashboard performance, automating back-office work, documentation, and helping customers. That is several kinds of work under one name. Ask who cuts scope when a customer issue, an on-call shift, and a product change land in the same week, and ask for a recent example. Pair that conversation with company culture interview questions so you are scoring behavior, not adjectives. A tiny team can still be run by checking. See signs of micromanagement for that failure mode.

How to apply for Plausible careers (official only)

Apply by email, and only by that email: jobs@plausible.io. Say what your experience is, which skills you are offering, and which tech you work with. For a customer-facing role, the profile says they ask what you have done and what you would bring. There is no Calm Companies application, and there is no second official form on this page. Do not send a resume to a lookalike domain, a recruiter in a direct message, or a board this directory does not use.

The directory snapshot says "No open roles yet." We are not naming requisitions, because the profile did not name any. The profile tells candidates to follow Twitter and Mastodon for openings. Use the accounts Plausible actually runs, not a search-ad lookalike. When Plausible is hiring, the same card describes the usual steps. A short intro, often with Uku or Marko. A technical assessment. The examples given are pair-programming for a product engineering role, or an infrastructure interview. A final interview with Uku and Marko about arrangements and compensation. Offers are negotiated in that final interview. What they are evaluating is whether you can be a manager-of-one, whether your communication is kind, and whether you have the skills the role needs.

Salary and compensation ranges are published in the job ads. This article does not copy those numbers. If a range matters, read it on the ad that is actually open.

1. Open the Plausible Analytics directory profile and score hours, meetings, remote, PTO, and autonomy against the arrangement you would actually take, part-time or full-time.
2. Read the snapshot language: "No open roles yet." Follow Plausible on Twitter and Mastodon if you want to hear when that changes. This page will not become the listing.
3. When you apply, email only jobs@plausible.io. Include experience, skills, and tech. If the role is customer-facing, say what you have done and what you bring.
4. Keep a copy of what you sent. When an ad exists, that ad is the source of truth for hours, location, and the compensation range.

Calm Companies will not send that email for you. The product is the scored directory and a weekly digest of openings from calmer teams, so you spend fewer evenings on companies that treat balance as a poster. If Plausible is a fit and a role is real, email them. If you want more companies with public operating habits, stay in the directory.

Honest caveats: when Plausible can still be the wrong desk

A clear profile cannot save you from a bad manager, an understaffed rotation, or a role whose shape fights your life. These are the Plausible-specific caveats we can name without inventing a study.

• The team size on the card is 2–10. Broad ownership is the shape of the job. Vacation coverage, customer issues, and the paid on-call rotation draw from the same small group. Autonomy and load are the same coin.
• Flexible hours are documented as 20–40 in listings. Paid on-call is also documented. Ask the cadence before you treat the listing as the whole week.
• The snapshot says no open roles yet. A deep dive does not open a requisition. The email address is the path when they are hiring. It is not a back door into a role that is not posted.
• PTO is partial. Varied vacation, and language about accommodating a wide range, do not add up to a day count. Ask what people took last year and whether they were offline.
• The work examples are generalist: product and API docs, onboarding, customer data, dashboard performance, back office, and helping customers. If you want a narrow lane, believe the list the first time you read it.
• "No more than one internal meeting" is a cap on internal meetings. Customer support is described as email. Ask what is still live.
• Remote worldwide still has time zones. Ask what that one internal meeting does to your evening if the people you work with are elsewhere.
• This page is not a jobs portal. It will not keep a future open-role list current.

If you are leaving a hostile job, a written-first week is not enough. You need a team that does not recreate the last one. The toxic-boss red flags guide and the is my boss toxic quiz are a faster read than another careers page. If you are still naming your non-negotiables, the calm company fit quiz is built for that filter.

Interview questions before you accept

Directory notes get you onto a shortlist. Interviews tell you whether the shortlist survives a manager. Ask process questions. "Do you have good work-life balance?" invites a speech. "What did last month's hours look like on this team?" invites a story you can score. The longer set lives in our work-life balance interview questions; the Plausible-shaped version is below.

1. Hours: "Listings say 20–40, part-time and full-time. What did a normal week look like on this team last month, in hours, and where did the paid on-call rotation sit inside or outside that range?"
2. Meetings: "The profile says typically no more than one internal meeting a week. What was last week's internal meeting, who had to attend, and which customer conversations were live rather than email?"
3. Remote / async: "If I am many time zones from the people I work with, what am I expected to attend live? Is any response-time expectation written down, or is the written-first default — GitHub, Basecamp, HEY, chat — the whole rule?"
4. PTO: "Vacation is described as varied and flexible, with no day count on the profile. How many days did people actually take last year, were they offline, and who covered on-call?"
5. Autonomy: "You hire for a manager-of-one, and the work is a wide range of tasks. When a customer issue, on-call, and a product change collide, who cuts scope — and can you give a recent example?"
6. Arrangements: "The final interview is where arrangements and compensation are negotiated, and the card says you can accommodate a wide range. For someone aiming at a specific point in the 20–40 range, what is actually negotiable?"
7. Hiring hygiene: "Am I writing to jobs@plausible.io, and is there an open role, or are you still on 'No open roles yet'?"

Ask a future peer if you can get one, and ask the person who runs the intro — often Uku or Marko — not only a forwarded note. If the answers diverge, believe the more specific one.

If you want more companies like this

Plausible is one named profile, and the written-first week is part of the name. Browse the Calm Companies directory and open two or three others that also document a week. Buffer names a four-day week; the Buffer careers deep dive is the calm-score version of that card. 37signals names a 40-hour week, 32 in summer, and write-first rituals; the 37signals careers deep dive scores that profile the same way. Beehiiv is the previous piece in this series: remote, with a named PTO floor and a fast-paced week rather than a named hour range. The Beehiiv careers deep dive is that scorecard. Doist names async as the default. Ghost is on the same shortlist. The 2026 walk-through is in best work-life balance companies 2026.

The practical workflow is short. Score Plausible. Email jobs@plausible.io only when a role is real. Subscribe if you want the next openings from teams that publish operating habits, instead of refreshing a careers page at midnight.

Frequently asked questions

Is Plausible Analytics a calm company to work for?

Several of the loudest calm signals are documented, which is uncommon. Hours are a named 20–40 range in listings, with part-time and full-time options. Internal meetings are typically capped at one a week, and written-first collaboration is named. Remote is worldwide. Autonomy is broad ownership and a manager-of-one hiring bar. PTO is only partial: varied vacation, no fixed number. A paid on-call rotation and a 2–10 person team are on the same card. The snapshot has no open roles. It can fit someone who wants a small, written-first, remote week and a generalist load. It is a poor fit if you need a published PTO count, a narrow job, or a role that is open today. Score the arrangement you would actually take.

Where should I apply for Plausible careers or Plausible jobs?

Only by email to jobs@plausible.io, with your experience, skills, and tech. Customer-facing roles should say what you have done and what you bring. The profile says to follow Twitter and Mastodon for openings. Calm Companies is not a Plausible jobs board, and a third-party scrape is not the application.

Does Plausible have open jobs right now?

The directory snapshot says "No open roles yet." This page does not invent titles. Check the profile again, and watch the channels it names, before you treat an email as an application to a live role. If nothing is open, there is nothing to apply for.

Is Plausible remote?

Yes, as a named practice. The directory lists work location as remote (worldwide), and it calls the company remote-first and flexible. Part-time and full-time both sit inside that remote setup. Ask what you must attend live, including the one internal meeting a typical week includes.

Is Plausible async-first?

The directory says the team favors asynchronous, written collaboration, and it names the tools: GitHub threads, Basecamp, HEY email threads, and internal chat. It also says they minimize synchronous meetings and typically keep internal meetings to no more than one a week. External and customer support is email. That is a documented written-first default, with a named cap rather than a claim of zero live conversations. Ask whether last week matched the sentence.

What hours does Plausible work?

Documented as flexible, with part-time and full-time options at 20–40 hours a week in listings. The profile also says they can accommodate a wide range of hours and arrangements. It does not publish one schedule for every person, and it does not say how the paid on-call rotation changes the week. Ask for last month on the arrangement you want.

What PTO does Plausible offer?

Partial. The snapshot lists varied vacation, describes vacation as flexible, and says the company can accommodate a wide range of vacation. No fixed policy number is published. Paid on-call is a separate perk, not a PTO figure. Salary ranges are published in job ads when ads exist; this page does not reprint them. Ask how many days people took and whether they were offline.

How is this different from Plausible's own hiring?

Plausible hires by email to jobs@plausible.io when they are hiring. The profile describes a short intro, often with Uku or Marko, a technical assessment, and a final conversation with Uku and Marko where arrangements, compensation, and the offer are negotiated. This page scores calm-company signals from the live directory profile. It does not run their hiring, and it does not list roles. The snapshot says no open roles yet. Decide here. Write there when there is something to apply for.

If you want more employers scored the way this page scores Plausible, browse the Calm Companies directory and join the newsletter for a weekly digest of openings from calmer teams.