2027 Capital Markets, Quantitative Technology Services Summer Analyst

We need to output HTML fragment with sections: About the role? Actually we have sections: About RBC Capital Markets (company description) maybe "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have content: About RBC Capital Markets (company overview) - could be "About the role"? Actually "About the role" is more about the job. We have "WHAT WILL YOU DO?" which is responsibilities. So we can have

Responsibilities

with list of duties. Also "WHAT DO YOU NEED TO SUCCEED?" includes qualifications and skills. Could split into Requirements (essential qualifications) and Skills (valuable experience). Also "WHAT'S IN IT FOR YOU?" includes benefits (mentorship, exposure, etc.) Could be Benefits. Also we have Pay: "The good-faith expected salary for the above position is $110,000 annualized ...". So we can include Pay section. Schedule: Work hours/week: 40, Employment Type: Full time. So we can include Schedule section (hours/week). Also location maybe not needed. We should not repeat job title. No Job ID. Remove boilerplate like EEO etc. We need to preserve all substantive info. Let's extract: About RBC Capital Markets: description paragraph(s). Could be placed under a heading "About the role"? But maybe better to have "About the role" summarizing the role? However we have no explicit "About the role" heading; we have "WHAT WILL YOU DO?" which is responsibilities. The company description could be placed under a heading "About RBC Capital Markets" but instruction only lists example headings; but we can use any heading? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when applicable. So we should map content to those headings. The company overview could go under "About the role"? Might be okay. But "About the role" usually describes the role, not company. However we have no separate company description heading; we could still include it as a paragraph before responsibilities? 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 adding other headings not listed, but 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 only. So we need to fit content into those categories. Let's map: - About the role: could include the introductory paragraph about the Summer Analyst Program and what you'll do? Actually that's responsibilities. Maybe "About the role" could contain the brief overview of the program (the first paragraph after "Job Description"? The posting starts with "Job Description ABOUT RBC CAPITAL MARKETS ..." then "WHAT WILL YOU DO?" So we could treat "About the role" as the description of the role/program (the Summer Analyst Program). That includes: "Join our Summer Analyst Program and make a real impact..." etc. That's actually under WHAT WILL YOU DO? but we can split. Better: Use "About the role" for the program overview (the first paragraph after "Job Description"? Actually the text: "Job Description ABOUT RBC CAPITAL MARKETS RBC Capital Markets is a premier investment bank..." then "WHAT WILL YOU DO? Join our Summer Analyst Program..." So the role description is after that. We'll put the program overview in About the role. Responsibilities: list of duties from WHAT WILL YOU DO? (the bullet-like sentences). We'll extract each sentence as list items. Requirements: essential qualifications (Entering final year..., Strong analytical..., Demonstrated interest..., History of academic excellence..., Strong communication..., Preferably pursuing a degree...). We'll list as

. Qualifications: maybe we could treat "Valuable experience and skills" as Qualifications or Skills. The instruction includes both Requirements and Qualifications and Skills. We could put essential qualifications under Requirements, and valuable experience under Skills. Or we could put valuable experience under Qualifications. Let's decide: Requirements = essential qualifications. Qualifications = valuable experience and skills? But Skills also listed. Could combine valuable experience and skills under Skills. However we have both "Valuable experience and skills (the more, the better):" then categories: Programming, Data Science & AI, Data Engineering, Cloud & Infrastructure, Software Engineering, Systems & DevOps, Financial acumen, Business Analysis. That's a list of skill areas. So we can put that under Skills. Benefits: WHAT'S IN IT FOR YOU? list of benefits (mentorship, exposure, tangible impact, career acceleration, skill development, network, culture). We'll list as
. Pay: The good-faith expected salary... $110,000 annualized depending on factors... Also note non-exempt and paid at equivalent hourly rate. We'll include that. Schedule: Work hours/week: 40, Employment Type: Full time. Also maybe mention Student/Coop (Fixed Term) but that's job type. We'll include hours/week and employment type. We should not include sections with filler like "commensurate with experience". Pay is specific ($110,000). Good. Now produce HTML fragment:

About the role

Join our Summer Analyst Program and make a real impact on the future of Capital Markets. You'll work on meaningful projects that shape how we serve clients - from building intelligent trading systems to developing data pipelines that power our decision-making. Alongside experienced technologists, you'll design, develop, and deploy tools that matter. This isn't a passive learning experience. You'll own real deliverables in a collaborative project team setting, guided by RBC Capital Markets' lead architects and technologists. You'll gain hands-on exposure to cutting-edge technologies including machine learning, data engineering, cloud infrastructure, and algorithmic trading systems. Dedicated mentoring sessions with business-aligned technology leaders will deepen your understanding of how technology drives client value across trading, risk management, and market operations. Beyond the work itself, you'll network with peers across Capital Markets through social events and skill-building sessions, building relationships that often lead to full-time opportunities.

But note that some of that is also responsibilities. Might duplicate. However we need to avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. We can split but ensure we don't lose any info. The "About the role" paragraph could be the overview; responsibilities list can be more specific duties. Let's extract responsibilities list from WHAT WILL YOU DO? after the first paragraph? Actually the WHAT WILL YOU DO? section includes: - Join our Summer Analyst Program and make a real impact on the future of Capital Markets. - You'll work on meaningful projects that shape how we serve clients - from building intelligent trading systems to developing data pipelines that power our decision-making. - Alongside experienced technologists, you'll design, develop, and deploy tools that matter. - This isn't a passive learning experience. You'll own real deliverables in a collaborative project team setting, guided by RBC Capital Markets' lead architects and technologists. - You'll gain hands-on exposure to cutting-edge technologies including machine learning, data engineering, cloud infrastructure, and algorithmic trading systems. - Dedicated mentoring sessions with business-aligned technology leaders will deepen your understanding of how technology drives client value across trading, risk management, and market operations. - Beyond the work itself, you'll network with peers across Capital Markets through social events and skill-building sessions, building relationships that often lead to full-time opportunities. - You'll have the opportunity to contribute to one or more of these areas: Architecture – Shape the foundational systems that power modern capital markets; eTrading & Algorithmic Trading Technology – Work on platforms that execute trades at scale with intelligence and precision; Commodities & Futures Technology – Apply data science and automation to commodity markets; Equities Technology – Leverage machine learning to enhance equity trading and market intelligence; Market Data Operations and Engineering – Build systems that aggregate, process, and deliver critical market data; Fixed Income & Currencies Technology – Develop analytical tools and trading systems for global markets; AI & Machine Learning Engineering – Build predictive models, develop recommendation systems, and optimize trading algorithms. We can turn each bullet into
• . The last bullet includes a colon and list of areas; we could keep as one li with sublist? Simpler: keep as one li containing the sentence and then maybe a nested ul for areas. But instruction: use
  • for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do nested. Thus Responsibilities section:

    Responsibilities

    • Join our Summer Analyst Program and make a real impact on the future of Capital Markets.
    • You'll work on meaningful projects that shape how we serve clients - from building intelligent trading systems to developing data pipelines that power our decision-making.
    • Alongside experienced technologists, you'll design, develop, and deploy tools that matter.
    • This isn't a passive learning experience. You'll own real deliverables in a collaborative project team setting, guided by RBC Capital Markets' lead architects and technologists.
    • You'll gain hands-on exposure to cutting-edge technologies including machine learning, data engineering, cloud infrastructure, and algorithmic trading systems.
    • Dedicated mentoring sessions with business-aligned technology leaders will deepen your understanding of how technology drives client value across trading, risk management, and market operations.
    • Beyond the work itself, you'll network with peers across Capital Markets through social events and skill-building sessions, building relationships that often lead to full-time opportunities.
    • You'll have the opportunity to contribute to one or more of these areas:
      • Architecture – Shape the foundational systems that power modern capital markets
      • eTrading & Algorithmic Trading Technology – Work on platforms that execute trades at scale with intelligence and precision
      • Commodities & Futures Technology – Apply data science and automation to commodity markets
      • Equities Technology – Leverage machine learning to enhance equity trading and market intelligence
      • Market Data Operations and Engineering – Build systems that aggregate, process, and deliver critical market data
      • Fixed Income & Currencies Technology – Develop analytical tools and trading systems for global markets
      • AI & Machine Learning Engineering – Build predictive models, develop recommendation systems, and optimize trading algorithms
    Now Requirements (essential qualifications):

    Requirements

    • Entering the final year of a four-year college or university program or enrolled in a relevant master's program (anticipating graduation Winter 2027 or Spring 2028)
    • Strong analytical and problem-solving skills
    • Demonstrated interest in technology, financial markets, or both
    • History of academic excellence
    • Strong communication and interpersonal skills
    • Preferably pursuing a degree in Computer Science, Engineering, Mathematics, Physics, Statistics, Data Science or Business Analytics
    Skills (valuable experience and skills):

    Skills

    • Programming: Python, Java, C#, C/C++, or Scala; familiarity with frameworks like .NET or J2EE
    • Data Science & AI: Experience with machine learning libraries, statistical modeling, or predictive analytics
    • Data Engineering: SQL and/or NoSQL databases; ETL pipeline development; familiarity with tools like Spark or Kafka