Skip to content

icon picker
Engineering at Coda

Meet the engineers who are building Coda, a new doc for teams.
Coda's engineering team is building, running, and continuously improving Coda. We are deeply involved in everything from innovating what users are able to do with the product (like our Packs Platform, templates, and doc building blocks) to driving user and revenue growth to managing performant and scalable distributed systems. We are a fast-moving team that produces high-quality products and high-quality code, towards creating a world-class experience for our makers.
Who are we?
We are very proud of the diverse and fun team we have assembled. Our team members have worked on some of the most widely-used technology products in the world, including YouTube, Google Drive/Docs, Google Shopping, Google Flights, Amazon AWS, Pinterest, and Microsoft Azure. Outside of work, we have a variety of hobbies that embody our makerness, like woodworking, pottery, art, and more. Check out the to learn more :)
What technologies do we use?
We use Typescript for most of our stack, React on the frontend and NodeJS on the backend. We also use Python for certain scripts and our data infrastructure. Our server infrastructure runs on Kubernetes in Amazon AWS, and we make heavy use of Terraform, Redis, Opensearch, and Postgres. For machine learning, we use scikit-learn. Finally, our data stack uses Snowflake for warehousing, Apache Airflow for orchestration, Mode Analytics, and Amplitude as frontends.
Where are we?
Geographically, we are distributed across the entire U.S., with offices in San Francisco, Mountain View, and Seattle. We have a large cohort in New York and are looking into a physical office there in the future. A large percentage of our team is working remotely — something the company is strongly supportive of.
Learn more about how we work.
Below, you’ll find more information about our team structure, culture, and written by members of Coda's engineering team and what values we stand by in our work.

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
) instead.