Senior Product Manager
for section headings. Use - for lists. Use
for prose.
We must not repeat job title as heading. No Job ID.
We must not create sections with filler like "commensurate with experience". Not present.
We need to decide which sections to include:
- About the role: maybe a brief description of the role (THE ROLE). Could be a paragraph.
- Responsibilities: from WHAT YOU'LL ACTUALLY DO (list of duties). Could be bullet list.
- Requirements/Qualifications/Skills: Could combine? The instruction says separate sections possible but we should only include if real content. Could have Requirements (must-haves) and Skills (nice-to-have). Or Qualifications (must-haves) and Skills (nice-to-have). We'll decide.
- Benefits: Not mentioned explicitly. No benefits described. So omit Benefits.
- Pay: Not mentioned. Omit.
- Schedule: Working Context mentions US-based, some travel to client sites and HatchWorks office locations may be required. That's schedule/travel info. Could be a short paragraph.
Thus sections: About the role, Responsibilities, Requirements (must-haves), Skills (nice-to-have), Schedule.
We need to ensure we don't create empty sections.
Let's extract content.
About the role: THE ROLE paragraph: "Most product managers ship features. Few have shipped AI systems that operational users trust enough to use every cycle. We're looking for a Senior Product Manager to own the product for a workstream inside one of our enterprise AI engagements — across forecasting, optimization, knowledge engineering, or user-facing interfaces. You will own backlog, sprint cadence, and the adoption outcomes for that workstream, partnering with a Principal PM or engagement lead on the broader program. This is not a feature-list role. You will work directly with client stakeholders and a delivery team of five-plus engineers and designers, making trade-offs daily about scope, sequencing, and what's worth shipping in the next sprint. If you've shipped AI products that actually move metrics — this is the role."
We can put that as
.
Responsibilities: WHAT YOU'LL ACTUALLY DO bullet points (though it's prose with line breaks). We'll convert each sentence starting with a dash? Actually it's a list of duties separated by line breaks and em dashes? Let's parse:
- Own product strategy for your workstream inside a multi-quarter enterprise AI engagement — from discovery through steady-state.
- Own adoption success criteria for your workstream — the structured measures that determine whether the system is actually being used, not just shipped. You instrument them and report on them to the engagement lead.
- Run discovery — operator interviews, SME workshops, behavior-pattern analysis. Convert tribal knowledge into shippable requirements.
- Contribute to structured-feedback taxonomies with users and SMEs — the vocabulary that turns every user override into a model-retuning signal.
- Manage the backlog for your workstream — within forecasting, optimization, knowledge engineering, or user-facing UIs. Sequence ruthlessly.
- Day-to-day contact for your workstream — regular working relationship with business leads, SMEs, and operators.
- Partner with the client's product counterpart on your workstream — build trust, share context, support ownership transfer.
- Run sprint cadence — two-week sprints, sprint reviews, and reporting into the engagement's steering cadence.
- Trade off ruthlessly — cut scope that doesn't move the metric. Defer complexity until the data rewards it. Right-size investment.
- Flag Phase 2 opportunities to the engagement lead — additional scope, new use cases within your workstream. The engagement doesn't end; it converts.
- Operate with consulting rigor — build credibility fast with new stakeholders, adapt your working style to each client's culture and tools, and turn ambiguity into a structured recommendation you can defend in the room.
We'll make each as
- .
Requirements (Must-Haves): The section "THE TECHNICAL BAR" includes Must-Haves list:
- Enterprise PM — 5+ years shipping products inside mid-size to Fortune 500 enterprises
- AI / ML Product — 2+ years working on AI products in production — recommendation systems, forecasting, optimization, NLP
- Operational Software — Built products for operational users (planners, schedulers, ops teams) — not consumer apps
- Stakeholder Range — Comfortable engaging business leaders and individual operators in the same week
- Backlog & Cadence — Run sprint-level delivery for a workstream; defensible prioritization under pressure
- Data Literacy — Read model outputs, understand calibration, interpret optimization results
- Discovery Practice — Experience running structured discovery — interviews, shadowing, workshop facilitation
- Vendor / Partner Coordination — Comfortable in multi-vendor environments — SI partners, internal platform teams
- Consulting Experience — Proven track record working as an external consultant or in a client-services model — building trust quickly, managing ambiguity, and adapting across client environments
- Core Tech Stack — Tools & Methods
- Methods — Continuous discovery · Outcome-based roadmapping · RICE / WSJF prioritization
- Cadence — Scrum · Shape Up · Adapted hybrid models
- Tools — Notion · Linear / Jira · Miro / FigJam · Loom
- Analytics — Mixpanel · Amplitude · SQL competence
- Adjacent — Figma literacy · Comfort reading code and reviewing PRs
We need to preserve all. Could format as nested lists? The instruction: Use
- for any list of duties/requirements/benefits. So we can have top-level
for each requirement, and sublists for sub-items. That's okay.
Skills (Nice-to-Have): NICE TO HAVE list:
- Experience mentoring or supporting junior PMs
- Worked with knowledge graphs, semantic web, or rules-engine products
- Contributed to internal AI product playbooks or best practices
We'll make .
Schedule: WORKING CONTEXT: "US-based. Some travel to client sites and HatchWorks office locations may be required by engagement. You'll execute with clarity and pace — the engineers and designers on your workstream take cadence from you."
We can make a .
Also there is "THE HUMAN BAR" which includes skills like cadence skill, outcome obsession, ruthless prioritization, operator empathy, delivery ownership. Could be considered skills but we already have skills section; maybe we could incorporate into Skills? But we already have nice-to-have; human bar is more about attributes. Could be considered part of Skills (maybe as additional bullet). However we must not invent sections; we can include them under Skills if we want. But we already have a Skills section for nice-to-have; we could add these as additional bullet points under Skills (maybe separate list). However the instruction: Prefer a few substantive sections over many thin ones. Could combine nice-to-have and human bar into Skills section. But we need to preserve all info. Let's create Skills section that includes both nice-to-have and human bar attributes.
But we must not duplicate. Let's extract human bar:
- Cadence skill is necessary.
- Outcome obsession is the differentiator.
- The product managers who thrive here cut scope that doesn't move the metric — and they're willing to defend that decision to clients who want everything.
- They run delivery like a craft, and they treat adoption as the only acceptable definition of done.
- Outcome obsession — ship-feature is not a goal. Move-metric is. You distinguish between the two every day.
- Ruthless prioritization — every sprint is a series of trade-offs. You make them, you defend them, you adjust them.
- Operator empathy — you spend time with the people who'll use what you ship. Tribal knowledge becomes spec.
- Delivery ownership — you own your workstream from discovery to handoff, in partnership with the engagement lead.
These are more like desired traits/skills. We'll include them as bullet points under Skills.
Thus Skills section will have two sublists: Nice-to-have (experience) and Human bar (traits). Could combine into one list but better to keep separate subheadings? However we cannot add extra headings beyond the allowed section headings? The instruction only says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings inside sections, but to be safe we can just have a single with all skill-related bullets, mixing nice-to-have and human bar. That preserves all.
Let's compile.
Now produce HTML fragment:
About the role
Most product managers ship features. Few have shipped AI systems that operational users trust enough to use every cycle. We're looking for a Senior Product Manager to own the product for a workstream inside one of our enterprise AI engagements — across forecasting, optimization, knowledge engineering, or user-facing interfaces. You will own backlog, sprint cadence, and the adoption outcomes for that workstream, partnering with a Principal PM or engagement lead on the broader program. This is not a feature-list role. You will work directly with client stakeholders and a delivery team of five-plus engineers and designers, making trade-offs daily about scope, sequencing, and what's worth shipping in the next sprint. If you've shipped AI products that actually move metrics — this is the role.
Responsibilities
- Own product strategy for your workstream inside a multi-quarter enterprise AI engagement — from discovery through steady-state.
- Own adoption success criteria for your workstream — the structured measures that determine whether the system is actually being used, not just shipped. You instrument them and report on them to the engagement lead.
- Run discovery — operator interviews, SME workshops, behavior-pattern analysis. Convert tribal knowledge into shippable requirements.
- Contribute to structured-feedback taxonomies with users and SMEs — the vocabulary that turns every user override into a model-retuning signal.
- Manage the backlog for your workstream — within forecasting, optimization, knowledge engineering, or user-facing UIs. Sequence ruthlessly.
- Day-to-day contact for your workstream — regular working relationship with business leads, SMEs, and operators.
- Partner with the client's product counterpart on your workstream — build trust, share context, support ownership transfer.
- Run sprint cadence — two-week sprints, sprint reviews, and reporting into the engagement's steering cadence.
- Trade off ruthlessly — cut scope that doesn't move the metric. Defer complexity until the data rewards it. Right-size investment.
- Flag Phase 2 opportunities to the engagement lead — additional scope, new use cases within your workstream. The engagement doesn't end; it converts.
- Operate with consulting rigor — build credibility fast with new stakeholders, adapt your working style to each client's culture and tools, and turn ambiguity into a structured recommendation you can defend in the room.
Requirements
- Enterprise PM — 5+
for prose. We must not repeat job title as heading. No Job ID. We must not create sections with filler like "commensurate with experience". Not present. We need to decide which sections to include: - About the role: maybe a brief description of the role (THE ROLE). Could be a paragraph. - Responsibilities: from WHAT YOU'LL ACTUALLY DO (list of duties). Could be bullet list. - Requirements/Qualifications/Skills: Could combine? The instruction says separate sections possible but we should only include if real content. Could have Requirements (must-haves) and Skills (nice-to-have). Or Qualifications (must-haves) and Skills (nice-to-have). We'll decide. - Benefits: Not mentioned explicitly. No benefits described. So omit Benefits. - Pay: Not mentioned. Omit. - Schedule: Working Context mentions US-based, some travel to client sites and HatchWorks office locations may be required. That's schedule/travel info. Could be a short paragraph. Thus sections: About the role, Responsibilities, Requirements (must-haves), Skills (nice-to-have), Schedule. We need to ensure we don't create empty sections. Let's extract content. About the role: THE ROLE paragraph: "Most product managers ship features. Few have shipped AI systems that operational users trust enough to use every cycle. We're looking for a Senior Product Manager to own the product for a workstream inside one of our enterprise AI engagements — across forecasting, optimization, knowledge engineering, or user-facing interfaces. You will own backlog, sprint cadence, and the adoption outcomes for that workstream, partnering with a Principal PM or engagement lead on the broader program. This is not a feature-list role. You will work directly with client stakeholders and a delivery team of five-plus engineers and designers, making trade-offs daily about scope, sequencing, and what's worth shipping in the next sprint. If you've shipped AI products that actually move metrics — this is the role." We can put that as
. Responsibilities: WHAT YOU'LL ACTUALLY DO bullet points (though it's prose with line breaks). We'll convert each sentence starting with a dash? Actually it's a list of duties separated by line breaks and em dashes? Let's parse: - Own product strategy for your workstream inside a multi-quarter enterprise AI engagement — from discovery through steady-state. - Own adoption success criteria for your workstream — the structured measures that determine whether the system is actually being used, not just shipped. You instrument them and report on them to the engagement lead. - Run discovery — operator interviews, SME workshops, behavior-pattern analysis. Convert tribal knowledge into shippable requirements. - Contribute to structured-feedback taxonomies with users and SMEs — the vocabulary that turns every user override into a model-retuning signal. - Manage the backlog for your workstream — within forecasting, optimization, knowledge engineering, or user-facing UIs. Sequence ruthlessly. - Day-to-day contact for your workstream — regular working relationship with business leads, SMEs, and operators. - Partner with the client's product counterpart on your workstream — build trust, share context, support ownership transfer. - Run sprint cadence — two-week sprints, sprint reviews, and reporting into the engagement's steering cadence. - Trade off ruthlessly — cut scope that doesn't move the metric. Defer complexity until the data rewards it. Right-size investment. - Flag Phase 2 opportunities to the engagement lead — additional scope, new use cases within your workstream. The engagement doesn't end; it converts. - Operate with consulting rigor — build credibility fast with new stakeholders, adapt your working style to each client's culture and tools, and turn ambiguity into a structured recommendation you can defend in the room. We'll make each as
- for any list of duties/requirements/benefits. So we can have top-level
- for each requirement, and sublists for sub-items. That's okay.
Skills (Nice-to-Have): NICE TO HAVE list:
- Experience mentoring or supporting junior PMs
- Worked with knowledge graphs, semantic web, or rules-engine products
- Contributed to internal AI product playbooks or best practices
We'll make
- Own product strategy for your workstream inside a multi-quarter enterprise AI engagement — from discovery through steady-state.
- Own adoption success criteria for your workstream — the structured measures that determine whether the system is actually being used, not just shipped. You instrument them and report on them to the engagement lead.
- Run discovery — operator interviews, SME workshops, behavior-pattern analysis. Convert tribal knowledge into shippable requirements.
- Contribute to structured-feedback taxonomies with users and SMEs — the vocabulary that turns every user override into a model-retuning signal.
- Manage the backlog for your workstream — within forecasting, optimization, knowledge engineering, or user-facing UIs. Sequence ruthlessly.
- Day-to-day contact for your workstream — regular working relationship with business leads, SMEs, and operators.
- Partner with the client's product counterpart on your workstream — build trust, share context, support ownership transfer.
- Run sprint cadence — two-week sprints, sprint reviews, and reporting into the engagement's steering cadence.
- Trade off ruthlessly — cut scope that doesn't move the metric. Defer complexity until the data rewards it. Right-size investment.
- Flag Phase 2 opportunities to the engagement lead — additional scope, new use cases within your workstream. The engagement doesn't end; it converts.
- Operate with consulting rigor — build credibility fast with new stakeholders, adapt your working style to each client's culture and tools, and turn ambiguity into a structured recommendation you can defend in the room.
- Enterprise PM — 5+
- .
Schedule: WORKING CONTEXT: "US-based. Some travel to client sites and HatchWorks office locations may be required by engagement. You'll execute with clarity and pace — the engineers and designers on your workstream take cadence from you."
We can make a
. Also there is "THE HUMAN BAR" which includes skills like cadence skill, outcome obsession, ruthless prioritization, operator empathy, delivery ownership. Could be considered skills but we already have skills section; maybe we could incorporate into Skills? But we already have nice-to-have; human bar is more about attributes. Could be considered part of Skills (maybe as additional bullet). However we must not invent sections; we can include them under Skills if we want. But we already have a Skills section for nice-to-have; we could add these as additional bullet points under Skills (maybe separate list). However the instruction: Prefer a few substantive sections over many thin ones. Could combine nice-to-have and human bar into Skills section. But we need to preserve all info. Let's create Skills section that includes both nice-to-have and human bar attributes. But we must not duplicate. Let's extract human bar: - Cadence skill is necessary. - Outcome obsession is the differentiator. - The product managers who thrive here cut scope that doesn't move the metric — and they're willing to defend that decision to clients who want everything. - They run delivery like a craft, and they treat adoption as the only acceptable definition of done. - Outcome obsession — ship-feature is not a goal. Move-metric is. You distinguish between the two every day. - Ruthless prioritization — every sprint is a series of trade-offs. You make them, you defend them, you adjust them. - Operator empathy — you spend time with the people who'll use what you ship. Tribal knowledge becomes spec. - Delivery ownership — you own your workstream from discovery to handoff, in partnership with the engagement lead. These are more like desired traits/skills. We'll include them as bullet points under Skills. Thus Skills section will have two sublists: Nice-to-have (experience) and Human bar (traits). Could combine into one list but better to keep separate subheadings? However we cannot add extra headings beyond the allowed section headings? The instruction only says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings inside sections, but to be safe we can just have a single
- with all skill-related bullets, mixing nice-to-have and human bar. That preserves all.
Let's compile.
Now produce HTML fragment:
About the role
Most product managers ship features. Few have shipped AI systems that operational users trust enough to use every cycle. We're looking for a Senior Product Manager to own the product for a workstream inside one of our enterprise AI engagements — across forecasting, optimization, knowledge engineering, or user-facing interfaces. You will own backlog, sprint cadence, and the adoption outcomes for that workstream, partnering with a Principal PM or engagement lead on the broader program. This is not a feature-list role. You will work directly with client stakeholders and a delivery team of five-plus engineers and designers, making trade-offs daily about scope, sequencing, and what's worth shipping in the next sprint. If you've shipped AI products that actually move metrics — this is the role.
Responsibilities
Requirements