Agentic AI Engineer - Intelligence Engineering (Agentic AI)

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 need to parse the job posting. First, we need to identify sections: The posting includes: - "Who You’ll Work With" (intro about team, description) - "What You’ll Do" (responsibilities) - "What You’ll Bring" (requirements/qualifications/skills) - "About Us" (company description) - "Compensation and Benefits" (pay and benefits) - "EEO and Accommodations" (boilerplate to remove) We need to produce sections: About the role (maybe from Who You’ll Work With?), Responsibilities (What You’ll Do), Requirements (What You’ll Bring), Qualifications (maybe same as Requirements?), Skills (maybe separate?), Benefits, Pay, Schedule. We need to avoid repeating job title as heading. No Job ID. We need to include only sections with real content. We need to use

for each section heading, then content:

for prose,

• for lists. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we should drop "EEO and Accommodations" entirely. Also drop "About Us"? It's company description; maybe we can include as "About the role"? Actually "About Us" is not about the role but about company. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. "Who You’ll Work With" could be considered "About the role" (team context). We'll put that under

  About the role

  . "What You’ll Do" => Responsibilities. "What You’ll Bring" => Requirements (maybe also Qualifications and Skills). We need to split into Requirements, Qualifications, Skills? The posting includes experience, hands-on, familiarity, etc. Could treat as Requirements. Qualifications maybe similar. Skills maybe separate list of technical skills. But we should not create thin sections; prefer few substantive sections. So we could combine Requirements and Qualifications into one section? But headings are prescribed; we can include both if we have content. However we should avoid filler. We could put all under "Requirements" and maybe also "Skills". But we need to decide. The posting includes: - 3+ years of software engineering experience building and delivering production systems - Hands-on experience with Python development, including APIs and backend services (FastAPI, Flask, or similar) - Experience building or contributing to AI/ML or data-driven systems, with exposure to GenAI or LLM-based solutions preferred - Familiarity with agent-based or workflow frameworks (e.g., LangGraph, AutoGen, CrewAI, or similar) or strong interest in learning them - Experience with RAG concepts, including embeddings, vector databases, and retrieval workflows (hands-on or foundational) - Experience working with at least one major cloud platform (AWS, Azure, or GCP) - Understanding of software development best practices, including testing, version control, and CI/CD pipelines - Ability to take requirements and turn them into working, production-grade solutions - Strong problem-solving skills and attention to detail - Nice to have: Experience with evaluation frameworks (e.g., RAGAS, LangSmith) - Exposure to monitoring, observability, or production support - Familiarity with prompt engineering and LLM interaction patterns - Experience working in Agile teams and client-facing environments Thus we can have a Requirements section with the required items (maybe bullet list). And a Skills section for nice-to-have? Or we could combine. But instruction: "Prefer a few substantive sections over many thin ones." So maybe we just have Requirements (including both required and nice-to-have) and Skills not needed. However they ask to use headings like Skills if we have content. Could we omit Skills if no specific content? We could put nice-to-have under Requirements as "Preferred qualifications". But better to have a Skills section for technical skills. Let's think: The posting includes both required and nice-to-have. We could have: - Requirements (required) - Qualifications (maybe same as Requirements) - Skills (technical skills) But that would be thin. Better to have: - About the role - Responsibilities - Requirements (including required and preferred) - Benefits - Pay Schedule: not mentioned (flexible working environment, some days may require in-person collaboration). That's schedule info: "We offer a flexible working environment to balance the need to work independently, with some days that may require in-person collaboration at our office." That's schedule info. So we can include Schedule section. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. We need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to extract content. About the role: From "Who You’ll Work With" paragraph(s). Let's capture: "At Slalom, we co-create modern technology and software products with clients who are ready to accelerate their digital product development. We imagine how things can be made better, then set out to realize what’s possible—driving innovation with quality, resilience, and purpose. By blending design, product engineering, analytics, and automation, we build the custom-built software and data products of tomorrow. As a Senior Engineer in Intelligence Engineering, you will play a hands-on role in designing, building, and deploying AI/ML and agentic AI solutions. You’ll work closely with architects, engineers, and product teams to turn concepts into working, production-ready systems, contributing directly to the development of intelligent products and automated workflows. You’ll help deliver projects from early-stage development through production, ensuring solutions are scalable, reliable, and aligned to client needs, while continuously growing your expertise in AI/ML and cloud engineering. We offer a flexible working environment to balance the need to work independently, with some days that may require in-person collaboration at our office." That's the content. Responsibilities: "What You’ll Do" bullet list (actually sentences). We need to convert to
  • . Each line is a responsibility. Let's list them: - Build and deploy AI/ML and GenAI solutions, including agentic workflows, APIs, and production services - Develop RAG pipelines, including data ingestion, embedding strategies, retrieval logic, and response generation - Implement agent-based systems using frameworks such as LangGraph, AutoGen, CrewAI, or similar - Write high-quality, maintainable code in Python, contributing directly to core system components - Develop and integrate APIs and services using frameworks such as FastAPI or Flask - Translate technical designs into working, scalable solutions aligned with architectural guidelines - Contribute to the implementation of ML/LLM pipelines, including data processing, inference workflows, and system integrations - Support the development of CI/CD pipelines, testing strategies, and deployment processes - Apply best practices to ensure performance, reliability, and maintainability of delivered solutions - Build solutions on cloud platforms such as AWS, Azure, or GCP, leveraging cloud-native AI and data services - Integrate with services such as vector databases, LLM platforms, and data pipelines - Support deployment and monitoring of applications in production environments - Implement evaluation and testing frameworks to measure system performance and quality (e.g., RAG accuracy, system behavior) - Contribute to observability and monitoring, including logging, tracing, and performance analysis - Help ensure solutions meet standards for quality, scalability, and security - Collaborate closely with architects, engineers, and product owners to deliver high-quality solutions - Participate in client-facing discussions, demos, and technical reviews - Contribute to agile delivery processes, including sprint planning, stand-ups, and retrospectives - Communicate technical concepts clearly to both technical and non-technical stakeholders - Travel may be required on a limited basis dependent on your client engagement or internal meetings/events. We need to ensure we keep all. Requirements: "What You’ll Bring" includes required and nice-to-have. We'll separate required vs nice-to-have maybe as sub-bullets? But we can just list all as bullet points, marking nice-to-have with "(Nice to have)" maybe. However we should not invent detail; we can keep the nice-to-have label as part of the text. Thus bullet list: - 3+ years of software engineering experience building and delivering production systems - Hands-on experience with Python development, including APIs and backend services (FastAPI, Flask, or similar) - Experience building or contributing to AI/ML or data-driven systems, with exposure to GenAI or LLM-based solutions preferred - Familiarity with agent-based or workflow frameworks (e.g., LangGraph, AutoGen, CrewAI, or similar) or strong interest in learning them - Experience with RAG concepts, including embeddings, vector databases, and retrieval workflows (hands-on or foundational) - Experience working with at least one major cloud platform (AWS, Azure, or GCP) - Understanding of software development best practices, including testing, version control, and CI/CD pipelines - Ability to take requirements and turn them into working, production-grade solutions - Strong problem-solving skills and attention to detail - Nice to have: Experience with evaluation frameworks (e.g., RAGAS, LangSmith) - Nice to have: Exposure to monitoring, observability, or production support - Nice to have: Familiarity with prompt engineering and LLM interaction patterns - Nice to have: Experience working in Agile teams and client-facing environments We could also separate "Nice to have" as separate subsection but that would be thin. We'll keep as bullet with label. Benefits: From "Compensation and Benefits" paragraph: "Slalom prides itself on helping team members thrive in their work and life. As a result, Slalom is proud to invest in benefits that include meaningful time off and paid holidays, parental leave, 401(k) with a match, a range of choices for highly subsidized health, dental, & vision coverage, adoption and fertility assistance, and short/long-term disability. We also offer yearly $350 reimbursement account for any well-being-related expenses, as well as discounted home, auto, and pet insurance." We need to put as
    • each benefit. Pay: The compensation ranges: "For this role, we are hiring at the following levels and salary ranges: East Bay, San Francisco, Silicon Valley: Senior Engineer: $129,000-$157,000 Engineer: $102,000-$125,000 Boston, Los Angeles, New Jersey, New York City, Orange County, San Diego, Seattle, Washington DC, White Plains: Senior Engineer: $118,000-$144,000 Engineer: $94,000-$114,000 All other locations: Senior Engineer: $108,000-$132,000 Engineer: $86,000-$105,000 In addition, individuals may be eligible for an annual discretionary bonus. Actual compensation will depend upon an individual’s skills, experience, qualifications, location, and other relevant factors. The pay range is subject to change and may be modified at any time." We need to preserve all substantive information. We'll put as

      maybe with the details. Schedule: From "We offer a flexible working environment to balance the need to work independently, with some days that may require in-person collaboration at our office." Also maybe travel mention. We'll include that. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce:

      About the role

      ...

      Responsibilities

      • ...
      ...

      Requirements

      • ...