HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
basecamp
handbook
Learning & Reference2017–2024
basecamp / handbook

handbook

37signals Employee Handbook

34Distinct people
36Mentions
1Explicit recommenders
6.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

37signals Employee Handbook

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

There are more than a few stories of things like this happening (or my favorite, outsourcing the actual dev work to China or india) but why would you when it's a lawsuit…

ShakataGaNai used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 11:34:28 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year36 dated mentions

Observed mentions: 2017-05-02 14:46:05 UTC to 2024-01-19 18:32:11 UTC.

0510152017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 15 mentions; 4 submissions, 11 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC15411
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC615
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC312
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC413
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC211
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC505

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Read on basecamp.com 37signals Employee Handbook In this handbook, you’ll find everything you need to know about 37signals policies and benefits. Hopefully it also offers a small peek at our culture. If you’re new to the company, welcome! It’s important that you review everything in this handbook, so you know what’s expected of you and what you can expect from us. Please note that this handbook may be updated at any time, and it’s up to you to keep abreast of those updates – though we’ll do our best to notify all staff of major changes. GitHub repo is a great way to follow along with changes. Please reach out to the People Ops team or to your manager if you have any questions about the information contained in this handbook. Sections Getting Started Benefits & Perks How We Work Making a Career Our Rituals Managing Work Devices Our Internal Systems A Note About Moonlighting State Leave Provisions Severance Packages Titles for Designers Titles for Ops Titles for Programmers Titles for QA Titles for Support
Read the full README on GitHub

What Hacker News says

6 sources
I work at Basecamp. From our handbook [1]: "Basecamp pays at the top 10% for our industry at San Francisco salary levels, regardless of where an employee lives. The comparison data is provided by a company called Radford that polls compensation data from all the major companies in our industry and plenty of our smaller peers as well. Because we don't pay bonuses, we match our base compensation to the base + bonus of our peer group." [1]: https://github.com/basecamp/handbook/blob/master/making-a-ca...
In How to run a calm workplace: review of Basecamp's book
Basecamp appears to be successfully managing this. If you look at their "About Us"[1] page, you see a lot of people who've been there for quite a while. Their solution appears to be: 1. Pay a lot of money: "Our target is to pay everyone at the company in the 95th percentile, or top 5%, of the market, regardless of their role."[2] Previously that was benchmarked to Chicago prices; as of late 2017, that's benchmarked to San Francisco prices.[3] 2. Offer an excellent benefits package that actually benefits people (i.e. isn't just an unused ping-pong table/game console and the promise of "great culture!").[4] Something specifically noticeable is that they offer the kind of benefits that maybe aren't big selling points when you're younger, but that become increasingly enticing as you get older, and especially if you have kids - a fantastic par
Read the rest
ental leave policy, good retirement policy, short summer weeks. 3. Respect your employees and treat them like adults. Harder to quantify, but if you click around their handbook[5], you see a lot of things that boil down to "We trust you to do the right thing, even in a very independent setting. We won't be looking over your shoulder constantly." I think that's a really scary idea for some people, and a really attractive proposition for others. If you find people who are in that latter group in your hiring process, I suspect it makes it easier to keep them around when most other jobs are not going to involve that level of trust. The idea of "interesting work keeps good people" - I dunno about that. It's hard to say what's interesting work. It's easy to say "adding new endpoints to a CRUD app" is not interesting, but for some people it might be, or at least it might be "sufficiently interesting" to make a career of it. I have friends in FinTech for whom tracking the market actually brings them joy, and I'm happy for them, but when I try to watch their screen while they tell me about what they're doing, my eyes start to glaze over. I don't know if what Basecamp does counts as "interesting work" for most people, but it seems like it's interesting enough, and the other parts of the company are good enough, for a lot of people to want to stay there for quite some time. [1]: https://basecamp.com/about/team [2]: https://m.signalvnoise.com/how-we-pay-people-at-basecamp-f1d... [3]: https://m.signalvnoise.com/basecamp-doesnt-employ-anyone-in-... [4]: https://github.com/basecamp/handbook/blob/master/benefits-an... [5]: https://github.com/basecamp/handbook
In Mistakes to avoid when asking for a raise

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.