by Rat Race Rebellion October 17, 2026
Hiring processes vary significantly from one employer to the next, but it’s rare for an employer to publicly document its process in enough detail that a candidate can know what to expect before applying. A few remote-first companies do – publishing the stages, questions, grading guidance, response-time commitments, and more. When a company publishes that level of detail, you learn two useful things: what will actually happen if your application advances, and what the employer considers important enough to commit to in public.
Five remote-first companies with publicly documented hiring processes are below. Each takes a genuinely different approach, and publishes enough detail on its own careers pages or handbook that a candidate can know what to expect before investing time in an application. The specifics come directly from the company’s own materials, with source links so you can verify any detail that matters to you.
Quick note on sourcing: Where possible, claims below are cited to each company’s own public documentation. In a few places, third-party candidate reports supplement the official materials – those are noted explicitly. Confirm current practice on the specific role you’re applying to; hiring processes evolve.
Doist – Pay Transparency Starts at the First Interview
Doist is the fully distributed company behind Todoist and Twist. Its careers page describes what it calls a “transparent application process” in five documented stages.
Stage 1 – Application. Candidates fill out an online application that includes longer-form questions. Doist explicitly commits to reviewing and responding to every candidate’s application. The application is designed to replace, not supplement, a traditional résumé.
Stage 2 – First interview, salary, and task assignment. If the application moves forward, Doist schedules a first interview via Google Meet. Here’s the differentiator: at the same time Doist shares the proposed salary range for the role, calculated through its “formula-based compensation model”, which benchmarks salaries to industry data and adjusts for location. The point is to let candidates decide early on whether it’s a fit, rather than invest multiple rounds before learning what the role pays. The stage may also include a task assignment depending on the role.
Stage 3 – References and background check. Doist runs both before an offer, with explicit notification before each step begins.
Stage 4 – Decision. The hiring committee makes the final call – not a single hiring manager. Doist’s careers page states: “We never leave candidates hanging.” Either outcome gets a response.
Stage 5 – Onboarding. Hired candidates receive access to a Todoist project mapping out onboarding, get paired with a mentor, and get the chance to co-work in person with that mentor for a week, wherever they’re based.
What this tells you about Doist: The upfront salary transparency and committee-based decision model suggest Doist has invested in reducing the asymmetry of information between the company and the candidate. The in-person mentor co-work during onboarding is unusual for a fully distributed company and signals a specific investment in connection beyond the screen.
GitLab – The Entire Hiring Process Lives in a Public Handbook
GitLab is the all-remote DevOps software company that operates one of the most publicly transparent hiring systems of any sizable employer. Its Candidate Handbook and internal hiring handbook are both published to its 2,000+ page public company handbook, which means candidates can read the actual process – including example questions, interviewer guidance, and the evaluation criteria the company publicly documents, before they apply.
Published stages. The handbook describes seven stages: Application Process, Screening Call, Assessment (role-dependent), Technical Interview (role-dependent), Team Interviews, References & TMRG Connection, and Offer & Background Screening.
Screening call specifics. GitLab’s handbook describes the screening call as a 30-to-40-minute conversation with a recruiter and publishes example questions candidates can expect: why GitLab, what the candidate wants next, context on their last three positions, STAR questions, location and relocation plans, visa status, notice period, and whether the salary range fits. Candidates can prepare directly against the published question categories.
Technical interview format. For engineering roles, the technical interview often involves a merge-request review – a format that mirrors how work actually happens at GitLab. GitLab’s handbook explicitly tells candidates to read its technical interview and code review guidelines before the interview, because the interview is graded against them.
Scorecards. GitLab’s talent acquisition framework requires interviewers to complete scorecards at every interview stage. The scorecards aren’t candidate-facing, but their existence (and the handbook’s documentation of what they measure) means the evaluation isn’t ad hoc.
What this tells you about GitLab: The handbook-first approach to hiring mirrors how GitLab operates generally – written documentation as the source of truth, async communication, async decision-making. If you prepare by reading GitLab’s handbook pages on hiring, you’re already demonstrating the kind of self-directed, documentation-first approach the company values.
Automattic – The Paid Trial Project
Automattic is the parent of WordPress.com, Tumblr, and other distributed products. Its hiring process is organized around a paid trial project that Automattic’s materials describe as a hands-on assessment for applicable positions – meaning candidates who advance past initial screens typically do real, paid work before an offer decision is made.
Trial length and pay. Automattic’s developer hiring page describes the trial as 2 to 8 weeks, totaling around 15-35 hours of work. Automattic’s own materials have described a flat trial rate for all trial projects, cited at $25/hr in recent public pages, with no relation to future salary. Candidates should confirm the current rate and whether a trial applies to their specific role directly with recruiting.
Engineering trials. Code tests involve modifying real code – frequently WordPress plugins. Candidates work with an assigned buddy who reviews work and answers questions during the trial. The trial itself is designed to simulate working at Automattic rather than just assess coding skill.
Design trials. Design trials happen on P2 (Automattic’s internal blogging system) and Slack, with an assigned designer-buddy. As of March 2026, Automattic’s design practice formally requires demonstrated AI and augmented-design experience; candidates with none are not advanced.
Final decision. After the trial, the hiring team submits a recommendation – including the candidate’s profile, feedback, and work summary, to the CEO (or acting CEO) for final approval. Automattic’s own materials note this review can take anywhere from a few days to a month.
What this tells you about Automattic: The paid-trial model has real trade-offs. The time commitment is substantial – potentially several weeks of part-time work on top of a current job or job search, which can be a meaningful burden for candidates with limited bandwidth. On the other hand, candidates are paid for their time from the first real task, and every hire has demonstrated real work alongside Automatticians before an offer. Both the burden and the paid-from-day-one framing are worth factoring into whether this process fits your situation.
Buffer – Values-First Screening and a Written Application
Buffer is the fully remote social media management company. Its publicly documented hiring philosophy emphasizes values-fit screening earlier and more prominently than most employers. The specifics of individual stages below come from a mix of Buffer’s own posts (some dated) and 2026 candidate reports, so treat Buffer’s values-first approach as the firmer claim and the stage details as directional.
Documented hiring philosophy. Buffer’s own values-interview post and How We Hire post describe conducting values screens for open roles, specifically to assess alignment with Buffer’s documented company values before investing in role-specific interviews. The company publicly describes culture-first screening as a core part of its hiring design.
Reported application format (candidate reports). Candidate reports on Glassdoor and InterviewPrep describe Buffer applications that have included essay-style questions and a short video introduction rather than a traditional résumé. These are candidate-reported details, not current Buffer documentation.
Reported interview flow (candidate reports and dated Buffer posts). Candidate reports and Buffer’s own earlier posts describe values screening followed by role/team interviews, an optional technical screen for technical roles, and a final interview with an executive team member – 4-5 rounds total with intentionally diverse interviewers.
Timeline variance. Interview timelines can differ significantly by role. Ask Buffer recruiting about the expected stages and timing for the position you’re considering.
What this tells you about Buffer: Values-first screening – before role fit – is unusual, and it signals that Buffer treats cultural alignment as the primary qualifier rather than a secondary check. The reported emphasis on written responses also suggests that written communication skills may play an important role in how candidates are evaluated, which would map to how work gets communicated in a fully distributed company.
Zapier -A Hiring Process Designed Around Candidate Experience
Zapier is the workflow automation company, remote-first since 2011. It publicly documents nine distinct stages and several candidate-respecting commitments that most employers don’t make publicly.
No résumé. Zapier’s application is short and focused, and it doesn’t ask for a résumé upload. Candidates respond to role-specific questions instead.
Guaranteed response within 7 days. Zapier commits publicly that a recruiter will reach out within seven days of application review – even if the candidate isn’t moving forward. In an industry where ghosting is common, this is a notable commitment.
The published stages. Application → Application review → Recruiter interview → Hiring manager interview → Skills assessment and interview (take-home assignment plus Zoom interview with hiring team, often including cross-functional interviews and future direct reports) → Final interview with an executive leader → Final decision → References and background check → Offer.
No surprise employer contact. Zapier explicitly commits not to contact a candidate’s current employer without consent. For references, it uses HiPeople; for background checks, it uses Certn. Both are named directly in Zapier’s own documentation.
Timing (third-party, not Zapier-official). Candidate reports suggest the full process typically runs 4-6 weeks from application to offer; software engineering roles have been reported at 3-5 weeks.
What this tells you about Zapier: The combination of no-résumé application, guaranteed response timing, and explicit protection of a candidate’s current employment is a hiring process designed around how the candidate experiences it – not just how it serves the company. That design philosophy is consistent with how Zapier operates generally: asynchronous, trust-based, structured.
What a Documented Hiring Process Actually Signals
The five companies above have one obvious thing in common – they publish detailed information about how they hire. That’s not just a convenience for candidates. It’s a signal about the companies themselves.
An employer willing to put its hiring stages, question categories, grading rubrics, timelines, and candidate commitments in public writing – is an employer that expects to be held accountable for them. Publishing a hiring process doesn’t guarantee a good candidate experience. But it gives applicants something concrete to evaluate, and a standard against which to compare what actually happens.
The specifics also tell you what each company values. GitLab’s handbook-first approach signals written documentation as the way work happens there. Automattic’s paid trial signals that candidates are treated as workers from the start. Doist’s upfront salary transparency signals a commitment to reducing asymmetric information between company and candidate. Buffer’s values-first screening signals that cultural alignment is a precondition for role evaluation, not an afterthought. Zapier’s candidate-experience design signals that the company has thought carefully about how it treats people from the first email forward.
None of this guarantees any of these companies is a good fit for any particular candidate. But reading each process before applying tells you what you’re signing up for, and gives you something concrete to compare against your own experience during the process.
Final Take
“The hiring process” isn’t a single thing. At the companies above, it ranges from a 5-step documented sequence with upfront salary disclosure (Doist) to a 7-stage handbook-published process with public evaluation guidance (GitLab) and a paid 2-8 week trial project (Automattic). Each represents a genuinely different philosophy about what hiring is for and how candidates should be treated through it.
If you’re applying to a remote-first company, the question worth asking before you submit anything is: what does this employer publicly say about how they hire? If the answer is a detailed, specific process you can read on the company’s own site, you’ve already learned something useful about the company.
And if the company doesn’t publish its process? Ask. How many interview rounds should you expect? Will there be an assessment? Who makes the final decision? When should you expect to hear back? A company doesn’t need a public handbook to answer those questions, but candidates shouldn’t have to navigate the process without answers.