Director of Product Execution
for headings, - for any list of duties/requirements/benefits, and
for prose.
We need to decide what is a list vs prose. The "What You'll Do" is a list of bullet points (each starting with a verb). We'll turn each into
- . Similarly "What You'll Bring" includes bullet-like sentences but not explicitly bulleted; we can treat each sentence as list item? The instruction: Use
- for any list of duties/requirements/benefits. So we need to identify lists. The posting has bullet-like lines but not marked with bullets. We could still treat each line as list item. Safer to treat them as
- . For prose sections like overview, we use
.
We must not repeat the job title as a heading. The job title is Director of Product Execution. Not to be used as heading.
We must not put Job ID/requisition numbers as headings; none present.
We must output only HTML fragment.
Let's extract content.
Overview (About the role):
"At LegitScript, we are passionate about making the internet and payment ecosystems safer and more transparent. We help companies of all sizes keep their services legal and safe for consumers. To do this, LegitScript combines big data with the world’s leading team of experts skilled in highly regulated and complex sectors, including transaction laundering detection, pharmaceuticals, online gambling, and more. The result? Unmatched accuracy and deep risk analysis that identifies which commercial entities play by the rules, and which do not. Our diverse industry partnerships provide unique insights that keep businesses and governments at the forefront of emerging trends. That’s why LegitScript is trusted by the world's largest search engines, internet platforms, payment companies, and regulatory agencies."
Then maybe a sentence: "Overview Strategy is worth what gets delivered. At LegitScript, the Director of Product Execution owns that delivery." Actually the text: "Overview Strategy is worth what gets delivered. At LegitScript, the Director of Product Execution owns that delivery." Might be part of overview. We'll include that as prose.
Now Responsibilities (What You'll Do):
List items:
- Own the portfolio view: what is committed, what is in flight, what is at risk, and what has been deliberately deferred.
- Own the prioritization process end to end, including the cadence, the criteria, and the forum where bets are ranked and the outcome is published.
- Set and hold the readiness bar for work entering the plan: a defined problem, an intended outcome, a measure, an owner, and both signatures.
- Drive scope discipline, breaking large bets into increments that deliver value on their own and retiring work that no longer earns its place.
- Identify and resolve cross-squad dependencies, sequencing conflicts, and capacity contention before they become delivery risk.
- Own the operating cadence for product, including planning, prioritization, roadmap review, launch readiness, and retrospectives.
- Run launches end to end from the product side, including readiness, enablement, communication, and post-launch measurement.
- Lead, coach, and grow the product management team, owning hiring, performance, and career development.
- Set the standard for product craft, including problem definition, discovery, requirements, and success metrics.
- Review product managers' work and give feedback that raises the standard, from sharper problem statements to clearer requirements.
- Define and track execution metrics, including delivery predictability, cycle time, scope change, and effort spent on abandoned work.
- Report progress to engineering leadership, the strategy organization, and the executive team with clarity and a clear point of view.
Now Requirements/Qualifications/Skills.
"What You'll Bring" paragraph:
"8+ years in product management, including 3+ years leading product managers or product teams.
A track record of delivering complex B2B software, ideally in SaaS, fintech, regtech, compliance, trust and safety, or another domain where accuracy and defensibility matter as much as speed.
Demonstrated ownership of a multi-team product portfolio, including sequencing work with visible cross-team dependencies and managing capacity across competing demands.
Experience running a prioritization process across competing domains, with an output trusted by the teams whose work was deferred as well as the teams whose work was chosen.
Experience executing a strategy you did not author, converting direction from strategy owners into delivered, measured outcomes.
Experience partnering with an engineering counterpart as a peer, with a clean boundary between product intent and technical execution.
Fluency in modern delivery practice, including incremental delivery, iterative planning, and release approaches that get value to customers early.
Enough technical depth to engage credibly with architecture and platform trade-offs, and the judgment not to mistake that for owning them.
Strong analytical practice, including defining delivery and outcome metrics, instrumenting for them, and changing course when the data says to.
Excellent written communication, with the ability to make a complex trade-off legible to an executive, an engineer, and a customer in the same document.
Comfort operating through change, including establishing durable operating practices where none exist and improving them without disrupting delivery.
A four-year college degree or a comparable blend of education and experience. We value practical skills, a strong work ethic, and a passion for learning, regardless of formal education"
Then "Preferred Experience in products that combine software automation with expert human review.
Domain experience in payments, healthcare, pharmaceuticals, supplements, financial crime, marketplaces, or advertising platforms.
Experience with platform, API, or integration products serving enterprise partners.
Experience establishing product operating discipline in an organization that did not previously have it."
Then "We succeed together, care deeply, stay curious, and inspire trust — and we look for those qualities in the people we hire."
Then benefits: "LegitScript offers competitive compensation, flexible work options, and a team that's genuinely invested in your success."
We need to split into sections: Requirements, Qualifications, Skills maybe.
We could treat "What You'll Bring" as Requirements (mandatory) and "Preferred Experience" as Qualifications or Skills. But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (mandatory), Qualifications (preferred), Skills (maybe specific skills like analytical, written communication). However we risk duplication. Better to have Requirements (mandatory + preferred) and Skills (specific skills). But we must not create thin sections with filler. Let's see content: we have many items that are experience/requirements. We could put all under Requirements. Then Skills could be empty -> we should not include Skills section if no specific skill list beyond what's already in Requirements. However we have items like "Strong analytical practice", "Excellent written communication", "Comfort operating through change". Those could be considered skills. But they are already in the list. If we make a Skills section, we would duplicate content. Better to have only Requirements section covering all, and Benefits section. Avoid Qualifications if we don't have separate distinct content. But we have "Preferred Experience" which could be Qualifications. That is distinct from mandatory requirements. So we can have Requirements (mandatory) and Qualifications (preferred). Skills maybe not needed.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
Check if any content for Benefits: yes.
Now we need to format.
We'll produce:
About the role
...overview...
Responsibilities
- ... each responsibility ...
...
Requirements
- 8+ years in product management, including 3+ years leading product managers or product teams.
- A track record of delivering complex B2B software, ideally in SaaS, fintech, regtech, compliance, trust and safety, or another domain where accuracy and defensibility matter as much as speed.
- Demonstrated ownership of a multi-team product portfolio, including sequencing work with visible cross-team dependencies and managing capacity across competing demands.
- Experience running a prioritization process across competing domains, with an output trusted by the teams whose work was deferred as well as the teams whose work was chosen.
- Experience executing a strategy you did not author, converting direction from strategy owners into delivered, measured outcomes.
- Experience partnering with an engineering counterpart as a peer, with a clean boundary between product intent and technical execution.
- Fluency in modern delivery practice, including incremental delivery, iterative planning, and release approaches that get value to customers early.
- Enough technical depth to engage credibly with architecture and platform trade-offs, and the judgment not to mistake that for owning them.
- Strong analytical practice, including defining delivery and outcome metrics, instrumenting for them, and changing course when the data says to.
- Excellent written communication, with the ability to make a complex trade-off legible to an executive, an engineer, and a customer in the same document.
- Comfort operating through change, including establishing durable operating practices where none exist and improving them without disrupting delivery.
- A four-year college degree or a comparable blend of education and experience. We value practical skills, a strong work ethic, and a passion for learning, regardless of formal education.
Qualifications
- Preferred experience in products that combine software automation with expert human review.
- Domain experience in payments, healthcare, pharmaceuticals, supplements, financial crime, marketplaces, or advertising platforms.
- Experience with platform, API, or integration products serving enterprise partners.
- Experience establishing product operating discipline in an organization that did not previously have it.
Benefits
- Competitive compensation
- Flexible work options
- A team that's genuinely invested in your success
We must not include Pay or Schedule sections.
Check for any boilerplate leftover: we removed visa sponsorship, international remote work, unsolicited applications, etc. Also removed the disclaimer about job description not comprehensive, etc. Also removed "We succeed together, care deeply, stay curious, and inspire trust — and we look for those qualities in the people we hire." That's a bit fluffy but could be considered part of Qualifications? It's more about culture; maybe we could include it as a separate paragraph under Benefits? But it's not a benefit
for prose. We need to decide what is a list vs prose. The "What You'll Do" is a list of bullet points (each starting with a verb). We'll turn each into
- for any list of duties/requirements/benefits. So we need to identify lists. The posting has bullet-like lines but not marked with bullets. We could still treat each line as list item. Safer to treat them as
- . For prose sections like overview, we use
. We must not repeat the job title as a heading. The job title is Director of Product Execution. Not to be used as heading. We must not put Job ID/requisition numbers as headings; none present. We must output only HTML fragment. Let's extract content. Overview (About the role): "At LegitScript, we are passionate about making the internet and payment ecosystems safer and more transparent. We help companies of all sizes keep their services legal and safe for consumers. To do this, LegitScript combines big data with the world’s leading team of experts skilled in highly regulated and complex sectors, including transaction laundering detection, pharmaceuticals, online gambling, and more. The result? Unmatched accuracy and deep risk analysis that identifies which commercial entities play by the rules, and which do not. Our diverse industry partnerships provide unique insights that keep businesses and governments at the forefront of emerging trends. That’s why LegitScript is trusted by the world's largest search engines, internet platforms, payment companies, and regulatory agencies." Then maybe a sentence: "Overview Strategy is worth what gets delivered. At LegitScript, the Director of Product Execution owns that delivery." Actually the text: "Overview Strategy is worth what gets delivered. At LegitScript, the Director of Product Execution owns that delivery." Might be part of overview. We'll include that as prose. Now Responsibilities (What You'll Do): List items: - Own the portfolio view: what is committed, what is in flight, what is at risk, and what has been deliberately deferred. - Own the prioritization process end to end, including the cadence, the criteria, and the forum where bets are ranked and the outcome is published. - Set and hold the readiness bar for work entering the plan: a defined problem, an intended outcome, a measure, an owner, and both signatures. - Drive scope discipline, breaking large bets into increments that deliver value on their own and retiring work that no longer earns its place. - Identify and resolve cross-squad dependencies, sequencing conflicts, and capacity contention before they become delivery risk. - Own the operating cadence for product, including planning, prioritization, roadmap review, launch readiness, and retrospectives. - Run launches end to end from the product side, including readiness, enablement, communication, and post-launch measurement. - Lead, coach, and grow the product management team, owning hiring, performance, and career development. - Set the standard for product craft, including problem definition, discovery, requirements, and success metrics. - Review product managers' work and give feedback that raises the standard, from sharper problem statements to clearer requirements. - Define and track execution metrics, including delivery predictability, cycle time, scope change, and effort spent on abandoned work. - Report progress to engineering leadership, the strategy organization, and the executive team with clarity and a clear point of view. Now Requirements/Qualifications/Skills. "What You'll Bring" paragraph: "8+ years in product management, including 3+ years leading product managers or product teams. A track record of delivering complex B2B software, ideally in SaaS, fintech, regtech, compliance, trust and safety, or another domain where accuracy and defensibility matter as much as speed. Demonstrated ownership of a multi-team product portfolio, including sequencing work with visible cross-team dependencies and managing capacity across competing demands. Experience running a prioritization process across competing domains, with an output trusted by the teams whose work was deferred as well as the teams whose work was chosen. Experience executing a strategy you did not author, converting direction from strategy owners into delivered, measured outcomes. Experience partnering with an engineering counterpart as a peer, with a clean boundary between product intent and technical execution. Fluency in modern delivery practice, including incremental delivery, iterative planning, and release approaches that get value to customers early. Enough technical depth to engage credibly with architecture and platform trade-offs, and the judgment not to mistake that for owning them. Strong analytical practice, including defining delivery and outcome metrics, instrumenting for them, and changing course when the data says to. Excellent written communication, with the ability to make a complex trade-off legible to an executive, an engineer, and a customer in the same document. Comfort operating through change, including establishing durable operating practices where none exist and improving them without disrupting delivery. A four-year college degree or a comparable blend of education and experience. We value practical skills, a strong work ethic, and a passion for learning, regardless of formal education" Then "Preferred Experience in products that combine software automation with expert human review. Domain experience in payments, healthcare, pharmaceuticals, supplements, financial crime, marketplaces, or advertising platforms. Experience with platform, API, or integration products serving enterprise partners. Experience establishing product operating discipline in an organization that did not previously have it." Then "We succeed together, care deeply, stay curious, and inspire trust — and we look for those qualities in the people we hire." Then benefits: "LegitScript offers competitive compensation, flexible work options, and a team that's genuinely invested in your success." We need to split into sections: Requirements, Qualifications, Skills maybe. We could treat "What You'll Bring" as Requirements (mandatory) and "Preferred Experience" as Qualifications or Skills. But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (mandatory), Qualifications (preferred), Skills (maybe specific skills like analytical, written communication). However we risk duplication. Better to have Requirements (mandatory + preferred) and Skills (specific skills). But we must not create thin sections with filler. Let's see content: we have many items that are experience/requirements. We could put all under Requirements. Then Skills could be empty -> we should not include Skills section if no specific skill list beyond what's already in Requirements. However we have items like "Strong analytical practice", "Excellent written communication", "Comfort operating through change". Those could be considered skills. But they are already in the list. If we make a Skills section, we would duplicate content. Better to have only Requirements section covering all, and Benefits section. Avoid Qualifications if we don't have separate distinct content. But we have "Preferred Experience" which could be Qualifications. That is distinct from mandatory requirements. So we can have Requirements (mandatory) and Qualifications (preferred). Skills maybe not needed. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Check if any content for Benefits: yes. Now we need to format. We'll produce:
About the role
...overview...
Responsibilities
- ... each responsibility ... ...
Requirements
- 8+ years in product management, including 3+ years leading product managers or product teams.
- A track record of delivering complex B2B software, ideally in SaaS, fintech, regtech, compliance, trust and safety, or another domain where accuracy and defensibility matter as much as speed.
- Demonstrated ownership of a multi-team product portfolio, including sequencing work with visible cross-team dependencies and managing capacity across competing demands.
- Experience running a prioritization process across competing domains, with an output trusted by the teams whose work was deferred as well as the teams whose work was chosen.
- Experience executing a strategy you did not author, converting direction from strategy owners into delivered, measured outcomes.
- Experience partnering with an engineering counterpart as a peer, with a clean boundary between product intent and technical execution.
- Fluency in modern delivery practice, including incremental delivery, iterative planning, and release approaches that get value to customers early.
- Enough technical depth to engage credibly with architecture and platform trade-offs, and the judgment not to mistake that for owning them.
- Strong analytical practice, including defining delivery and outcome metrics, instrumenting for them, and changing course when the data says to.
- Excellent written communication, with the ability to make a complex trade-off legible to an executive, an engineer, and a customer in the same document.
- Comfort operating through change, including establishing durable operating practices where none exist and improving them without disrupting delivery.
- A four-year college degree or a comparable blend of education and experience. We value practical skills, a strong work ethic, and a passion for learning, regardless of formal education.
Qualifications
- Preferred experience in products that combine software automation with expert human review.
- Domain experience in payments, healthcare, pharmaceuticals, supplements, financial crime, marketplaces, or advertising platforms.
- Experience with platform, API, or integration products serving enterprise partners.
- Experience establishing product operating discipline in an organization that did not previously have it.
Benefits
- Competitive compensation
- Flexible work options
- A team that's genuinely invested in your success
- . For prose sections like overview, we use