Engineering Manager (Hands-On)

Your New Role

We are looking to hire a hands-on engineering manager who will be responsible for line management of a group of around 5 engineers at different levels, as well as writing code.

As an Engineering Manager and part of the engineering team at Overleaf, you will be helping to make Overleaf the go-to place for scientific writing by both inspiring your engineers to do their best work, and making your own contributions directly to the platform.

As a manager you will:

• Hold regular 1:1s with your engineers
• Be responsible for their career progression and development
• Provide coaching and point them at relevant training when needed
• Advocate for them during planning to ensure they get assigned to the right projects
• Provide constructive feedback and manage performance issues where necessary
• Input into the decision-making process when choosing which projects and features to work on
• Sit on hiring panels

As a member of the engineering team you will:

• Write application code, primarily in JavaScript
• Review pull requests from other engineers
• Take on a tech-lead role for individual projects and features, when appropriate

Key projects on our road map this year include:

• Consolidate our two project history systems — we currently have two from our integration with ShareLaTeX in 2017, each with hundreds of TB to be consolidated
• Make our project PDF preview faster and less bandwidth-hungry — we have prototypes showing big wins that now need getting ready for production

In the longer term, we are planning projects around improved collaboration features for teams, improvements to our rich text mode to help non-LaTeX users, and more.

Our Tech

Overleaf is based on open-source software, and most of our product code is itself open source. You can find it on GitHub: https://github.com/overleaf/overleaf

We run a mainly Node.js back end using MongoDB, PostgreSQL and Redis. We use a microservices architecture, with about a dozen services. On the front end, we mainly use React.

We're hosted on Google Cloud Platform using Google Kubernetes Engine. We use Docker to manage our development environments. We support continuous delivery and typically deploy at least a few times a day.

How We Work

Overleaf is remote-first — all staff work remotely and this is part of our values. We also have an office space in London for those that want to use it, and when the pandemic settles down we'll again get the whole team together in London a few times a year for face-to-face time.

Our core hours for meetings are 2pm–5pm UK time; we try to schedule all team meetings during this time, including daily 10–15 minute standup calls and biweekly company update calls. We try to keep meetings to a minimum for developers.

We always collect user feedback to inform our work. We have UX professionals on our team, and we run many surveys and user interviews. Our engineers work closely with the product team in product trios (PM, engineer, UX) during both discovery and delivery of new features.

Our development process is based on the “Shape Up” model, using 6-week delivery cycles and a 2-week cooldown between them. In each cycle, we have multiple delivery tracks, each with its own tech lead. Engineers move between delivery teams each cycle.

We use GitHub pull requests for each feature with code review to share knowledge and best practices. We test thoroughly with automated unit and acceptance tests, supported by continuous integration (CI). We're also fans of linting to minimise bike-shedding.

How We Hire

The stages in our hiring process are typically:

1. We will aim to update you on the status of your application within 14 days from when we receive it.
2. We'll follow up by email with any questions we have about your application, usually around logistics, your ambitions and your expectations about the role.
3. We’ll schedule a 30-minute call for an initial discussion to discuss the role and your experience, to see if they look like a good fit.
4. We'll schedule a more in-depth interview, which is typically two hours long. The first hour is discussion, and the second hour is technical. For the technical, you'll have the option of either completing a homework assignment, which requires about one hour of your time before the interview, or solving a problem in the interview, if you prefer. The problems are practical in nature (no fizz-buzz or reversing linked lists), and you can use Google, man pages, etc., and ask us questions.
5. We'll make an offer. We usually interview in batches, so there may be a short delay while we interview other candidates, but we will try to keep you informed throughout the process.

If you have a deadline, please let us know in your application, and we will try to be accommodating.

We require that you:

• Have at least a year’s experience with line-managing engineers
• Have 2–3 years of experience working as a senior engineer on a SaaS-like product.
• Will work for us full time (or nearly full time)
• Are based in the US, Canada, the UK or Europe
• Will usually be available in our core hours, 2pm–5pm UK time

Experience with the technologies we use helps, but you don't need to know them all; your ability to learn is much more important to us.

• Remote and flexible working.
• Salary £70k–£85k per year depending on experience.
• You would join a small, dedicated and growing team.
• We're substantially (around 80%) open-source, so your work will often be on open source code.
• We're backed by Bethnal Green Ventures (https://bethnalgreenventures.com/) and Digital Science (https://www.digital-science.com/), through which we're part of a wider community of startups in science, health and ed-tech.
• Our London office is shared with several other Digital Science companies, so there are lots of interesting people to meet, and clubs and sports activities outside of work.
• We get everyone together in London for team meetings several times a year for valuable face-to-face time (pandemic permitting).
• We’ll provide a new Mac, PC or Linux laptop, along with a stipend for other equipment.
• We provide a training budget; many of our developers choose to attend relevant industry conferences or buy training materials.
• We run regular remote hackathons to keep learning and experimenting.
• We run a weekly internal seminar series with short talks from staff about their work or personal projects, new technologies and techniques.

How to Apply

Please apply here: https://apply.workable.com/overleaf/j/5BE7E0FE2F/