The pandemic forced many organizations to transition to be all-remote companies. Many realized the benefits and decided to keep the remote structure. This shift necessitates implementing a remote hiring process to grow a remote workforce.
As one of the world's largest all-remote companies, GitLab has been hiring and onboarding remote workers, remotely for over a decade. We've detailed what we learned in the Principles of Hiring section of our Handbook. On this page, we're sharing best practices for a streamlined remote hiring process anyone can implement.
One advantage of being an all-remote company is the ability to hire talent from a global pool, giving access to a tremendous amount of talent that many other companies overlook.
It can be a struggle for organizations to find, recruit, retain, and compensate employees in competitive markets, including most major cities. Imagine the influx of highly qualified applicants if the location requirement were removed from all job descriptions. For a glimpse at what this looks like, please visit GitLab's Jobs page.
In addition to giving your organization a competitive edge, here are some other advantages:
All-remote hiring widens the talent pool and allows you to hire from any countries where you have legal status. This can greatly improve your company's cultural diversity. Diversity, Inclusion & Belonging (DIB) has been fundamental to GitLab's success, and we strongly encourage prioritizing DIB in hiring practices.
GitLab strives to hire team members who are passionate, empathetic, kind, tenacious, and ambitious, regardless of their location. By opening the talent acquisition funnel to as broad a swath of the world as we can, we create a more inclusive hiring environment, lean on tight collaboration to drive progress across time zones, and focus our hiring decisions on results rather than location.
Because you don't have to organize travel or schedule around multiple calendars, remote testing and meeting speeds up the applicant search, narrowing, and interview process. You can asynchronously circulate recorded interviews and solicit feedback from team members unable to attend the interview.
Cutting travel cuts considerable costs, making remote testing and interviewing highly cost-effective. I can also be less disruptive to end the process with candidates who are not a good fit at any point, without the guilt of wasting the candidate's or the company's time or money.
Hiring an all-remote team from across the globe allows GitLab to pay local rates, which you can learn more about on the company blog. By hiring brilliant minds in locations with lower costs of living, GitLab is able to save money to hire even more people as we scale our business.
Remote interviews for remote jobs enable you to gauge a person's ability to communicate and interact onscreen, providing insight into how they will handle the virtual communication required in a remote role.
Supporting remote work is different than allowing it. Before hiring for a remote role, ensure that it is set up to be successful. Prepare management with training on how to be a great remote manager.
Prepare a well-designed remote interview process to ensure that you'll hire the right person and that they'll be prepared with accurate expectations.
We've published our hiring process, including example screening questions, in our handbook.
While this may be unique, we see it as simply staying true to our transparency value. The process shouldn't be a mystery.
Letting candidates know what to expect allows them to focus on whether the role and the company are right for them, while we evaluate that too.
In this GitLab Unfiltered video, GitLab's Head of Remote speaks with Remotefit co-founder Javier on building and sustaining culture while being open about processes in the talent acquisition and hiring process.
To be transparent, we showcase our culture to prospective hires in advance. For example, there's a section of our Jobs FAQ called "What's it like to work at GitLab?"
You cannot expect to hire people who are passionate about executing your strategy if you wait to share the plan after they are onboard. Some candidates may opt out of the interview funnel if they realize they aren't a good fit for the company's mission, vision, and values.
It's silly to think that a company would withhold its strategy, culture, or workflows until after someone gets hired. These elements determine whether a team member will thrive. Why would you hold that back? — Darren Murph, Head of Remote at GitLab
In this GitLab Unfiltered video, GitLab co-founder / CEO Sid Sijbrandij discusses hiring (amongst other topics) with researchers from INSEAD.
"A company might claim, 'Our strategy is very important, and you need to be aligned to it! We'll only tell you after you join.'
I think that's bananas. That's what every company in the world does. If your strategy is really important, make sure people buy in before they join. And make sure that people who don't buy in don't join the company.
Execution depends on people; being public about what we do. allows us to attract the best people to best execute our strategy." — GitLab co-founder and CEO Sid Sijbrandij
Remote work is the last great competitive advantage for employers. Remote maximizes a person's freedom and autonomy to integrate work into their life instead of the other way around. If two employers offer a talented applicant the same title, salary, and benefits, the tipping point will be the employer that supports remote work.
We've gathered extra ways to attract top talent to your organization (Note: this list assumes a workplace supports remote and permission to play behaviors.)
Not everyone is suited for remote work. There can be many reasons why a remote job isn't right for an individual, based on their career stage, their working preferences, or what they hope to get out of their next role.
However, there are plenty of people who thrive in remote jobs (as GitLab's global team can attest). In our 10+ years of remote hiring, here are the qualities we've learned to seek out.
There are nuances to loving remote work and being a great remote worker. An operating principle at GitLab calls it being a "manager of one".
GitLab is an asynchronous company. Much of what we do is communicated through text. People with lengthy in-office careers, who default to verbal communication, may be uncomfortable communicating via text at first.
How do you screen for text-communication skills? Whether they realize it or not, most people have worked remotely. If your company has multiple locations, there's a good chance you worked with people outside of your office.
If someone has not worked in a remote environment, chances are that they have worked outside of their office (e.g., working while traveling, advancing a university project while away from campus, etc.) Ask candidates for examples of how they managed those instances, looking specifically for how they embrace autonomy and blameless problem solving.
Even if your company didn't define it this way, those offices were remote to one another. You had to navigate Zoom calls, time zone differences, etc. For example, you may be based in Seattle with colleagues in Singapore and London. Asking applicants to dive into those situations will help uncover how they handle remote work.
Look for ways candidates align with company values. Share them in advance and ask the candidates to explain which values resonate with them and why.
Having prior experience working remotely is appreciated, but even more are attributes like timeliness, dependability, respect, a heart for collaboration, perseverance, empathy, kindness, and ambition.
Self-awareness and agile thinking are required to thrive in an all-remote setting. One way to screen for this is to test a candidate's ability to perform thinking writing, as described in this Hacker News thread. Thinking writing is the ability to draft ideas, then read them, modify them, change their order, remove some, refine/add others, and share with everyone through a low level of shame.
Other qualities unique to a remote workplace are:
When asked if anyone could learn to work well in an all-remote setting during an INSEAD case study interview, GitLab co-founder and CEO Sid Sijbrandij replied:
"What's essential in all-remote is that you are a manager of one.
You're not going to have someone expecting you at the office and hold your hand, so you have to be able to manage yourself and work independently.
It is critical that you can write well — be concise and precise in your written communication- to bridge time zones and leverage asynchronous communication".— GitLab co-founder & CEO Sid Sijbrandij
We’ve created a guide on How to Conduct a Remote Interview, and included some highlights below.
The full list of questions to ask a remote candidate is here, but these are the most insightful:
Candidates need to be comfortable with video calls since they are a primary medium for communication in a remote role. At GitLab, we use Zoom to connect with candidates via video calls.
This GitLab Unfiltered video demonstrates how to conduct a remote interview process.
For more, watch Shane Bouchard, UX Manager, and Jeremy Watson, Senior Product Manager, discuss interviewing and finding great designers. — This approach reinforces several of GitLab's values.
When hiring in an all-remote organization, it is critical to onboard new team members well. You have to give new hires the information they need to do their jobs, and you have to empower them to think remotely. Remote onboarding relies heavily on documentation, anticipating the needs of new team members, and a dedication to continuously improving the process based on feedback.
Onboarding is a continuous process during a team member's first year. Investing upfront in your onboarding process will yield long-term benefits:
Companies that invest in onboarding report 54% more productivity from new hires. Studies show that 87% of team members are less likely to leave a company when they feel engaged.
Companies that invest in onboarding report 54% more productivity from new hires. Studies show that 87% of team members are less likely to leave a company when they feel engaged.
We are so convinced in the power of onboarding well that we've created a Complete Guide to Remote Onboarding for New Hires. To help new hires focus on three key onboarding dimensions–organizational, technical, and social–we assign a mentor or onboarding buddy.
To help prevent New Job Anxiety and aid onboarding and the adjustment to an all-remote culture, new team members are assigned an onboarding buddy.
A mentor or onboarding buddy is a friendly point of contact for a new team member. This individual sets the example for building relationships and models how to communicate in a variety of ways, such as video calls, check-ins on Slack, and coffee chats.
Knowing that remote workers can experience loneliness or burnout, it's important to prioritize relationship-building through regular social interactions. Remote workers can socialize using informal communication.
Model good informal communication practices with new hires by scheduling regular check-ins throughout their first few months. These can be a blend of formal and informal meetings used to gauge how they are progressing in their onboarding and to ensure they are acclimating to the work, team, company, and culture.
GitLab hires globally because we envision a world where talented, driven individuals seek employment and find roles based on business needs rather than geographic location. In our 10+ years of global hiring, we have significantly developed our best practices. Here are a few things to keep in mind; please see the hiring section of our handbook for more in-depth coverage.
GitLab is often asked about which countries we hire in, and why. The simplest answer is that we continually strive to have the widest possible global hiring coverage, limited only by logistics and legality.
Each country has unique and complex rules, laws and regulations, which can affect how we conduct business, as well as the employability of the citizens in those countries. For companies that are just beginning to work remotely and seek to expand globally, the process of setting up entities in compliance with each country's requirements is a lengthy one.
We are growing rapidly and continuously expanding our hiring capabilities in other geographies. In countries listed in our entity_mapper.yml file that don't have contractor: true, we have a payroll and can employ people directly. In all other listed countries, we can hire people as a contractor.
Learn more at our Country Hiring Guidelines section in the Employment Solutions (International Expansion & Relocations) handbook page.
Rather than attempting to incorporate in every country where an all-remote company has even a single employee, organizations must weigh the benefits of creating a legal entity with other options. There are four means of engagement with GitLab. These are commonly used arrangements that can be considered by other all-remote companies.
Learn more about employee types and hiring partners across countries in the Contracts, Probation Periods & PIAA handbook page.
It is not always practical to understand the nuances of local regulations in-house. Wherever GitLab has an entity or contractor, we have external counsel to advise and ensure that we are compliant.
In countries where GitLab utilizes a professional employer organization (PEO), counsel within the PEO advises us to ensure hiring compliance.
Generally speaking, it becomes feasible to consider creating an entity within a country once a company reaches 20+ team members in that country. While total costs vary significantly from country to country, creating an entity within a country can cost as little as a few hundred dollars to tens of thousands of dollars.
A company must also hire skilled team members to oversee compliance with local taxes, laws, benefits, etc. in each country where there is an entity.
For countries where a company is not already incorporated or has a local entity, consider the below as a guide.
Beyond the administrative challenges associated with using various vehicles (entities, PEOs, contractors, etc.) to hire team members, companies should be proactive in recognizing how this will impact culture and morale.
While GitLab believes that there are far more pros than cons to hiring globally — creating a geographically diverse team, finding the world's best talent, hiring in underserved areas and connecting with people from diverse socioeconomic backgrounds — it's wise to evaluate how nonuniform hiring mechanisms may conflict with a company's values.
When leveraging a third-party to hire, it is difficult to ensure that they will treat your employees how you would ideally like to see them treated. Third-party companies are under no obligation to understand or implement your values.
It is imperative that the hiring team communicate this in advance, ideally during the interview phase, to manage expectations of employees who are hired by a third-party firm that may not always act in accordance to your values.
Moreover, one should aim to leverage a single Professional Employer Organization (PEO) over the long term. Switching PEOs is disruptive to team members and creates mental and administrative burden. A growing company should pay particular attention to feedback from employees who rely on PEOs, and plan beyond current hiring needs.
This is a common question from remote-first and all-remote companies who are understandably interested in streamlining the process of hiring talented team members from an array of countries. The short answer, for now, is "no."
Some PEOs serve an array of regions, but offer varying levels of service and disparate experiences from country to country. Seek out advice where possible to gather country-level feedback.
Remote is a new company that intends to tackle this challenge over time.
Remote is working on solving global employment by allowing companies to employ people locally through Remote. That is, full employment local to each and every employee, but a single invoice for the employer. Remote manages payroll, benefits, and compliance, according to the standards of the employer.
Be intentional about due diligence when vetting PEOs. Some firms advertise global reach, but do not offer high-touch, reliable end-to-end service in every country. Instead, they leverage third-parties themselves in various countries, creating yet another layer in the process that may negatively impact employee experience.
Even when the world is your talent pool, there will be niche roles requiring a specialized applicant search. To that end, GitLab built a Sourcing team tasked with finding the best talent and nurturing the candidate pipeline — a strategy any company can implement.
While GitLab is location-agnostic, we ensure that we have local Sourcers based in every macro-region (e.g., Americas, APAC, and EMEA) poised to share their market expertise and leverage our presence in these territories.
Our sourcing effort is extremely important for bringing diverse talent onboard. Our Sourcers regularly network with recruiters and business verticals so they can quickly tap into real-time knowledge of specific markets when a niche position comes available.
Driven by our Collaboration value, we organize source-a-thons, which become a place for everyone to share market insights and contribute to hiring. These sessions are extremely productive as they help Sourcers better partner with their hiring managers and calibrate expectations. You can learn more about how GitLab's Sourcing team operates here.
GitLab believes that all-remote is the future of work, and remote companies have a shared responsibility to show the way for other organizations who are embracing it. If you or your company has an experience that would benefit the greater world, consider creating a merge request and adding a contribution to this page.
Return to the main all-remote page.
