Advisory Intern, Forensic Technology - Summer 2027 (Atlanta, Boston, Chicago, New York, Greater Washington DC)

We need to output HTML fragment with sections: Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We need to parse the job posting. Job Summary: description about intern responsibilities etc. We have Job Duties list (bulleted). That's responsibilities. Education Qualifications, Knowledge, Skills and Abilities: includes Education, Experience, License/Certification, Software, Languages, Other Knowledge, Skills, & Abilities. We need to map to sections: About the role (maybe job summary), Responsibilities (job duties), Requirements (education/experience?), Qualifications (maybe same as requirements?), Skills (technical skills), Benefits (maybe from About Us? There's mention of ESOP, benefits, but not specific benefits like health etc. There's "Benefits may be subject to eligibility requirements." Not specific. So we should not create Benefits section unless specific content. There's no explicit benefits list. So skip Benefits. Pay: there is salary ranges per state. That's specific content. So include Pay section with those ranges. Schedule: not mentioned. So skip. We also have "About Us" which could be About the role? Actually About the role is about the position; we have Job Summary which describes role. So we can put that under About the role. We need to avoid repeating job title as heading. Not include Job ID etc. We need to use

• for any list of duties/requirements/benefits. So responsibilities list as ul. For requirements/qualifications/skills we need to decide what goes where. The posting has sections: Education Qualifications, Knowledge, Skills and Abilities: with subparts: Education, Experience, License/Certification, Software, Languages, Other Knowledge, Skills, & Abilities. We could combine Education and Experience into Requirements or Qualifications. Since we have both Requirements and Qualifications headings allowed. We need to decide which to use. Probably Requirements for education/experience/license, Qualifications for skills/knowledge? But we also have Skills heading. Could put technical skills under Skills. Let's structure:

  About the role

  Job summary paragraph(s).

  Responsibilities

  • ...
  ...

  Requirements

  Education: Currently pursuing a Bachelor’s or Master’s degree, required; Currently pursuing a degree with focus in Accounting, Analytics, Computer Science, Statistics, Finance, Economics, Engineering, or Information Systems, preferred.

  Experience: Leadership experience, preferred.

  License/Certification: N/A (maybe we can drop as it's N/A). Since it's N/A we should not include filler. So we can omit License/Certification if it's N/A. The instruction: never emit a heading followed by filler/placeholder text. So we should not include a section that just says N/A. So we can skip License/Certification entirely.

  Skills

  Understanding of relational databases, preferably SQL Server, preferred; Experience with Python, R, and/or other programming languages or tools, preferred; Experience with querying structured and unstructured data, cleaning and profiling datasets, building repeatable analytics, and visualizing results, preferred; Experience with data visualization software (e.g., Tableau, PowerBI), preferred; Familiarity with agentic AI tools and AI-driven workflow automation, preferred; Proficient in Microsoft Office Suite, Word, Excel, and PowerPoint, preferred.

  Other Knowledge, Skills, & Abilities

  maybe we could put under Skills or Qualifications. But we have a separate "Other Knowledge, Skills, & Abilities" list: Ability to work with high degree of professionalism and autonomy; Demonstrated curiosity and coachability; Excellent verbal and written communication skills; Ability to translate complex data into simple, concise business observations; Strong organizational skills; Ability to work in deadline-driven environment; Ability to interact effectively with people at all organizational levels; Ability to work collaboratively while maintaining accountability. These are soft skills. Could be included under Skills or maybe under Qualifications. Since we already have Skills heading for technical skills, we could add another section for "Abilities" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put these under Qualifications (makes sense). Or we could merge them into Skills as well. Let's decide: Use Qualifications for education/experience/license? Actually we already used Requirements for education/experience. Then Qualifications could be for the "Other Knowledge, Skills, & Abilities". Skills heading for technical skills. Thus:

  Qualifications

  • Ability to work with a high degree of professionalism and autonomy
  ... etc
  Pay section: include ranges per state. Could be a

  with list. Could also be

  • but it's not a list of duties; but we can still use

    . The instruction: Use

    • for any list of duties/requirements/benefits. Pay is not a list of duties/requirements/benefits, but we could still use

      . We'll output ranges as a

      maybe with
      or semicolons. We must not include boilerplate like EEO, etc. So remove those paragraphs. Also remove "About Us" maybe we could incorporate into About the role? Actually About the role already has job summary. The About Us is about the firm; not needed for the role. Could be omitted as not specific to role. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The About Us is substantive but not about the role. However the instruction says to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't say we must include About Us. The allowed headings are limited; we could omit About Us entirely. The job summary already covers role. So we can drop About Us. Thus final HTML:

      About the role

      An intern in the Forensic Technology practice utilizes their educational background and organizational skills as they serve the firm's dynamic client base. The intern’s responsibilities include problem solving, consulting, and fact-finding on active cases as well as internal practice initiatives (e.g., business development and service offering innovation). In this role, the intern will have the opportunity to gain an understanding of the business by working on various stages of a forensic consulting engagement across issues like bribery and corruption, fraud, money laundering, disputes, litigation, corporate compliance, and data breach response. On these engagements, the intern will work side-by-side with more experienced team members who can provide direction, coaching, and learning opportunities.

      Responsibilities

      • Provides data analytics services to a variety of clients, including outside counsel, regulators, and companies involved in litigation, investigation, dispute, regulatory, and compliance matters
      • Contributes to forensic engagements related to fraud, anti-money laundering, insurance risks, foreign corrupt practices act (FCPA), disputes, and other matters
      • Supports ETL processes by forensically extracting, cleaning, and transforming data for in-depth data analytics with big datasets
      • Assists in preparation of high-quality, accurate client deliverables and insights
      • Acts with professionalism and integrity when working with confidential and sensitive information
      • Maintains a proactive and logical approach to information gathering, combining complex ideas and clear and effective information presentation
      • Develops strong knowledge of technical programs, including SQL, R, Python, Power BI, Tableau, and AI-enabled tools
      • Reviews own work product carefully to ensure accuracy, completeness, and quality, and supports overall team quality standards
      • Other duties as required

      Requirements

      Education: Currently pursuing a Bachelor’s or Master’s degree, required; Currently pursuing a degree with focus in Accounting, Analytics, Computer Science, Statistics, Finance, Economics, Engineering, or Information Systems, preferred.

      Experience: Leadership experience, preferred.

      Qualifications

      • Ability to work with a high degree of professionalism and autonomy
      • Demonstrated curiosity and coachability, with a willingness to learn and develop skills in technical programs
      • Excellent verbal and written communication skills, including notetaking and documentation of methods, procedures, and processes
      • Ability to translate complex data into simple, concise business observations
      • Strong organizational skills, with the ability to meet project deadlines and maintain close attention to detail
      • Ability to work in a deadline-driven environment
      • Ability to interact effectively with people at all organizational levels of the Firm
      • Ability to work collaboratively with others while maintaining accountability for the work product

      Skills

      Understanding of relational databases, preferably SQL Server, preferred; Experience with Python, R, and/or other programming languages or tools, preferred; Experience with querying structured and unstructured data, cleaning and profiling datasets, building repeatable analytics, and visualizing results, preferred; Experience with data visualization software (e.g., Tableau, PowerBI), preferred; Familiarity with agentic AI tools and AI-driven workflow automation, preferred; Proficient in Microsoft Office Suite, Word, Excel, and PowerPoint, preferred.

      Pay

      California Range: $40.00/hr - $45.00/hr; Colorado Range: $34.00/hr - $38.00/hr; Illinois Range: $36.00/hr - $40.00/hr; Maryland Range: $34.00/hr - $38.00/hr; Massachusetts Range: $36.00/hr - $40.00/hr; Minnesota Range: $32.00/hr - $36.00/hr; New Jersey Range: $38.00/hr - $42.00/hr; NYC/Long Island/Westchester Range: $36.00/hr - $40.00/hr; Washington Range: $35.00/hr - $40.00/hr; Washington DC Range: $34.00/hr - $38.00/hr.

      We must not include any extra text. Ensure no markdown fences. Output only HTML. Check for any filler like "N/A" - we omitted License/Certification. Good. Check for any duplicated lines: we have not repeated. Check for any boilerplate: removed EEO, etc. Check for any mention of "Other duties as required" we kept as a responsibility item; that's okay. Check for "Supervisory Responsibilities N/A" we omitted. Check for "Languages N/A" omitted. Check for "Individual salaries that are offered..." we kept only the ranges; we omitted the explanatory sentence about factors. That's okay because it's not specific detail? It's somewhat generic but still substantive. However we could keep it as a sentence. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The sentence about factors is substantive but generic. Should we keep? It's not filler like "commensurate with experience". It's a description of how pay is determined. Might be considered substantive. However we already have Pay section with ranges; we could add a brief sentence before ranges: "Individual salaries that are offered to a candidate are determined after consideration of numerous factors including but not limited to the candidate’s qualifications, experience, skills, and geography." That's not filler. Let's include it as a

      before the ranges. Thus Pay section:

      Pay

      Individual salaries that are offered to a candidate are determined after