IB Sr Associate / Jr Vice President – Clean Energy & Power (New York)

We need to output HTML fragment with sections: About the role? Actually the posting includes "Why Stifel" intro, then "What You'll Be Doing", "What We're Looking For", "What You'll Bring", "Education & Experience", "Licenses & Credentials", "Systems & Technology", "Compensation Range", "About Stifel". We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can adapt headings to match content. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should use those exact headings if applicable. However we need to include a section only when posting has real, specific content for it. So we need to map content to these headings. We have: - About the role: could be "What You'll Be Doing" (responsibilities). So we could use

About the role

with responsibilities list. - Responsibilities: maybe same as About the role? But we should not duplicate. Probably we use About the role for responsibilities. - Requirements: could be "What We're Looking For" (skills/requirements). Or "Education & Experience", "Licenses & Credentials", "Systems & Technology". Those are qualifications. - Qualifications: maybe Education & Experience, Licenses & Credentials, Systems & Technology. - Skills: maybe "What You'll Bring" (skills/competencies). - Benefits: we have compensation range and benefits description. So we can have Pay and Benefits sections. - Pay: compensation range. - Benefits: other benefits. - Schedule: not present, so omit. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: "Why Stifel" intro maybe considered fluff? It's about culture but could be considered part of About the role? Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Why Stifel" intro is not exactly boilerplate but it's promotional. Might be okay to keep as part of About the role? But we need to preserve all substantive information. The intro about culture is substantive? Might be considered fluff but it's about firm culture. Could be included in About the role? However we have limited headings; we could include a short paragraph under About the role before list. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

Why Stifel strives for a culture that puts its clients and associates first: a culture where everyone belongs, everyone is welcome, and everyone contributes to the success of our clients, their careers, and the firm as a whole. Let’s talk about how you can find your place here at Stifel, where success meets success.

• Serve as project manager on live transactions in the Clean Energy & Power sector, managing the process from origination to close.
• Lead and support execution of M&A, recapitalizations, and capital raises (debt, public, and private equity) transactions.
• Develop and oversee integrated financial models, valuation analyses, and client presentation materials.
• Prepare valuations and offering memorandums for M&A and private placement processes, and participate in due diligence and drafting sessions for public and private offerings.
• Serve as a trusted point of contact for clients, supporting relationship management and delivery of financial solutions.
• Mentor and develop Analysts and junior staff, targeting areas for their development and fostering a collaborative, high‑performance culture.
• Contribute to business development efforts by identifying and pursuing new client opportunities.
• Build sector expertise in Clean Energy & Power and represent the firm at industry events and client meetings.
• Work on multiple projects and transactions at any given time.

Requirements

• Play a critical role as project manager on deal teams, managing the process from origination to close (already covered? maybe duplicate). Actually this is from "What We're Looking For". We'll list those bullet points.
But we need to avoid duplication. Better to separate: Requirements = "What We're Looking For". So list those. Let's extract "What We're Looking For" bullet points: - Play a critical role as project manager on deal teams, managing the process from origination to close - Lead and support execution of M&A, recapitalizations, and capital raises (debt, public, and private equity) transactions - Develop and oversee integrated financial models, valuation analyses, and client presentation materials - Prepare valuations and offering memorandums for M&A and private placement processes, and participate in due diligence and drafting sessions for public and private offerings - Serve as a trusted point of contact for clients, supporting relationship management and the delivery of financial solutions - Mentor and develop Analysts and junior staff, targeting areas for their development and fostering a collaborative, high-performance culture - Contribute to business development efforts by identifying and pursuing new client opportunities - Build sector expertise in Clean Energy & Power and represent the firm at industry events and client meetings - Work on multiple projects and transactions at any given time These are similar to responsibilities. Might be duplication. But we need to preserve all substantive information; duplication is okay? The instruction says remove duplicated lines. So we should avoid repeating same content. We need to decide which section to put which content. We could treat "What You'll Be Doing" as responsibilities, and "What We're Looking For" as requirements (skills/experience). However they overlap heavily. To avoid duplication, we could combine them into one section (About the role) and not repeat. But we need to include Requirements section if there is distinct content like education/experience, licenses, systems. Thus we can put education/experience, licenses, systems under Requirements or Qualifications. Let's map: - About the role: responsibilities (What You'll Be Doing) plus intro culture. - Requirements: Education & Experience, Licenses & Credentials, Systems & Technology. - Qualifications: maybe Skills (What You'll Bring). - Benefits: Compensation Range + other benefits. - Pay: maybe we separate compensation range as Pay, and Benefits as other benefits. But we need to avoid thin sections. Could combine Pay and Benefits into one Benefits section? But instruction says use headings Pay, Benefits, Schedule etc. We can include both if we have content. We have compensation range: Salary: USD $175,000.00/Yr. - USD $250,000.00/Yr. plus note about actual salaries may vary, base salary component, other benefits. We also have benefits list: discretionary bonuses, health/dental/vision/prescription insurance, Stifel Total Health Connect, flexible spending accounts, tuition & certification assistance programs, paid time off, etc. Thus we can have:

Pay

Salary range: USD $175,000.00 per year – USD $250,000.00 per year. Actual salaries may vary based on qualifications, skills, and overall competencies; base salary is one component of Stifel’s overall compensation package.

Benefits

• Discretionary bonuses
• Health, dental, vision, and prescription insurance
• Stifel Total Health Connect
• Flexible spending accounts
• Tuition & certification assistance programs
• Paid time off
• And other offerings (see Stifel careers benefits page)
We should not include link? Might be okay to keep as plain text: "To view a more comprehensive list of Stifel’s current offerings, please visit https://www.stifel.com/careers/benefits." But that's application instruction? It's not exactly application instruction but maybe considered boilerplate? It's a link to benefits. Might be okay to keep as a note. But we should remove application instructions like "Applications are accepted until the position is filled." That's boilerplate; remove. Now About Stifel section: we could include as a separate section maybe "About Stifel" but not in prescribed headings. However we could treat as "About the role"? Already used. Could add a section "About Stifel" but not in list of allowed headings? The instruction says use

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

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. So we should not add extra headings like About Stifel. We could incorporate that info into About the role or Benefits? Probably better to include under About the role as a brief firm overview. Thus About the role will contain intro culture + responsibilities + firm overview. Now Requirements: we need to include Education & Experience, Licenses & Credentials, Systems & Technology. We'll list them as bullet points under Requirements. Qualifications: Skills (What You'll Bring). We'll list those as bullet points. Now we need to ensure we don't repeat content. Let's extract Education & Experience bullet points: - Minimum Required: Bachelor's degree in Finance or related field - Minimum Required: 6 years post-undergraduate experience in Investment Banking or Private Equity, including prior experience at the Associate level - Minimum Required: Direct transaction experience in the Clean Energy & Power sector Licenses & Credentials: - Minimum Required: NASD licenses Systems & Technology: - Proficient in Microsoft Excel, Word, PowerPoint, Outlook Now Skills (What You'll Bring) bullet points: We need to parse the list: Client Skills: Able to win the confidence of clients; sensitive to clients' needs in both anticipating and delivering upon requests; able to build strong, long-term business relationships. Deal Management: Able to manage financing and M&A transactions from start to finish; excellent analytical, modeling, and client management skills. Entrepreneurial Mindset: Strong ability to work in an entrepreneurial culture; exercises good judgment in assessing the risks and rewards of new business opportunities. Time Management: Able to organize and prioritize multiple tasks and responsibilities; able to follow through and meet deadlines; able to manage expectations appropriately; able to use firm's resources efficiently. Teamwork: Works well within assigned project teams; accessible to and respectful of all team members, regardless of relative seniority; willing to train and mentor others; strives to be a value added resource to other groups throughout the firm. Work Ethic and Attitude: Dedicated to accomplishing goals; willing to take on additional responsibilities to produce outstanding work; strives for excellence; maintains a positive attitude through stressful situations. Personal Characteristics: Demonstrates professionalism, integrity, maturity, intellectual curiosity, initiative and good judgment; takes pride of ownership for wins and accountability for losses/mistakes; knows when to ask for help. Effective communication skills and able to relay information well in both written and verbal form. Solid analytical skills - uses logic and reasoning to identify complex problems; review related information and develop options and implement solutions. Good interpersonal interaction and able to work well with others. We can combine into bullet points, each maybe a sentence. Now we need to ensure we don't include boilerplate like "Minimum Required:" repeated; we can keep as part of bullet. Now produce HTML. We'll start with

About the role

then a paragraph with intro culture and firm overview, then
for responsibilities. Then

Requirements

with
for education/experience, licenses, systems. Then

Qualifications

with
for skills. Then

Pay