Senior Consultant

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: 1. About the company (Avèro Advisors) - this is background info 2. How We Work / Our Ethos / What We Offer / Join Us - these are company culture/benefits 3. The Opportunity - this is the role description 4. What You'll Do - responsibilities 5. What You Bring - requirements/qualifications 6. Who Thrives Here - more about ideal candidate 7. The Pay Range - compensation According to rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists - Use

  for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) - Include section ONLY when posting has real, specific content - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no /, no markdown code fences The job title is "Senior Consultant" (mentioned in "The Opportunity" section). The page already shows it, so I shouldn't repeat as heading. Let me structure: 1. About the company - could be "About the company" or "About Avèro Advisors" but the rules mention "About the role" as example heading. However, the posting has substantial company info. I'll include an "About the company" section. 2. The Opportunity - this is the role overview. Could be "About the role". 3. What You'll Do - Responsibilities 4. What You Bring - Requirements/Qualifications (split into Required and Preferred) 5. Who Thrives Here - could be "Qualifications" or "Skills" or "Ideal candidate" 6. The Pay Range - Pay section The posting also has "How We Work", "Our Ethos", "What We Offer", "Join Us" - these are company culture/benefits. Could be under "Benefits" or "Culture". The rules say "Benefits" as example heading. Since they describe what they offer (high growth, impactful work, inclusive culture), I'll include a Benefits section. But note: "What We Offer" includes "High Growth Opportunity", "Impactful Work", "Inclusive Culture". That's benefits/culture. Also "How We Work" and "Our Ethos" are company methodology/values. I need to decide which sections to include. The rules: "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it". Let me map: - About the company: includes "About Avèro Advisors", "How We Work", "Our Ethos" - all substantive. - About the role: "The Opportunity" paragraph. - Responsibilities: "What You'll Do" with bullet points. - Requirements: "What You Bring" required skills. - Qualifications: "What You Bring" preferred qualifications. - Benefits: "What We Offer" (high growth, impactful work, inclusive culture) and maybe "Join Us" but that's more fluff. - Pay: "The Pay Range" is specific: 60,000 - 75,000 USD per year. "Who Thrives Here" is more about ideal candidate traits - could be part of Qualifications or separate "Skills" section. The rules mention "Skills" as example heading. It lists traits like strategic thinker, comfortable leading, etc. Could be "Qualifications" or "Skills". I'll include as "Qualifications" or "Ideal candidate". But the rules say use headings like "Qualifications", "Skills". I'll use "Qualifications" for preferred qualifications and maybe "Skills" for the traits? But "Who Thrives Here" is more cultural fit. Could be "Culture" but not in example headings. The example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "Skills" is an option. However, "Who Thrives Here" lists behavioral traits, not technical skills. Might fit "Qualifications" or "Skills". I'll put under "Qualifications" as a subsection? But the rules want

  for section headings. I could have "Qualifications" heading and then sub-sections? But the output is flat HTML fragment with

  and

  /

  . I can have multiple

  sections. Better to have: - About the company - About the role - Responsibilities - Requirements - Qualifications (for preferred) - Benefits - Pay And "Who Thrives Here" could be part of Qualifications or a separate "Skills" section. Since it's about traits, maybe "Skills" but it's soft skills. I'll include as "Qualifications" with a note? Actually, the posting separates "Required Skills & Experience" and "Preferred Qualifications" and then "Who Thrives Here". So three categories. I'll make "Requirements" for required, "Qualifications" for preferred, and "Ideal candidate" for who thrives? But the rules don't have "Ideal candidate". They have "Skills". Could use "Skills" for the traits. However, the traits are not skills per se. But the rules say "Skills" as example heading. I'll use "Skills" for "Who Thrives Here". But the rules: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can use "Skills". Good. Now, "How We Work", "Our Ethos", "What We Offer", "Join Us" - these are company description. I'll put under "About the company" as prose and lists. Let me draft HTML. First, "About the company" heading, then paragraphs for About Avèro Advisors, How We Work, Our Ethos. Then "What We Offer" as a list under Benefits? Actually "What We Offer" is benefits. So maybe separate "Benefits" section for What We Offer. And "How We Work" and "Our Ethos" are more about methodology and values, could be under "About the company". I'll structure:

  About the company

  Avèro Advisors is a fast-growing boutique management consulting firm that modernizes technology and business operations for state and local governments. We guide public-sector clients through high-stakes transformation initiatives spanning ERP modernization, permitting & licensing, budgeting, HR, data, and AI adoption. Our marquee clients include the Port of Portland (OR), Monroe County (NY), Santa Fe County (NM), Clackamas County (OR), Tarrant County (TX), and other forward-thinking governments across the United States. Recognized for our exceptional momentum, Avèro has earned a place on the Inc. 5000 list for five consecutive years, reflecting our continued growth and commitment to excellence.

  How we work

  • Service-centric, not SaaS: We don’t sell software; we deliver expertise, clarity, and outcomes.
  • AI-accelerated: Our proprietary Vision & Velocity™ delivery framework embeds generative-AI accelerators, reusable automations, and data-driven insights into every phase of an engagement.
  • Runs on EOS®: Traction tools, quarterly Rocks, Scorecards, and Level-10 meetings ensure transparency, accountability, and consistent execution across the firm.

  Our ethos

  Avèro stands as a beacon of innovation, driven by the purpose of making government interactions simpler through technology. We focus on enabling agencies to implement efficient, automated enterprise systems that improve service delivery and enhance the lives of citizens. As a minority-owned, MBE/DBE-certified firm, we are deeply committed to diversity, inclusion, and expanding opportunity—within our company and the communities we serve.

  But the rules say use

  for section headings like "About the role", "Responsibilities", etc. "How we work" and "Our ethos" are not in the example list, but they are substantive. The rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g.", so other headings are allowed. But they also say "Prefer a few substantive sections over many thin ones." So maybe combine "How we work" and "Our ethos" into "About the company" as prose. But they are distinct. However, to keep sections few, I could put all company info under "About the company" with subheadings? But we can't use subheadings (only

  ). Could use

  for each, but that might be too many thin sections. The content is substantive though. Alternatively, I could have "About the company" with paragraphs and lists. The "How We Work" is a list of three items. "Our Ethos" is a paragraph. "What We Offer" is a list of three items. "Join Us" is a paragraph. I think it's okay to have multiple

  sections if they have real content. The rules: "include a section ONLY when the posting has real, specific content for it". Each has specific content. But the example headings are typical job posting sections. The company description sections are not typical but they are part of the posting. The user wants to reformat the job posting. The posting includes company info. I should include it. However, the rules also say: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The company info is not boilerplate. I'll include: - About the company (with About Avèro Advisors, How We Work, Our Ethos) - Benefits (What We Offer) - About the role (The Opportunity) - Responsibilities (What You'll Do) - Requirements (Required Skills & Experience) - Qualifications (Preferred Qualifications) - Skills (Who Thrives Here) - Pay (The Pay Range) But "Benefits" is an example heading. "What We Offer" is benefits. Good. "Join Us" is a closing paragraph, could be part of Benefits or About the role. I'll include in Benefits or omit as fluff? It says "Join Us At Avèro Advisors, we’re not just consultants—we’re change-makers... we want to hear from you." That's a call to action, maybe not needed. But it's part of the posting. I'll include as a paragraph in Benefits or About the company. Let's decide. I'll create the following sections: 1. About the company 2. How we work (maybe as subsection but use h3) 3. Our ethos 4. Benefits 5. About the role 6. Responsibilities 7. Requirements 8. Qualifications 9. Skills 10. Pay But that's many sections. The rules: "Prefer a few substantive sections over many thin ones." So maybe combine "How we work" and "Our ethos" into "About the company". And "Benefits" includes "What We Offer" and "Join Us". "About the role" is one paragraph. "Responsibilities" is a list. "Requirements" is a list. "Qualifications" is a list. "Skills" is a list. "Pay" is a paragraph. That's 7 sections: About the company, Benefits, About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. 8 sections. But "