AI Business Systems Engineer (HYBRID)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Let's extract content: - Intro: "AI Business Systems Engineer - Wakefield, MA – C-4 Analytics The ideal candidate understands the benefits of in-person teamwork and is available to work from our office a minimum of three days per week." This is about schedule? It mentions minimum three days per week in office. That's schedule info. - Then description of company: "C-4 Analytics is a fast-growing, private, full-service digital marketing company that excels at helping automotive dealerships increase sales, increase market share, and lower cost per acquisition. C-4 Analytics is committed to developing innovative solutions for every dealer in every market and to providing the highest levels of accountability and customer service." - "We are currently hiring for an AI Business Systems Engineer, Wakefield, MA to serve as a cross-functional builder and thought partner for applying AI across the company. This is a business-first role for someone who deeply understands how organizations operate, can identify high-leverage opportunities for automation and intelligence, and has the technical fluency to design and implement solutions end-to-end. The ideal candidate combines strong business judgment, an engineering mindset, and an expert-level understanding of modern AI capabilities." - "If you are unable to complete the application due to a disability, contact us to ask for accommodation or an alternative application process." This is boilerplate? It's about accommodation; maybe we can keep? It's not cookie/navigation/legal/EEO etc. It's about accommodation request. Might be considered EEO? It's about disability accommodation. Might be considered EEO/equal-opportunity boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove that line. - Then "The Gig: Your Mission" with bullet points: The AI Visionary, The Workflow Wizard, The Systems Architect, The Hands-On Builder. Those are responsibilities. - Then "A Day In The Life" with bullet points: Build smarter solutions..., Integrate systems..., Own the solution..., Stay current... - Then "What You Need to Succeed: The Rare Trifecta" with subpoints: Business Process Strength, Engineering Mindset, AI Expertise. Those are qualifications/requirements. - Then "Core Background": Experience: Typically 4+ years of professional experience owning systems end-to-end. Demonstrated history of shipping solutions that other teams rely on daily. We Value: Consulting roles with implementation responsibility, internal tools/business systems teams, and experience in startup/scale-up environments. We Are Not Seeking: Pure ML research profiles, AI "evangelists" without execution depth, or product managers who do not build/implement. - Then "Hard Qualifiers (Non-Negotiable)" list: Experience building cross-functional business systems, not isolated tools. Ability to go from whiteboard concept to live, production workflow. Focus on business impact and ROI, not novelty for its own sake. Comfort pushing back on weak ideas, even with senior stakeholders. - Then "Soft Qualifiers (Equally Important)" list: Low ego and high ownership. Impatience with unnecessary process and wasted effort. Calm, structured thinking in ambiguous situations. Practical decision-making over "perfect" architecture. - Then "Specific Skills & Expertise": Must-Have: Proven track record in building cross-functional systems, strong familiarity with AI models, experience with automation platforms and APIs, and excellent communication. Nice-to-Have: Background in operations/consulting, experience with CRMs/data platforms, light scripting (Python/JavaScript). - Then "What This Role Is NOT": Not a research or theory role—this is about building. Not a departmental analyst—this is cross-functional. Not a pure software engineering role—this is business-driven systems building. - Then Salary: "$100,000 to $130,000 USD per year (competitive and negotiable)." - Benefits: "Health insurance, retirement plans, professional development, and unlimited paid time off! Check out our careers and culture page for more details." - Then note about "Understanding the Different Between AI Automation Specialist and AI Business Systems ..." This seems like extra explanation; maybe we can include as part of description? It's not a standard section but could be considered part of responsibilities or description. However we should not create sections unless there is real specific content. Could embed within a

under maybe "About the role" or "Responsibilities". But we need to decide sections. We have schedule info: minimum three days per week in office. That's schedule. We have Pay: salary range. We have Benefits: health insurance, retirement plans, professional development, unlimited paid time off. We have Responsibilities: The Gig bullet points and A Day In The Life bullet points. We have Requirements/Qualifications: The Rare Trifecta, Core Background, Hard Qualifiers, Soft Qualifiers, Specific Skills & Expertise, What This Role Is NOT. We could combine many into a single "Requirements" section with subpoints? But we must use

• for any list of duties/requirements/benefits. So we can have multiple lists. We need headings: maybe About the role (company description), Responsibilities, Requirements, Benefits, Pay, Schedule. We should not create sections with filler. Ensure each heading has substantive content. Let's craft:

  About the role

  C-4 Analytics is a fast-growing, private, full-service digital marketing company that excels at helping automotive dealerships increase sales, increase market share, and lower cost per acquisition. C-4 Analytics is committed to developing innovative solutions for every dealer in every market and to providing the highest levels of accountability and customer service. We are currently hiring for an AI Business Systems Engineer, Wakefield, MA to serve as a cross-functional builder and thought partner for applying AI across the company. This is a business-first role for someone who deeply understands how organizations operate, can identify high-leverage opportunities for automation and intelligence, and has the technical fluency to design and implement solutions end-to-end. The ideal candidate combines strong business judgment, an engineering mindset, and an expert-level understanding of modern AI capabilities.

  That covers company description and role overview.

  Responsibilities

  • The AI Visionary: Be the go-to expert applying AI across Sales, Marketing, Ops, Finance, and beyond.
  • The Workflow Wizard: Map processes, spot bottlenecks, and eliminate manual effort with brilliant AI solutions.
  • The Systems Architect: Proactively propose and translate ambiguous business needs into structured, end-to-end system designs.
  • The Hands-On Builder: Design and execute game-changing, AI-powered workflows using modern automation tools and APIs.
  • Build smarter solutions: Apply AI for decision support, content generation, classification, and data enrichment.
  • Integrate systems: Ensure internal systems (CRM, data platforms, cloud tools) are seamlessly connected.
  • Own the solution: Take projects from lightbulb moment to production, ensuring reliability and business relevance.
  • Stay current: Serve as the internal expert on the latest AI models and tooling.
  We could also include the note about AI Automation Specialist vs AI Business Systems Engineer? Might be considered extra description; but we could incorporate into responsibilities or about. However it's a bit of a comparison; maybe we can add a paragraph under About the role? But it's not strictly required. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that note somewhere. It's under "Note: Understanding the Different Between AI Automation Specialist and AI Business Systems". That's a substantive note distinguishing the role. We could add a

  after responsibilities or within About the role. Let's add a

  under About the role after the company description. But we need to avoid duplication. Let's add a paragraph: "Note: Understanding the Difference Between AI Automation Specialist and AI Business Systems Engineer ..." and then the content. We'll include that as a

  under About the role. Now Requirements: we need to capture all the qualifications. We could have a single

  Requirements

  with multiple
  lists? But spec says use
  • for any list of duties/requirements/benefits. It doesn't forbid multiple lists under same heading. We'll do multiple
    for each category. We'll include: - Business Process Strength, Engineering Mindset, AI Expertise (The Rare Trifecta) as list items. - Core Background: Experience: Typically 4+ years... etc. - We Value: Consulting roles..., internal tools..., startup/scale-up. - We Are Not Seeking: Pure ML research..., AI evangelists..., product managers... - Hard Qualifiers (Non-Negotiable): list. - Soft Qualifiers (Equally Important): list. - Specific Skills & Expertise: Must-Have list, Nice-to-Have list. - What This Role Is NOT: list. We need to ensure we don't create headings like "Hard Qualifiers" etc unless we want to; but we can just embed them as list items under Requirements. However the instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we could use Qualifications or Skills as headings. But we can also just use Requirements heading and include all details. That's acceptable. We must not create sections with filler. So we will have Requirements heading with substantive content. Now Benefits: we have health insurance, retirement plans, professional development, unlimited paid time off. Also note "Check out our careers and culture page for more details." That's maybe extra but we can include as part of benefits

    or list. We'll create

    Benefits

    with
    list. Pay:

    Pay

    with

    salary range. Schedule:

    Schedule

    with

    about minimum three days per week in office. We should not repeat job title as heading. Already not. We must not include Job ID etc. Now ensure we removed boilerplate: The accommodation request line removed. Also the "We are C-4 Analytics Powered by JazzHR" at end removed. Also the "The Vibe At C-4 Analytics" paragraph is fluff; maybe we can keep as part of About the role? It's cultural description; could be considered substantive? It's not required but it's part of posting. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that vibe paragraph as well. It's not boilerplate; it's company culture description. We can include under About the role as a paragraph. Thus About the role will have multiple paragraphs: company description, role overview, note about difference, vibe paragraph. Let's craft. Now produce HTML fragment. Check for any repeated content: ensure we didn't miss any. Let's list all substantive pieces: - Company description: fast-growing, private, full-service digital marketing company... increase sales, market share, lower CPA... committed to innovative solutions... highest levels of accountability and customer service. - Role purpose: hiring for AI Business Systems Engineer, Wakefield, MA to serve as cross-functional builder and thought partner for applying AI across company. Business-first role: understands org operation, identifies high-leverage opportunities for automation/intelligence, technical fluency to design/implement end-to-end. Ideal candidate combines strong business judgment, engineering mindset, expert-level understanding of modern AI capabilities. - Note about difference between AI Automation Specialist and AI Business Systems Engineer: includes description of each and the quote. - Vibe paragraph: "The Vibe At C-4 Analytics ..." includes many sentences. - Responsibilities: The Gig bullet points (4) and A Day In The Life bullet