Senior Staff Portfolio Manager
SiriusXM · New York, NY · 1 mo ago
HybridFinance$156k–$200k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we have "Who We Are" (company description) maybe not needed as section? The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. We have content: "Who We Are" (company overview) maybe not a standard heading but could be "About the company"? Not in list. Probably we should include "About the role"? Not present. We have "How You’ll Make An Impact" (role description) maybe treat as "About the role". Then "What You’ll Do" as Responsibilities. Then "What You’ll Need" as Requirements/Qualifications/Skills. Also we have Pay range: "We expect the base salary for this position to be in the range of $156,200 to $200,000". Also mention discretionary incentives. So we can include Pay section. Benefits? Not mentioned. Schedule? Not mentioned. So we include About the role (How You’ll Make An Impact), Responsibilities (What You’ll Do), Requirements (What You’ll Need), Pay (salary range). Possibly also Qualifications separate? But we can combine Requirements and Qualifications. The instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Pay.
We need to use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. We have content: "Who We Are" (company overview) maybe not a standard heading but could be "About the company"? Not in list. Probably we should include "About the role"? Not present. We have "How You’ll Make An Impact" (role description) maybe treat as "About the role". Then "What You’ll Do" as Responsibilities. Then "What You’ll Need" as Requirements/Qualifications/Skills. Also we have Pay range: "We expect the base salary for this position to be in the range of $156,200 to $200,000". Also mention discretionary incentives. So we can include Pay section. Benefits? Not mentioned. Schedule? Not mentioned. So we include About the role (How You’ll Make An Impact), Responsibilities (What You’ll Do), Requirements (What You’ll Need), Pay (salary range). Possibly also Qualifications separate? But we can combine Requirements and Qualifications. The instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Pay.
We need to use for each section heading. 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: EEO, legal, etc. Also remove duplicated lines, navigation, cookie, application instructions. Also remove "Must have legal right to work in the U.S."? That's a requirement; it's substantive. Keep it. Also "At SiriusXM, we carefully consider..." that's about compensation; we already have Pay. Keep.
We need to not include Job ID/requisition numbers as headings; we can drop them or put in a short
. The posting ends with "R-2026-06-16". That's likely a requisition ID. We can drop it or put in a short
maybe as metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can either drop it or include a short
. Probably drop it.
Now we need to extract content.
Who We Are: description of SiriusXM etc. This is company overview; maybe not needed as a section but could be included as "About the company"? Not in list. Could be omitted? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We have content for Who We Are, but not a standard heading. Could we treat it as "About the role"? No. Could we include a section "About the company"? Not in the list of allowed headings; but the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not create other headings like "Who We Are". So we may omit that section. However we need to preserve ALL substantive information; if we omit Who We Are, we lose that info. But maybe it's considered boilerplate? It's company description, maybe not essential for the job posting? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Could we embed it in a
under About the role? Possibly as part of role description? But it's not about the role. Could we add a section "About the company" but not in list? Might be okay if we treat it as a heading but not in the list? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests those are typical. Safer to include it as a
without a heading? But we need headings for sections. Could we put it under a heading "About the role"? Not accurate. Maybe we can treat "Who We Are" as "About the role"? Not correct.
Alternative: we could include a section "About the company" as an
even though not listed; risk of violating instruction? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, but the examples are given. It might be okay to use other headings as long as they are . However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can add a heading for Who We Are if we have content. I'd include it.
But to be safe, maybe we can incorporate the Who We Are content into a
under a heading "About the role"? Not ideal but maybe acceptable. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings.
I'll include a section "About the company" as
About the company
with the Who We Are paragraph(s). Then sections: About the role (How You’ll Make An Impact), Responsibilities (What You’ll Do), Requirements (What You’ll Need), Pay (salary range and incentives). We'll not include Benefits, Schedule.
Now we need to extract the content precisely.
Who We Are paragraph: It starts with "Who We Are SiriusXM and its brands (Pandora, SiriusXM Media, AdsWizz, Simplecast, and SiriusXM Connect) are leading a new era of audio entertainment and services by delivering the most compelling subscription and ad-supported audio entertainment experience for listeners -- in the car, at home, and anywhere on the go with connected devices. Our vision is to shape the future of audio, where everyone can be effortlessly connected to the voices, stories and music they love wherever they are. This is the place where a diverse group of emerging talent and legends alike come to share authentic and purposeful songs, stories, sounds and insights through some of the best programming and technology in the world. Our critically-acclaimed, industry-leading audio entertainment encompasses music, sports, comedy, news, talk, live events, and podcasting. No matter their individual role, each of our employees plays a vital part in bringing SiriusXM’s vision to life every day. SiriusXM SiriusXM is the leading audio entertainment company in North America, and the premier programmer and platform for subscription and digital advertising-supported audio products. SiriusXM’s platforms collectively reach approximately 150 million listeners, the largest digital audio audience across paid and free tiers in North America, and deliver music, sports, talk, news, comedy, entertainment and podcasts. Pandora, a subsidiary of SiriusXM, is the largest ad-supported audio entertainment streaming service in the U.S. SiriusXM's subsidiaries Simplecast and AdsWizz make it a leader in podcast hosting, production, distribution, analytics and monetization. The Company’s advertising sales organization, which operates as SiriusXM Media, leverages its scale, cross-platform sales organization and ad tech capabilities to deliver results for audio creators and advertisers. SiriusXM, through SiriusXM Canada Holdings, Inc., also offers satellite radio and audio entertainment in Canada. In addition to its audio entertainment businesses, SiriusXM offers connected vehicle services to automakers."
We need to preserve all that. Might be long but okay.
How You’ll Make An Impact: paragraph(s). Let's extract:
"The Senior Staff Portfolio Manager is a senior individual contributor on the Planning & Portfolio team, responsible for the operational integrity and strategic governance of SiriusXM's technology portfolio. This role owns executive reporting, financial data governance, program tooling, and cross-functional coordination across Lisa Garnett-Willis's engineering and technology organization. The role requires strong financial acumen, deep familiarity with portfolio tooling and data infrastructure, and the ability to partner directly with Finance, Engineering leadership, and senior TPM leads. In addition, this role defines and continuously improves portfolio governance standards (cadences, controls, and success metrics) that drive portfolio transparency, audit readiness, and delivery accountability across the organization."
That's the content.
What You’ll Do: bullet list of duties. Let's extract each sentence as a bullet.
- Own quarterly capitalization and FP&A coordination, ensuring timesheet data and project classifications are accurate and audit-ready at the organizational level. This includes establishing classification standards, resolving ambiguous cases with Finance and Engineering leadership, and proactively surfacing capitalization risk and remediation actions.
- Maintain and evolve the Team Resource Manager (TRM), EOS, and related portfolio data infrastructure by improving data models, integrations, and controls to ensure a trusted, scalable single source of truth for portfolio and financial reporting.
- Drive executive reporting cycles including WBR inputs, OK2 gate review documentation, and exec dashboard maintenance and translate insights into clear decision-ready narratives, recommendations, and follow-through on actions.
- Partner with TPM and Engineering leads on SDLC governance, initiative tracking, and Jira hierarchy compliance by defining standards, enabling adoption, and running periodic compliance/quality checks to ensure portfolio health is visible and actionable.
- Manage 3P vendor SOWs and Jira Cloud migration deliverables in coordination with Legal and Engineering including scope governance, milestone tracking, vendor performance management, and risk/issue escalation.
- Own portfolio documentation and process standards; ensure team knowledge is captured and scalable through playbooks, templates, and training that increase consistency and reduce dependency on tribal knowledge.
- Provide senior portfolio management support for complex, cross-functional programs including escalation tracking and stakeholder reporting by driving alignment on scope, milestones, dependencies, and executive communications across multiple teams.
- Help define and mature portfolio governance practices across the organization including the operating model for portfolio reviews, gates, and metrics, and the continuous improvement roadmap based on stakeholder feedback and data.
We need to keep each as - .
What You’ll Need: requirements.
Extract:
"Typically requires a minimum of 8 years of related experience with a Bachelor’s degree; or 7 years and a Master’s degree; or a PhD with 5 years experience; or equivalent experience.
Strong financial acumen; direct experience with capitalization, CapEx tracking, or FP&A processes required
Vendor Management experience including SOW governance and delivery/financial performance management.
Proficiency with Jira, EOS or similar enterprise portfolio tooling, and Google Workspace with ability to define standards and improve data quality at scale.
Demonstrated ability to operate independently with senior stakeholders and drive cross-functional alignment in ambiguous environments with competing priorities.
Exceptional analytical skills and high bar for data quality and process rigor (controls, auditability, and repeatable operating cadences).
Experience shaping or maturing governance practices at the organizational level preferred
Experience with automation and/or AI tools such as ChatGPT, Gemini, etc.
Must have legal right to work in the U.S."
Also there is a line: "At SiriusXM, we carefully consider a wide range of factors when determining compensation, including your background and experience. These considerations can cause your compensation to vary. We expect the base salary for this position to be in the range of $156,200 to $200,000 and will depend on your skills, qualifications, and experience. Additionally, this role might be eligible for discretionary short-term and long-term incentives."
We'll put that in Pay section.
Now we need to strip boilerplate: EEO statement
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, legal, etc. Also remove duplicated lines, navigation, cookie, application instructions. Also remove "Must have legal right to work in the U.S."? That's a requirement; it's substantive. Keep it. Also "At SiriusXM, we carefully consider..." that's about compensation; we already have Pay. Keep. We need to not include Job ID/requisition numbers as headings; we can drop them or put in a short
. The posting ends with "R-2026-06-16". That's likely a requisition ID. We can drop it or put in a short
maybe as metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can either drop it or include a short
. Probably drop it. Now we need to extract content. Who We Are: description of SiriusXM etc. This is company overview; maybe not needed as a section but could be included as "About the company"? Not in list. Could be omitted? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We have content for Who We Are, but not a standard heading. Could we treat it as "About the role"? No. Could we include a section "About the company"? Not in the list of allowed headings; but the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not create other headings like "Who We Are". So we may omit that section. However we need to preserve ALL substantive information; if we omit Who We Are, we lose that info. But maybe it's considered boilerplate? It's company description, maybe not essential for the job posting? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Could we embed it in a
under About the role? Possibly as part of role description? But it's not about the role. Could we add a section "About the company" but not in list? Might be okay if we treat it as a heading but not in the list? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests those are typical. Safer to include it as a
without a heading? But we need headings for sections. Could we put it under a heading "About the role"? Not accurate. Maybe we can treat "Who We Are" as "About the role"? Not correct. Alternative: we could include a section "About the company" as an
even though not listed; risk of violating instruction? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, but the examples are given. It might be okay to use other headings as long as they are
. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can add a heading for Who We Are if we have content. I'd include it. But to be safe, maybe we can incorporate the Who We Are content into a
under a heading "About the role"? Not ideal but maybe acceptable. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings. I'll include a section "About the company" as
About the company
with the Who We Are paragraph(s). Then sections: About the role (How You’ll Make An Impact), Responsibilities (What You’ll Do), Requirements (What You’ll Need), Pay (salary range and incentives). We'll not include Benefits, Schedule. Now we need to extract the content precisely. Who We Are paragraph: It starts with "Who We Are SiriusXM and its brands (Pandora, SiriusXM Media, AdsWizz, Simplecast, and SiriusXM Connect) are leading a new era of audio entertainment and services by delivering the most compelling subscription and ad-supported audio entertainment experience for listeners -- in the car, at home, and anywhere on the go with connected devices. Our vision is to shape the future of audio, where everyone can be effortlessly connected to the voices, stories and music they love wherever they are. This is the place where a diverse group of emerging talent and legends alike come to share authentic and purposeful songs, stories, sounds and insights through some of the best programming and technology in the world. Our critically-acclaimed, industry-leading audio entertainment encompasses music, sports, comedy, news, talk, live events, and podcasting. No matter their individual role, each of our employees plays a vital part in bringing SiriusXM’s vision to life every day. SiriusXM SiriusXM is the leading audio entertainment company in North America, and the premier programmer and platform for subscription and digital advertising-supported audio products. SiriusXM’s platforms collectively reach approximately 150 million listeners, the largest digital audio audience across paid and free tiers in North America, and deliver music, sports, talk, news, comedy, entertainment and podcasts. Pandora, a subsidiary of SiriusXM, is the largest ad-supported audio entertainment streaming service in the U.S. SiriusXM's subsidiaries Simplecast and AdsWizz make it a leader in podcast hosting, production, distribution, analytics and monetization. The Company’s advertising sales organization, which operates as SiriusXM Media, leverages its scale, cross-platform sales organization and ad tech capabilities to deliver results for audio creators and advertisers. SiriusXM, through SiriusXM Canada Holdings, Inc., also offers satellite radio and audio entertainment in Canada. In addition to its audio entertainment businesses, SiriusXM offers connected vehicle services to automakers." We need to preserve all that. Might be long but okay. How You’ll Make An Impact: paragraph(s). Let's extract: "The Senior Staff Portfolio Manager is a senior individual contributor on the Planning & Portfolio team, responsible for the operational integrity and strategic governance of SiriusXM's technology portfolio. This role owns executive reporting, financial data governance, program tooling, and cross-functional coordination across Lisa Garnett-Willis's engineering and technology organization. The role requires strong financial acumen, deep familiarity with portfolio tooling and data infrastructure, and the ability to partner directly with Finance, Engineering leadership, and senior TPM leads. In addition, this role defines and continuously improves portfolio governance standards (cadences, controls, and success metrics) that drive portfolio transparency, audit readiness, and delivery accountability across the organization." That's the content. What You’ll Do: bullet list of duties. Let's extract each sentence as a bullet. - Own quarterly capitalization and FP&A coordination, ensuring timesheet data and project classifications are accurate and audit-ready at the organizational level. This includes establishing classification standards, resolving ambiguous cases with Finance and Engineering leadership, and proactively surfacing capitalization risk and remediation actions. - Maintain and evolve the Team Resource Manager (TRM), EOS, and related portfolio data infrastructure by improving data models, integrations, and controls to ensure a trusted, scalable single source of truth for portfolio and financial reporting. - Drive executive reporting cycles including WBR inputs, OK2 gate review documentation, and exec dashboard maintenance and translate insights into clear decision-ready narratives, recommendations, and follow-through on actions. - Partner with TPM and Engineering leads on SDLC governance, initiative tracking, and Jira hierarchy compliance by defining standards, enabling adoption, and running periodic compliance/quality checks to ensure portfolio health is visible and actionable. - Manage 3P vendor SOWs and Jira Cloud migration deliverables in coordination with Legal and Engineering including scope governance, milestone tracking, vendor performance management, and risk/issue escalation. - Own portfolio documentation and process standards; ensure team knowledge is captured and scalable through playbooks, templates, and training that increase consistency and reduce dependency on tribal knowledge. - Provide senior portfolio management support for complex, cross-functional programs including escalation tracking and stakeholder reporting by driving alignment on scope, milestones, dependencies, and executive communications across multiple teams. - Help define and mature portfolio governance practices across the organization including the operating model for portfolio reviews, gates, and metrics, and the continuous improvement roadmap based on stakeholder feedback and data. We need to keep each as - . What You’ll Need: requirements. Extract: "Typically requires a minimum of 8 years of related experience with a Bachelor’s degree; or 7 years and a Master’s degree; or a PhD with 5 years experience; or equivalent experience. Strong financial acumen; direct experience with capitalization, CapEx tracking, or FP&A processes required Vendor Management experience including SOW governance and delivery/financial performance management. Proficiency with Jira, EOS or similar enterprise portfolio tooling, and Google Workspace with ability to define standards and improve data quality at scale. Demonstrated ability to operate independently with senior stakeholders and drive cross-functional alignment in ambiguous environments with competing priorities. Exceptional analytical skills and high bar for data quality and process rigor (controls, auditability, and repeatable operating cadences). Experience shaping or maturing governance practices at the organizational level preferred Experience with automation and/or AI tools such as ChatGPT, Gemini, etc. Must have legal right to work in the U.S." Also there is a line: "At SiriusXM, we carefully consider a wide range of factors when determining compensation, including your background and experience. These considerations can cause your compensation to vary. We expect the base salary for this position to be in the range of $156,200 to $200,000 and will depend on your skills, qualifications, and experience. Additionally, this role might be eligible for discretionary short-term and long-term incentives." We'll put that in Pay section. Now we need to strip boilerplate: EEO statement