Integration Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also must not include sections with placeholder like "commensurate with experience". We need to extract substantive content from posting. Let's parse the posting: - "Who You’ll Work With" paragraph: description of team, Slalom Technologists, Global Systems Integration team vision, etc. This could be "About the role" or maybe "About the team". We can treat as "About the role" or "About the team". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have sections: 1. Who You’ll Work With: description of team and environment. Could be "About the role" (or maybe "About the team"). 2. What You’ll Do: list of duties/responsibilities. That's "Responsibilities". 3. What You’ll Bring: list of qualifications/experience/skills. That could be "Requirements" and "Qualifications" and "Skills". We need to decide how to split. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements, Qualifications, Skills into one section maybe "Requirements" or "Qualifications". But we have to use headings exactly as given? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; we can choose which to include. We should not create sections with filler. So we need to see if we have distinct content for each. We have "What You’ll Bring" includes: Bachelor’s degree, 10+ years experience, proven experience in consulting, proficiency with integration platforms, proficiency with API Gateway platforms, strong understanding of integration patterns, strong understanding of API management, hands-on experience building API specs, experience with cloud integration platforms, knowledge of data formats, proficiency or familiarity with Python or Java, problem-solving skills, communication skills, certification, experience with microservices, knowledge of ESBs and SOA, willingness to travel up to 30%, Preferred Expertise: familiarity with DevOps, building APIGEE infrastructure, migrating APIs, linter tools. That's a mix of requirements, qualifications, skills. Could be split into Requirements (education, experience), Qualifications (certifications, etc.), Skills (technical proficiencies). But to avoid many thin sections, maybe combine into one "Requirements" section that includes all. However the instruction says prefer a few substantive sections over many thin ones. So maybe we have three sections: About the role, Responsibilities, Requirements (or Qualifications). But we also have Compensation and Benefits section with specific pay ranges and benefits. That's "Pay" and "Benefits". Also we have "About Us" which is company description; could be "About the role"? Actually "About Us" is company overview; could be part of "About the role" or separate "About the company". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put company overview under "About the role". Or we could omit if not needed. The instruction: include a section ONLY when the posting has real, specific content for it. So we need to decide. We have content for: - About the role: could combine "Who You’ll Work With" and "About Us" (company description). That's substantive. - Responsibilities: "What You’ll Do" list. - Requirements: education, experience, consulting, willingness to travel, maybe certifications. - Qualifications: maybe certifications, etc. But we could combine. - Skills: technical proficiencies list. - Benefits: list of benefits (time off, parental leave, 401k, health, etc.) and well-being reimbursement, insurance discounts. - Pay: salary ranges per location and bonus eligibility. - Schedule: not mentioned (no schedule info). So we should not include Schedule. Thus we can have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Possibly also Qualifications if we separate certifications etc. But we can combine Requirements and Qualifications into one "Requirements" section to avoid thin sections. However we have separate headings allowed; we could still include both if they have substantive content. Let's see if we can split meaningfully: Requirements: Bachelor’s degree, 10+ years experience, proven consulting experience, willingness to travel up to 30%. Qualifications: Certifications in relevant integration technologies or platforms (maybe also preferred expertise?). But the posting says "Certification in relevant integration technologies or platforms." That's a qualification. Also "Preferred Expertise:" list could be under Qualifications or Skills. But we could treat "Preferred Expertise" as part of Skills or Qualifications. Skills: Proficiency with integration platforms, API Gateway platforms, understanding of patterns, API management, building API specs, cloud platforms, data formats, Python/Java, problem-solving, communication, microservices, ESB/SOA, DevOps, CI/CD, APIGEE infrastructure, migrating APIs, linter tools. Thus we have enough for each. We must not include boilerplate: EEO, Accommodations, etc. Also remove "About Us" maybe we incorporate into About the role. Also remove "Compensation and Benefits" heading but we will create Benefits and Pay sections. We must not include application instructions like "We will accept applicants until December 18th date, or until the position is filled." That's maybe part of Pay? Actually it's about timeline; not schedule. Could be omitted as it's not a section heading. The instruction: remove duplicated lines, application instructions. So we should omit that line. Also remove "Please note, this recipient is not able to support recruitment inquiries beyond this purpose." etc. Also remove "EEO and Accommodations" section. Also remove "We are committed to pay transparency..." maybe keep as part of Pay? It's about compensation; we can keep but it's not specific pay range; it's a statement. Could be included in Pay section as a note. But we might keep it as part of Pay section's prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all specifics: salary ranges per location, benefits list, etc. We must not repeat job title as heading. We must output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

...combined Who You’ll Work With and About Us...

Responsibilities

• ...
...

Requirements

• Bachelor’s degree in Computer Science, Information Technology, or a related field.
• 10+ years of experience in integration development, architecture and design.
• Proven experience in a consulting role, working directly with clients.
• Willingness to travel up to 30% as needed and/or be in person at client site in your home city.

Qualifications

• Certification in relevant integration technologies or platforms.

Skills

• Proficiency with integration platforms and middleware (e.g., Boomi, Workato, MuleSoft, Informatica, Celigo, Snaplogic, Microsoft Azure Integration Services (ADF, Azure Fabric Services, etc.), Apache Camel, Solace, Google Integration Services).
• Proficiency with API Gateway platforms (e.g., APIGEE Edge, APIGEE X, Azure API Management, AWS API Management, Kong API Management).
• Strong understanding of integration patterns and best practices.
• Strong understanding of API management, RESTful and SOAP web services, and message queuing.
• Hands-on experience in building API specs, APIs on gateway and testing them using tools to validate the functionality.
• Experience with cloud integration platforms and services (AWS, Azure, Google Cloud).
• Knowledge of data formats such as JSON, XML, and CSV.
• Proficiency or familiarity with Python or Java.
• Excellent problem-solving skills and attention to detail.
• Strong communication and interpersonal skills.
• Experience with microservices architecture and containerization (Docker, Kubernetes).
• Knowledge of enterprise service buses (ESBs) and service-oriented architecture (SOA).
• Familiarity with DevOps practices and CI/CD pipelines.
• Experience building APIGEE infrastructure on APIGEE X and APIGEE Edge.
• Experience migrating APIs.
• Experience with linter tools.

Benefits

• 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.
• Short/long-term disability.
• Yearly $350 reimbursement account for any well‑being‑related expenses.
• Discounted home, auto, and pet insurance.

Pay

Slalom is hiring at the following levels and targeted base pay salary ranges:

• San Diego, Los Angeles, Orange County, Seattle, Boston, Houston, New Jersey, New York City, Washington DC, Westchester:
  • Senior Consultant: $141,000‑$173,000
  • Principal: $174,000‑$213,000
• All other locations:
  • Senior Consultant: $129,000‑$158,000
  • Principal: $160,000‑$195,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 salary pay range is subject to change and may be modified at any time.

We must not include schedule section. Check for any duplicated lines: we removed boilerplate. Check that we didn't include job title heading. Check that we didn't include any placeholder like "commensurate with experience". Not present. Check that we preserved all substantive info: Who You’ll Work With and About Us combined; we need to ensure we didn't lose any detail from those paragraphs. Let's craft About the role paragraph: Original "Who You’ll Work With": "As a modern technology company, our Slalom Technologists are disrupting the market and bringing to life the art of the possible for our clients. We have passion for building strategies, solutions, and creative products to help our clients solve their most complex and interesting business problems. We surround our technologists with interesting challenges, innovative minds, and emerging technologies. The Global Systems Integration team has a vision of building a hyperconnected future. Our team brings a tool agnostic perspective to our clients, meeting them where they’re at and providing tailored solutions to meet them on their enterprise integration journey and walk with them as they mature their integrated solutions. The experts in this team are dedicated to delivering client centric solutions focused on Business Process Automation, Integration Strategy & Architecture, API Management, and Cloud, Application, & Data Integrations."