Director of Product Management, Measurement
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only use those headings. The "About Us" description is not required to be a heading; we could embed it maybe under About the role? But we must preserve all substantive information. The "About Us" is about the company, not the role. The instruction says we should not repeat the job title as heading, but we can include other content. However they only gave examples of headings; we could still include other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; maybe we can also include other headings if needed, but they gave examples. Safer to stick to those headings only. But we need to preserve all substantive info, including company description. Where to put it? Could be part of About the role? But About the role is separate. Perhaps we can include a brief paragraph under About the role that includes company context. However the posting already has an "About The Role" section. So we can map that to About the role heading. The "About Us" could be omitted? But we must preserve ALL substantive information. If we omit it, we lose info. However maybe we can incorporate it under About the role as a preamble. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the company description somewhere. Could we add a
before any headings? The output is just HTML fragment; we can include a
with company description before the headings. That would preserve it without needing a heading. That seems acceptable. Now we need to extract sections: - About the role: The posting has "About The Role" paragraph: "Our Decision Maker Targeting products are a critical part of our clients’ strategic execution.... In this critical role, you will drive the product vision and execution of our measurement and insights products as we grow our offering and client base. The ideal candidate would combine enterprise product expertise with a deep technical understanding of media measurement and/or research methods." We should put that under
About the role
and thenwith that content. - Responsibilities: The posting has "What You’ll Do" bullet list (actually sentences). We need to convert to
- . The list items: Define and build the next generation of our Measurement & Optimization offerings in collaboration with a cross-functional team of engineers, data scientists, product managers, and sales and client service leads Own the product strategy, business planning, roadmap and requirements definition for your own product offering Evangelize product solutions with internal teams, clients and industry partners Collect user and client feedback via both direct and indirect channels and translate them into product requirements where applicable Collaborate with key clients on implementation strategy and adoption of new features Manage high visibility product launches and define and track KPIs to measure success and identify ongoing improvements This role may also manage 1-2 Product Managers under them We should include each as
- .
- Requirements: The posting has "Experiences And Capabilities You Bring" with sub-sections: Experience and domain expertise, Leading Mixed-discipline Teams, Technical Depth. These are more like qualifications/skills. We need to map to Requirements, Qualifications, Skills sections. The instruction: Use headings for Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements are mandatory experience/skills; Qualifications maybe similar; Skills maybe specific abilities. We have to avoid thin sections; prefer few substantive sections. We could combine all into one Requirements section? But we need to follow headings if we have content. We could put all under Requirements and leave Qualifications and Skills omitted if no specific content. However we have distinct content: Experience and domain expertise (8+ years, etc), Leading Mixed-discipline Teams, Technical Depth. Could be considered Requirements. Could also split: Requirements = Experience and domain expertise; Qualifications = Leading Mixed-discipline Teams; Skills = Technical Depth. That seems reasonable.
We must not create sections with filler like "commensurate with experience". We have real content.
Thus:
Requirements
withor
- ? The content is prose with bullet-like details. Could use
- for each bullet. The content includes multiple sentences; we can break into items. Let's extract: Experience and domain expertise: - 8+ years of experience in a product management role, including 3+ years managing direct reports - Deep understanding of digital marketing, advertising technology, market research, or a similar industry, with specific expertise in media effectiveness measurement - Hands-on familiarity with the data that flows out of the ad tech stack — DSPs (e.g., DV360, The Trade Desk, Amazon DSP), ad servers, and SSPs —including log-level/impression-level data, bid and delivery signals, and audience and taxonomy data - Personally rolled out measurement technology solutions to large enterprises and/or their agencies, owning both the client-facing reporting layer and the underlying methodology Leading Mixed-discipline Teams: - Proven track record leading mixed-discipline teams where you are the connective tissue between functions — partnering with data scientists on methodology and model validation, with analysts on insight generation and QA, with engineers on data pipelines and platform tradeoffs, and mentoring junior PMs on scoping and execution - You can translate a statistical approach into a client-ready narrative, and a client asks into a well-specified technical requirement - Experience working closely and managing asynchronous communication with a geographically distributed team Technical Depth: - Strong SQL — you write your own queries against large datasets to validate outputs, size opportunities, and debug discrepancies rather than waiting on a ticket - Experience owning products built on big-data platforms such as Spark/Databricks, BigQuery, Redshift, or Snowflake, with a working understanding of batch vs. streaming, partitioning, cost/performance tradeoffs, and why a pipeline change can move a client-facing number - Experience shipping a client-facing application end to end — you have owned a standalone product surface, not just a reporting feed or an internal tool. That includes partnering with design on information architecture and UX for complex, data-dense interfaces; making deliberate calls on self-serve vs. guided workflows; and handling the realities of a production app such as onboarding, permissions and multi-tenancy, performance under real query loads, and instrumentation to understand how clients actually use it We could put each bullet as
- .
Now Benefits: The posting mentions compensation package: base salary, annual cash bonus, generous equity compensation. Also mentions hybrid schedule: Work from home on Monday and Friday and in Applecart’s New York City office Tuesday through Thursday.
Thus Benefits could include: generous equity compensation, annual cash bonus, maybe other benefits not listed. The posting only mentions compensation components. Benefits could be the equity compensation and bonus. But we also have Pay section for base salary range. Schedule section for hybrid schedule.
Thus:
Benefits
with- Annual cash bonus
- Generous equity compensation
before any headings. Also there is "A Few Facts About Us" with lots of info about clients, growth, leadership, investors, board, media coverage. That's also substantive. We must preserve all substantive information. So we need to include that as well. Where to put? Could be another
after the company description or maybe under a heading like "About the company"? Not in allowed headings. But we can just include as
elements without headings. The instruction didn't forbid other
elements. It said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we cannot have other headings, but to be safe we can avoid extra headings and just use paragraphs. Thus we will output:
Applecart is the leading technology company that C-suites rely on to reach business-critical decision makers. ... (the About Us paragraph)
Then anotherA Few Facts About Us Applecart’s platform has been used by hundreds of industry-leading clients ...
(the long paragraph). We need to ensure we preserve all info, not summarizing. We'll copy the text exactly as given, but we need to ensure we don't include boilerplate like "cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The posting didn't have those explicitly; but we should avoid any such. Now we need to ensure we don't repeat the job title as heading. The job title is "Director of Product Management, Measurement". We are not using it as heading. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. We'll start with afor About Us. Copy the About Us paragraph exactly: "Applecart is the leading technology company that C-suites rely on to reach business-critical decision makers. The most important decisions are made by the hardest people to reach and influence. Historically, C-suite leaders have lacked the tools to reach the stakeholders who matter most to their business. The C-suites of hundreds of Fortune 500 companies, major agencies, trade associations, nonprofits, and governments use Applecart to put their best content in front of business-critical decision makers and those they trust — from policymakers and investors to CEOs, key employees, members of the media and more. Decision makers are informed by what they read, learn from advisors, hear from colleagues, and discuss with family and friends. To break through to them, you must reach them through the only channel that really moves them: those they know and trust. Applecart’s platform uses publicly available data to map billions of social relationships between nearly every American adult and enable clients to deliver content directly to decision makers and those who matter most to them." Now after that, we have "We are hiring a Director of Product Management, Measurement in our New York City office." That's a sentence about hiring. Could be included as a
maybe before About the role. But we might incorporate it into About the role? Actually the "About The Role" heading follows after that sentence. We could keep that sentence as a
before the About the role heading. Thus after About Us paragraph, we add a
"We are hiring a Director of Product Management, Measurement in our New York City office." Then
About the role
andwith the About The Role paragraph. Now Responsibilities:
Responsibilities
- with each
- .
Now Requirements:
Requirements
- with items from Experience and domain expertise.
Now Qual