San Francisco
Retool is a fast way of building internal software. Our goal is to make it easier for engineers to build custom, internal software. Software has transformed industries, but it's expensive to plan, build, and maintain. And that's a shame, because it's so useful! Our goal is to make this large class of software faster, cheaper, and more enjoyable to build. Because then we'll have a lot more of it, and that's a good thing.

We're based in San Francisco. Culturally, we're tightly knit, and enjoy spending time together. If we weren't working at Retool, there's a good chance many of us would be friends anyways. We enjoy spending time with others who are fun to be around, have some sense of humor, and can reason, debate, and make decisions without bitterness.

We're profitable and growing quickly. Our investors include Sequoia Capital, Y Combinator, as well as the founders of Github, Gusto, PagerDuty, Segment and Stripe. 


As an engineer, you'll work on a variety of products and problems, all across Retool. You'll generate product ideas, as well as architect, implement, and release them.

Retool is built in primarily Javascript and Typescript. It's Node on the back-end, and React on the front-end.

We like engineers owning projects, from start to finish. For example, new features often start off as customer ideas. So it'll be your responsibility to talk to the customer and scope out what a solution might look like, in addition to actually building it, testing it, documenting it, and releasing + iterating on it with the customer.

Problems you might work on:

    • Improve the UX of the Retool core editor, which involves plenty of interesting problems, both technical (e.g. "how do we implement our drag and drop system in a performant way?") and otherwise (e.g. "how do we handle the pushing of existing components when dragging new components on?").
    • Build entirely new product lines (e.g. an interface to share queries — both SQL, and REST + GraphQL across your company)
    • Debug customer problems + build features for them (e.g. "the Google Sheets integration doesn't support adding rows", and "what's the best way to support that? Via cell ranges, or via a lightweight, home-grown ORM?")
    • Write technical blog posts (e.g. "here's how we implemented role-based access controls") and documentation (e.g. if you build the Google Sheets integration, you will write documentation on how it's used)
    • Help assess and recruit future engineers