Senior Product Manager, Metrics & Measurement
CreatorIQ · Los Angeles Metropolitan Area · 1 mo ago
RemoteRemoteMarketing$121k–$145k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
First, there is a description about CreatorIQ, mission, values, etc. That's likely "About the role" or maybe "About the company". The instruction: use
.
Requirements: The list after "Who you are and what you’ll need for this position:" includes:
- 5+ years in product management, or equivalent experience, including at least 2 years on a measurement, analytics, or data product.
- Enough engineering depth to work as a technical peer to your engineers : able to read code, review a technical design, and contribute to an engineering design review.
- Strong SQL skills, including multi-table joins, window functions, aggregations, and common table expressions, with the ability to validate a metric end to end in the data yourself.
- Experience querying both an analytical store (e.g., Amazon Redshift, ClickHouse, or Snowflake) and a transactional store (e.g., PostgreSQL or SQL Server), and knowing which fits which question.
- Ability to write Python, or an equivalent language, to test an API, parse a response, validate a data set, or prototype an idea.
- Ability to work directly with a third-party API : reading documentation, building requests, authenticating, and inspecting responses , including working knowledge of OAuth 2.0 (authorization flow, access tokens, refresh tokens, scopes, and token expiry).
- Comfort on the command line, able to navigate a shell, run a script, and read its output without a graphical tool.
- AI Capable: Uses approved AI tools independently to improve work quality and efficiency, for example, an AI coding tool such as Cursor or Claude Code for scripting and data work, or a language model to draft a specification, build a data-mapping table, or debug an API response , including drafting, summarizing, researching, analyzing, and reviewing outputs for accuracy.
- Working knowledge of how social platforms measure content performance: reach, impressions, views, engagement rate, video completion rate, and audience demographics.
- Clear written and verbal communication, able to translate a technical constraint for a non-technical colleague and a business requirement for an engineer.
We need to keep each as . Note some have extra spaces or punctuation; we can keep as is.
Skills (Nice To Have):
- Direct experience with a major social platform API, such as the Meta Graph API, the TikTok API, or the YouTube Data API.
- Experience managing a relationship with an external platform, vendor, or data provider.
- Experience at an influencer marketing platform, a social media management platform, or a social analytics company.
- Familiarity with data warehouse schema design, enough to discuss table and index design with engineers.
- Experience defining or auditing engagement rate, or a similar calculated metric, in a customer-facing product.
We'll put these as under Skills.
Benefits: The list after "What You Will Get From Us":
- People: work with talented, collaborative, and friendly people who love what they do.
- Guidance: utilize our learning platform to fully get the training and tools you’ll need to become successful here from your first day with us.
- Surprise meal stipends: work from home can’t stop the enjoyment of someone else making a meal for you!
- Work/life harmony: 15 days vacation, floating and set holidays, wellness allowance, and paid parental leave.
- Whole Health Package: medical, dental, vision, life, disability insurance, and more.
- Savings: a 401k (USA) plan to help you plan ahead.
- Work from home stipend: to assist you in setting up a home office that works for you (or buy a new dog leash - your choice!).
We need to keep each as . The headings like "People:" etc are part of the benefit description; we can keep them inside .
Pay: Compensation Range: $121K - $145K.
Schedule: flexible work model.
We also have some other paragraphs like "CreatorIQ is the operating system for creator-led growth..." at top; that's boilerplate about company but could be considered "About the company". Not required; we could omit as it's somewhat generic but it's substantive. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that info somewhere. Where? Could be part of "About the role" or maybe a separate "About the company" heading. Since we don't have a heading for About the company in the examples, but we could still add
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
First, there is a description about CreatorIQ, mission, values, etc. That's likely "About the role" or maybe "About the company". The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide appropriate headings.
We have content: "Senior Product Manager, Metrics & Measurement We're looking for Senior Product Manager, Metrics & Measurement to join our Content & Measurement team and own how CreatorIQ measures content performance across platforms. This is a new, hands-on role spanning three areas: defining what each platform's metrics actually mean, unifying data from multiple platforms into a single measurement product customers can trust, and shaping the analytics surfaces customers rely on every day. You'll partner closely with the product managers who own platform partnerships, with engineering and data teams, and with platform partners themselves, querying data, writing SQL, and calling APIs yourself before you write a specification. Reporting to the Sr Director, Product & Engineering, you'll play a central role in how CreatorIQ's Creator Graph™ turns fragmented platform data into a trustworthy system of record for performance measurement."
That's role description: could be "About the role".
Then "In This Role, You’ll Get To" bullet list: define metric and data requirements, define what each performance metric means, design cross-platform measurement logic, specify custom metrics, write technical specs, validate metrics hands-on, track platform API changes, write product requirements docs, prioritize measurement roadmap.
That's responsibilities.
Then "Who you are and what you’ll need for this position:" list of requirements: 5+ years product management, etc. That's qualifications/requirements.
Then "Nice To Have" list: direct experience with major social platform API, etc. That could be "Preferred Qualifications" or "Skills". We'll treat as "Skills" maybe.
Then "Confidence can sometimes hold us back..." that's encouragement, maybe not needed.
Then "What You Will Get From Us" list: People, Guidance, Surprise meal stipends, Work/life harmony, Whole Health Package, Savings, Work from home stipend. That's benefits.
Then "Who We Are" description about company: could be "About the company" but not required; maybe we can include as "About the role"? Already have about the role. Could add "About the company" but not in list of headings; but we could still use About the company? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those examples. Safer to stick to those.
We have compensation range: "$121K - $145K". That's Pay. So we need a Pay section.
Schedule: not mentioned; flexible work model combines in-person and remote work. That's schedule info: "We operate in a flexible work model that combines both in-person and remote work to boost collaboration, enhance innovation, and adapt to individual work styles." That's schedule info. So we can include Schedule section.
Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule.
We need to decide which heading for the qualifications list: "Who you are and what you’ll need for this position:" is requirements/qualifications. Could use "Requirements". Then "Nice To Have" could be "Skills" or "Preferred Qualifications". Since we have Skills heading, we can put nice-to-have there.
We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Remove duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
About the company? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those examples. Safer to stick to those.
We have compensation range: "$121K - $145K". That's Pay. So we need a Pay section.
Schedule: not mentioned; flexible work model combines in-person and remote work. That's schedule info: "We operate in a flexible work model that combines both in-person and remote work to boost collaboration, enhance innovation, and adapt to individual work styles." That's schedule info. So we can include Schedule section.
Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule.
We need to decide which heading for the qualifications list: "Who you are and what you’ll need for this position:" is requirements/qualifications. Could use "Requirements". Then "Nice To Have" could be "Skills" or "Preferred Qualifications". Since we have Skills heading, we can put nice-to-have there.
We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Remove duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
Compensation Range: $121K - $145K
Schedule
We operate in a flexible work model that combines both in-person and remote work to boost collaboration, enhance innovation, and adapt to individual work styles.
We need to ensure we include all substantive info from each section. Let's extract details. About the role: The paragraph(s) before responsibilities: "Senior Product Manager, Metrics & Measurement We're looking for Senior Product Manager, Metrics & Measurement to join our Content & Measurement team and own how CreatorIQ measures content performance across platforms. This is a new, hands-on role spanning three areas: defining what each platform's metrics actually mean, unifying data from multiple platforms into a single measurement product customers can trust, and shaping the analytics surfaces customers rely on every day. You'll partner closely with the product managers who own platform partnerships, with engineering and data teams, and with platform partners themselves, querying data, writing SQL, and calling APIs yourself before you write a specification. Reporting to the Sr Director, Product & Engineering, you'll play a central role in how CreatorIQ's Creator Graph™ turns fragmented platform data into a trustworthy system of record for performance measurement." We should keep that as is. Responsibilities: The bullet list after "In This Role, You’ll Get To". Let's capture each: - Define the metric and data requirements each platform integration must meet, partnering with the product managers who own platform partnerships. - Define what each performance metric means on each platform: reach, impressions, views, engagement rate, completion rate, and platform-specific metrics, and document how each platform calculates it. - Design the cross-platform measurement logic that lets customers compare performance across platforms in a single, trustworthy view. - Specify custom metrics for customers, including the exact calculation and data requirements behind each one. - Write technical specifications for mapping metrics across platform APIs, covering field mapping, refresh cadence, and known limitations. - Validate metrics and data hands-on: writing SQL, running scripts, and calling APIs directly before finalizing a specification. - Track platform API changes and represent measurement requirements in partner and integration reviews. - Write product requirements documents engineers can build from, and prioritize the measurement roadmap against customer impact, platform constraints, and engineering cost. We need to preserve each as