🙋 What will you be doing ?

Growing and supporting the careers of your direct reports
Establishing measurable goals, both at the team and individual level
Collaborating and creating alignment between engineering and other functions‌
Identifying gaps where additional staff are needed, hiring engineers and iterating on our hiring process
Ensuring quality within engineering by striving for continuous improvement and making success measurable
Designing and managing processes to support the success of a global remote team

🙌 You will be valued for

Ability to understand, evaluate, and support the work of your direct reports
Proficiency translating strategy and large initiatives into actionable work for your team
Ability to empower your team through delegation, enabling team success and individual growth
Experience managing remote or distributed teams
Desire to work in the open, share context, and communicate honestly, directly and proactively
A product-oriented mindset: the desire to deliver value to our users

🛠 How we work

Engineering defines success as our ability to rapidly and continuously deliver a high volume of meaningful value to users.
We are an async, distributed organization that focuses on end-to-end participation in the crafting and delivering of value as part of a larger Product Delivery team that includes Product, Design, and Support.
Work is managed through 2 week cycles based on an experiment using Kanban methodologies and a reliance on managing flow rather than the people. Retros and kickoffs are done async.
The culture is based on working agreements, experiments, and core organization values: lead through ownership, deliver value continuously, operate in the open, bias to document, keep it simple, and be rigorous.
Experimentation is core to engineering at GitBook and owned at every level. It extends to processes, technical work, culture, communication, and more. These experiments are created, documented, owned, and agreed to by the team.

​​✨ What’s next ?

First, we will take the time to review your application and we will get back to you within a week, regardless of our decision.

Here’s what our process looks like:

1. Discovery call with our Head of Engineering, to ensure there is a correlation between GitBook’s expectations, the role and your own expectations. [30 minutes]
2. A structured “career story” interview with two future teammates, where we will walk through your career and learn more about your journey. [60 minutes]
3. A technical interview with two members of our engineering team, where we will explore examples from your prior work and role play some tech-focused scenarios.[45 minutes]
4. Cross-team interview with Product and Support to discuss how you work and communicate across functions [45 minutes]
5. A written “take-home” exercise where we will ask you to present your thoughts and suggestions on issues we’ve faced at GitBook. You will have the opportunity to do discovery by communicating with the team through Slack and short one-off calls. [~4 hours of work, to be returned within one week, and with compensation].
6. The last discussion will be an opportunity to meet with Samy (co-founder) to learn more about GitBook history, ambition and culture, followed by a conversation with Patrick (Head of Engineering) to answer any remaining questions and gain alignment. [60 minutes total/30 minutes each]