Wealth Builder Intern
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We need to map content to these headings appropriately.
We have:
- About Us: description of firm. Could be "About the role"? Actually "About the role" is not present. But we could use "About Us" as maybe "About the role"? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those headings when appropriate. If content doesn't match, maybe we shouldn't create a heading. But we need to preserve all substantive info. We could embed content under appropriate headings: "About the role" could contain description of the internship program. "Responsibilities" could contain "What You'll Actually Do". "Requirements" could contain "Who Thrives Here" (qualifications). "Skills" could contain specific skills (Microsoft Office, etc). "Benefits" from benefits section. "Pay" from compensation. "Schedule" from work schedule.
We must not repeat job title as heading. No job ID.
We must discard boilerplate like Privacy Policy, Vision/Mission/Values maybe? Vision/Mission/Values might be considered boilerplate? It's substantive? It's about firm values; could be included under "About the role"? But maybe we can include as part of "About the role" or separate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Vision/Mission/Values is not exactly boilerplate but could be considered generic. However they said "Prefer a few substantive sections over many thin ones." So we might combine Vision/Mission/Values into About the role or omit if not specific to role. The posting includes "Our Vision: To be the trusted partner in medicine, business, and life. Our Mission: By providing valued advice and support, we help strengthen care, mitigate risk, and build financial futures to enhance the lives of those we serve. Our Values ..." This is generic firm info, not specific to role. Might be considered boilerplate? It's not navigation/legal but still generic. I'd consider it okay to include under "About the role" as context. But we need to decide.
We must not create sections with filler like "commensurate with experience". In compensation section we have "$10,000 stipend for a 10-week program. The schedule is Monday – Thursday 9am – 4pm, and Friday 9am – 3pm local time. The base salary will be commensurate with an individual's work experience and educational background. US Pay Range $10,000 - $10,000 USD". The phrase "commensurate with an individual's work experience and educational background" is filler; we should avoid including that as a heading? Actually we can still include the compensation info but we should not create a Pay section if it only contains filler? The posting does state specific stipend $10,000 and schedule. So we can include Pay and Schedule sections with that info, but we should avoid the filler phrase. We can omit that sentence.
Similarly Benefits section: "Curi Capital offers eligible team members and their dependents comprehensive health benefits, including medical, dental, vision, and life insurance. Other benefits for eligible team members include education assistance, annual bonus opportunity, 401(k) with employer match, short-term and long-term disability, flexible time off, and 13 paid holidays annually." That's substantive.
We need to output only HTML fragment, no markdown.
Let's structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those headings when appropriate. If content doesn't match, maybe we shouldn't create a heading. But we need to preserve all substantive info. We could embed content under appropriate headings: "About the role" could contain description of the internship program. "Responsibilities" could contain "What You'll Actually Do". "Requirements" could contain "Who Thrives Here" (qualifications). "Skills" could contain specific skills (Microsoft Office, etc). "Benefits" from benefits section. "Pay" from compensation. "Schedule" from work schedule.
We must not repeat job title as heading. No job ID.
We must discard boilerplate like Privacy Policy, Vision/Mission/Values maybe? Vision/Mission/Values might be considered boilerplate? It's substantive? It's about firm values; could be included under "About the role"? But maybe we can include as part of "About the role" or separate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Vision/Mission/Values is not exactly boilerplate but could be considered generic. However they said "Prefer a few substantive sections over many thin ones." So we might combine Vision/Mission/Values into About the role or omit if not specific to role. The posting includes "Our Vision: To be the trusted partner in medicine, business, and life. Our Mission: By providing valued advice and support, we help strengthen care, mitigate risk, and build financial futures to enhance the lives of those we serve. Our Values ..." This is generic firm info, not specific to role. Might be considered boilerplate? It's not navigation/legal but still generic. I'd consider it okay to include under "About the role" as context. But we need to decide.
We must not create sections with filler like "commensurate with experience". In compensation section we have "$10,000 stipend for a 10-week program. The schedule is Monday – Thursday 9am – 4pm, and Friday 9am – 3pm local time. The base salary will be commensurate with an individual's work experience and educational background. US Pay Range $10,000 - $10,000 USD". The phrase "commensurate with an individual's work experience and educational background" is filler; we should avoid including that as a heading? Actually we can still include the compensation info but we should not create a Pay section if it only contains filler? The posting does state specific stipend $10,000 and schedule. So we can include Pay and Schedule sections with that info, but we should avoid the filler phrase. We can omit that sentence.
Similarly Benefits section: "Curi Capital offers eligible team members and their dependents comprehensive health benefits, including medical, dental, vision, and life insurance. Other benefits for eligible team members include education assistance, annual bonus opportunity, 401(k) with employer match, short-term and long-term disability, flexible time off, and 13 paid holidays annually." That's substantive.
We need to output only HTML fragment, no markdown.
Let's structure:
About the role
Curi Capital, founded in 2005, is a rapidly growing national registered investment advisory firm (RIA) based in Chicago. We are committed to building meaningful relationships and making a difference in our clients’ financial wellness. Our mission is focused on enriching the lives of our teammates, clients, partners, and the communities in which we live and work. Curi Capital is perennially ranked among Barron’s Top 100 Independent Registered Investment Advisors globally. Our values—Accountability, Curiosity, Teamwork, Inclusion, and Service Commitment—are at the core of our culture. Program Duration: 10 Weeks, Paid | Eligible: College Juniors Build Real Experience At a Top-Ranked RIA Curi Capital is a national registered investment advisory firm recognized by Barron's among the Top 100 Independent RIAs in the world. Our Wealth Management Internship Program gives college juniors a genuine look at how a wealth management firm operates, working alongside the advisors and leaders who guide clients through some of the most important financial decisions of their lives.
But we might be duplicating. Could shorten but must preserve all substantive info. We need to keep all info; we can't omit details like "Program Duration: 10 Weeks, Paid | Eligible: College Juniors". That's substantive. So include. Better to have separate sections: About the role (firm overview), Responsibilities (What You'll Actually Do), Requirements (Who Thrives Here), Skills (specific skills like Microsoft Office, leadership, analytical thinking, communication, organization, confidentiality), Benefits, Pay, Schedule. Let's extract: Firm overview: About Us paragraph(s). Also includes Vision/Mission/Values maybe we can incorporate into About the role. Program Duration etc: maybe part of About the role. Responsibilities: bullet list from "What You'll Actually Do": - Partner with the Wealth Builder team on meaningful projects and research that inform actual client and business decisions - Sit in on Wealth Builder client and prospect meetings, seeing firsthand how our advisors build trust and deliver recommendations - Get hands-on exposure to planning, portfolio construction, and the technical work behind the scenes that most students never see until years into their careers - Communicate directly with clients, vendors, and internal teams, sharpening the professional instincts you'll rely on for the rest of your career - By the end of the summer, you won't just have a line on your resume. You'll have a genuine, firsthand understanding of what a career in wealth management actually looks like, and the clarity to know where your own skills and interests fit best. That's a mix of bullet and prose; we can make- for each duty.
Requirements: "Who Thrives Here" bullet list:
- Are pursuing a degree in Finance, Trust and Wealth Management, or general business
- Have taken on a leadership role in a club, organization, or job, and know how to own a responsibility
- Bring sharp analytical thinking and genuine curiosity about financial markets and business strategy
- Communicate clearly and confidently, whether in a client meeting, a team huddle, or a written summary
- Are organized enough to juggle multiple projects and self-motivated enough to run with ambiguity
- Have a solid handle on Microsoft Office, especially Outlook, Word, and Excel
- Take confidentiality and integrity seriously, because our clients expect high integrity from each and every member of the team
- Provide practical examples of how you demonstrate accountability, curiosity, teamwork, inclusion, and service commitment
We could split into Requirements (education, experience) and Skills (specific abilities). But we can just put all under Requirements.
Skills: maybe we can pull out Microsoft Office, analytical thinking, communication, organization, confidentiality, etc. But to avoid thin sections, we could combine Requirements and Skills into one section? The instruction says prefer few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one section called "Requirements". That would be okay.
Benefits: as given.
Pay: stipend $10,000 for 10-week program. Also mention base salary commensurate... we should avoid filler. So we can state: "Compensation: $10,000 stipend for the 10-week program." We could also note that the base salary is commensurate with experience but that's filler; maybe we omit.
Schedule: Monday – Thursday 9am – 4pm, Friday 9am – 3pm local time.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does.
Now produce HTML:
About the role
... (firm overview, program duration, eligibility)
Responsibilities
- Partner with the Wealth Builder team on meaningful projects and research that inform actual client and business decisions
- Sit in on Wealth Builder client and prospect meetings, seeing firsthand how our advisors build trust and deliver recommendations
- Get hands-on exposure to planning, portfolio construction, and the technical work behind the scenes that most students never see until years into their careers
- Communicate directly with clients, vendors, and internal teams, sharpening the professional instincts you'll rely on for the rest of your career
- By the end of the summer, you won't just have a line on your resume. You'll have a genuine, firsthand understanding of what a career in wealth management actually looks like, and the clarity to know where your own skills and interests fit best.
Requirements
- Are pursuing a degree in Finance, Trust and Wealth Management, or general business
- Have taken on a leadership role in a club, organization, or job, and know how to own a responsibility
- Bring sharp analytical thinking and genuine curiosity about financial markets and business strategy
- Communicate clearly and confidently, whether in a client meeting, a team huddle, or a written summary
- Are organized enough to juggle multiple projects and self-motivated enough to run with ambiguity
- Have a solid handle on Microsoft Office, especially Outlook, Word, and Excel
- Take confidentiality and integrity seriously, because our clients expect high integrity from each and every member of the team
- Provide practical examples of how you demonstrate accountability, curiosity, teamwork, inclusion, and service commitment
Benefits
- Comprehensive health benefits, including medical, dental, vision, and life insurance
- Education assistance
- Annual bonus opportunity
- 401(k) with employer match
- Short-term and long-term disability
- Flexible time off
- 13 paid holidays annually
Pay
$10,000 stipend for the 10‑week program.
Schedule
Monday – Thursday 9 am – 4 pm; Friday 9 am – 3 pm local time.
We need to ensure no extra fluff like "US Pay Range $10,000 - $10,000 USD" (that's redundant). We omitted filler. Check that we didn't repeat job title. Good. We didn't include Vision/Mission/Values separately; we incorporated into About the role? Actually we didn't include them. We omitted them entirely. Is that okay? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Vision/Mission/Values is substantive info about the firm. If we omit, we lose detail. Should we include