This job ad has been posted over 40 days ago! (*)
Overleaf is a scaleup and social enterprise that builds modern collaborative authoring tools for scientists — like Google Docs for Science. We make an online, real-time collaborative editor for papers, theses and other documents written in the LaTeX markup language.
We have over 11 million registered users from around the world, over 400,000 people use our platform each day and we host over 100 million user-created projects. Our company is growing and we are looking for Frontend Engineers to help improve our platform.
We’ve been recognised as one of the UK’s top 100 fastest growing businesses and included in the FEBE Growth 100 list. We were Best SaaS for Nonprofits or Education in the 2020 SaaS Awards Program, and a finalist in the Digital Leaders Impact Awards 2022. We’re part of the Digital Science family of science, health and ed-tech companies.
Overleaf is based on open-source software, and most of our product code is open-source. You can find it on GitHub: https://github.com/overleaf/overleaf
On the front end, we mainly use React. On the backend, we run a microservices architecture, mainly in Node.js using MongoDB, PostgreSQL and Redis, running on Google Kubernetes Engine.
Your New Role
We are looking to hire a frontend engineer to help improve our platform. This is a complex web app that allows users to edit their scientific documents in collaboration with others, in real-time.
We are working on projects that include improved collaboration features for teams, and improvements to our rich text editor to help non-LaTeX users get started with our platform.
There will be opportunities to work on the backend, so both frontend and full-stack engineers are welcome to apply. (We also have openings for backend engineers.)
As part of the engineering team at Overleaf, you will be helping to make Overleaf the go-to place for scientific writing.
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 we get the whole team together a few times a year (usually in the UK) 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 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 4-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 practice code review, invest in automated testing and are big fans of linting.
How We Hire
The stages in our hiring process are typically:
If you have a deadline, please let us know in your application, and we will try to be accommodating.
We’re an equal opportunity employer. All applicants will be considered for employment without attention to race, color, religion, sex, sexual orientation, gender identity, national origin, veteran or disability status. Underrepresented groups often do not apply and we encourage them even if they do not meet all the requirements.