Technical Program Manager
Listed by employer · Checked
Posted within 60 days ·
- Work arrangement
- remote
- Employment
- FullTime
- Stated compensation
- Not specified
- Stated sponsorship
- Not stated
Does the location policy fit?
Choose where you would work from. We’ll compare it with the posting’s stated requirements.
Likely eligible to apply remotely
Checked for applicants in United States; employer sponsorship is not needed. Based on the source posting · not a hiring or work-authorization guarantee.
The stated geographic scope includes your country.
Why this result?
2 supporting signals
- The stated geographic scope includes your country.
- The role is described as remote; geographic restrictions still apply.
2 still unclear
- Visa sponsorship is not specified.
- Confirm that you can meet the stated working-hour or timezone requirements.
This checks the posting’s stated requirements, not your legal right to work. Confirm details with the employer.
Requirements
3 with evidence6 unclear or unstated- Remote policy
- remote
“Provider workplace type: remote”
From employer posting metadata - Geographic scope
- US, CA
“Provider location: US - Remote • Provider location: Canada - Remote • Provider location: US/Canada - Western Region”
From employer posting metadata - Timezone / hours
- Comfort working across time zones with a distributed team.
“Comfort working across time zones with a distributed team.”
See matched passage in original description ↓ - Employment type
- FullTime
7 fields not stated in this posting
- Employer sponsorship
- Not specified
- Degree requirement
- Not specified
- Security clearance
- Not mentioned
- Citizenship requirement
- Not mentioned
- Minimum experience (years)
- Not specified
- Work authorization
- Not specified
- Compensation
- Not specified
These details were not stated in the tracked posting. Confirm with the employer.
Original job description
Reading view uses normalized posting text so exact evidence excerpts can be highlighted.
Show less description
Original formatting and links
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 Role
Redpanda 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.
You Have:
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 fast-growing software company.
Experience running a cross-functional release, launch or planning cycle end to end, and the scars to show for it.
A builder's habit. You have automated part of your own job, you are comfortable with Jira, structured data, and spreadsheets, and you have used Claude or similar tools to build something real rather than to write emails. You do not need to be an engineer. You do need to want to ship.
The confidence to ask a senior engineer or a VP “What does this depend on, and is it on track?” and to follow through on the answer, with warmth and without flinching.
Clear writing. You can turn a messy situation into a one-page plan, a decision with options, or a status people actually read.
High ownership. You notice what is falling through the cracks and pick it up before anyone asks.
Comfort working across time zones with a distributed team.
Nice to Have:
You have shipped software, or sat close enough to engineers shipping it to know what a release train, a fix version, and a code freeze are.
You have built something on an agent platform, with MCP, or with an LLM in the loop, and can talk about what broke.
You have worked with product managers on roadmaps or planning and understand the difference between what to build and whether everyone is ready for it. This role is the second of those, not the first.
You know Salesforce, HubSpot, or the other systems of record a company runs on.
You have been the first person in a new function and enjoyed it.
U.S. base salary range for this role is $140,000 - $164,000 (CA, NY, WA) and $133,000 - $156,000 (other US locations). Our salary ranges are determined by role, level, and location. We strive to consider each candidate's job-related skills, location, experience, relevant education or training to determine individual base salary. Your talent partner will share more about the specific salary range for your preferred location during the hiring process.
Join Redpanda if you’d enjoy being part of a fast-moving, diverse, people-first organization with team members around the globe and a culture based on trust, transparency, communication, and kindness. You'll dive into a nimble, high-impact team with the latest AI tools — and the budget to actually use them.
No similar roles found yet — browse all redpanda-data jobs.
Explore stated remote geography
These collections reflect applicant location statements, not authorization or citizenship.
