/jobs

Technical Program Manager

Last updated:

We're looking for a Technical Program Manager to streamline how we ship at Pydantic, with a particular focus on Pydantic Logfire, our observability platform built for the AI engineering era. You'll partner directly with engineers, the founder, and product to turn ambitious roadmaps into shipped software, without adding bureaucracy.

This is not your typical TPM role. We are a small, senior, remote-first team that values substance over process. If you are looking for a gig where you run six standing meetings a day and produce decks for executive review, this isn't it. We are looking for a TPM who can drop into a fast-moving engineering org, identify what's actually slowing us down, and unblock it, often by writing the doc, chasing the dependency, or running the cross-team sync yourself.

This role might appeal to you if you have experience in roles such as:

  • Technical Program Manager
  • Engineering Manager (with strong delivery instincts)
  • Chief of Staff to a CTO or VP Engineering
  • Senior Product Manager on infra/DevTools
  • Technical Founder

You are interested in getting in early at a company with genuine product-market fit. Pydantic Validation is downloaded 500M+ times a month, Pydantic AI is the fastest-growing agent framework, and Logfire is the observability platform the AI engineering ecosystem is converging on. The pace is high, the surface area is broad, and the leverage for a great TPM is enormous.

Your goal is to increase the throughput and predictability of Logfire delivery, so engineers can spend more time building and less time on coordination overhead.

1. Run the Delivery Engine

  • Own the cadence: roadmap reviews and planning cycles, light-touch but reliable
  • Make project status legible across teams without forcing engineers to write status reports
  • Track commitments, dependencies, and risks; flag the ones that actually matter early

2. Translate Strategy into Plans

  • Turn fuzzy strategic goals from leadership into concrete programs with owners, milestones, and definitions of done
  • Push back when scope is unrealistic; help right-size before commitments are made externally
  • Keep the bridge between business priorities (sales commitments, launches, customer escalations) and engineering reality

3. Own the Compliance Track

  • Logfire serves regulated customers. SOC 2, GDPR, and customer security reviews are part of how we win deals
  • Coordinate evidence collection, audit prep, and policy upkeep so engineers can stay focused on building
  • Be the single point of contact for security questionnaires and customer due diligence; turn them around fast
  • Treat compliance as a delivery program, not a paperwork tax. The goal is to make the work invisible to the rest of the team

4. Unblock, Don't Babysit

  • Be the person who chases the missing decision, finds the right reviewer, or writes the spec that's been sitting in someone's drafts
  • Drive cross-functional alignment between engineering, product, design, sales, and marketing on launches
  • Improve the workflow: if something is broken in how we plan, ship, or hand off, fix it

5. Help Build the Playbook

  • We're early. There is no PMO. There is no project management template library. You'll write the lightweight processes that fit our culture.
  • Your judgment on what's worth tracking (and what isn't) shapes how we scale engineering
  • Technical enough to be useful in the room. You don't need to ship Rust, but you should be comfortable reading a design doc, understanding a system architecture diagram, and asking sharp questions in an engineering review. You'll be working with senior engineers, and they should respect your input.
  • Allergic to process for its own sake. You believe meetings, docs, and rituals exist to serve delivery, not the other way around. You can tell the difference between coordination that helps and ceremony that doesn't.
  • A doer, not a coordinator. You don't just track work, you do whatever moves the program forward, whether that's writing the launch checklist, drafting the customer comms, or running the retro yourself.
  • Strong writer. Most of our coordination happens async in writing. Crisp summaries, clear next steps, and tight project briefs are non-negotiable.
  • Comfortable with early-stage ambiguity. We're ~25 people. Priorities shift. Roadmaps change. You bring structure without rigidity.
  • Familiar with modern tooling. Linear, Notion, GitHub, Slack: you have opinions on how to use them well, and you don't need a Jira admin to make changes.
  • Fluent with AI as a collaborator. Much of the friction this role removes (vanishing meeting notes, specs that never get written, status that has to be chased) is exactly what AI is good at. You instinctively reach for transcription, draft briefs and PRDs with a coding agent, and use LLMs to compress information rather than create more of it. See why this matters at a distributed company like ours.
  • Bonus: observability, DevTools, or AI infra background. Familiarity with the space helps you ramp faster and contribute to product conversations sooner.

Day to day:

  • Run the planning cadence: quarterly goals, weekly check-ins with engineers, async status across teams
  • Maintain a clear, current view of what's in flight, what's blocked, and what's at risk
  • Drive cross-functional launches: coordinate engineering, product, design, marketing, and sales on shared timelines
  • Write project briefs, kickoff docs, and post-launch retros
  • Improve our planning and tracking tooling (Linear, Notion) so it works for engineers, not against them
  • Work async with a remote team across US and UK time zones

On programs:

  • Some initiatives span multiple teams over multiple quarters, and you'll own the end-to-end view
  • Customer escalations, security reviews, compliance projects, and major launches will land on your plate
  • You'll partner closely with the founder and senior engineers on capacity planning and prioritization trade-offs

What success looks like:

  • Month 2: Planning cadence is running smoothly; the team has a clear weekly view of delivery status
  • Quarter 1: At least one major cross-functional program has shipped on time under your stewardship
  • Quarter 2+: The engineering team tells us they can't imagine going back
  1. Required: Live and work in a timezone between PT (UTC-8) and CET (UTC+1)
  2. Required: Able to travel to EU, UK, and US up to 4 times per year for offsites (next one is in London, June 2026)
  3. Required: Fluent in English

Pydantic Validation is the data validation library that powers modern Python development - 500 million downloads per month, used by virtually every tech company you've heard of. Why? Because we obsess over developer experience and write code we'd actually want to use ourselves.

We're applying that same engineering mindset to Pydantic Logfire, our observability platform with first class support for AI engineering, built for today's development reality: AI workloads, multi-language environments, and cloud infrastructure that's designed to be straightforward to set up and maintain.

We build with technologies developers actually want to work with:

  • OpenTelemetry for standardized instrumentation
  • SQL for intuitive querying (no proprietary query language to learn)
  • Rust, Python, and TypeScript for performance and productivity
  • Postgres, DataFusion, and object storage for scalable backends

Unlike other companies that pay lip service to open source, we commit over 20% of our engineering team to maintaining and expanding our open source ecosystem. This includes the core Pydantic Validation library and Pydantic AI - our rapidly growing framework that's becoming the standard for AI application development. We're signatories of the open source pledge and build on open standards because we believe in interoperability, not lock-in. Use our OpenTelemetry-based SDK with any compatible backend - we're confident you'll choose us on merit.

We're backed by Sequoia Capital and run a fully remote team across multiple time zones (with regular in-person offsites - next one is June 2026 in London).

Join our team of exceptional engineers who value substance over hype, practical approaches over perfectionism, and meaningful progress over busyness. We've built a culture that balances technical ambition with sustainable practices—minimal meetings and respect for your expertise and time. We're creating tools that genuinely improve developers' lives, and we're looking for thoughtful contributors who share our commitment to quality and our passion for elegant solutions.

  • 💰 Compensation: Competitive salary and stock options
  • 🌍 Truly Remote: Work from anywhere within our timezone range - no office requirements
  • 🌐 Global & Diverse: Join a multi-cultural team of 8+ nationalities
  • 💪 Impact: Direct influence on tools used by millions of developers worldwide
  • 🎯 Focus on Growth: Regular opportunities for learning and professional development
  • 🤝 Team Gatherings: Connect with the team at our regular international off-sites
  • 🏥 Healthcare: Comprehensive health coverage for you and your dependents
  • 🎮 Flexible Hours: Work when you're most productive
  • 💻 Equipment: Budget for your home office setup
  • ⚖️ Work-Life Balance: flexible working hours and 33 days PTO no matter where you live (including public holidays, which you can choose to take or not)

To apply, email [email protected] with the job title in the subject line. We'd also appreciate a few lines explaining why you think you'd be a good fit for the role and what you've done in the past that evidences that.

No recruiters or agencies please. Unsolicited recruiters will be marked as spam.

Explore Logfire.

Get started

Explore our open source packages

Product shot