Product Manager

Here's a thinking process: 1. **Analyze the Request:** - User wants me to reformat a job posting into clean, well-structured semantic HTML. - Rules: - Use `

` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use `

• ` for lists of duties/requirements/benefits - Use `

  ` for prose - Do NOT repeat the job title as a heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short `

  ` or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Input Text:** The text is a job posting for SageOx, a startup. Let me extract the meaningful sections and content. Key parts: - Company description: "SageOx is a well-funded, early-stage startup at the frontier of how AI is shaping the world. At SageOx, we believe the future of work is deeply human and collaborative." - Role description: "There's no trail yet. Pioneering and breaking trails is one of our company's core values. You're one of the first ten people cutting it. Why this role exists You'll be the first product manager at SageOx, reporting directly to the CPO. The company is small enough and early enough that the decisions you make will have a foundational impact on our customers and on the trajectory of the product and the company. Everyone at SageOx is a builder who ships to production, and you will be too. But you'll also augment the team with specific product craft — understanding customer needs before they can even articulate them, testing solutions, communicating direction, exercising judgement in a way that accelerates the team. That craft is changing fast in the agentic era, and you'll help define what it becomes. We want someone excited by that shift: hands-on enough to prototype an idea and get the team excited about it, and already thinking about how teams will work with agents a few years from now, not just today. Unlike traditional Product roles, you'll focus as much on the culture, rituals, and workflows around how SageOx is used as you do on specific features. Deep empathy for customers and understanding of interpersonal dynamics are critical for informing the right decisions. This role will morph over time as needs evolve but will largely focus on: Understand what customers need. Stay close to how teams actually work with agents and how they use SageOx — usage data, customer conversations, support threads, the moments where someone (or some agent) reached for context and didn't find it. Turn that raw signal into a clear, current picture of what customers are trying to do, what's missing, and what's getting in their way. Think deeply about value — creating, communicating, and capturing it. SageOx creates a new category of products, so there's no recipe to copy for how we create, communicate, and capture value. You'll need to work out what specific moments in the customer experience create the most value, which of those moments a team would pay for, and how the product should be shaped and packaged so that what's valuable to customers is also what sustains the company. Steer, and build the system that lets us experiment. Ideas are abundant here and execution is cheap. What's scarce is having judgement on which bets to pursue based on the evidence we collect. This role helps steer: framing the questions worth answering, and building the process by which we build, put things in front of real teams, validate quickly, and drop what doesn't hold up." - How This Person Operates: "Driven by curiosity, courageous in experimenting, humble in success. Ships features and experiments instead of producing strategy decks without execution. Moves from an ambiguous customer problem to testable hypotheses to a finished experiment. Balances speed with taste. The goal is not maximum output; it is the right product — envisioned, packaged, priced, and communicated to the right customers. That often means saying no, cutting scope, and synthesizing rather than adding. Seasoned in customer discovery — meeting customers where they are, observing unobtrusively, asking sharp questions — and changing direction when evidence contradicts the original idea." - What We're Looking For: "We don't care which door you came through — product management, engineering, marketing, founding a company, or design. We care that you can find the right thing to build and get it built. 3–10 years shipping pioneering products. The title matters less than the evidence: things you shipped, decisions you made, and what happened after. Mission alignment: believes deeply in what SageOx is building. Lives and breathes the product every day, all day long. Deep, hands-on fluency with AI: you not only use AI in all aspects of your work but also have deep curiosity about the ecosystem — emerging technologies, products, practices. Zero-to-one experience: you've lived through creating something from nothing — ambiguous problem, small team, no playbook. Experiment-minded: makes many parallel bets and picks the winners; can talk in hypotheses, baselines, and results. Deep customer empathy: wants to understand and solve customer problems, and orients toward finding those customers. Thinks deeply, communicates clearly, writes well: AI slop is all around us — stand on your own thinking, clarity, and craft. Strong sense of ownership: owns outcomes; makes things happen with limited resources; has a great sense of direction and prioritization amid the ambiguity of an early-stage startup. Cultural fit: embodies SageOx's values. Great to have Founder or early-employee experience somewhere that grew fast. Connected to the builder scene in Seattle, San Francisco, and online. Location — Seattle, in person Same as every role here. In person, five days a week, in Seattle. We move fast and the work benefits enormously from being in the room. One narrow exception: Bay Area-based candidates who can get to Seattle at least one week a month, for the first six months. How We Hire No traditional interviews. We'll clear an initial assessment and invite you to a work trial: 3–5 days in Seattle, working on something real alongside the team, the way the team actually works. Most of what matters shows up there faster than any interview loop could reveal. Before applying, please learn more about our work trials. Ajit wrote up why we hire this way: Read the post SageOx Today $15M seed led by Canaan, with A.Capital, Pioneer Square Labs, and Founders' Co-op. Founded by Ajit Banerjee (AWS EC2/EBS, XetHub → Hugging Face), Ryan Snodgrass (early Amazon, Kindle/AWS-scale cloud systems), and Milkana Brace (EVP of Product at Remitly). Small on purpose. More about the team → Compensation Competitive salary and meaningful equity. We'll talk specifics once we know it's a real mutual fit. Apply We're not working with recruiters or recruiting agencies/consultants at this time — direct applications only, please." Now, I need to map this to the requested sections, using `

  ` for headings like: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Let's review the rules about sections: - Include a section ONLY when the posting has real, specific content for it - Never emit a heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences Let's identify what content exists for each potential section: - "About the role": The posting has a "Why this role exists" section and "How This Person Operates". That's substantial. I could use an "About the role" or "Role description" section. The rules say use `

  ` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I need to decide which headings to use based on actual content. - "Responsibilities": The "Why this role exists" and "This role will morph over time but will largely focus on:" section contains responsibilities/duties. I can put that under a Responsibilities section or similar. - "Requirements": The "What We're Looking For" section has requirements. It lists years, skills, experience, etc. - "Qualifications": Similar to Requirements. The rule says use `

  • ` for any list of duties/requirements/benefits. I could combine Requirements and Qualifications, or use one heading. The rule says include a section ONLY when the posting has real, specific content. Both have specific content. I might need to decide whether to split them or combine. The examples given: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I think I can use some of these, but only if there's real content. I'll need to be careful not to create thin sections. - "Skills": The "What We're Looking For" has skills listed: "Deep, hands-on fluency with AI", "Zero-to-one experience", "Experiment-minded", "Deep customer empathy", "Thinks deeply, communicates clearly, writes well", "Strong sense of ownership", "Cultural fit". That's substantive. - "Benefits": The posting has "Competitive salary and meaningful equity. We'll talk specifics once we know it's a real mutual fit." That's about compensation/benefits. But the rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It also says: "Prefer a few substantive sections over many thin ones." And: "never emit a heading followed by filler/placeholder text". The benefits section here is very brief: "Competitive salary and meaningful equity. We'll talk specifics once we know it's a real mutual fit." Is that enough to warrant a "Benefits" section? It's specific but sparse. I could fold it into a short `

    ` or include it in a "Compensation" section, but the rule says don't create Pay/Schedule/Benefits unless the posting actually states them. It does state them, but minimally. I need to decide. The rule also says: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should include the compensation info, but maybe not as a dedicated "Benefits" heading if it's too thin. I could put it in a short `

    ` or under a "Compensation" heading, but the allowed headings are the ones listed. I'll see. - "Pay": Similar to Benefits. The posting says "Competitive salary and meaningful equity. We'll talk specifics once we know it's a real mutual fit." No specific numbers. The rule says never create Pay section unless the posting actually states them. It states "competitive salary" but no details. I think I should not create a "Pay" section because it would be thin/filler. The rule is strict: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, but vaguely. I'll interpret "actually states them" as having meaningful content, not just "competitive salary". I'll fold it into a `

    ` maybe. - "Schedule": The posting has "In person, five