Junior Risk Analyst

We need to output HTML fragment with sections: About the role? Actually we have "About Invesco" description, then "What’s in it for you?" benefits, then "Job Description" with responsibilities, then "Work Experience / Knowledge", "Skills / Other Personal Attributes Required", "Formal Education", "License / Registration / Certification", salary range, workplace model, etc. We must not repeat job title as heading. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to appropriate headings. The instructions: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings if content exists. We should not create sections with filler. We need to decide which sections to include. We have: - About Invesco (company overview) could map to "About the role"? Actually "About the role" is about the job, not company. But we have "About Invesco" describing company. Could we treat as "About the role"? Might be okay but better to have "About the role" summarizing job purpose. However we have "Job Description" with responsibilities. The "About Invesco" is more about company. The instruction says we can use those headings as examples; we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings where appropriate. We can also add other headings if needed? Probably stick to those. We need to include sections only when posting has real specific content. We have: - Responsibilities: many bullet points under "Key Responsibilities / Duties:" -> we can put under

Responsibilities

with

• . - Requirements: could combine Work Experience / Knowledge, Skills / Other Personal Attributes Required, Formal Education, License / Registration / Certification. Could be under

  Requirements

  or separate Qualifications and Skills. The instruction list includes Requirements, Qualifications, Skills. We could split: Qualifications (education, experience), Skills (technical/personal). But we need to avoid thin sections. Let's think. We have: Work Experience / Knowledge: experience, analytical skills, Python, etc. Skills / Other Personal Attributes Required: intellectual curiosity, communication, organized, etc. Formal Education: Bachelor's degree etc. License / Registration / Certification: progress towards CFA etc. We could combine into

  Requirements

  containing all those as subpoints? But they want
  • for any list of duties/requirements/benefits. So we could have a single

    Requirements

    with a
    • list combining all requirement items. That would be substantive. Benefits: we have "What’s in it for you?" list: Flexible paid time off, Hybrid work schedule, 401(K) matching..., Health & wellbeing benefits, Parental Leave benefits, Employee stock purchase plan. That's specific benefits. So we can have

      Benefits

      with
      • . Pay: we have salary range: $85,000-105,000 Base/year. Also mention total compensation includes salary and incentive pay and will vary based on skills, experience and location. That's specific enough for Pay section. So

        Pay

        with

        containing that info. Schedule: we have "Full Time / Part Time Full time" and workplace model: employees expected to spend at least four full days each week working in an Invesco office. That's schedule info. So we can have

        Schedule

        with

        describing full-time and expectation of 4 days in office. We also have "About Invesco" description. Could map to

        About the role

        maybe summarizing role purpose? But we have no explicit "About the role" paragraph. However we could treat the initial "About Invesco" as "About the role"? Might be a stretch but we could include a section "About the role" with that description. 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 they gave examples. Safer to include About the role with the company overview? Might be considered filler? It's substantive about the company, not role. But maybe they expect we include About the role with a brief description of the role (maybe from first paragraph after "Job Description"? Actually there is no explicit role summary. The "What’s in it for you?" is benefits. The "Job Description" starts with responsibilities. So we could omit About the role section if we don't have specific role summary. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". If we don't have a specific "About the role" paragraph, we should not create that heading. So we skip About the role. Thus sections: Responsibilities, Requirements, Benefits, Pay, Schedule. We need to ensure we preserve all substantive information. Let's extract details. Responsibilities list: from "Key Responsibilities / Duties:" bullet points (each line starts with a verb). We need to capture all. Let's copy them: - Produce and support daily/weekly performance measurement for assigned equity index and ETF portfolios, including benchmark comparisons, return decomposition, and tracking difference monitoring - Support index-relative attribution and diagnostics (sector/industry, factor, and security contributions) and translate results into clear narratives for stakeholders - Perform daily monitoring of attribution outputs and triage/clean up anomalies (e.g., missing/misaligned identifiers, stale or incorrect benchmark mappings, corporate action timing impacts, return outliers); coordinate with Technology, Operations, and Data teams to remediate root causes and document resolutions - Assist in producing daily, weekly, and ad-hoc risk, performance, and tracking reports for passive strategies and ETFs, with a focus on accuracy, repeatability, and timeliness - Help identify, validate, and explain changes in active risk, tracking error, and tracking difference, including key implementation drivers (rebalance timing, corporate actions, cash management, and trading costs) - Monitor and reconcile holdings vs. benchmark, index events, and corporate actions; investigate breaks that impact performance, attribution, and risk outputs; coordinate fixes and confirm resolution - Prepare analysis and materials for portfolio reviews, risk forums, and governance routines supporting the passive/ETF platform - Assist with monitoring compliance with internal risk limits and product guidelines (e.g., tracking error thresholds, concentration/issuer limits where applicable) and documenting alerts or breaches - Collaborate with portfolio managers, traders, ETF capital markets, and internal partners to support effective risk oversight and issue resolution - Respond promptly to complex performance, attribution, and risk queries from portfolio managers, Sales, Product, and Risk leadership - Maintain and enhance processes for risk, tracking, and performance exception monitoring, escalation, and documentation (including clear commentary for alerts, breaches, and material attribution outliers) - Contribute to process improvements and automation of performance/attribution and risk analytics and reporting using Python (and other approved tools), improving timeliness, controls, and data quality - Partner with Technology, Operations, Trading, and Data teams to resolve data breaks, support system enhancements, and improve inputs (e.g., benchmark files, corporate actions, index rebalances) - Provide ad-hoc analytics to support Equity Passive/ETF initiatives, new product reviews, index changes, and cross-department priorities as needed That's all. Now Requirements: combine Work Experience / Knowledge, Skills / Other Personal Attributes Required, Formal Education, License / Registration / Certification. Let's list each item as separate

        maybe. Work Experience / Knowledge: - 1+ years of relevant experience (internships included) in investment risk, performance measurement/attribution, portfolio analytics, trading/markets, or a related asset-management function; exposure to index/passive or ETFs is a plus - Strong analytical and quantitative skills, with interest in benchmarking, performance measurement, and attribution, as well as portfolio risk (e.g., factor exposures, volatility, drawdowns, tracking error, sector/industry exposures) - Strong Python skills for data analysis/automation (SQL experience a plus) - Experience with risk and performance/attribution systems and data workflows; FactSet and/or MSCI Risk Metrics experience a plus (index, benchmark, corporate action, and ETF data experience preferred) Skills / Other Personal Attributes Required: - Intellectual curiosity and interest in global equity markets, index investing, and ETF mechanics - Strong written and verbal communication skills - Well-organized, dependable, proactive, and detail-oriented (comfortable working with large datasets and repeatable processes) - Ability to manage multiple priorities, exercise sound judgment, and communicate clearly with portfolio managers and partners; comfort presenting concise findings and raising issues early - Collaborative mindset with a desire to learn from senior investment and risk professionals and partner effectively with trading, operations, product, and technology teams Formal Education: - Bachelor’s degree in finance, economics, mathematics, statistics, engineering, or a related field (advanced degree a plus) License / Registration / Certification: - Progress towards CFA, CIPM, or FRM is desirable We could also include that the salary range is $85,000-105,000 Base/year. And total compensation includes salary and incentive pay and will vary based on skills, experience and location. Schedule: Full time, and workplace model: employees expected to spend at least four full days each week working in an Invesco office (as of Oct 1, 2025). Also maybe mention "Full Time / Part Time Full time". So we can say: Full-time position; expected to work at least four days per week in office per Invesco's workplace model effective Oct 1, 2025. Benefits list: - Flexible paid time off - Hybrid work schedule - 401(K) matching of 100% up to the first 6% with a discretionary supplemental contribution - Health & wellbeing benefits - Parental Leave benefits - Employee stock purchase plan Now we need to output HTML fragment only, no /, no markdown. We'll produce:

        Responsibilities

        • ...
        ...

        Requirements

        • ...
        ...

        Benefits

        • ...
        ...

        Pay

        The salary range for this position in Downers Grove, IL is $85,000‑105,000 base per year. Total compensation includes salary and incentive pay and will vary based on skills, experience, and location.

        Schedule

        Full‑time role. Per Invesco’s workplace model effective October 1, 2025, employees are expected to spend at least four full days each week working in an Invesco office.

        We need to ensure we use correct hyphens and maybe en dash? Use regular hyphen. We should not include any boilerplate like EEO etc. We removed. Check that we didn't miss any substantive info: The "About Invesco" description about company is omitted; but is that considered substantive? It's about the company, not the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit that, we are losing substantive info about the company. However the instruction also says we can omit cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines