Technical Program Manager
-
Business
Job Description & How to Apply Below
Redpanda is the first runtime and control plane for agent-data interaction — a unified platform that combines streaming, SQL analytics, and intelligent connectivity with the governance layer enterprise AI agents need in production.
Built on infrastructure already trusted by Fortune 500 companies and fast-growing startups, Redpanda enforces governance entirely outside the agent's data path, controlling what agents see, limiting what they do, and capturing a tamper-proof record of everything they touch, so organizations never have to choose between innovation and control.
About the RoleRedpanda is building an operating system for how it runs itself: one shared layer on our own agentic platform where direction, priorities, and dependencies are visible to everyone, routine planning and shipping work is handled by agents and deterministic code, and every team builds its tools on a common foundation. We’re doing to ourselves what we sell to customers, with the CEO’s attention and the CFO as sponsor.
You’ll be one of the first people to build and run that system. Half the role is building: tools like the executive portfolio view, the release readiness engine, and the company memory, built with our engineers and with Claude as your pair, and adopted because you made them useful. The other half is people: leading the cross-functional teams that get releases out the door, running planning sessions where hard tradeoffs get made, and unblocking work across teams you don’t manage.
You’ll report to the CFO and work closely with our Staff Technical Program Manager, who leads the practice. It’s an early-career role with unusual room to grow. If you want to learn how a company works from the inside while building the software that runs it, this is the job.
You Will:Lead the cross-functional tiger team for each product release and launch: engineering, product, docs, marketing, sales enablement, and support. Run the weekly release readiness drumbeat, know who owes what by when, and make sure nothing ships to a team that did not know it was coming.
Run technical planning sessions with engineering and product leaders through each two-month planning cycle: frame the choices, hold the room to the company strategy, and make sure what gets ranked has an owner, a date, and named dependencies.
Build the capabilities of our internal operating system, working with the internal AI apps team on our platform: the portfolio view the executive team plans from, the release readiness engine, the dependency ledger, the team profiles, and the company memory. You will write the requirements, build what you can yourself with Claude and our tooling, ship it, and own whether people adopt it.
Own the cross-team dependency picture. Keep the ledger between functions live, spot conflicts before they become escalations, and bring them to the right decision-maker with options.
Make accountability come from visibility rather than status-chasing. Extend the deterministic reports and agents that already tell engineering leaders how their teams are doing, so the same is true for every function.
Keep the decision record. Every tool adopted or retired and every process changed gets written down with its reason in the company memory, and you will drive the consolidation plan that retires third-party tools as our own system absorbs them.
Work embedded with the teams you serve, in their channels and their planning, bringing their needs back to the shared roadmap and taking shared tooling back to them.
Two to five years in a role where you made things happen across teams you did not manage: technical program or project management, release or launch management, engineering or product operations, or a chief-of-staff style role, ideally at a…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).
View / Apply for Jobs
Matching My Jurisdiction