We’re building a mobile parking app for San Francisco — not just another parking service, but a full-scale navigation platform that aggregates data from 20+ sources into a seamless user experience.

Core product modules:

• Data aggregator pulling from 20+ parking services and municipal systems in San Francisco (via APIs, scraping, and partnerships)
• Custom routing algorithm to the optimal parking spot based on price, distance, availability, and restrictions
• Custom map layer with proprietary parking data visualization
• Crowdsourcing layer (users update parking data in real time)
• Gamification system for user engagement and retention

We have a founder with a clear product vision and a development team. What we’re missing is a person who takes that vision and turns it into a working system without losing a single feature or detail along the way.

We don’t need a classic product manager focused on unit economics and competitor analysis. We need a technical leader who thinks in systems, dependencies, and integrations — someone who will ensure that every one of 20+ aggregator connectors works, the routing algorithm accounts for all variables, and crowdsourced data is properly validated.

In short: you will be the person responsible for making sure the product is built completely and correctly.

• Decompose the product into components and build a dependency map across all modules (aggregator, routing, map, gamification, crowdsourcing)
• Own each of 20+ aggregator integrations end-to-end: from API research to production — documentation, status tracking, fallback scenarios, monitoring
• Write detailed technical specifications for the dev team (not napkin-level user stories, but full documents describing logic, edge cases, and data formats)
• Manage the backlog with a focus on technical completeness: no integration should be “lost,” no edge case should be ignored
• Ensure implementation quality: you don’t need to do code reviews, but you must know what to check and what questions to ask the developers
• Build a testing and monitoring process for integrations and their stability (external APIs go down — plan for it)
• Serve as the bridge between the founder (vision) and the developers (execution), ensuring nothing gets lost in translation
• Maintain a single source of truth for the product: what’s integrated, what’s in progress, what’s blocked, and why

• Engineering or technical degree. You must be able to read API documentation and understand what it says
• 3+ years of experience as a Technical PM, Technical Program Manager, System Analyst, or Tech Lead who transitioned into management
• Hands-on experience with products involving multiple external integrations (aggregators, marketplaces, platforms with many data sources)
• Ability to write technical specifications that a developer can pick up and execute without additional clarification
• Systems thinking: you see not individual tasks, but how modules affect each other
• English C1 (product documentation, API providers, and most materials are in English)

• Experience with geo-services, maps, or navigation (Google Maps API, Mapbox, HERE, OSM)
• Background at companies like InDrive, 2GIS, Yandex Go, Waze, Uber, Lyft, or similar
• Experience working with crowdsourced data and its validation
• Familiarity with the US parking market or mobility services

Let’s save each other’s time. This role is not a fit if you:

• Are a product manager who operates at the level of “strategy → hypothesis → A/B test → metric.” We’re not at that stage yet
• Want to “own the product” and decide what to build. The vision exists — we need execution
• Are not willing to dig into technical documentation and figure out why a specific API is returning a 403
• Believe that a PM’s job is to set priorities and let the team work. We need someone in the details