The team is Export, part of the Editing Platform group. The company's focus is reliability, speed, and format flexibility.
This is the second Staff Engineer on Export. You will split the domain with the existing Staff Engineer so that neither of you is a single point of failure on the hardest parts of the system.
Beyond the main download flow, the system supports print production, AI model training, and thumbnail generation, and must work with every new editor feature. The role will evolve over time as the company and the tools it depends on change.
The company will decide on applicants based on experience, skills, and passion, and on how they strengthen the company and its culture. You are welcome to apply even if you do not match every item listed. Interviews are conducted virtually.
When you apply, share the pronouns you use and any reasonable adjustments you may need during the interview process.
Responsibilities
Set the technical direction for the Chromium-based export pipeline that renders designs into files, and design its architecture so it stays reliable as both the editor and Chromium change.
Be the go-to person for the hardest rendering problems, including upgrade breakages, race conditions, and production incidents caused by upstream Chromium changes.
Decide how the company responds to upstream change in advance. Build monitoring and tests that catch Chromium regressions first, and design for frequent changes in Chromium's output structure.
Set direction for PDF accessibility and compliance (PDF/UA, WCAG) in exported files for Enterprise customers. Decide how deeply files are tagged, where the line sits, and what to build versus buy.
Own export reliability and performance at over 50 million weekly downloads, covering format optimisation, distributed systems design, and failure modes that appear only at that volume.
Grow the engineers around you through design reviews, pairing on difficult debugging, and documentation that moves one person's Chromium knowledge to the whole team.
Work across the Editing Platform group and beyond it, so teams shipping new editor features know their work will hold up at download time.
Requirements
Deep experience with Chromium or another browser rendering engine, having worked inside the engine itself.
Strong C++ skills for working in large third-party codebases and building an accurate understanding of code you did not write.
Strong Java backend experience, as the product is built on Java.
Background in rendering pipelines, graphics programming, or print production systems.
Experience owning a technical domain end to end, including setting architecture, making trade-offs, and living with the results.
Experience debugging layered systems that span multiple codebases and languages, and leading others through such investigations.
Experience mentoring engineers and raising standards through design review.
Experience building or maintaining systems whose upstream dependencies change often, with a considered approach to keeping that sustainable.
PDF specification knowledge, or experience with PDF generation and post-processing.
Experience with accessibility standards in document or file output.
Conditions
Interviews are conducted virtually.
Equal opportunity: the company celebrates all types of skills and backgrounds.