Technology Portfolio Analyst

We need to output HTML fragment with sections: Overview? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. The posting includes Overview, Responsibilities, Qualifications, Preferred Qualifications, Salary range (Pay), Benefits. Also maybe "Duration: FTE Location: MN-Inver Grove, 100% Remote" is metadata; we can fold into short

or drop. We should not repeat job title. No markdown fences. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes EEO statement and ADA accommodation; those are boilerplate, should be removed. Also "No matter where or when you begin a career with Turnberry, you'll find a far-reaching choice of benefits and incentives." That's maybe fluff but still part of benefits description; we can keep as part of benefits? It's somewhat generic but still about benefits. Might keep but it's not specific detail; but it's not boilerplate? It's a generic statement about benefits; but we can keep as part of benefits paragraph. We need to include sections: Overview (maybe as About the role?), Responsibilities, Qualifications (maybe combine Qualifications and Preferred Qualifications? The instruction says use headings like Qualifications, Skills, Benefits, Pay, Schedule. We have Qualifications (required) and Preferred Qualifications. Could combine into Qualifications section with subpoints? But we should not invent headings not listed. Could have Qualifications and then maybe a separate Skills? But we have no explicit Skills section; we could embed skills within Qualifications. Better to follow instruction: Use headings for sections that exist. So we can have Overview (maybe as About the role), Responsibilities, Qualifications, Benefits, Pay. No Schedule. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive info: Let's extract. Overview paragraph: "Every Turnberry consultant belongs to a practice, an internal group of consultants and leaders with shared experience and expertise. Each of these practices aligns to one of the core services Turnberry offers to clients. As a Technology Portfolio Analyst, you will join Turnberry's Business Transformation practice. Turnberry's Business Transformation practice is dedicated to diagnosing and addressing core business challenges including regulatory compliance, full-scale implementation, managing change and driving continuous improvement across transformation initiatives." That's overview. Responsibilities list bullet points: many lines. We'll put each as

• . Qualifications: list of required qualifications bullet points. We'll put as
• . Preferred Qualifications: also list; we could include under Qualifications as separate subsection? But we cannot create new headings not in list. Could add a

  for Preferred Qualifications? Not in allowed list but maybe acceptable as it's a heading. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive; we could still use other headings? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we could incorporate Preferred Qualifications into Qualifications section, maybe as a note. However we must preserve all substantive info; we can include them as part of Qualifications list, maybe differentiate with a note. That's okay. Benefits: list of benefits: comprehensive healthcare package (medical, dental, vision), disability and group term life insurance, health and flexible spending accounts, a utilization bonus, 401(k) with match, flexible time off for salaried employees, parental leave for salaried employees, flexible work arrangements (all benefits are subject to eligibility requirements). Also mention "No matter where or when you begin a career with Turnberry, you'll find a far-reaching choice of benefits and incentives." Could be a sentence. Pay: The salary range for this role is $62,000 to $85,000 or the hourly equivalent. Pay is based on several factors including but not limited to education, work experience, certifications, etc. We should not include Schedule. We need to strip boilerplate: EEO statement, ADA accommodation request, etc. Also remove duplicated lines: I see some duplicated lines in Qualifications: after list there is a repeated list of skills (Data stewardship and data quality monitoring...). That seems like a duplication of the qualifications list rephrased. We need to preserve all substantive info but not duplicate. The duplicated lines appear to be a summary of skills; we should include them only once. We'll combine. Let's extract Qualifications required: - Experience working with data management, portfolio management, enterprise architecture, or a related analytical function - Proficiency in Microsoft Excel, including formulas and functions used for validation, analysis, and reconciliation - Strong attention to detail and ability to maintain high standards for data accuracy - Experience gathering requirements and translating them into practical dashboards, reports, or process improvements - Strong written and verbal communication skills, including the ability to draft clear stakeholder communications - Ability to organize work, manage follow-up activities, and monitor progress across multiple requests or campaigns - Analytical and problem-solving skills with the ability to identify trends, issues, and improvement opportunities Then there is a repeated list: Data stewardship and data quality monitoring, Dashboard creation and reporting, Requirements gathering and stakeholder engagement, Survey administration and campaign tracking, Written communications and status reporting, Excel-based analysis, reconciliation, and validation, Process improvement and documentation, Organization, follow-through, and attention to detail. These are essentially same as above but phrased differently. We'll include them as part of Qualifications but avoid duplication. We could merge them into a single list, but we need to preserve all info; we can include them as additional bullet points but ensure not repeating same meaning. However many are similar; we could keep both sets but that would be duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicated lines are still substantive but repeating same info. Should we keep both? It says remove duplicated lines. So we should deduplicate. Thus we will produce a Qualifications list that combines unique items. Let's list unique items: - Experience working with data management, portfolio management, enterprise architecture, or a related analytical function - Proficiency in Microsoft Excel, including formulas and functions used for validation, analysis, and reconciliation - Strong attention to detail and ability to maintain high standards for data accuracy - Experience gathering requirements and translating them into practical dashboards, reports, or process improvements - Strong written and verbal communication skills, including the ability to draft clear stakeholder communications - Ability to organize work, manage follow-up activities, and monitor progress across multiple requests or campaigns - Analytical and problem-solving skills with the ability to identify trends, issues, and improvement opportunities - Data stewardship and data quality monitoring - Dashboard creation and reporting - Requirements gathering and stakeholder engagement (already similar to earlier) - Survey administration and campaign tracking - Written communications and status reporting (similar to strong written/verbal) - Excel-based analysis, reconciliation, and validation (similar to proficiency) - Process improvement and documentation - Organization, follow-through, and attention to detail (similar to strong attention) We need to deduplicate further: many overlap. Let's create a concise set that captures all unique concepts: - Experience in data management, portfolio management, enterprise architecture, or related analytical function - Proficiency with Microsoft Excel (formulas, functions for validation, analysis, reconciliation) - Strong attention to detail and commitment to data accuracy - Experience gathering requirements and translating them into dashboards, reports, or process improvements - Strong written and verbal communication skills, including drafting clear stakeholder communications - Ability to organize work, manage follow-up, and monitor progress across multiple requests or campaigns - Analytical and problem-solving skills to identify trends, issues, and improvement opportunities - Data stewardship and data quality monitoring - Dashboard creation and reporting - Survey administration and campaign tracking - Process improvement and documentation - Organization and follow-through That seems comprehensive. Now Preferred Qualifications list: - Experience with LeanIX or a similar enterprise architecture, CMDB, or technology portfolio management platform - Experience creating dashboards or reports using business intelligence or reporting tools - Familiarity with data quality frameworks, governance practices, or metadata management concepts - Understanding of application or technology portfolio management processes - Experience coordinating stakeholder surveys, outreach campaigns, or data collection initiatives - Comfort working cross-functionally with business and technology teams We'll include these as part of Qualifications maybe under a subheading? But we cannot add new headings. Could we add a

  for Preferred Qualifications? Not in examples but maybe allowed as it's a section heading. 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 says "use

  for section headings (e.g ...)". It implies those are the typical ones; but we could still use other headings if needed. However to be safe, we could incorporate Preferred Qualifications into Qualifications section, perhaps as a separate paragraph labeled "Preferred Qualifications:" but not as a heading. That would preserve info without extra heading. Thus Qualifications section will contain both required and preferred, maybe with a note. Now Benefits section: list as

  • . Pay section:

    with salary range and note. Overview section:

    with overview text. Responsibilities section:

    • each duty. Now we need to ensure we don't include any boilerplate like EEO, ADA, etc. Let's craft HTML. Start with maybe a

      for location/duration? The instruction: fold minor metadata into a short

      or drop it. We could include a short

      for Duration: FTE Location: MN-Inver Grove, 100% Remote. That's minor metadata. We'll include as a

      at top. Then Overview

      About the role

      maybe? The instruction says use

      for section headings (e.g. About the role, Responsibilities...). So we should use About the role as heading for overview. Good. Thus:

      About the role

      Overview text...

      Then Responsibilities:

      Responsibilities

      • ...
      Then Qualifications:

      Qualifications

      • ...
      Then Benefits:

      Benefits

      • ...
      Then Pay:

      Pay

      ...

      We should not include Schedule. Now ensure we preserve all substantive info from overview, responsibilities, qualifications (required+preferred), benefits, pay. Let's write the overview text exactly as given: "Every Turnberry consultant belongs to a practice, an internal group of consultants and leaders with shared experience and expertise. Each of these practices aligns to one of the core services Turnberry offers to clients. As a Technology Portfolio Analyst, you will join Turnberry's Business Transformation practice. Turnberry's Business Transformation practice is dedicated to diagnosing and addressing core business challenges including regulatory compliance, full-scale implementation, managing change and driving continuous improvement across transformation initiatives." Now responsibilities list (copy each bullet): - Maintain and update technology portfolio data in LeanIX to ensure accuracy, completeness, and consistency - Monitor data quality, identify gaps or inconsistencies, and follow up with stakeholders to resolve issues - Create dashboards and reports that provide meaningful insights into the technology portfolio and support decision-making - Gather business