About the RoleStartups are defined by their feature set. Generational platforms are defined by their reliability. As the team scales toward 40 engineers by EOY and the platform scales past 10m users, powering events with up to 20k attendees, our infrastructure is rapidly becoming one of the most important determinants of our success.
As our founding Technical Product Manager, you'll partner directly with our CEO, Product Team, Director of Engineering, and a team of Senior and Staff Engineers to shape the roadmap, architect the team, and own execution of our most complex technical problems with one goal in mind: make Posh the most scalable and reliable events platform to ever exist.
Your work will span across 2 core teams:
- Platform: Owning observability/incident response, backend services, notifications, authentication/permission systems, localization, and experimentation infrastructure to optimize reliability and empower user-facing teams to create novel technical innovations
- Internal Operations: blurring the lines between product, GTM, marketing, and operations to empower teams with software tooling that accelerates their goals
This role reports to the CEO, working in lockstep with the entire leadership team to ruthlessly prioritize projects, allocate resources, and accelerate velocity.
This is an in-person position at our SoHo NYC office, 5 days a week.What You'll Own & Achieve- Own infrastructure end-to-end: Turn company objectives into an actionable roadmap, defining, tracking, and improving key reliability metrics to establish the infrastructure necessary to support hundreds of millions of users. Free our engineers from the planning work they currently absorb so they can focus on building.
- Be the technical translator between Platform and the rest of the company: Collaborate at the intersection of deeply technical backend engineers and non-technical stakeholders to prioritize engineering needs & limitations against company objectives, scope & milestone robust projects, and communicate the importance of technical decisions to the broader organization.
- Run incident response as a first-class program: Own on-call rituals, observability, and post-mortems to ensure best-in-class SLAs and SLOs. Make sure every meaningful incident becomes a durable improvement in reliability or developer experience.
- Drive build-vs-buy decisions: Lead the evaluation of where to invest in homegrown tools vs. third-party integrations, balancing cost, effort, and long-term leverage.
- Make Platform's impact legible: Establish the dashboards and rituals that prove Platform improvements are making Posh more reliable while improving developer experience.
- Partner on architecture, not just timelines: You won't be the architect, but you should be deep enough in the system to push back on scope, identify hidden complexity, surface tradeoffs to leadership, and earn the trust of our Staff engineers in technical conversations. Engineers should treat you as a peer in the design phase, not a project manager who shows up after the decisions are made.
- Scale the Platform operating model: As your team grows into two clear sub-pods (Product Infrastructure and Internal Infrastructure), help define the boundaries, the shared rituals, and the handoff points between them.
- Bring AI leverage into how Platform itself operates: Use agentic workflows to optimize decision making, compress planning, improve documentation, and automate coordination work at every step of the PDLC. Hold a real perspective on how AI is changing infra engineering and bring that thinking to the roadmap.
Who You Are- 4+ years of backend software engineering experience, ideally on marketplace infrastructure, payments, distributed systems, or developer platforms - followed by 2+ years in a PM, TPM, or Technical Program Manager role. You know what world-class infrastructure looks like because you've built it.
- A track record of being the person engineers want in the room during design reviews. You can read an RFC, push back on a data model, ask the right questions about scaling assumptions, and add real signal in architecture conversations.
- Strong fluency in system design, payments architecture, and cloud infrastructure. You don't need to write production code, but you should be one technical conversation away from doing so if you wanted to.
- Demonstrated ability to drive cross-functional programs across multiple engineering teams - defining scope, surfacing risk early, managing dependencies, and shipping on time with minimal oversight.
- Excellent written communication. You can take a tangled technical problem, write a one-page memo that an exec or a non-technical stakeholder can act on, and write a separate technical spec that engineers can build from.
- A bias toward urgency and ownership. You don't wait to be told what the priority is - you propose it, defend it, and revise it as the data changes.
- You're obsessed with AI, constantly trying new tools and evolving your perspective on how LLMs are reshaping both how infrastructure gets built and how work gets done.
- You have high EQ, holding a battle-tested perspective on what it takes to build trust and collaborate effectively.
Nice to Have- Background owning internal tooling as a product surface, with measurable wins on non-technical team velocity and operational efficiency.
- Experience owning and optimizing on-call practices and incident response programs.
- You're deeply passionate about the value of in-person connection, with a personal connection to IRL events and/or communities that mean something to you.
