Overleaf

Jobs posted: 3

Headquarters: London, UK

Overleaf is a startup and social enterprise that builds modern collaborative authoring tools for scientists — like Google Docs for Science — with over 3 million users around the world.

What We Do

Overleaf is a startup and social enterprise that builds modern collaborative authoring tools for scientists — like Google Docs for Science. We have over three million registered users from around the world. Our primary product is an online, real time collaborative editor for papers, theses, technical reports and other documents written in the LaTeX markup language.

Who We Are

Overleaf was founded by two mathematicians who were inspired by their own experiences in academia to create a better solution for scientific collaboration and communication. Now we are a team of thirty based mainly in and around the UK and in the US. We were recognised as one of the UK's top 100 fastest growing businesses in 2018.

In September 2018, we officially launched 'Overleaf v2', the latest version of our platform, which we've been working on since our acquisition of ShareLaTeX, the other major online LaTeX editor, in 2017. We've now integrated the two products and teams.

How We Work

Overleaf is remote-first — all founders and staff work remotely. We also have an office by King's Cross station for those in the London area, and we get the whole team together in London several times a year for face-to-face time.

We encourage flexible working. Our core hours are 2pm–5pm UK time, during which we have a 10–15 minute daily standup call for the whole development team. We have few standing meetings for the development team, but we do many smaller video or voice calls for pairing or within project groups.

We don't yet have standing teams, but we form and dissolve smaller teams on a per-project basis; we try to give everyone the opportunity to serve as a team lead if they want to.

We always collect user feedback to inform our work. We have UX professionals on our team, and we run many surveys and user interviews.

We organise our work with Kanban. We use GitHub pull requests for each feature with code review to share knowledge and best practices (and catch bugs). We test thoroughly with automated unit and acceptance tests, supported by continuous integration (CI). We're also fans of linting to minimise bikeshedding (and to catch bugs).