Why we started Pydantic

Driven by curiosity, frustration and coffee

I started working on Pydantic out of a mixture of frustration that type hints do nothing at runtime and curiosity as to whether they could be used to validate data.

Turns out I was right (or lucky) and with Pydantic's crazy growth, the maintainers behind it now get to build other products with the same principles — that the most powerful tools can still be easy to use.

Samuel Colvin, Creator of Pydantic
Samuel Colvin, Creator of Pydantic
@samuelcolvin

Proudly backed by

Sequoia Logo
Sequoia Logo
Sequoia Logo

Our team

The Pydantic team

/careers

Build developer tools loved the world over

From our open source projects to enterprise solutions, we're building tools where the developer experience is our north star. If that sounds up your street, we'd love to hear from you.

/careers

A few good reasons to join us

icon

Make your mark. Help set the agenda, not just implement it-your ideas won't get lost in bureaucracy. Your contributions have the potential for outsized impact on this team.

icon

Lead. We seek people who are opinionated and knowledgeable, and who are excited to design both the application and the way we build frontends.

icon

Work with great people. Pydantic's widespread recognition means we've been lucky enough to hire some of the best Python and full stack developers in the world.

icon

Work remotely. We're a remote-first company, although we get together in person roughly once a quarter for a week — usually abroad.

icon

Build developer tools. We think there's nothing more fun to develop than tools for developers (we hope you agree).

Join the team

We're hiring for the following roles:

Growth Marketing & Developer Relations Engineer

Logfire

Design Engineer

Pydantic