IT Program & Portfolio Manager

We need to output HTML fragment with sections: About Us? Actually "About Us" is part of description; but we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction: 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. So we need to map content to these headings. We have content: About Us (company description) maybe fits "About the role"? Actually "About the role" is a summary of role. We have "Role Summary". That could be "About the role". Then responsibilities: "What You’ll Do" bullet list. Requirements/Qualifications: "Skills And Experience". Benefits: "What We Offer". Pay: "The salary range is $120,000 - $140,000 dependent on experience." Also "Compensation Range: $120K - $140K". Schedule: "This is a hybrid role where you will work from the Manhattan office two - three days a week." We need to include sections only when posting has real specific content. All these have content. We must not include boilerplate like EEO, etc. Remove duplicated lines. Also remove "Applicants must be authorized to work in the United States. The Community Preservation Corporation does not provide employment sponsorship of any kind." That's maybe not required but could be considered minor metadata; we can fold into a short p or drop. Probably drop as not needed. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like bullet points under responsibilities, skills, benefits. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  About the role

  Role Summary ...

  Responsibilities

  • Technology Portfolio Management ... (list each bullet)
  ...
  But we have many bullet points under "What You’ll Do" with subheadings like Technology Portfolio Management, Program & Project Governance, etc. Those are subheadings but we are not to create extra headings unless needed? 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 we should follow that pattern. Probably we can keep subheadings as

  or just keep as

  with bold? But we must not invent headings not listed? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can treat each bullet as

  and include the subheading text inside the

  as plain text. Thus each responsibility bullet can be a

  containing the description. Similarly for Skills And Experience: we can treat as Requirements/Qualifications section. We need to decide whether to split Skills And Experience into Requirements and Qualifications or Skills. The instruction lists both Requirements and Qualifications as possible headings. We have "Skills And Experience". Could map to either Requirements or Qualifications or Skills. Probably best to use

  Skills

  for the list of skills and experience. Or we could use Requirements. Let's use Skills. Thus:

  Skills

  • 7+ years of experience in program management, portfolio management, PMO, technology operations, or a related field, with 5+ years leading complex cross-functional initiatives and working with senior stakeholders.
  ...

  Benefits: "What We Offer" list. Pay:

  Pay

  The salary range is $120,000 - $140,000 dependent on experience.

  Schedule:

  Schedule

  This is a hybrid role where you will work from the Manhattan office two - three days a week.

  We also need to include maybe "About Us" as part of About the role? Actually About the role should be role summary. We'll put that. We need to ensure we don't include duplicated lines like "Compensation Range: $120K - $140K" duplicate; we already have pay. We need to remove boilerplate: EEO, etc. Now produce HTML. Let's craft. Check that we preserve all substantive information: The About Us description (company mission) maybe not required? It's about the company, not role. The instruction says preserve ALL substantive information; do not invent or summarize away detail. Should we include About Us? It's substantive about the company. But the headings we have are limited; we could include an

  About the Company

  but not in the list. However instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings; but we could also add other headings if needed? It says "use

  for section headings (e.g. ...)" meaning those are examples of headings we should use; but we could also use other headings if needed? Safer to stick to those headings. The About Us content could be placed under About the role? Not ideal but maybe we can incorporate into About the role paragraph as a brief intro? However About the role is supposed to be role summary; we could prepend company description as part of role summary? Might be okay. But the instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It doesn't forbid other headings besides those examples. However they gave a list of possible headings; they likely expect us to use those headings for the sections we have. The About Us is not a role; but we could treat it as "About the role" includes company context? Might be okay. Alternatively we could add an

  About the Company

  but that's not in the list; risk of being considered not following instruction. I'd rather include it as a

  before the headings, not as a heading. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but to be safe we can avoid extra headings. We'll put About Us as a

  before the first heading. Thus output:

  About Us ...

  Then

  About the role

  with role summary. Then responsibilities etc. Let's compile About Us text: "The Community Preservation Corporation (CPC) believes stable and sustainable affordable housing is the foundation of strong communities, and we strive to contribute to comprehensive neighborhood revitalization through our lending and partnerships. A nationally recognized leader in affordable housing finance, CPC has provided a consistent source of capital to underserved housing markets throughout New York State since our inception in 1974. Today, CPC stands as the largest CDFI solely committed to investing in multifamily housing, having invested more than $15 billion to finance the creation and preservation of more than 230,000 units of quality housing in neighborhoods across New York State and beyond. CPC has a robust construction lending platform, a mortgage bank, and equity and impact investment platforms that focus on our three goals: Expanding Affordable Housing, Closing the Racial Wealth Gap and Investing in the Green Economy. As a member of our team, you'll have the opportunity to work on impactful projects that make a real difference in people's lives. We're looking for talented individuals who are passionate about our mission and share our values of commitment, respect, excellence, accountability, and collaboration." That's a lot; we keep it. Now Role Summary: "The IT Program & Portfolio Manager is a key member of CPC’s Business Technology organization responsible for establishing and managing the processes, governance, and visibility required to successfully deliver CPC’s technology portfolio. Reporting to the CIO, this role will work across Technology Operations, Applications, Data & Analytics, and Strategy & Portfolio Management to coordinate programs and projects, maintain the enterprise technology roadmap, facilitate prioritization, track delivery, manage dependencies and risks, and provide clear reporting to technology and business leadership. The Program & Portfolio Manager will serve as the central coordination point between technology teams, business stakeholders, vendors, and executive leadership, ensuring initiatives are well-defined, appropriately prioritized, effectively governed, and aligned with CPC’s business priorities. The ideal candidate is a highly organized, collaborative, and business-oriented program leader who can bring structure and transparency to a complex portfolio while enabling teams to execute successfully." Now Responsibilities: list each bullet under "What You’ll Do". We need to capture all bullet points. Let's extract: Technology Portfolio Management - Establish and maintain CPC’s consolidated Technology Portfolio and Roadmap across Technology Operations, Applications, Data & Analytics, Digital Workplace, Automation & AI, and other strategic initiatives. - Maintain visibility into active, planned, proposed, and completed initiatives. - Establish consistent project intake, evaluation, prioritization, and approval processes. - Partner with the CIO and technology leaders to align investments and resources with CPC business priorities. - Identify portfolio-level dependencies, resource constraints, risks, and competing priorities. - Maintain portfolio information and dashboards within Smartsheet or other designated portfolio management platforms. Program & Project Governance - Establish practical and consistent program/project management standards, templates, stage gates, status reporting, and governance practices. - Facilitate regular program and project review meetings with technology leaders, project owners, business stakeholders, and vendors. - Ensure projects have clearly defined scope, objectives, ownership, milestones, timelines, risks, dependencies, and success measures. - Track project commitments and follow up on actions, decisions, issues, and deliverables. - Escalate material risks, delays, resource constraints, and decisions requiring leadership attention. - Support project teams in removing obstacles and maintaining delivery momentum. Executive Reporting & Communication - Develop concise portfolio dashboards and executive reporting covering overall portfolio health, milestones, risks, dependencies, budget, and business outcomes. - Prepare materials for CIO leadership reviews, Technology Steering Committee meetings, and other governance forums. - Translate detailed project information into clear business-oriented communications for senior leadership. - Maintain a regular communication cadence so stakeholders understand what is being delivered, what is changing, and where decisions or support are required. Business Relationship & Demand Management - Partner with business and technology leaders to understand emerging needs and translate them into structured technology initiatives. - Coordinate technology demand and project intake across CPC business functions. - Facilitate early discussions around business objectives, expected outcomes, requirements, timing, and resource needs. - Ensure technology initiatives have appropriate business ownership and sponsorship. - Promote transparency around prioritization decisions and portfolio capacity. Program & Project Delivery - Directly manage selected strategic or cross-functional technology programs and projects as needed. - Coordinate activities across internal teams, external vendors, consultants, and business stakeholders. - Establish project plans, milestones, deliverables, RAID logs, decision logs, and communication plans. - Monitor scope, schedule, budget, quality, and delivery performance. - Support change management, communications, training, and adoption activities associated with major technology initiatives. Financial & Vendor Coordination - Partner with the CIO and technology leaders to track project budgets, forecasts, vendor commitments, and planned technology