Head of Product, Enterprise

A Note From the Founder I have built product at Citizen since the first line of code, and I am still in it every day. Now I build with agents, and so does the rest of the company. Engineering, operations, and finance already run this way. The gap between an idea and a working build on my phone is measured in hours, and it is changing how fast we move more than anything in our history. The enterprise business is working. Cities, hospitals, campuses, and private security teams are buying the same real-time intelligence that made Citizen the #1 safety app in America, and they are renewing. The next step is scale: a product that gets a customer signed to live in days, an API and integrations that put Citizen inside the systems they already run, and packaging that lets a small team serve many more of them. That is a product leader's job, and I want to build it with you, next to me, every day. You will hear no from me, and I expect to hear it back, with the data. The Role Citizen is the #1 safety app in the U.S. Every day, thousands of videos are captured live at the scene of real incidents and distributed in real time to people in every major American city. No other product, consumer or enterprise, has this. Under the app is a real-time machine. First-responder radio in every market we cover, video arriving from the scene, a Mission Control floor deciding in seconds what a city hears, and alerts that reach a phone before the sirens do. That machine is becoming agentic, and the same signal that reaches a resident's phone is what a security director, an emergency manager, or a newsroom needs on their screen, with the context, the tools, and the delivery their job demands. Designing that product, for institutions that act in the real world in real time, is the job here. You are the Head of Product, Enterprise: the enterprise products and consoles, the public API and how it is packaged and priced, the integrations that put Citizen inside the tools cities already run, and the path from signed contract to live customer. You report to the Founder. Sales owns the relationships and the contracts; you own the product and its velocity. Enterprise customers renew and expand on what ships, and that number is yours. A peer owns the consumer product; you share one codebase, one data platform, and one standard for what agents may decide. You will never hire a product manager. Your headcount is agents. The production work of product management, discovery synthesis, competitive reads, spec drafts, partner documentation, onboarding runbooks, the weekly pipeline and renewal read, is done by an agent team you build and operate. One person with the right systems and the right judgment now carries what a product org of six carried three years ago. That is the job, and this is the first moment it has been possible. Why Now Citizen built the public safety category, and the institutions responsible for safety now want what the public already has. The enterprise business has customers, renewals, and a pipeline; what comes next is a product that scales as fast as the demand for it. The levers are known: time from signed to live, integrations that make Citizen part of the workflow, packaging that fits how a city or a hospital buys. The next step is one person who owns those levers end to end. Until recently that took a department. Now they need agents, taste, and the nerve to decide. How We Work Every role at Citizen is two things: the craft, and the operation of AI to multiply it. You are a product leader first. Judgment about what to build and what to kill. A feel for what people will open every day and what they will pay for. The ability to tell a founder with strong opinions that the data says otherwise. Every function here runs with agents doing the production work. Engineering ships through them, operations runs on them, and the weekly read assembles itself. You will inherit that stack on day one and build your own on top of it. If you are still writing specs from a blank page or assembling the weekly read by hand in month three, something has gone wrong. What this job is not: a roadmap of other people's requests, a quarterly planning calendar, a PM team to build, or a layer between the Founder and the product. The agents produce the artifacts. You produce the decisions. What you Will Build Each of these is a system you design and operate, not a department you run. Signed to live. The path from contract to a customer using Citizen every day: provisioning, geofences, user setup, training, the first week. You make it take days, with agents doing the setup and a human checking the result. Time from signed to onboarded is the first number you own. The enterprise product. The consoles and alerts that a security director, an emergency manager, or a communications team uses on a bad day and on a normal one: what ships, in what order, and what we choose not to build. Specs come out of customer calls and the data, drafted by agents you direct, and prototypes are in front of a customer in days, not in a deck in weeks. Design partners. A small set of customers who build with us. You choose them, put prototypes in front of them, and decide what becomes the product. The API and its packaging. How Citizen's real-time intelligence is consumed by other systems, how it is priced, what the tiers are, and how a developer or an agent gets from docs to a working integration without a call. You own the public API as a product. Integrations and partners. Citizen inside the systems cities already run: dispatch, camera networks, mass notification, the tools a campus or a hospital already pays for. You decide which integrations to build, in what order, and you get them live. The listening loop. Every enterprise call, every support ticket, every renewal conversation, every lost deal: read daily, by agents, and turned into a standing proposal for what the product should do next. You decide what gets built. The proposal never waits for a research sprint. The renewal and expansion number. Customers renew and expand on what ships. You own the product drivers of that number, you build the loop that refreshes them, and you explain the variance before anyone asks. Finance owns the forecast and the P&L; Sales owns the quota. The agentic product itself. Where an agent should listen, verify, write, or route on the way to an institution's screen, and where a human must. Which decisions a city's safety can hand to a machine and which it never should. You own that standard for the enterprise surface, with your consumer peer and the Founder. Partnership. Daily with the Founder on direction. With Sales on what customers are asking for and what we commit to. With engineering leadership on what ships and when. With Real-Time Operations on what the people running the city actually need, with your consumer peer on the shared platform, with Finance on the model, and with the agents that already work here. Your First 90 Days - Days 1–30. Sit in on every enterprise call and every onboarding. Read the contracts, the pipeline, the renewal history, and the API docs. Sit on the Mission Control floor through a live incident. Use the enterprise product as a customer would. Take over the weekly enterprise read by the end of the month, and stand up the first agent that reads the listening loop for you. - Days 31–60. Bring the Founder the enterprise product plan: what we sell, the packaging and the API tiers, the integration order. Ship your first signed-to-live improvement with a measured time. Have spec drafting and onboarding runbooks running end to end through agents. - Days 61–90. Present the twelve-month enterprise product plan with the numbers behind it. Have one customer live on a new integration, one packaging decision in market, and one loop that a human no longer touches. HOW SUCCESS IS MEASURED - Time from signed to onboarded, falling - Integrations live, and customers using them - Renewal rate and expansion revenue, against a plan you own the drivers of - Customers served per person on the team, rising - Enterprise and API reliability against the commitments Sales makes - Loops running without you: the count of product functions carried end to end by agents you built, with the bar held or raised Who You Are Five things. Each one is a filter. - You have replaced a function you used to manage with a system you built. You can show the agents what they do without you, and what they still cannot. - You have owned a B2B product through the full cycle: shipped it, sold it alongside a sales team, onboarded the customers, and renewed them. You can show the renewal or expansion number and the work behind it. You did not need to found the company; you needed to own the number. - You have packaged and priced something technical, an API, a platform, an integration, so that a customer could buy it without a meeting and a developer could use it without a call. - You are quantitative to the point of building the model and reading the pipeline yourself, and you know when a number is lying to you. - You want this mission and this city. Safety is a real thing that happens to real people on their worst day, and the institutions that respond deserve the best tools in the world. You want to build them in New York, in the office, next to the Founder, every day. It does not work any other way. You will hear no from the Founder. You will say it back, with data, and you will be right often enough to earn the job of saying it. Compensation Base salary of $250,000–$290,000 per year, plus equity. Full numbers in the first conversation.