Technical Program Manager II, Shopping Platforms
Pinterest · San Francisco, CA · 3 wk ago
RemoteRemoteProject Management$104k–$214k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting.
First, remove boilerplate: About Pinterest paragraph, The Team paragraph, etc. Keep substantive info.
We need to identify sections:
- About the role: maybe the paragraph after "About Pinterest"? Actually "About Pinterest" is generic company description; we can treat as About the role? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to create headings accordingly.
We need to extract content for each.
Let's read the posting:
"About Pinterest Millions of people around the world come to our platform to find creative ideas, dream about new possibilities and plan for memories that will last a lifetime. At Pinterest, we’re on a mission to bring everyone the inspiration to create a life they love, and that starts with the people behind the product. Discover a career where you ignite innovation for millions, transform passion into growth opportunities, celebrate each other’s unique experiences and embrace the flexibility to do your best work. Creating a career you love? It’s Possible. At Pinterest, AI isn't just a feature, it's a powerful partner that augments our creativity and amplifies our impact, and we’re looking for candidates who are excited to be a part of that. To get a complete picture of your experience and abilities, we’ll explore your foundational skills and how you collaborate with AI. Through our interview process, what matters most is that you can always explain your approach, showing us not just what you know, but how you think. You can read more about our AI interview philosophy and how we use AI in our recruiting process here."
That's generic company description; could be About the role? Might be considered "About the role" but it's more about company. However we can still put it under About the role.
Next: "The Team Pinterest's Shopping & Delivery Infrastructure team builds and operates the catalog, indexing, retrieval, and serving systems that power Shopping and ads across every Pinterest surface, from search and homefeed to P2P and international markets. Our mission is to make Pinterest's shopping and delivery stack unified, scalable, and low-latency so we can drive sustainable revenue growth, exceptional Pinner experiences, and measurable advertiser outcomes. We're in the middle of a multi-year transformation of the stack, and we work closely with catalog, indexing, retrieval, serving, ads quality, and product teams to make Pinterest's shopping infrastructure faster, more reliable, and ready to scale."
That could be part of About the role or maybe separate but we only have limited headings. Could include under About the role as well.
Next: "What You'll Do" bullet list:
- Independently drive a well-defined portfolio of Shopping catalog and indexing programs, keeping engineering owners, timelines, and dependencies on track.
- Run the day-to-day working-team cadence including standups, planning, decision-tracking, and documentation, so the team stays aligned on priorities and next steps.
- Build and maintain program dashboards and reporting that give engineering and cross-functional stakeholders a clear view of progress, risk, and decisions.
- Manage cross-team dependencies with partner teams across catalog, indexing, retrieval, serving, and ads quality.
- Communicate clearly in writing and verbally across
- Use GenAI as the default operating model for EP PgM execution—producing AI-assisted first drafts of core program artifacts, modernizing high-toil workflows into AI-first mechanisms (e.g., intake triage, status synthesis, action/decision extraction, risk & dependency tracking), and synthesizing signals to proactively surface risks, decision/trade-offs, and escalation paths.
- Prototype solutions to augment decisions through data (e.g. dashboards, data analysis) or simplify processes (e.g. process and workflow helpers, or internal tools) using AI coding assistants (“vibe coding”).
- Follow Pinterest AI guidance for risk, governance, and safety-by-design: appropriately handle sensitive data, validate AI-generated outputs, document assumptions/limits, and ensure AI-assisted workflows meet applicable policy/compliance expectations before broad adoption.
Note: There's a line "Communicate clearly in writing and verbally across" seems incomplete; maybe cut off. We'll keep as is.
Next: "What We're Looking For" list:
- 2–4 years of TPM experience independently driving technical programs to completion, ideally within infrastructure, platform, or data-adjacent environments.
- Solid foundational understanding of distributed systems concepts — services, streaming pipelines, batch vs real-time processing.
- Strong execution and follow-through, with a track record of running multiple concurrent workstreams without dropping the ball.
- Comfortable working with data — building dashboards, tracking metrics, and turning progress into clear status updates.
- Excellent written and verbal communication, with experience managing cross-team dependencies and stakeholder expectations.
- Experience with ads, monetization, streaming systems (Flink/Kafka), or financial-controls processes is a plus; willingness to learn the domain is essential.
- Workflow design, AI fluency, data & insights orientation: experience turning repeatable program work into durable, low-toil mechanisms and improving decision-making by using GenAI (e.g., strong prompting, vibe coding lightweight scripts/tools, dashboards, data analysis and leveraging agents where appropriate)
- Safety-by-design AI fluency: experience operating within AI governance expectations (risk assessment, data handling, model/output validation, auditability/traceability) and proactively identifying where AI use is not appropriate or requires additional controls.
- Bachelor’s degree in Computer Science, Engineering, a related field or equivalent experience.
Next: "Join us and help scale the systems that power Pinterest's Shopping and Ads business!" (maybe a closing line).
Then relocation statement, in-office requirement statement, etc. Those are boilerplate; we should remove.
Then: "At Pinterest we believe the workplace should be equitable, inclusive, and inspiring for every employee. In an effort to provide greater transparency, we are sharing the base salary range for this position. The position is also eligible for equity. Final salary is based on a number of factors including location, travel, relevant prior experience, or particular skills and expertise. Information regarding the culture at Pinterest and benefits available for this position can be found here. US based applicants only $103,965—$214,044 USD"
Thus we have Pay: salary range $103,965—$214,044 USD. Also mention equity eligibility.
Benefits: Not explicitly listed; only mention "Information regarding the culture at Pinterest and benefits available for this position can be found here." No specific benefits given. So we should NOT create Benefits section because no specific content.
Schedule: In-office requirement statement: "This role will need to be in the office for in-person collaboration 1–2 times every 6 months and therefore can be situated anywhere in the country." That's schedule info (hybrid). So we can create Schedule section with that.
Also we have relocation statement: "This position is not eligible for relocation assistance." Could be part of Schedule or maybe separate but we can include in Schedule or maybe as a note. Since we only have Schedule heading, we can include both.
Now we need to decide sections:
- About the role: combine the initial About Pinterest paragraph and The Team description? Could be two paragraphs.
- Responsibilities: the "What You'll Do" list.
- Requirements: maybe the "What We're Looking For" list (experience, skills). Could split into Requirements and Qualifications? But we have both headings. We could put experience/skills under Requirements, and education under Qualifications. Or we could put all under Requirements and leave Qualifications empty (but we shouldn't emit empty heading). So we need to allocate content to both headings if we have distinct content.
We have:
Requirements (experience, skills):
- 2–4 years of TPM experience...
- Solid foundational understanding of distributed systems concepts...
- Strong execution and follow-through...
- Comfortable working with data...
- Excellent written and verbal communication...
- Experience with ads, monetization, streaming systems (Flink/Kafka), or financial-controls processes is a plus; willingness to learn the domain is essential.
- Workflow design, AI fluency, data & insights orientation...
- Safety-by-design AI fluency...
Qualifications:
- Bachelor’s degree in Computer Science, Engineering, a related field or equivalent experience.
Thus we can have Requirements (bullet list of experience/skills) and Qualifications (bullet list of education).
Skills: Could be separate but we already have skills in Requirements; maybe we can combine. But we have a heading Skills; we could put specific technical skills there (e.g., distributed systems, data, AI fluency, etc.) but that duplicates. Better to follow instruction: prefer few substantive sections over many thin ones. So we might omit Skills if content overlaps with Requirements. However we have distinct content for Skills? Not really; the posting doesn't have a separate "Skills" section besides those listed. So we can omit Skills.
Benefits: omit as no specific.
Pay: we have salary range.
Schedule: we have in-office requirement and relocation note.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule.
Now we need to format as HTML fragment: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to create headings accordingly.
We need to extract content for each.
Let's read the posting:
"About Pinterest Millions of people around the world come to our platform to find creative ideas, dream about new possibilities and plan for memories that will last a lifetime. At Pinterest, we’re on a mission to bring everyone the inspiration to create a life they love, and that starts with the people behind the product. Discover a career where you ignite innovation for millions, transform passion into growth opportunities, celebrate each other’s unique experiences and embrace the flexibility to do your best work. Creating a career you love? It’s Possible. At Pinterest, AI isn't just a feature, it's a powerful partner that augments our creativity and amplifies our impact, and we’re looking for candidates who are excited to be a part of that. To get a complete picture of your experience and abilities, we’ll explore your foundational skills and how you collaborate with AI. Through our interview process, what matters most is that you can always explain your approach, showing us not just what you know, but how you think. You can read more about our AI interview philosophy and how we use AI in our recruiting process here."
That's generic company description; could be About the role? Might be considered "About the role" but it's more about company. However we can still put it under About the role.
Next: "The Team Pinterest's Shopping & Delivery Infrastructure team builds and operates the catalog, indexing, retrieval, and serving systems that power Shopping and ads across every Pinterest surface, from search and homefeed to P2P and international markets. Our mission is to make Pinterest's shopping and delivery stack unified, scalable, and low-latency so we can drive sustainable revenue growth, exceptional Pinner experiences, and measurable advertiser outcomes. We're in the middle of a multi-year transformation of the stack, and we work closely with catalog, indexing, retrieval, serving, ads quality, and product teams to make Pinterest's shopping infrastructure faster, more reliable, and ready to scale."
That could be part of About the role or maybe separate but we only have limited headings. Could include under About the role as well.
Next: "What You'll Do" bullet list:
- Independently drive a well-defined portfolio of Shopping catalog and indexing programs, keeping engineering owners, timelines, and dependencies on track.
- Run the day-to-day working-team cadence including standups, planning, decision-tracking, and documentation, so the team stays aligned on priorities and next steps.
- Build and maintain program dashboards and reporting that give engineering and cross-functional stakeholders a clear view of progress, risk, and decisions.
- Manage cross-team dependencies with partner teams across catalog, indexing, retrieval, serving, and ads quality.
- Communicate clearly in writing and verbally across
- Use GenAI as the default operating model for EP PgM execution—producing AI-assisted first drafts of core program artifacts, modernizing high-toil workflows into AI-first mechanisms (e.g., intake triage, status synthesis, action/decision extraction, risk & dependency tracking), and synthesizing signals to proactively surface risks, decision/trade-offs, and escalation paths.
- Prototype solutions to augment decisions through data (e.g. dashboards, data analysis) or simplify processes (e.g. process and workflow helpers, or internal tools) using AI coding assistants (“vibe coding”).
- Follow Pinterest AI guidance for risk, governance, and safety-by-design: appropriately handle sensitive data, validate AI-generated outputs, document assumptions/limits, and ensure AI-assisted workflows meet applicable policy/compliance expectations before broad adoption.
Note: There's a line "Communicate clearly in writing and verbally across" seems incomplete; maybe cut off. We'll keep as is.
Next: "What We're Looking For" list:
- 2–4 years of TPM experience independently driving technical programs to completion, ideally within infrastructure, platform, or data-adjacent environments.
- Solid foundational understanding of distributed systems concepts — services, streaming pipelines, batch vs real-time processing.
- Strong execution and follow-through, with a track record of running multiple concurrent workstreams without dropping the ball.
- Comfortable working with data — building dashboards, tracking metrics, and turning progress into clear status updates.
- Excellent written and verbal communication, with experience managing cross-team dependencies and stakeholder expectations.
- Experience with ads, monetization, streaming systems (Flink/Kafka), or financial-controls processes is a plus; willingness to learn the domain is essential.
- Workflow design, AI fluency, data & insights orientation: experience turning repeatable program work into durable, low-toil mechanisms and improving decision-making by using GenAI (e.g., strong prompting, vibe coding lightweight scripts/tools, dashboards, data analysis and leveraging agents where appropriate)
- Safety-by-design AI fluency: experience operating within AI governance expectations (risk assessment, data handling, model/output validation, auditability/traceability) and proactively identifying where AI use is not appropriate or requires additional controls.
- Bachelor’s degree in Computer Science, Engineering, a related field or equivalent experience.
Next: "Join us and help scale the systems that power Pinterest's Shopping and Ads business!" (maybe a closing line).
Then relocation statement, in-office requirement statement, etc. Those are boilerplate; we should remove.
Then: "At Pinterest we believe the workplace should be equitable, inclusive, and inspiring for every employee. In an effort to provide greater transparency, we are sharing the base salary range for this position. The position is also eligible for equity. Final salary is based on a number of factors including location, travel, relevant prior experience, or particular skills and expertise. Information regarding the culture at Pinterest and benefits available for this position can be found here. US based applicants only $103,965—$214,044 USD"
Thus we have Pay: salary range $103,965—$214,044 USD. Also mention equity eligibility.
Benefits: Not explicitly listed; only mention "Information regarding the culture at Pinterest and benefits available for this position can be found here." No specific benefits given. So we should NOT create Benefits section because no specific content.
Schedule: In-office requirement statement: "This role will need to be in the office for in-person collaboration 1–2 times every 6 months and therefore can be situated anywhere in the country." That's schedule info (hybrid). So we can create Schedule section with that.
Also we have relocation statement: "This position is not eligible for relocation assistance." Could be part of Schedule or maybe separate but we can include in Schedule or maybe as a note. Since we only have Schedule heading, we can include both.
Now we need to decide sections:
- About the role: combine the initial About Pinterest paragraph and The Team description? Could be two paragraphs.
- Responsibilities: the "What You'll Do" list.
- Requirements: maybe the "What We're Looking For" list (experience, skills). Could split into Requirements and Qualifications? But we have both headings. We could put experience/skills under Requirements, and education under Qualifications. Or we could put all under Requirements and leave Qualifications empty (but we shouldn't emit empty heading). So we need to allocate content to both headings if we have distinct content.
We have:
Requirements (experience, skills):
- 2–4 years of TPM experience...
- Solid foundational understanding of distributed systems concepts...
- Strong execution and follow-through...
- Comfortable working with data...
- Excellent written and verbal communication...
- Experience with ads, monetization, streaming systems (Flink/Kafka), or financial-controls processes is a plus; willingness to learn the domain is essential.
- Workflow design, AI fluency, data & insights orientation...
- Safety-by-design AI fluency...
Qualifications:
- Bachelor’s degree in Computer Science, Engineering, a related field or equivalent experience.
Thus we can have Requirements (bullet list of experience/skills) and Qualifications (bullet list of education).
Skills: Could be separate but we already have skills in Requirements; maybe we can combine. But we have a heading Skills; we could put specific technical skills there (e.g., distributed systems, data, AI fluency, etc.) but that duplicates. Better to follow instruction: prefer few substantive sections over many thin ones. So we might omit Skills if content overlaps with Requirements. However we have distinct content for Skills? Not really; the posting doesn't have a separate "Skills" section besides those listed. So we can omit Skills.
Benefits: omit as no specific.
Pay: we have salary range.
Schedule: we have in-office requirement and relocation note.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule.
Now we need to format as HTML fragment: use for each heading, then content:
for prose,
- for lists. We must not repeat job title as heading (not present). No Job ID. We must preserve all substantive information; do not invent or summarize away detail. We need to ensure we keep all details from the lists. Let's extract exact text. About the role: combine the two paragraphs: Paragraph1: "About Pinterest Millions of people around the world come to our platform to find creative ideas, dream about new possibilities and plan for memories that will last a lifetime. At Pinterest, we’re on a mission to bring everyone the inspiration to create a life they love, and that starts with the people behind the product. Discover a career where you ignite innovation for millions, transform passion into growth opportunities, celebrate each other’s unique experiences and embrace the flexibility to do your best work. Creating a career you love? It’s Possible. At Pinterest, AI isn't just a feature, it's a powerful partner that augments our creativity and amplifies our impact, and we’re looking for candidates who are excited to be a part of that. To get a complete picture of your experience and abilities, we’ll explore your foundational skills and how you collaborate with AI. Through our interview process, what matters most is that you can always explain your approach, showing us not just what you know, but how you think. You can read more about our AI interview philosophy and how we use AI in our recruiting process here." Paragraph2: "The Team Pinterest's Shopping & Delivery Infrastructure team builds and operates the catalog, indexing, retrieval, and serving systems that power Shopping and ads across every Pinterest surface, from search and homefeed to P2P and international markets. Our mission is to make Pinterest's shopping and delivery stack unified, scalable, and low-latency so we can drive sustainable revenue growth, exceptional Pinner experiences, and measurable advertiser outcomes. We're in the middle of a multi-year transformation of the stack, and we work closely with catalog, indexing, retrieval, serving, ads quality, and product teams to make Pinterest's shopping infrastructure faster, more reliable, and ready to scale." We should keep as is, maybe separate paragraphs. Now Responsibilities: list items from "What You'll Do". Need to capture each bullet exactly. Let's list them: 1. Independently drive a well-defined portfolio of Shopping catalog and indexing programs, keeping engineering owners, timelines, and dependencies on track. 2. Run the day-to-day working-team cadence including standups, planning, decision-tracking, and documentation, so the team stays aligned on priorities and next steps. 3. Build and maintain program dashboards and reporting that give engineering and cross-functional stakeholders a clear view of progress, risk, and decisions. 4. Manage cross-team dependencies with partner teams across catalog, indexing, retrieval, serving, and ads quality