What GitBook does

GitBook builds a modern documentation platform that helps teams create, maintain, and publish beautiful technical docs. If you’ve ever read well-organised API documentation or an internal knowledge base that actually made sense, there’s a good chance GitBook powered it.

Founded in Lyon, France, GitBook helps development teams turn scattered knowledge into structured, searchable documentation. The platform integrates with GitHub and GitLab, supports Markdown, and makes it easy to publish docs that stay current. They serve thousands of teams including companies like Snyk, Personio, and many open-source projects.

At 37 people across 13 countries, GitBook is by far the smallest company in this guide – and that’s precisely what makes them interesting.

Remote culture: what it’s actually like

GitBook is a masterclass in how a small distributed team can punch well above its weight. Their approach is refreshingly different from the typical tech startup playbook.

The most distinctive cultural feature: no product managers. Engineers own the product. They talk to users directly, make product decisions, and ship. If you’re an engineer who’s tired of being handed specs and told what to build, this is the kind of setup that might change your relationship with work.

With 37 people across 13 countries, every person matters. There’s no bureaucracy, because at this scale, bureaucracy is physically impossible. You either contribute meaningfully or the gap is obvious. The autonomy is genuine – and so is the accountability.

The sustainable pace is notable. No VC-fuelled growth pressure, no “scale at all costs” mentality. GitBook builds deliberately, and the team culture reflects that restraint.

The honest assessment: working at a 37-person distributed company is fundamentally different from working at a 1,800-person one. The intimacy is real – you’ll know everyone and everyone will know your work. But so is the exposure. There’s nowhere to hide, limited role specialisation, and if a project needs doing, you’ll likely be doing it regardless of your job title. This is ideal for generalists and people who want maximum impact. It’s less ideal for specialists who want to go deep in a narrow domain.

Hiring in Europe: the details

Countries: Across 13 countries, primarily European. GitBook actively prioritises European candidates – this is an EU-first hiring approach that’s rare in a market dominated by US-centric companies. For European job seekers, this is a genuine structural advantage.

Employment model: Direct hire. At this scale, GitBook maintains direct relationships with employees across their operating countries.

Timezone expectations: European timezone alignment is expected given the Lyon-based founding and EU-first team distribution. This is a feature, not a limitation, for European candidates – you’re in the preferred timezone.

Salary approach: Competitive for the stage and size. GitBook can’t match the packages of billion-dollar companies, but the sustainability, EU-first positioning, and quality of the work environment are part of the compensation proposition.

Language requirements: English is the working language.

Who they’re looking for

With 37 people, GitBook hires rarely – but when they do, it’s typically:

  • Software engineering (TypeScript, React, Node.js)
  • Design
  • Customer-facing roles
  • Marketing and content

Every hire has an outsized impact. They’re not looking for people who need extensive onboarding or hand-holding. They want self-starters who can pick things up quickly and contribute meaningfully from the first week.

What current and former employees say

Employees describe GitBook as a place where you have genuine ownership over your work, where the team is tight-knit, and where the EU-first approach creates a work culture that feels distinctly European rather than a European satellite of a US company.

The challenges are inherent to the scale: limited career ladder, broad responsibilities, and the intensity of being one of 37 people responsible for a product used by thousands of engineering teams. When things go wrong, there’s no large team to absorb the impact. When things go right, the satisfaction of your individual contribution is tangible.

People who thrive at GitBook are European developers and generalists who value ownership over hierarchy, want to work on a product they can see the full shape of, and prefer a small team where their work visibly matters.

How to apply

Specific tips: Use the product. Create documentation for a personal or open-source project using GitBook – understanding the platform from a user’s perspective is the strongest signal you can send. Engage with the team on Twitter/X and in developer communities – in a company this small, being noticed is much easier than at a 4,000-person organisation. Roles don’t open often, but when they do, competition is manageable because most candidates have never heard of GitBook.

See our full guide to Remote-First Companies That Actually Hire in Europe.