Senior Product Operations Manager
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real content. The posting includes company description (About Tekmetric) maybe not exactly "About the role". The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those as examples, but we can use appropriate headings. Likely we should use headings like "About Tekmetric", "Working the Tekmetric Way", "What You'll Do", "What You'll Bring", "Why You'll Love Working With Us". However they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests they expect those specific headings if content exists. But we can adapt: If we have content about the role, we could use "About the role". But the posting has "About Tekmetric" (company overview) not exactly role. Could treat as "About the role"? Might be okay to use "About Tekmetric" as heading? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but gives examples. Safer to use those exact headings when applicable. Let's map:
- About the role: we have company description and culture; could be considered "About the role". We'll put that content under About the role
.
- Responsibilities: we have "What You'll Do" with bullet list.
- Requirements/Qualifications/Skills: we have "What You'll Bring" includes years experience, statistical methods, etc. Could split into Requirements and Qualifications and Skills. But we can combine into one section maybe "Requirements". However instruction: prefer a few substantive sections over many thin ones. So we could have one section for qualifications/requirements/skills. Use heading maybe "Requirements". Or "Qualifications". Choose one. Let's use "Requirements". It covers experience, skills, etc.
- Benefits: we have "Why You'll Love Working With Us" includes health, wellness, 401k, etc. So Benefits
.
- Pay: not present, omit.
- Schedule: not present (though hybrid/remote and travel expectations could be considered schedule? But they said only create Schedule if posting actually states them. It mentions hybrid/remote work models, travel expected, offsites attendance expected. That is about work arrangement, could be considered schedule. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state hybrid/remote work models, travel expected, offsites. That is about work arrangement, maybe schedule. But the heading "Schedule" might be appropriate. However they gave examples of Schedule as a heading. The posting does mention hybrid/remote work models, travel expected, offsites. That is about work location and expectations, not exactly schedule (hours). Might be considered schedule. Safer to include a Schedule section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state hybrid/remote work models, travel expected, offsites. So we could include Schedule. But we already have Benefits. Could we incorporate those details into Benefits? Probably not; they are work arrangement. Let's create a Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip the EEO statement, fraud warnings, etc. Also remove "Tekmetric is an equal opportunity employer..." and the fraud warning paragraphs. Also remove "Please contact us to request accommodation." etc. Also remove "Tekmetric will never ask for your personal financial..." etc. Also remove "All legitimate Tekmetric job postings are listed at tekmetric.com/careers." etc. Also remove recruiter communications line. Also remove "Please visit this link for further information Fraudulent Job Offers". So we keep only the substantive content: company description, culture, what you'll do, what you'll bring, why you'll love working with us (benefits), and maybe schedule details (hybrid/remote, travel, offsites). Also note the line "At Tekmetric, great work happens anywhere, but great teams are built through intentional connection. We offer hybrid and remote work models based on your proximity to our office hubs. Because we value in-person collaboration, travel is an expected part of every role. We come together several times a year for team and company-wide offsites to align on goals and strengthen relationships. Attendance at these events is expected and fully supported." That's schedule/work arrangement.
Now we need to format.
Let's extract content:
About Tekmetric paragraph(s):
"Tekmetric is the all-in-one, cloud-based software helping auto repair shops run smarter, grow faster, and serve customers better. Built by a shop owner and shaped by the needs of the industry, Tekmetric brings together innovation, real-world experience, and a thriving community to help shops thrive - not just survive. From running a shop, to securing payments to engaging customers, our platform simplifies operations so shop owners can focus on what really matters: delivering exceptional service, earning trust, and growing sustainably. Officially founded in Houston in 2017, Tekmetric has grown from a single shop’s vision to the industry’s leading solution - all by staying true to our values of transparency, integrity, innovation, and a service-first mindset. But we’re not just building shop management software. We’re building a movement. We’re empowering repair shops to rise above the daily grind, create meaningful connections with their customers, and lead the industry forward - one interaction at a time. Come build with us. Join the journey. Shape the future of auto repair."
Working the Tekmetric Way paragraph(s):
"At Tekmetric, we’re building a culture where winning matters - not for ego, but because when our customers win, we win together. We move fast, stay curious, and take full ownership of our results — no excuses, no finger-pointing. If you thrive in ambiguity, take initiative, and view honest feedback as fuel for growth, you’ll feel right at home here. We’re direct but respectful, ambitious yet grounded, and collaborative at every level. Everyone leads through impact and is encouraged to speak up, share ideas, and challenge assumptions (even your manager’s). This is a place for builders, not bystanders. Success here takes focus, follow-through, and a willingness to roll up your sleeves — but if you’re driven by meaningful work and real results, it’s deeply rewarding. You’ll join a team that cares about the work, supports one another, and takes smart risks to achieve bold goals. Be yourself, stay mission-focused, and you’ll thrive. If that energizes you, we can’t wait to meet you."
Then schedule/hybrid remote paragraph:
"At Tekmetric, great work happens anywhere, but great teams are built through intentional connection. We offer hybrid and remote work models based on your proximity to our office hubs. Because we value in-person collaboration, travel is an expected part of every role. We come together several times a year for team and company-wide offsites to align on goals and strengthen relationships. Attendance at these events is expected and fully supported."
What You'll Do (Responsibilities) includes several paragraphs and bullet-like sentences. We need to turn into
- for any list of duties/requirements/benefits. The responsibilities are described in paragraphs with bullet-like sentences starting with verbs. We can convert each sentence into a list item. Let's list them:
- Metrics Program Design & Outcome Modeling
- Partner with product leadership to design and evolve Tekmetric's product metrics program, contributing to what we measure, why it matters, and how metrics connect to the outcomes the business is trying to drive.
- Build and maintain a multi-variable outcome model that captures the relationships between product inputs and business results across retention, revenue, customer health, and engagement.
- Apply statistical methods, including regression, correlation analysis, and predictive modeling, to validate metric definitions and ensure the model reflects how the business actually works, not just what's easy to measure.
- Contribute to the frameworks, taxonomies, and standards that make metrics consistent, trustworthy, and actionable across product and leadership.
- Insights & Analytics
- Conduct proactive, deep-dive analyses to uncover customer behavior trends, product usage patterns, friction points, and revenue-impact opportunities.
- Deliver strategic insights that inform prioritization, roadmap decisions, and OKRs, not just findings, but clear recommendations with a point of view on what to do next and why it matters.
- Translate data into compelling narratives for executive reviews, board decks, and product planning cycles.
- Manage your own backlog of analytical work, identifying what needs attention, setting priorities, and closing the loop with stakeholders on what was learned and what it means.
- Enablement & Data Democratization
- Develop easy-to-use dashboards, templates, and toolkits that empower PMs and cross-functional teams to self-serve insights.
- Train stakeholders on how to interpret and leverage product data to make better decisions.
- Standardize reporting practices across product teams, ensuring consistency and clarity.
- Data Infrastructure & Collaboration
- Partner with Engineering and Data teams to define and maintain event tracking, taxonomy standards, and data governance practices across the product.
- Ensure data accuracy, completeness, and consistency to support strategic product decisions.
- Build and maintain core product metrics, dashboards, and self-service data models within the existing analytics stack (Looker, Pendo, Mixpanel, Redshift).
We could keep headings inside responsibilities? But we only need to output HTML fragment; we could include
Responsibilities
then a with - items. The subheadings could be or just part of li text. Probably fine to include them as part of li.
What You'll Bring (Requirements) includes bullet-like sentences:
- 5-8+ years in Product Operations, Product Analytics, Business Intelligence, or related roles.
- Genuine foundation in statistical methods, including regression, correlation, and predictive modeling. This is the one area where we're not looking for someone who will learn on the job; you need to bring it.
- Exposure to analytics or metrics program work. You've seen what a well-built program looks like and you're ready to help build one, not just operate within one that already exists.
- Track record of translating complex data into actionable recommendations that influenced product and business decisions.
- Experience working in SaaS or platform products is strongly preferred.
- Strong command of SQL and proficiency with modern BI/analytics tools (Looker preferred).
- Fluency with AI tools as a core part of how you work. You use AI to synthesize, analyze, and scale your output, and you think about how to structure data and workflows to take advantage of it.
- A communicator who can answer "so what?" without being asked. You know how to find the right stakeholders,
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests they expect those specific headings if content exists. But we can adapt: If we have content about the role, we could use "About the role". But the posting has "About Tekmetric" (company overview) not exactly role. Could treat as "About the role"? Might be okay to use "About Tekmetric" as heading? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but gives examples. Safer to use those exact headings when applicable. Let's map:
- About the role: we have company description and culture; could be considered "About the role". We'll put that content under About the role
.
- Responsibilities: we have "What You'll Do" with bullet list.
- Requirements/Qualifications/Skills: we have "What You'll Bring" includes years experience, statistical methods, etc. Could split into Requirements and Qualifications and Skills. But we can combine into one section maybe "Requirements". However instruction: prefer a few substantive sections over many thin ones. So we could have one section for qualifications/requirements/skills. Use heading maybe "Requirements". Or "Qualifications". Choose one. Let's use "Requirements". It covers experience, skills, etc.
- Benefits: we have "Why You'll Love Working With Us" includes health, wellness, 401k, etc. So Benefits
.
- Pay: not present, omit.
- Schedule: not present (though hybrid/remote and travel expectations could be considered schedule? But they said only create Schedule if posting actually states them. It mentions hybrid/remote work models, travel expected, offsites attendance expected. That is about work arrangement, could be considered schedule. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state hybrid/remote work models, travel expected, offsites. That is about work arrangement, maybe schedule. But the heading "Schedule" might be appropriate. However they gave examples of Schedule as a heading. The posting does mention hybrid/remote work models, travel expected, offsites. That is about work location and expectations, not exactly schedule (hours). Might be considered schedule. Safer to include a Schedule section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state hybrid/remote work models, travel expected, offsites. So we could include Schedule. But we already have Benefits. Could we incorporate those details into Benefits? Probably not; they are work arrangement. Let's create a Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip the EEO statement, fraud warnings, etc. Also remove "Tekmetric is an equal opportunity employer..." and the fraud warning paragraphs. Also remove "Please contact us to request accommodation." etc. Also remove "Tekmetric will never ask for your personal financial..." etc. Also remove "All legitimate Tekmetric job postings are listed at tekmetric.com/careers." etc. Also remove recruiter communications line. Also remove "Please visit this link for further information Fraudulent Job Offers". So we keep only the substantive content: company description, culture, what you'll do, what you'll bring, why you'll love working with us (benefits), and maybe schedule details (hybrid/remote, travel, offsites). Also note the line "At Tekmetric, great work happens anywhere, but great teams are built through intentional connection. We offer hybrid and remote work models based on your proximity to our office hubs. Because we value in-person collaboration, travel is an expected part of every role. We come together several times a year for team and company-wide offsites to align on goals and strengthen relationships. Attendance at these events is expected and fully supported." That's schedule/work arrangement.
Now we need to format.
Let's extract content:
About Tekmetric paragraph(s):
"Tekmetric is the all-in-one, cloud-based software helping auto repair shops run smarter, grow faster, and serve customers better. Built by a shop owner and shaped by the needs of the industry, Tekmetric brings together innovation, real-world experience, and a thriving community to help shops thrive - not just survive. From running a shop, to securing payments to engaging customers, our platform simplifies operations so shop owners can focus on what really matters: delivering exceptional service, earning trust, and growing sustainably. Officially founded in Houston in 2017, Tekmetric has grown from a single shop’s vision to the industry’s leading solution - all by staying true to our values of transparency, integrity, innovation, and a service-first mindset. But we’re not just building shop management software. We’re building a movement. We’re empowering repair shops to rise above the daily grind, create meaningful connections with their customers, and lead the industry forward - one interaction at a time. Come build with us. Join the journey. Shape the future of auto repair."
Working the Tekmetric Way paragraph(s):
"At Tekmetric, we’re building a culture where winning matters - not for ego, but because when our customers win, we win together. We move fast, stay curious, and take full ownership of our results — no excuses, no finger-pointing. If you thrive in ambiguity, take initiative, and view honest feedback as fuel for growth, you’ll feel right at home here. We’re direct but respectful, ambitious yet grounded, and collaborative at every level. Everyone leads through impact and is encouraged to speak up, share ideas, and challenge assumptions (even your manager’s). This is a place for builders, not bystanders. Success here takes focus, follow-through, and a willingness to roll up your sleeves — but if you’re driven by meaningful work and real results, it’s deeply rewarding. You’ll join a team that cares about the work, supports one another, and takes smart risks to achieve bold goals. Be yourself, stay mission-focused, and you’ll thrive. If that energizes you, we can’t wait to meet you."
Then schedule/hybrid remote paragraph:
"At Tekmetric, great work happens anywhere, but great teams are built through intentional connection. We offer hybrid and remote work models based on your proximity to our office hubs. Because we value in-person collaboration, travel is an expected part of every role. We come together several times a year for team and company-wide offsites to align on goals and strengthen relationships. Attendance at these events is expected and fully supported."
What You'll Do (Responsibilities) includes several paragraphs and bullet-like sentences. We need to turn into
- for any list of duties/requirements/benefits. The responsibilities are described in paragraphs with bullet-like sentences starting with verbs. We can convert each sentence into a list item. Let's list them:
- Metrics Program Design & Outcome Modeling
- Partner with product leadership to design and evolve Tekmetric's product metrics program, contributing to what we measure, why it matters, and how metrics connect to the outcomes the business is trying to drive.
- Build and maintain a multi-variable outcome model that captures the relationships between product inputs and business results across retention, revenue, customer health, and engagement.
- Apply statistical methods, including regression, correlation analysis, and predictive modeling, to validate metric definitions and ensure the model reflects how the business actually works, not just what's easy to measure.
- Contribute to the frameworks, taxonomies, and standards that make metrics consistent, trustworthy, and actionable across product and leadership.
- Insights & Analytics
- Conduct proactive, deep-dive analyses to uncover customer behavior trends, product usage patterns, friction points, and revenue-impact opportunities.
- Deliver strategic insights that inform prioritization, roadmap decisions, and OKRs, not just findings, but clear recommendations with a point of view on what to do next and why it matters.
- Translate data into compelling narratives for executive reviews, board decks, and product planning cycles.
- Manage your own backlog of analytical work, identifying what needs attention, setting priorities, and closing the loop with stakeholders on what was learned and what it means.
- Enablement & Data Democratization
- Develop easy-to-use dashboards, templates, and toolkits that empower PMs and cross-functional teams to self-serve insights.
- Train stakeholders on how to interpret and leverage product data to make better decisions.
- Standardize reporting practices across product teams, ensuring consistency and clarity.
- Data Infrastructure & Collaboration
- Partner with Engineering and Data teams to define and maintain event tracking, taxonomy standards, and data governance practices across the product.
- Ensure data accuracy, completeness, and consistency to support strategic product decisions.
- Build and maintain core product metrics, dashboards, and self-service data models within the existing analytics stack (Looker, Pendo, Mixpanel, Redshift).
We could keep headings inside responsibilities? But we only need to output HTML fragment; we could include
Responsibilities
then a with - items. The subheadings could be or just part of li text. Probably fine to include them as part of li.
What You'll Bring (Requirements) includes bullet-like sentences:
- 5-8+ years in Product Operations, Product Analytics, Business Intelligence, or related roles.
- Genuine foundation in statistical methods, including regression, correlation, and predictive modeling. This is the one area where we're not looking for someone who will learn on the job; you need to bring it.
- Exposure to analytics or metrics program work. You've seen what a well-built program looks like and you're ready to help build one, not just operate within one that already exists.
- Track record of translating complex data into actionable recommendations that influenced product and business decisions.
- Experience working in SaaS or platform products is strongly preferred.
- Strong command of SQL and proficiency with modern BI/analytics tools (Looker preferred).
- Fluency with AI tools as a core part of how you work. You use AI to synthesize, analyze, and scale your output, and you think about how to structure data and workflows to take advantage of it.
- A communicator who can answer "so what?" without being asked. You know how to find the right stakeholders,
About the role
. - Responsibilities: we have "What You'll Do" with bullet list. - Requirements/Qualifications/Skills: we have "What You'll Bring" includes years experience, statistical methods, etc. Could split into Requirements and Qualifications and Skills. But we can combine into one section maybe "Requirements". However instruction: prefer a few substantive sections over many thin ones. So we could have one section for qualifications/requirements/skills. Use heading maybe "Requirements". Or "Qualifications". Choose one. Let's use "Requirements". It covers experience, skills, etc. - Benefits: we have "Why You'll Love Working With Us" includes health, wellness, 401k, etc. SoBenefits
. - Pay: not present, omit. - Schedule: not present (though hybrid/remote and travel expectations could be considered schedule? But they said only create Schedule if posting actually states them. It mentions hybrid/remote work models, travel expected, offsites attendance expected. That is about work arrangement, could be considered schedule. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state hybrid/remote work models, travel expected, offsites. That is about work arrangement, maybe schedule. But the heading "Schedule" might be appropriate. However they gave examples of Schedule as a heading. The posting does mention hybrid/remote work models, travel expected, offsites. That is about work location and expectations, not exactly schedule (hours). Might be considered schedule. Safer to include a Schedule section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state hybrid/remote work models, travel expected, offsites. So we could include Schedule. But we already have Benefits. Could we incorporate those details into Benefits? Probably not; they are work arrangement. Let's create a Schedule section. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. We need to use- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip the EEO statement, fraud warnings, etc. Also remove "Tekmetric is an equal opportunity employer..." and the fraud warning paragraphs. Also remove "Please contact us to request accommodation." etc. Also remove "Tekmetric will never ask for your personal financial..." etc. Also remove "All legitimate Tekmetric job postings are listed at tekmetric.com/careers." etc. Also remove recruiter communications line. Also remove "Please visit this link for further information Fraudulent Job Offers". So we keep only the substantive content: company description, culture, what you'll do, what you'll bring, why you'll love working with us (benefits), and maybe schedule details (hybrid/remote, travel, offsites). Also note the line "At Tekmetric, great work happens anywhere, but great teams are built through intentional connection. We offer hybrid and remote work models based on your proximity to our office hubs. Because we value in-person collaboration, travel is an expected part of every role. We come together several times a year for team and company-wide offsites to align on goals and strengthen relationships. Attendance at these events is expected and fully supported." That's schedule/work arrangement. Now we need to format. Let's extract content: About Tekmetric paragraph(s): "Tekmetric is the all-in-one, cloud-based software helping auto repair shops run smarter, grow faster, and serve customers better. Built by a shop owner and shaped by the needs of the industry, Tekmetric brings together innovation, real-world experience, and a thriving community to help shops thrive - not just survive. From running a shop, to securing payments to engaging customers, our platform simplifies operations so shop owners can focus on what really matters: delivering exceptional service, earning trust, and growing sustainably. Officially founded in Houston in 2017, Tekmetric has grown from a single shop’s vision to the industry’s leading solution - all by staying true to our values of transparency, integrity, innovation, and a service-first mindset. But we’re not just building shop management software. We’re building a movement. We’re empowering repair shops to rise above the daily grind, create meaningful connections with their customers, and lead the industry forward - one interaction at a time. Come build with us. Join the journey. Shape the future of auto repair." Working the Tekmetric Way paragraph(s): "At Tekmetric, we’re building a culture where winning matters - not for ego, but because when our customers win, we win together. We move fast, stay curious, and take full ownership of our results — no excuses, no finger-pointing. If you thrive in ambiguity, take initiative, and view honest feedback as fuel for growth, you’ll feel right at home here. We’re direct but respectful, ambitious yet grounded, and collaborative at every level. Everyone leads through impact and is encouraged to speak up, share ideas, and challenge assumptions (even your manager’s). This is a place for builders, not bystanders. Success here takes focus, follow-through, and a willingness to roll up your sleeves — but if you’re driven by meaningful work and real results, it’s deeply rewarding. You’ll join a team that cares about the work, supports one another, and takes smart risks to achieve bold goals. Be yourself, stay mission-focused, and you’ll thrive. If that energizes you, we can’t wait to meet you." Then schedule/hybrid remote paragraph: "At Tekmetric, great work happens anywhere, but great teams are built through intentional connection. We offer hybrid and remote work models based on your proximity to our office hubs. Because we value in-person collaboration, travel is an expected part of every role. We come together several times a year for team and company-wide offsites to align on goals and strengthen relationships. Attendance at these events is expected and fully supported." What You'll Do (Responsibilities) includes several paragraphs and bullet-like sentences. We need to turn into
- for any list of duties/requirements/benefits. The responsibilities are described in paragraphs with bullet-like sentences starting with verbs. We can convert each sentence into a list item. Let's list them:
- Metrics Program Design & Outcome Modeling
- Partner with product leadership to design and evolve Tekmetric's product metrics program, contributing to what we measure, why it matters, and how metrics connect to the outcomes the business is trying to drive.
- Build and maintain a multi-variable outcome model that captures the relationships between product inputs and business results across retention, revenue, customer health, and engagement.
- Apply statistical methods, including regression, correlation analysis, and predictive modeling, to validate metric definitions and ensure the model reflects how the business actually works, not just what's easy to measure.
- Contribute to the frameworks, taxonomies, and standards that make metrics consistent, trustworthy, and actionable across product and leadership.
- Insights & Analytics
- Conduct proactive, deep-dive analyses to uncover customer behavior trends, product usage patterns, friction points, and revenue-impact opportunities.
- Deliver strategic insights that inform prioritization, roadmap decisions, and OKRs, not just findings, but clear recommendations with a point of view on what to do next and why it matters.
- Translate data into compelling narratives for executive reviews, board decks, and product planning cycles.
- Manage your own backlog of analytical work, identifying what needs attention, setting priorities, and closing the loop with stakeholders on what was learned and what it means.
- Enablement & Data Democratization
- Develop easy-to-use dashboards, templates, and toolkits that empower PMs and cross-functional teams to self-serve insights.
- Train stakeholders on how to interpret and leverage product data to make better decisions.
- Standardize reporting practices across product teams, ensuring consistency and clarity.
- Data Infrastructure & Collaboration
- Partner with Engineering and Data teams to define and maintain event tracking, taxonomy standards, and data governance practices across the product.
- Ensure data accuracy, completeness, and consistency to support strategic product decisions.
- Build and maintain core product metrics, dashboards, and self-service data models within the existing analytics stack (Looker, Pendo, Mixpanel, Redshift).
We could keep headings inside responsibilities? But we only need to output HTML fragment; we could include
Responsibilities
then a- with
- items. The subheadings could be or just part of li text. Probably fine to include them as part of li. What You'll Bring (Requirements) includes bullet-like sentences: - 5-8+ years in Product Operations, Product Analytics, Business Intelligence, or related roles. - Genuine foundation in statistical methods, including regression, correlation, and predictive modeling. This is the one area where we're not looking for someone who will learn on the job; you need to bring it. - Exposure to analytics or metrics program work. You've seen what a well-built program looks like and you're ready to help build one, not just operate within one that already exists. - Track record of translating complex data into actionable recommendations that influenced product and business decisions. - Experience working in SaaS or platform products is strongly preferred. - Strong command of SQL and proficiency with modern BI/analytics tools (Looker preferred). - Fluency with AI tools as a core part of how you work. You use AI to synthesize, analyze, and scale your output, and you think about how to structure data and workflows to take advantage of it. - A communicator who can answer "so what?" without being asked. You know how to find the right stakeholders,
- for any list of duties/requirements/benefits. The responsibilities are described in paragraphs with bullet-like sentences starting with verbs. We can convert each sentence into a list item. Let's list them:
- Metrics Program Design & Outcome Modeling
- Partner with product leadership to design and evolve Tekmetric's product metrics program, contributing to what we measure, why it matters, and how metrics connect to the outcomes the business is trying to drive.
- Build and maintain a multi-variable outcome model that captures the relationships between product inputs and business results across retention, revenue, customer health, and engagement.
- Apply statistical methods, including regression, correlation analysis, and predictive modeling, to validate metric definitions and ensure the model reflects how the business actually works, not just what's easy to measure.
- Contribute to the frameworks, taxonomies, and standards that make metrics consistent, trustworthy, and actionable across product and leadership.
- Insights & Analytics
- Conduct proactive, deep-dive analyses to uncover customer behavior trends, product usage patterns, friction points, and revenue-impact opportunities.
- Deliver strategic insights that inform prioritization, roadmap decisions, and OKRs, not just findings, but clear recommendations with a point of view on what to do next and why it matters.
- Translate data into compelling narratives for executive reviews, board decks, and product planning cycles.
- Manage your own backlog of analytical work, identifying what needs attention, setting priorities, and closing the loop with stakeholders on what was learned and what it means.
- Enablement & Data Democratization
- Develop easy-to-use dashboards, templates, and toolkits that empower PMs and cross-functional teams to self-serve insights.
- Train stakeholders on how to interpret and leverage product data to make better decisions.
- Standardize reporting practices across product teams, ensuring consistency and clarity.
- Data Infrastructure & Collaboration
- Partner with Engineering and Data teams to define and maintain event tracking, taxonomy standards, and data governance practices across the product.
- Ensure data accuracy, completeness, and consistency to support strategic product decisions.
- Build and maintain core product metrics, dashboards, and self-service data models within the existing analytics stack (Looker, Pendo, Mixpanel, Redshift).
We could keep headings inside responsibilities? But we only need to output HTML fragment; we could include