Senior Product Manager
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we need to map our sections to these headings? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those generic headings if applicable, but we can also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they want us to use those exact headings when appropriate. But we have content like "About Accumulus Technologies" (company description) maybe map to "About the role"? Actually "About the role" is a heading for role overview. The posting includes "Role Overview". Could map to "About the role". Then sections like "Product Strategy and Ownership" etc could be under "Responsibilities". "Required Qualifications" under "Requirements" or "Qualifications". "Compensation And Benefits" under "Benefits" and maybe "Pay". "Schedule" maybe not present.
We must not repeat the job title as a heading. The job title is "Senior Product Manager". Not to be used.
We must not put Job ID/requisition numbers as headings.
We must preserve all substantive information, remove boilerplate.
We must include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text.
We need to output only HTML fragment, no /, no markdown fences.
Thus we need to decide which sections to include.
We have:
- About Accumulus Technologies (company description) -> could be "About the role"? Actually "About the role" is more about role overview. But we have "Role Overview". Could map to "About the role". We'll put that content under About the role
with paragraphs.
- Responsibilities: we have many sections describing responsibilities: Product Strategy and Ownership, Discovery and Validation, AI Product Leadership..., User Experience..., Product Outcomes..., Execution and Delivery, Market, Regulatory, and Adoption Leadership. We can combine them under a single Responsibilities
with - items each summarizing? But we must preserve ALL substantive information; cannot summarize away detail. If we combine into list items, we need to keep the detail. Could use
for each responsibility section, but then we need headings? The instruction says use
for section headings (e.g., About the role, Responsibilities, Requirements...). It doesn't forbid using other headings like ? It says use for section headings (e.g., About the role, Responsibilities...). Likely they expect only those headings, and content under them in
or
- . So we should not create additional headings like "Product Strategy and Ownership". Instead we should embed that content under the appropriate generic heading (Responsibilities). But we must preserve all detail; we can put paragraphs under Responsibilities that contain the detailed text.
Thus we will have:
About the role
Role Overview ... (the paragraph)
Then Responsibilities
We need to include all responsibility details. Could break into multiple paragraphs each covering a responsibility area. That's fine.
Then
Requirements
(or Qualifications). The posting has "Required Qualifications" and "Strongly Preferred". We could combine under Requirements (or Qualifications). Use Requirements
and list items for each bullet.
Then Benefits
(maybe also Pay). The posting has "Compensation And Benefits" with base salary, bonus, 401k, insurance, vacation, parental leave. So we can have Benefits
with - items. Also Pay maybe separate but we can include salary under Benefits. The instruction says include Pay section only if posting actually states them. It does state base salary and bonus. Could create
Pay
with salary and bonus. But also Benefits section for other benefits. However they said prefer a few substantive sections over many thin ones. So maybe combine Pay and Benefits into one Benefits section. But they gave example headings including Pay and Benefits separate. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation and benefits, so we could have both Pay and Benefits sections. But to avoid many thin sections, we could combine. However they said "Prefer a few substantive sections over many thin ones." So maybe better to have one Benefits section that includes pay and other benefits. But they gave Pay as an example heading; but not required to use it if we combine. I'd lean to combine into Benefits.
We also have no schedule info, so omit Schedule.
Thus final HTML:
About the role
Role Overview The Senior Product Manager will independently own complex, ambiguous product areas end to end—from identifying and validating the right problems to setting product direction, guiding delivery, driving adoption, and iterating based on evidence. You will work directly with global health authorities, life sciences sponsors, regulatory operations professionals, internal subject matter experts, and Technology teams to uncover meaningful problems and develop scalable solutions. You will be expected to exercise strong product judgment, make clear recommendations—including when not to build—and remain accountable for whether the product changes user behavior and creates business value. This is a hands-on role for a product leader who can move fluidly between strategy, customer discovery, rapid prototyping, analytics, and execution in a complex, regulated enterprise environment.
Responsibilities
Product Strategy and Ownership: Independently own one or more strategic product areas, translating broad company goals into a clear product direction, and execution plan. Develop a deep understanding of regulatory engagements, user workflows, market dynamics, and the technical and compliance constraints that shape the Accumulus Platform. Frame ambiguous opportunities, evaluate alternatives, make principled prioritization decisions, and provide clear recommendations about what to build, what not to build, and why. Continuously assess product direction based on user evidence, business priorities, platform strategy, technical feasibility, risk, and market change. Articulate the value and future direction of the platform to internal leaders, customers, partners, and other market-facing audiences.
Discovery and Validation: Lead discovery directly with regulator, and sponsor users to uncover underlying needs, behaviors, constraints, and opportunities rather than relying on stated requirements alone. Design and execute research plans, interviews, workflow studies, experiments, and concept tests that reduce uncertainty and test the most important product hypotheses. Rapidly prototype possible solutions, place them in front of users, synthesize what is learned, and recommend whether and how Accumulus should proceed. Combine qualitative insight, product data, market evidence, and technical input to make well-reasoned product decisions before and after launch. Build trusted relationships with users and stakeholders while maintaining independent product judgment.
AI Product Leadership and AI-Native Ways of Working: Identify where AI can create meaningful user and business value, and distinguish those opportunities from use cases where AI would add unnecessary complexity or risk. Lead discovery and validation of AI-enabled workflows with regulators and customers, with explicit attention to accuracy, trust, transparency, explainability, human oversight, privacy, security, and quality. Partner with Technology and other stakeholders on build, buy, or partner decisions; model and data considerations; evaluation approaches; and the path from prototype to production. Use AI fluently and responsibly in day-to-day product work, including research synthesis, analysis, product requirements, rapid prototyping, product analytics, and communication. Help establish product practices for evaluating, monitoring, and improving AI-enabled capabilities after launch.
User Experience And Product Quality: Own the clarity, usability, and coherence of the end-to-end product experience; do not treat UX quality as a separate team's responsibility. Use modern prototyping tools, including Figma and AI-assisted tools, to explore workflows quickly, gather feedback, and iterate before committing to development. Translate discovery findings into intuitive workflows, interaction requirements, and implementation-ready product artifacts. Work closely with frontend engineers and other Technology partners throughout implementation to preserve product intent and ensure a high-quality user experience. Apply strong product and UX judgment without needing to be a visual designer.
Product Outcomes and Analytics: Define clear success measures for product initiatives, including adoption, engagement, workflow, quality, and business outcomes. Partner with Technology and analytics stakeholders to ensure the product is instrumented appropriately and that the team can understand how users behave. Monitor adoption and usage, investigate where expected behavior change is or is not occurring, and combine quantitative and qualitative evidence to determine next steps. Use post-launch learning to improve the product, inform investment decisions, and determine whether to iterate, scale, reposition, or stop an initiative.
Execution and Delivery: Translate validated product direction into clear epics, user stories, workflows, acceptance criteria, and supporting artifacts that enable effective engineering execution. Partner closely with Engineering in an agile environment to prioritize and refine the backlog, clarify intent, make scope and sequencing tradeoffs, and unblock delivery. Identify cross-team dependencies, technical and product risks, and decision points early; present practical mitigation options and make timely tradeoffs. Work in partnership with program management and business operations to support predictable, high-quality delivery across teams. Ensure product issues identified during development or after release are understood, prioritized, and resolved appropriately.
Market, Regulatory, and Adoption Leadership: Stay informed about relevant regulatory expectations, industry standards, and market developments, and work with regulatory, legal, security, privacy, and quality partners to shape compliant solutions. Serve as a product subject matter expert for internal teams, customers, prospective customers, partners, and market-facing communications. Collaborate with product marketing, customer success, commercial, and operations teams on positioning, launch planning, enablement, adoption, and scalable operating processes. Identify future growth opportunities and differentiated value propositions that advance Accumulus' mission and platform strategy.
Requirements
- Bachelor's degree or commensurate experience.
- Seven or more years of product management experience, including a proven record of independently leading complex enterprise software products or product areas from discovery through delivery and iteration.
- Five or more years of experience with enterprise SaaS platforms or supporting software in complex organizational environments.
- Demonstrated strength in customer discovery, problem framing, hypothesis development, rapid experimentation, prototyping, and evidence-based product decision-making.
- Strong product and UX judgment, with the ability to define coherent workflows and create prototypes without relying on a dedicated Product Designer.
- Experience defining product success measures, partnering on instrumentation, analyzing adoption and usage behavior, and using qualitative and quantitative evidence to guide decisions.
- Demonstrated AI-native ways of working and a practical understanding of the opportunities, limitations, risks, and responsible design considerations associated with AI-enabled products.
- Strong technical fluency and the ability to collaborate effectively with Engineering on architecture, integrations, data, security, scalability, and delivery tradeoffs.
- Experience shipping complex software through agile development processes while balancing user value, business outcomes, technical feasibility, compliance, and delivery risk.
- Excellent written, verbal, facilitation, and formal presentation skills, including the
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they want us to use those exact headings when appropriate. But we have content like "About Accumulus Technologies" (company description) maybe map to "About the role"? Actually "About the role" is a heading for role overview. The posting includes "Role Overview". Could map to "About the role". Then sections like "Product Strategy and Ownership" etc could be under "Responsibilities". "Required Qualifications" under "Requirements" or "Qualifications". "Compensation And Benefits" under "Benefits" and maybe "Pay". "Schedule" maybe not present.
We must not repeat the job title as a heading. The job title is "Senior Product Manager". Not to be used.
We must not put Job ID/requisition numbers as headings.
We must preserve all substantive information, remove boilerplate.
We must include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text.
We need to output only HTML fragment, no /, no markdown fences.
Thus we need to decide which sections to include.
We have:
- About Accumulus Technologies (company description) -> could be "About the role"? Actually "About the role" is more about role overview. But we have "Role Overview". Could map to "About the role". We'll put that content under About the role
with paragraphs.
- Responsibilities: we have many sections describing responsibilities: Product Strategy and Ownership, Discovery and Validation, AI Product Leadership..., User Experience..., Product Outcomes..., Execution and Delivery, Market, Regulatory, and Adoption Leadership. We can combine them under a single Responsibilities
with - items each summarizing? But we must preserve ALL substantive information; cannot summarize away detail. If we combine into list items, we need to keep the detail. Could use
for each responsibility section, but then we need headings? The instruction says use
for section headings (e.g., About the role, Responsibilities, Requirements...). It doesn't forbid using other headings like ? It says use for section headings (e.g., About the role, Responsibilities...). Likely they expect only those headings, and content under them in
or
- . So we should not create additional headings like "Product Strategy and Ownership". Instead we should embed that content under the appropriate generic heading (Responsibilities). But we must preserve all detail; we can put paragraphs under Responsibilities that contain the detailed text.
Thus we will have:
About the role
Role Overview ... (the paragraph)
Then Responsibilities
We need to include all responsibility details. Could break into multiple paragraphs each covering a responsibility area. That's fine.
Then
Requirements
(or Qualifications). The posting has "Required Qualifications" and "Strongly Preferred". We could combine under Requirements (or Qualifications). Use Requirements
and list items for each bullet.
Then Benefits
(maybe also Pay). The posting has "Compensation And Benefits" with base salary, bonus, 401k, insurance, vacation, parental leave. So we can have Benefits
with - items. Also Pay maybe separate but we can include salary under Benefits. The instruction says include Pay section only if posting actually states them. It does state base salary and bonus. Could create
Pay
with salary and bonus. But also Benefits section for other benefits. However they said prefer a few substantive sections over many thin ones. So maybe combine Pay and Benefits into one Benefits section. But they gave example headings including Pay and Benefits separate. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation and benefits, so we could have both Pay and Benefits sections. But to avoid many thin sections, we could combine. However they said "Prefer a few substantive sections over many thin ones." So maybe better to have one Benefits section that includes pay and other benefits. But they gave Pay as an example heading; but not required to use it if we combine. I'd lean to combine into Benefits.
We also have no schedule info, so omit Schedule.
Thus final HTML:
About the role
Role Overview The Senior Product Manager will independently own complex, ambiguous product areas end to end—from identifying and validating the right problems to setting product direction, guiding delivery, driving adoption, and iterating based on evidence. You will work directly with global health authorities, life sciences sponsors, regulatory operations professionals, internal subject matter experts, and Technology teams to uncover meaningful problems and develop scalable solutions. You will be expected to exercise strong product judgment, make clear recommendations—including when not to build—and remain accountable for whether the product changes user behavior and creates business value. This is a hands-on role for a product leader who can move fluidly between strategy, customer discovery, rapid prototyping, analytics, and execution in a complex, regulated enterprise environment.
Responsibilities
Product Strategy and Ownership: Independently own one or more strategic product areas, translating broad company goals into a clear product direction, and execution plan. Develop a deep understanding of regulatory engagements, user workflows, market dynamics, and the technical and compliance constraints that shape the Accumulus Platform. Frame ambiguous opportunities, evaluate alternatives, make principled prioritization decisions, and provide clear recommendations about what to build, what not to build, and why. Continuously assess product direction based on user evidence, business priorities, platform strategy, technical feasibility, risk, and market change. Articulate the value and future direction of the platform to internal leaders, customers, partners, and other market-facing audiences.
Discovery and Validation: Lead discovery directly with regulator, and sponsor users to uncover underlying needs, behaviors, constraints, and opportunities rather than relying on stated requirements alone. Design and execute research plans, interviews, workflow studies, experiments, and concept tests that reduce uncertainty and test the most important product hypotheses. Rapidly prototype possible solutions, place them in front of users, synthesize what is learned, and recommend whether and how Accumulus should proceed. Combine qualitative insight, product data, market evidence, and technical input to make well-reasoned product decisions before and after launch. Build trusted relationships with users and stakeholders while maintaining independent product judgment.
AI Product Leadership and AI-Native Ways of Working: Identify where AI can create meaningful user and business value, and distinguish those opportunities from use cases where AI would add unnecessary complexity or risk. Lead discovery and validation of AI-enabled workflows with regulators and customers, with explicit attention to accuracy, trust, transparency, explainability, human oversight, privacy, security, and quality. Partner with Technology and other stakeholders on build, buy, or partner decisions; model and data considerations; evaluation approaches; and the path from prototype to production. Use AI fluently and responsibly in day-to-day product work, including research synthesis, analysis, product requirements, rapid prototyping, product analytics, and communication. Help establish product practices for evaluating, monitoring, and improving AI-enabled capabilities after launch.
User Experience And Product Quality: Own the clarity, usability, and coherence of the end-to-end product experience; do not treat UX quality as a separate team's responsibility. Use modern prototyping tools, including Figma and AI-assisted tools, to explore workflows quickly, gather feedback, and iterate before committing to development. Translate discovery findings into intuitive workflows, interaction requirements, and implementation-ready product artifacts. Work closely with frontend engineers and other Technology partners throughout implementation to preserve product intent and ensure a high-quality user experience. Apply strong product and UX judgment without needing to be a visual designer.
Product Outcomes and Analytics: Define clear success measures for product initiatives, including adoption, engagement, workflow, quality, and business outcomes. Partner with Technology and analytics stakeholders to ensure the product is instrumented appropriately and that the team can understand how users behave. Monitor adoption and usage, investigate where expected behavior change is or is not occurring, and combine quantitative and qualitative evidence to determine next steps. Use post-launch learning to improve the product, inform investment decisions, and determine whether to iterate, scale, reposition, or stop an initiative.
Execution and Delivery: Translate validated product direction into clear epics, user stories, workflows, acceptance criteria, and supporting artifacts that enable effective engineering execution. Partner closely with Engineering in an agile environment to prioritize and refine the backlog, clarify intent, make scope and sequencing tradeoffs, and unblock delivery. Identify cross-team dependencies, technical and product risks, and decision points early; present practical mitigation options and make timely tradeoffs. Work in partnership with program management and business operations to support predictable, high-quality delivery across teams. Ensure product issues identified during development or after release are understood, prioritized, and resolved appropriately.
Market, Regulatory, and Adoption Leadership: Stay informed about relevant regulatory expectations, industry standards, and market developments, and work with regulatory, legal, security, privacy, and quality partners to shape compliant solutions. Serve as a product subject matter expert for internal teams, customers, prospective customers, partners, and market-facing communications. Collaborate with product marketing, customer success, commercial, and operations teams on positioning, launch planning, enablement, adoption, and scalable operating processes. Identify future growth opportunities and differentiated value propositions that advance Accumulus' mission and platform strategy.
Requirements
- Bachelor's degree or commensurate experience.
- Seven or more years of product management experience, including a proven record of independently leading complex enterprise software products or product areas from discovery through delivery and iteration.
- Five or more years of experience with enterprise SaaS platforms or supporting software in complex organizational environments.
- Demonstrated strength in customer discovery, problem framing, hypothesis development, rapid experimentation, prototyping, and evidence-based product decision-making.
- Strong product and UX judgment, with the ability to define coherent workflows and create prototypes without relying on a dedicated Product Designer.
- Experience defining product success measures, partnering on instrumentation, analyzing adoption and usage behavior, and using qualitative and quantitative evidence to guide decisions.
- Demonstrated AI-native ways of working and a practical understanding of the opportunities, limitations, risks, and responsible design considerations associated with AI-enabled products.
- Strong technical fluency and the ability to collaborate effectively with Engineering on architecture, integrations, data, security, scalability, and delivery tradeoffs.
- Experience shipping complex software through agile development processes while balancing user value, business outcomes, technical feasibility, compliance, and delivery risk.
- Excellent written, verbal, facilitation, and formal presentation skills, including the
for each responsibility section, but then we need headings? The instruction says use
for section headings (e.g., About the role, Responsibilities, Requirements...). It doesn't forbid using other headings like ? It says use for section headings (e.g., About the role, Responsibilities...). Likely they expect only those headings, and content under them in
for section headings (e.g., About the role, Responsibilities...). Likely they expect only those headings, and content under them in
or
- . So we should not create additional headings like "Product Strategy and Ownership". Instead we should embed that content under the appropriate generic heading (Responsibilities). But we must preserve all detail; we can put paragraphs under Responsibilities that contain the detailed text.
Thus we will have:
About the role
Role Overview ... (the paragraph)
ThenResponsibilities
We need to include all responsibility details. Could break into multipleparagraphs each covering a responsibility area. That's fine. Then
Requirements
(or Qualifications). The posting has "Required Qualifications" and "Strongly Preferred". We could combine under Requirements (or Qualifications). UseRequirements
and list items for each bullet. ThenBenefits
(maybe also Pay). The posting has "Compensation And Benefits" with base salary, bonus, 401k, insurance, vacation, parental leave. So we can haveBenefits
with- items. Also Pay maybe separate but we can include salary under Benefits. The instruction says include Pay section only if posting actually states them. It does state base salary and bonus. Could create
Pay
with salary and bonus. But also Benefits section for other benefits. However they said prefer a few substantive sections over many thin ones. So maybe combine Pay and Benefits into one Benefits section. But they gave example headings including Pay and Benefits separate. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation and benefits, so we could have both Pay and Benefits sections. But to avoid many thin sections, we could combine. However they said "Prefer a few substantive sections over many thin ones." So maybe better to have one Benefits section that includes pay and other benefits. But they gave Pay as an example heading; but not required to use it if we combine. I'd lean to combine into Benefits. We also have no schedule info, so omit Schedule. Thus final HTML:About the role
Role Overview The Senior Product Manager will independently own complex, ambiguous product areas end to end—from identifying and validating the right problems to setting product direction, guiding delivery, driving adoption, and iterating based on evidence. You will work directly with global health authorities, life sciences sponsors, regulatory operations professionals, internal subject matter experts, and Technology teams to uncover meaningful problems and develop scalable solutions. You will be expected to exercise strong product judgment, make clear recommendations—including when not to build—and remain accountable for whether the product changes user behavior and creates business value. This is a hands-on role for a product leader who can move fluidly between strategy, customer discovery, rapid prototyping, analytics, and execution in a complex, regulated enterprise environment.
Responsibilities
Product Strategy and Ownership: Independently own one or more strategic product areas, translating broad company goals into a clear product direction, and execution plan. Develop a deep understanding of regulatory engagements, user workflows, market dynamics, and the technical and compliance constraints that shape the Accumulus Platform. Frame ambiguous opportunities, evaluate alternatives, make principled prioritization decisions, and provide clear recommendations about what to build, what not to build, and why. Continuously assess product direction based on user evidence, business priorities, platform strategy, technical feasibility, risk, and market change. Articulate the value and future direction of the platform to internal leaders, customers, partners, and other market-facing audiences.
Discovery and Validation: Lead discovery directly with regulator, and sponsor users to uncover underlying needs, behaviors, constraints, and opportunities rather than relying on stated requirements alone. Design and execute research plans, interviews, workflow studies, experiments, and concept tests that reduce uncertainty and test the most important product hypotheses. Rapidly prototype possible solutions, place them in front of users, synthesize what is learned, and recommend whether and how Accumulus should proceed. Combine qualitative insight, product data, market evidence, and technical input to make well-reasoned product decisions before and after launch. Build trusted relationships with users and stakeholders while maintaining independent product judgment.
AI Product Leadership and AI-Native Ways of Working: Identify where AI can create meaningful user and business value, and distinguish those opportunities from use cases where AI would add unnecessary complexity or risk. Lead discovery and validation of AI-enabled workflows with regulators and customers, with explicit attention to accuracy, trust, transparency, explainability, human oversight, privacy, security, and quality. Partner with Technology and other stakeholders on build, buy, or partner decisions; model and data considerations; evaluation approaches; and the path from prototype to production. Use AI fluently and responsibly in day-to-day product work, including research synthesis, analysis, product requirements, rapid prototyping, product analytics, and communication. Help establish product practices for evaluating, monitoring, and improving AI-enabled capabilities after launch.
User Experience And Product Quality: Own the clarity, usability, and coherence of the end-to-end product experience; do not treat UX quality as a separate team's responsibility. Use modern prototyping tools, including Figma and AI-assisted tools, to explore workflows quickly, gather feedback, and iterate before committing to development. Translate discovery findings into intuitive workflows, interaction requirements, and implementation-ready product artifacts. Work closely with frontend engineers and other Technology partners throughout implementation to preserve product intent and ensure a high-quality user experience. Apply strong product and UX judgment without needing to be a visual designer.
Product Outcomes and Analytics: Define clear success measures for product initiatives, including adoption, engagement, workflow, quality, and business outcomes. Partner with Technology and analytics stakeholders to ensure the product is instrumented appropriately and that the team can understand how users behave. Monitor adoption and usage, investigate where expected behavior change is or is not occurring, and combine quantitative and qualitative evidence to determine next steps. Use post-launch learning to improve the product, inform investment decisions, and determine whether to iterate, scale, reposition, or stop an initiative.
Execution and Delivery: Translate validated product direction into clear epics, user stories, workflows, acceptance criteria, and supporting artifacts that enable effective engineering execution. Partner closely with Engineering in an agile environment to prioritize and refine the backlog, clarify intent, make scope and sequencing tradeoffs, and unblock delivery. Identify cross-team dependencies, technical and product risks, and decision points early; present practical mitigation options and make timely tradeoffs. Work in partnership with program management and business operations to support predictable, high-quality delivery across teams. Ensure product issues identified during development or after release are understood, prioritized, and resolved appropriately.
Market, Regulatory, and Adoption Leadership: Stay informed about relevant regulatory expectations, industry standards, and market developments, and work with regulatory, legal, security, privacy, and quality partners to shape compliant solutions. Serve as a product subject matter expert for internal teams, customers, prospective customers, partners, and market-facing communications. Collaborate with product marketing, customer success, commercial, and operations teams on positioning, launch planning, enablement, adoption, and scalable operating processes. Identify future growth opportunities and differentiated value propositions that advance Accumulus' mission and platform strategy.
Requirements
- Bachelor's degree or commensurate experience.
- Seven or more years of product management experience, including a proven record of independently leading complex enterprise software products or product areas from discovery through delivery and iteration.
- Five or more years of experience with enterprise SaaS platforms or supporting software in complex organizational environments.
- Demonstrated strength in customer discovery, problem framing, hypothesis development, rapid experimentation, prototyping, and evidence-based product decision-making.
- Strong product and UX judgment, with the ability to define coherent workflows and create prototypes without relying on a dedicated Product Designer.
- Experience defining product success measures, partnering on instrumentation, analyzing adoption and usage behavior, and using qualitative and quantitative evidence to guide decisions.
- Demonstrated AI-native ways of working and a practical understanding of the opportunities, limitations, risks, and responsible design considerations associated with AI-enabled products.
- Strong technical fluency and the ability to collaborate effectively with Engineering on architecture, integrations, data, security, scalability, and delivery tradeoffs.
- Experience shipping complex software through agile development processes while balancing user value, business outcomes, technical feasibility, compliance, and delivery risk.
- Excellent written, verbal, facilitation, and formal presentation skills, including the
- items. Also Pay maybe separate but we can include salary under Benefits. The instruction says include Pay section only if posting actually states them. It does state base salary and bonus. Could create