Senior Product Manager

We need to output HTML fragment with sections: About the company, About the role, maybe sections like Product Judgment & Strategic Thinking etc. But we must follow rules: use

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

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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. We need to parse the job posting: It includes "About The Company", "About The Role", then many bullet-like paragraphs describing competencies, then "Core Requirements What We're Looking For" with bullet list of requirements, then "Important differentiators" list, then "Working Style & Culture Fit" paragraph. We need to produce sections: maybe "About the company", "About the role", "Responsibilities" (maybe combine the competencies as responsibilities), "Requirements" (core requirements), "Skills" (important differentiators), maybe "Working Style & Culture Fit" as a section? The rules say we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to these headings where appropriate. We should not create sections without real content. We have no explicit Benefits, Pay, Schedule info. So we should not include those sections. We have "About The Company" -> heading About the company (maybe "About the company"). We have "About The Role" -> heading About the role. Then we have a bunch of competencies like "Product Judgment & Strategic Thinking", "First Principles & Root Cause Thinking", etc. These could be considered responsibilities or qualifications. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have a "Responsibilities" section that lists those competencies as bullet points. Or we could have "Qualifications" for core requirements. But we also have "Important differentiators" which could be Skills. Thus propose sections: - About the company (paragraph) - About the role (paragraph) - Responsibilities (list of bullet points from the competencies) - Requirements (list from Core Requirements) - Skills (list from Important differentiators) - Working Style & Culture Fit (maybe as a paragraph under a heading like "Culture Fit" but not in allowed list; but we could incorporate into "About the role" or maybe not include as separate heading because not in list. However we could still include a heading if we want but the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

  for section headings (e.g. those). It might be okay to add other headings but better to stick to those. The "Working Style & Culture Fit" could be placed under "About the role" as a paragraph. We must not repeat the job title as a heading. No job title given explicitly but it's Senior Product Manager. We'll not include that. We must preserve all substantive information. So we need to include all the bullet points from competencies, core requirements, important differentiators, and the paragraphs. We need to format lists with

  • . For prose, use

    . We must not include duplicated lines. There's a duplicated "Systems Thinking" paragraph appears twice; we should include only once. We need to remove boilerplate: no cookie/navigation/legal/EEO etc. Not present. Now craft HTML. Structure:

    About the company

    PreVeil is a fast-growing tech company transforming secure communication and compliance for the modern enterprise. Our encrypted email and file sharing platform combines end-to-end encryption with a simple user experience and has been named PC Magazine's Best Encrypted Email and File Sharing Solution five years running. Trusted by more than 3,000 defense contractors, PreVeil has become the gold standard for protecting sensitive information and achieving compliance efficiently. We're profitable, growing 100% year-over-year, and building for the long term.

    About the role

    PreVeil is hiring a Senior Product Manager to own core product strategy, drive execution, and build exceptional user experiences across our portfolio. You’ll sit at the intersection of customer insight, product excellence, and business goals—defining what we build, why we build it, and how we ship it with speed and impact. Think like an owner: every feature is an investment, every problem demands first-principles rigor, and you’re constantly prioritizing resources to deliver maximum value to users and the business. This is a high-ownership role on a lean, fast-moving team empowered to solve hard product problems. You’ll move fast, dig deep to uncover real root causes, and rally engineering, design, and go-to-market teams around a clear, compelling vision. You won’t be doing it alone. You’ll collaborate closely with top-tier engineers, designers, and company leaders dedicated to building the future of secure and compliant communication and collaboration for the enterprise.

    Then responsibilities: list each competency as bullet. We have list: - Product Judgment & Strategic Thinking - Evaluate competing approaches rigorously, form a clear and well-reasoned point of view, and articulate tradeoffs with conviction - Define and own the product roadmap for your area — set direction, prioritize ruthlessly, and align the team around what matters most and why - Operate at both the strategic and tactical level: think in years, execute in weeks - First Principles & Root Cause Thinking - Dig beneath the surface of customer feedback and product problems to find the real underlying need, constraint, or opportunity - Relentlessly ask why until you understand what's actually true — not just what's visible or what's been assumed - Reason from fundamentals to reach better conclusions faster, especially in ambiguous or novel situations - Pattern Recognition & Connecting the Dots - Spot connections others miss — draw on a broad base of experience to recognize when a new problem rhymes with an old one - Connect signals across customers, market trends, and product gaps to form insight faster than the data alone would suggest - Synthesize across disparate inputs — user research, eng constraints, competitive dynamics, business goals — into a coherent picture - Deep Customer & Market Understanding - Develop a genuine, granular understanding of how customers think, work, and struggle — not just what they ask for - Build relationships with customers directly; bring the voice of the user into every product decision - Stay ahead of market trends and competitive dynamics to inform strategy and identify opportunities - Systems Thinking (only once) - Understand how different parts of the product connect and affect each other — design solutions that work across the whole, not just the immediate problem - Anticipate second-order effects of product decisions on users, engineering, and the business - Hold the full product architecture in mind while working on specific problems - Execution & Delivery Rigor - Drive initiatives from discovery through launch with focus, discipline, and follow-through - Break down complex problems into clear MVPs and iterative steps that ship with velocity and impact - Be the kind of PM engineering and design can build with confidently — reliable, unblocking, and always moving things forward - Leadership, Motivation & Collaboration - Lead and motivate without formal authority — earn trust and followership through clarity of vision, genuine respect, and consistency - Keep the team aligned and energized through ambiguity, setbacks, and competing priorities - Partner closely with engineering, design, and go-to-market as a true peer — not a ticket writer or gatekeeper - Communication & Written Clarity - Communicate with precision and confidence across audiences — customers, engineers, designers, and leadership - Write sharp, clear product specs that reduce ambiguity and accelerate execution - Distill complex technical and strategic topics into language anyone can act on We need to ensure we don't duplicate any bullet. Also note there is a repeated "Systems Thinking" block; we include once. Now Requirements: list from "Core Requirements What We're Looking For". The bullet points: - 7+ years of product management experience, with a track record of owning products end-to-end — strategy through launch through business outcomes - Enterprise B2B SaaS, collaboration or productivity software experience strongly preferred - Demonstrated ability to deeply understand customers and translate that understanding into product decisions - Strong product instincts — you know what good looks like and can explain why - First principles thinker who digs to root causes and doesn't accept surface-level answers - Systems thinker who understands how product decisions ripple across the product, users, and the business - Growth mindset and genuine curiosity — you lead with questions, learn fast, and are truly open to feedback - Exceptional communicator — clear in writing, sharp in meetings, compelling to leadership - High-execution PM who drives things to completion and is deeply reliable - Leads and motivates without authority — earns trust through vision, respect, and consistency - Collaborative, low-ego, and maker-first — you thrive in a small team and take direction well Now Important differentiators list: - Strong technical fluency — fluent in APIs, system architecture, and technical tradeoffs; can hold your own in engineering discussions - Familiarity with admin and end-user personas in enterprise software - Data-informed — uses quantitative metrics and qualitative research together, not one or the other - Ability to prototype ideas quickly using AI-assisted tools, or similar to validate and communicate concepts early - Actively uses AI as a force multiplier — e.g. research synthesis, written artifacts, prioritization analysis, and process efficiency - Pattern recognition — connects dots across customers, market signals, and product gaps faster than the data alone suggests - Comfort operating in ambiguity with a strong bias for action Now Working Style & Culture Fit paragraph: "This role is for someone who thinks rigorously and executes relentlessly — someone who earns the trust of their team through clarity, consistency, and care. You'll be joining a small team that moves fast and expects a lot, but also invests deeply in doing things right. We Value A strong point of view, formed through genuine investigation and held with intellectual honestySpeed and decisiveness, paired with the rigor to know when to slow down and go deeperPeople who make the team around them sharper, more aligned, and more motivatedThe kind of reliability that means you don't have to be asked twice — and the judgment to know when to ask for help" We need to format as prose; maybe split into sentences for readability but keep as

    . Could be one paragraph. Now we must not include any filler like "commensurate with experience". Not present. Now produce HTML. We need to ensure we use

    for each section heading. We'll output:

    About the company

    ...

    About the role

    ...

    Responsibilities

    • ... (each bullet as
    • containing the sub-bullets? Actually each main competency could be a
    • with inner
      for subpoints. But spec says use
      • for any list of duties