Senior Product Manager, Forward Deployed Platform

We need to output HTML fragment with sections as per rules. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, duplicated lines, application instructions, EEO, etc. Keep substantive info. We need to parse the posting. Key sections: - About MGT Insurance (company description) maybe "About the role"? Actually "About the role" heading is for description of role. The posting includes "About MGT Insurance" then description of role. We'll treat that as "About the role" maybe. Or we could have "About the role" containing the description of MGT and role. - Responsibilities: The "What You Own" bullet list: Partner delight, Implementation outcomes, Closing the gap yourself, The playbook, Feeding the platform. Also "What Great Looks Like" maybe part of responsibilities or qualifications? It describes success metrics. Could be under Responsibilities or Qualifications. We'll treat as Responsibilities. - Requirements: Minimum Requirements (all TPM Roles) bullet list: shipped meaningful work with AI engineering tool, public GitHub, 5+ years experience at scale firm ideally InsureTech/FinTech/Consulting, build things directly. - Qualifications: Role-Specific Qualifications bullet list: led complex implementations, talk through lessons, Insurance Depth, Partner-facing judgement, Productizing instinct, Growth stage experience, References from peer department managers. - Skills: Not explicitly listed; maybe we can infer from responsibilities: AI tooling, coding, data analysis, PRD writing, etc. But we should not invent. If no explicit skills section, we should not create one. - Benefits: Not mentioned besides compensation? There's compensation section: "Compensation $190,000 - $300,000 annual base salary, plus bonus and equity." That's Pay. Benefits not mentioned. So we include Pay section. - Schedule: Not mentioned. So omit. - Also there is a note about not accepting unsolicited resumes etc - that's boilerplate/application instructions, remove. - Also "We recognize that no candidate will meet every qualification..." appears twice; we can keep once maybe but it's not substantive? It's a statement encouraging applicants; could be considered boilerplate but it's repeated. Might be okay to keep once? The instruction: remove duplicated lines. So we should keep only one instance. - Also "Our Commitment to Diversity, Equity & Inclusion" and EEO statement: remove as boilerplate. - Also "This job description is intended to outline..." remove. Thus we produce sections: About the role, Responsibilities, Requirements, Qualifications, Pay. Check if any other sections like Skills: maybe we can extract from responsibilities: "write compelling PRDs and then execute, directly contributing code, analyzing data in our warehouse". That's skills but not explicit heading. We could create a Skills section if we have explicit list; but we don't have a list. Safer to omit Skills. Now format: Use

for each section heading. Then content: For prose use

. For lists use

• . We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like "Partner delight. Implementations don’t succeed on timelines alone. Ship great solutions on time, but invest in relationships with our platform partners over the long haul as their success is our success." etc. We need to keep bullet points exactly as in text, maybe rephrase slightly? Must preserve meaning. We'll copy sentences. Let's extract content. About the role: Combine MGT description and role overview. From posting: "About MGT Insurance MGT is the first AI-driven, neo-insurer focused on evolving commercial P&C insurance for the brokers and small business owners. By combining the expertise of industry veterans with state-of-the-art technology, we are ushering in the next evolution of commercial insurance and working to move the industry forward through the use of modern technology, better processes, and a rock-star team. We seek visionary leaders who thrive in dynamic, entrepreneurial settings, and excel in autonomous roles. MGT's Platform team brings our AI-native insurance stack to partners: carriers, MGAs, and programs whose workflows never fit a standard configuration on the first try. We're hiring a Forward Deployed Product Manager to lead those implementations from kickoff to live, working in a cross functional pod with an Insurance, Operations, and Data talent. You sit with the partner, understand what their workflow actually needs, close the gap with code, configuration, and persuasion, and then turn what you learned into platform features so the next implementation is faster. This is not a roadmap-and-jira role, and it is not project management. Product and engineering lanes are merging at MGT, and product talent operates fluidly across strategy, data, design, and engineering. PMs that succeed at MGT embrace end-to-end execution and lean into our comparative advantage: agility. You will write compelling PRDs and then execute, directly contributing code, analyzing data in our warehouse, and own results from concept through to post go live." That's the role description. We'll put that in

  maybe multiple paragraphs. Responsibilities: "What You Own" bullet list: - Partner delight. Implementations don’t succeed on timelines alone. Ship great solutions on time, but invest in relationships with our platform partners over the long haul as their success is our success. - Implementation outcomes. Lead partner implementations to live in a pod with IPM, Ops, and Data. You own the product decisions, the gap analysis between platform and partner workflow, and the go-live. - Closing the gap yourself. Configure, script, and build what the implementation needs, in code, with modern AI tooling, rather than filing it to a backlog and waiting. - The playbook. Turn each implementation into a written, reusable playbook. Drive cycle time down and prove it. - Feeding the platform. Convert recurring one-off customizations into productized platform features. You are the Platform team's highest-signal source of roadmap truth. Also "What Great Looks Like" could be considered responsibilities or qualifications; but it's more about success metrics. Might fit under Responsibilities as expected outcomes. We'll include as a separate bullet list under Responsibilities maybe. "What Great Looks Like": - Partners name you as the reason the go-live worked, and Engineering names you as the FDE who unblocked rather than escalated. - You've led three or more partner implementations to live, each with a written playbook that made the next one faster. - Implementation cycle time is trending down and you can show the chart, with the specific changes that moved it. - The top recurring customization requests from your implementations are on the Platform roadmap as productized features. - Your pod runs on evidence: partner workflow maps, data-backed gap analyses, and working prototypes instead of Gantt charts. We'll include these as responsibilities. Minimum Requirements (all TPM Roles): - You have shipped meaningful work (beyond simple prototypes) with an AI engineering tool (Claude Code, Codex, Devin, etc.) and can show us your public GitHub. - You have 5+ years of experience at a firm that achieved scale, ideally InsureTech, FinTech, or Consulting. - You build things directly. No agile coaches or scrum managers. Role-Specific Qualifications: - You've led complex implementations to live. You can talk through what has gone well and poorly on large custom implementations and how you took those lessons into subsequent projects. - Insurance Depth. FinTech or regulated industry experience helps, but direct experience in InsureTech or at a large carrier or brokerage is ideal. - Partner-facing judgement. You can say no to a partner gracefully, negotiate scope, and keep trust through a rough go-live. Partners trust you even if in conflict. - Productizing instinct. You've turned bespoke customer requests into platform features and can explain how you decided what to generalize. - Growth stage experience. MGT is a small, high-accountability organization and that's a plus for you. - References from peer department managers (Engineering, Ops, Partner leadership) that loved working with you. Compensation/Pay: - Compensation $190,000 - $300,000 annual base salary, plus bonus and equity. We need to ensure not to repeat duplicated lines: The phrase "We recognize that no candidate will meet every qualification and encourage individuals with relevant experience and interest in the role to apply." appears twice. We'll keep only one instance maybe after qualifications? But it's more like a statement encouraging applicants; could be considered boilerplate but it's not duplicated if we keep once. However it's not substantive detail about role; maybe we can drop it as it's more of a generic encouragement. The instruction: remove duplicated lines. It doesn't say to remove all such encouragement lines, but we could keep one. However it's not a section heading; we could place it in a

  under Qualifications or at end. But it's not really required. Safer to omit it entirely as it's not substantive detail about role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." This line is not substantive about role; it's a generic encouragement. Could be considered boilerplate. I'd remove it. Thus we will not include that line. Now produce HTML. Structure:

  About the role

  ... (maybe multiple paragraphs)

  Responsibilities

  • Partner delight. Implementations don’t succeed on timelines alone. Ship great solutions on time, but invest in relationships with our platform partners over the long haul as their success is our success.
  • Implementation outcomes. Lead partner implementations to live in a pod with IPM, Ops, and Data. You own the product decisions, the gap analysis between platform and partner workflow, and the go-live.
  • Closing the gap yourself. Configure, script, and build what the implementation needs, in code, with modern AI tooling, rather than filing it to a backlog and waiting.
  • The playbook. Turn each implementation into a written, reusable playbook. Drive cycle time down and prove it.
  • Feeding the platform. Convert recurring one-off customizations into productized platform features. You are the Platform team's highest-signal source of roadmap truth.
  • Partners name you as the reason the go-live worked, and Engineering names you as the FDE who unblocked rather than escalated.
  • You've led three or more partner implementations to live, each with a written playbook that made the next one faster.
  • Implementation cycle time is trending down and you can show the chart, with the specific changes that moved it.
  • The top recurring customization requests from your implementations are on the Platform roadmap as productized features.
  • Your pod runs on evidence: partner workflow maps, data-backed gap analyses, and working prototypes instead of Gantt charts.

  Requirements

  • You have shipped meaningful work (beyond simple prototypes) with an AI engineering tool (Claude Code, Codex, Devin, etc.) and can show us your public GitHub.
  • You have 5+ years of experience at a firm that achieved scale, ideally InsureTech, FinTech, or Consulting.
  • You build things directly. No agile coaches or scrum managers.

  Qualifications

  • You've led complex implementations to live. You can talk through what has gone well and poorly on large custom implementations and how you took those lessons into subsequent projects.
  • Insurance Depth. FinTech or regulated industry experience helps, but direct experience in InsureTech or at a large carrier or brokerage is ideal.
  • Partner-facing judgement. You can say no to a partner gracefully, negotiate scope, and keep trust through a rough go-live. Partners trust you even if in conflict.