37signals Careers: Is 37signals a Calm Company to Work For?

Most "37signals careers" results are either 37signals' own jobs page or a board copying that page. Searches for Basecamp careers or HEY careers land in the same place: 37signals is the independent company behind those products. That is the right door to apply. It is the wrong place to decide whether a normal Tuesday will be calm. A jobs 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. It is not a 37signals jobs portal, and it does not invent openings, interview stages, or survey scores. It scores the live 37signals 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 — or, for applications and stated hours, on 37signals' official jobs page and the How We Work handbook linked from the directory — we say so. When it is not, we tell you to ask. Then we send you to apply where 37signals actually hires.

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

Calm Companies does not post 37signals requisitions, collect applications, or promise that a role is open. 37signals' own jobs page does that. As of the latest check, that page may say there are no openings. That is already more honest than a scraped "Basecamp careers" listing that implies a door is open. The directory exists so you can read operating habits before you spend an evening on a form that does not exist yet. If you already know you want the company behind Basecamp and HEY, bookmark the official apply path below and the notify signup. If you are still deciding whether 37signals is a calm company to work for, stay here and score the week first.

Apply on 37signals.com/jobs. Decide with a scorecard. Do not confuse those two jobs.

The 37signals 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, official jobs page, or linked handbook 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. The directory names a standard 40-hour week, reduced to 32 hours in summer. The official jobs page repeats 8-hour days and 40-hour weeks as what the company expects. That is a named week — and a reason to ask whether summer 32 holds on the team you would join.
• Meetings: documented as a bias, not a count. Most collaboration is written first. Real-time is the exception. Daily and weekly check-ins replace status meetings. The company states a preference for fewer meetings and minimal email. Ask what a normal calendar looks like on the product you would join.
• Remote / async: documented. Fully remote, no physical headquarters. Async rituals are named (daily and Monday written check-ins, Kickoffs, Heartbeats). Real-time still exists via pings, video, screen-share, and occasional in-person work.
• PTO: documented on the directory. 20 vacation days plus 11 local holidays, with vacation rollover up to 27 days, and a paid sabbatical of 6 weeks every three years. Ask how many days peers actually took and whether they stayed on chat.
• Autonomy: documented. The handbook's ideal contributor is a "manager of one." Write-first updates, small independent teams, and a public How We Work handbook. Whether your manager protects that focus is still an interview question.

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 calm title in a loud week is still a loud week.

What the 37signals directory profile actually says

37signals is an independent, self-funded, fully remote software company. It builds Basecamp, HEY, Fizzy, Omarchy, and ONCE. The team invented Ruby on Rails and has published books about how it works. The current directory card lists it as software development, a 51–100 person team, and no open roles yet. Product category is not a calm-score. Inventing Rails does not tell you how Tuesday works.

How they work is more useful. There is no headquarters. People live and work where they choose, across dozens of cities and multiple continents. If you move across a state or country border, you notify People Ops because taxes may change. Teams share a six-week cycle and a two-week cooldown. The cooldown is for bug fixes, write-ups, and planning. Teams publish a Kickoff for the next cycle and a Heartbeat that summarizes what shipped. That is a named cadence, not a vibe.

Async rituals are written down. A daily check-in asks "What did you work on today?" each afternoon and is required at least twice a week. A weekly check-in asks "What will you be working on this week?" on Monday mornings. Check-ins are scoped by department so you do not read every team's status. Kickoffs and Heartbeats sit on top of that. Most collaboration starts as a message, todo, or document so others can read on their schedule. When real-time is needed, the company uses pings, video calls, screen-sharing, or occasional in-person work.

• Employees are expected to be self-directed. The handbook calls the ideal contributor a "manager of one."
• The stated environment is calm and low-distraction, with fewer meetings and minimal email.
• Regular rituals include an All Hands at the end of each cycle, periodic Everyone on Support shifts so staff stay close to customers, and company meet-ups twice a year.
• Meet-ups are typically about a week (most people arrive Sunday, meet Monday–Thursday, travel Friday). Attendance is expected; occasional absences are allowed.
• Work location: fully remote / no HQ, with a move-notify rule for taxes.

How they hire is equally concrete, and it is the part "Basecamp careers" scrapes get wrong. Openings are posted on the company's jobs page. You can sign up there to be notified about future openings or subscribe to the jobs RSS feed. The company says it will not share that email and will only use it for job notifications. It does not place independent value on background, location, previous employers, or educational credentials. The focus is who you are today and what you can do. Managers of One tend to thrive. Specific interview steps are not listed when the page is empty; when a role is posted, that listing is the source of truth for how to apply.

Hours: 40, then 32 in summer

A named week is the loudest calm signal on the 37signals card. The directory snapshot is specific: a standard 40-hour week, reduced to 32 hours in summer. The official jobs page says the same thing in different words: 8-hour days and 40-hour weeks are plenty of time to do great work, so that is all the company expects. It also names a calm company and deliberate, concerted effort, with fewer meetings, hardly any email, and fewer interruptions than you are used to.

That wording is honest and still incomplete. A 40-hour policy can hide evening support, cycle crunches, or a summer 32 that only exists on paper. Cooldown weeks are recovery baked into the product cycle — useful, and different from vacation. If you need the hour count to survive a life outside work, ask the hiring team what last summer actually looked like on this product, and whether Everyone on Support shifts stretch a day past eight hours. Then score the answer the way you would score any other named week in the directory.

A 40-hour week that still expects you on chat at 9pm is a branding exercise. Ask for last month, not the policy PDF.

Meetings, remote, PTO, and autonomy

Meetings are documented as a default, not a number. Write first. Real-time second. Daily and weekly written check-ins replace a lot of status theater. That is stronger than most careers pages, and it is still not "two hours of calls a week." All Hands at the end of a cycle, Kickoff, Heartbeat, Everyone on Support, and twice-yearly meet-ups are live time you can name. Ask how many hours of meetings the role usually carries in a normal cycle week, who can decline one, and whether decisions default to writing. If nobody can describe a normal calendar, assume the calendar is the job.

Remote is documented. Fully distributed, no physical headquarters, live where you choose — with the tax-notify rule when you move. Remote without async is often worse than a well-run office. 37signals names the async default the way Doist does, and more explicitly than the Buffer snapshot. Screen the communication default anyway. Our remote work policy red flags are the hidden-exception version of this: remote on the card, office hours in the chat. Pings and video still exist here. Ask what you must attend live if you are several timezones away from the rest of the product team.

PTO is clearer on this profile than on many directory cards. The snapshot lists 20 vacation days plus 11 local holidays, vacation rollover up to 27 days, and a paid sabbatical of 6 weeks every three years. Medical (U.S. Blue Cross Blue Shield PPO, company pays 75% of the premium), dental and vision (MetLife, company pays 100%), life and disability, and a Vanguard 401(k) with a 100% match up to 6% of salary are on the same perks block. Numbers are not usage. In the interview, ask how many vacation days people on this team took last year and whether they stayed reachable. The linked Benefits & Perks handbook page is the company's own write-up; treat the listing as the source of truth for the country and role you would take.

Autonomy is handbook-plus-interview. "Manager of one," write-first updates, and small independent teams are named. Those can describe a calm owner or a person who is expected to invent the job every cycle. On a 51–100 person remote company, broad ownership is normal. Ask who cuts scope when a cycle overfills, and whether managers are described as protectors of focus or distributors of tasks. Pair that conversation with company culture interview questions so you are scoring behavior, not adjectives. Intrusive checking is a different failure mode; see signs of micromanagement.

How to apply for 37signals careers (official only)

Apply on 37signals' official jobs page: 37signals.com/jobs. That is the URL our directory uses for 37signals careers. There is no separate Basecamp careers portal or HEY careers portal. Those searches are navigational: same company, same jobs page, same notify signup and RSS feed. Do not send a resume to a lookalike domain, a "Basecamp recruiter" in a DM, or a form that is not on 37signals.com.

The jobs page may currently say there are no openings. Believe that line. A calm-score does not create a requisition. Sign up on that page to be notified, or subscribe to the jobs RSS feed, then read the How We Work handbook linked from the directory so you already know the week you would be joining. When a listing appears, that listing — not a job-board scrape — is how you apply and what to expect.

1. Open the 37signals directory profile and score hours, meetings, remote, PTO, and autonomy against the product you would join.
2. Open 37signals.com/jobs. If a role is listed, read it. If the page says there are no openings, use the notify signup or RSS feed and stop refreshing third-party boards.
3. Apply only through the official path on that listing. If there is no listing, there is no role.
4. Keep a copy of what you submitted. Openings and requirements change; the listing is the source of truth for location, salary, and eligibility.

Calm Companies will not submit that form 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 37signals is a fit and a role appears, apply there. If you want more companies with named weeks and public habits, stay in the directory.

Honest caveats: when 37signals can still be the wrong desk

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

• There may be no openings. A deep-dive is not a hidden job. If you need a role this month, score other documented profiles in the directory while you wait on the notify list.
• "Manager of one" is a filter. People who want a highly sequenced corporate ladder, frequent live coaching, or a manager who assigns every next task should believe that line the first time they read it.
• Everyone on Support is periodic by design. Customer-adjacent weeks can be louder than a cooldown even when the handbook is kind.
• Twice-yearly, roughly week-long meet-ups are expected. If you cannot travel, ask what occasional absence looks like on the team — do not assume remote means never in a room.
• The official jobs page states two political norms: avoid political debates on internal systems, and the company does not weigh in on politics publicly outside topics related to its business. You should be at peace with both before you apply.
• A 51–100 person company usually means broader ownership. Autonomy and load are often the same coin.
• Meeting load is a bias, not a quantified weekly cap. Write-first does not prove a meeting-light cycle on every product.

If you are leaving a hostile job, a 40-hour 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 summer's 32-hour weeks look like on this team?" invites a story you can score. The longer set lives in our work-life balance interview questions; the 37signals-shaped version is below.

1. Hours: "Is a normal week eight-hour days, and what is the last time a cycle or an Everyone on Support shift ran past that?"
2. Meetings: "How many hours of live calls does this role usually carry in a cycle week, and who is allowed to decline one?"
3. Remote / async: "If I am several timezones away from the rest of the product team, what am I expected to attend live? What is the expected response time on a ping during local business hours?"
4. PTO: "How many vacation days did people on this team actually take last year, and were they offline? How does the sabbatical work in practice?"
5. Autonomy: "When a six-week cycle overfills, who cuts scope — and can you give a recent example?" If the answer is always "we just push through," the scorecard just failed, whatever the handbook says.
6. Hiring hygiene: "Am I talking to 37signals, or to an agency? Where is this role listed on 37signals.com/jobs?"

Ask a future peer and the hiring manager, not only the recruiter. Recruiters describe the intended company. Peers describe last Tuesday. If the answers diverge, believe the more specific one.

If you want more companies like this

37signals is one named profile, not the product. Browse the Calm Companies directory and open two or three others that also document a week. Buffer names a four-day week and public finances; a sibling careers deep dive in this series may still be pending merge, so start with that directory card. Ghost names one or two video calls a week for most people. Doist names async as the default and extended paid time off. The 2026 shortlist walk-through is in best work-life balance companies 2026.

The practical workflow is short. Score 37signals. Apply on the official jobs page if a role appears. 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 37signals a calm company to work for?

It is one of the more documentable profiles in the directory: fully remote, a named 40- and 32-hour week, write-first rituals, a public How We Work handbook, and numeric PTO plus a sabbatical. That is a strong starting brief. It is not a guarantee that every product team is quiet, or that a cycle never overfills. Score the team you would join.

Where should I apply for 37signals careers, Basecamp careers, or HEY careers?

Only on 37signals' official jobs page at 37signals.com/jobs. Basecamp and HEY are products of the same company. There is no separate official careers portal. Calm Companies is not a 37signals jobs board.

Does 37signals have open jobs right now?

The official jobs page may currently say there are no openings. The directory card matches that with "no open roles yet." Sign up on 37signals.com/jobs for notifications or subscribe to the jobs RSS feed. Do not treat a third-party "Basecamp careers" listing as a live requisition.

Is 37signals fully remote?

Yes, as a named practice. The directory and official jobs page both describe a fully remote company with no physical headquarters. People live and work where they choose and notify People Ops when a move may change taxes. Twice-yearly meet-ups are expected. Async response-time norms are named as rituals, not as a minutes-to-reply SLA. Ask what you must attend live.

What hours does 37signals work?

The directory names a standard 40-hour week, reduced to 32 hours in summer. The official jobs page says 8-hour days and 40-hour weeks are what the company expects. Confirm summer hours and support-shift load with the hiring team.

What PTO does 37signals offer?

The directory snapshot lists 20 vacation days plus 11 local holidays (vacation rolls over up to 27 days) and a paid sabbatical of 6 weeks every three years, plus the medical, dental, vision, life, disability, and 401(k) match notes above. Ask peers how much time they actually took and whether they stayed on chat.

How is this different from 37signals' own jobs page?

37signals' page lists roles when they exist, plus the company's story and a link to the handbook. This page scores calm-company signals from the live directory profile and tells you how to apply without pretending we run 37signals hiring. Use both. Apply there. Decide here.

If you want more employers that document a week the way 37signals does, browse the Calm Companies directory and join the newsletter for a weekly digest of openings from calmer teams.