Integration Engineer

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 content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also remove EEO and accommodation sections. Also remove "About Us" maybe? The instruction: "Prefer a few substantive sections over many thin ones." We need to decide which sections to include. We have content: "Who You’ll Work With" (intro about team). "What You’ll Do" (responsibilities). "What You’ll Bring" (requirements/qualifications/skills). "Compensation and Benefits" (pay and benefits). Also "About Us" (company description) maybe could be "About the role"? Actually "About Us" is company overview, not role. Could be omitted as not required? The instruction says include a section ONLY when posting has real, specific content for it. We have content for About the role? Not explicitly; we have "Who You’ll Work With" which is about team, could be considered "About the role". Could map to "About the role". Could also include "Responsibilities" from "What You’ll Do". "Requirements" from "What You’ll Bring". "Skills" maybe also from that. "Benefits" and "Pay" from compensation section. We should not create Schedule section because none. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive info; do not invent or summarize away detail. So we need to keep details like specific technologies, years, etc. We need to format lists appropriately. Let's parse sections: Who You’ll Work With: paragraph describing team, vision, etc. Could be placed under

  About the role

  with

  . What You’ll Do: list of responsibilities (multiple sentences). Could be turned into

  • each responsibility. What You’ll Bring: includes education, experience, technical proficiencies, etc. Could be split into Requirements (education, years experience) and Skills (technologies). But we can combine into one section maybe "Requirements" with list. Compensation and Benefits: includes pay ranges per location, bonus, benefits description (time off, parental leave, 401k, health, etc). Also mentions discretionary bonus. So we need Pay and Benefits sections. Could combine? The instruction says prefer few substantive sections over many thin ones, but we need to include Pay and Benefits only if posting actually states them. It does state both. Could we make one section "Compensation and Benefits" with both? But headings allowed are only the listed ones: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have separate

    Pay

    and

    Benefits

    . Or we could put pay under Pay and benefits under Benefits. That seems fine. We must not include "About Us" as a heading unless we map to About the role? The "About Us" is company description; could be considered "About the role"? Not exactly but we could include it under About the role as extra prose. However we already have "Who You’ll Work With" which is about team; we could combine both under About the role. We need to remove EEO and accommodation lines, also remove "We will accept applicants until December 18th date, or until the position is filled." That's application instruction; remove. Also remove contact email for pay questions? That's maybe part of compensation but it's contact info; could be considered application instruction? It's not exactly instruction to apply but it's a contact for pay questions. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The contact email for pay questions might be considered legal? It's not exactly EEO. Might keep? Safer to remove? The instruction says preserve ALL substantive information; contact email for pay questions is substantive? It's about compensation inquiries. Might be considered part of compensation section. However it's not a duty/requirement/benefit. It's more like administrative. I'd lean to keep it as part of Pay section maybe as a note. But it's not a list item; could be a

    . However it's not explicitly prohibited. I'd keep it. Also remove "EEO and Accommodations" section entirely. Now craft HTML. Structure:

    About the role

    Who You’ll Work With ... plus About Us description maybe.

    But we need to avoid duplication: "Who You’ll Work With" paragraph and "About Us" paragraph. We'll combine. Let's extract Who You’ll Work With text: "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." About Us text: "Slalom is a fiercely human business and technology consulting company that leads with outcomes to bring more value, in all ways, always. From strategy through delivery, our agile teams across 52 offices in 12 countries partner with clients to co-create powerful customer experiences, modern ways of working, and meaningful impact. What sets us apart? We believe work should be challenging and fulfilling, not perfect, but possible. That’s why we prioritize purpose, flexibility, connection, and recognition, so our people can thrive and love what they do, most days." We can combine into one

    maybe two paragraphs. Now Responsibilities: list each bullet from "What You’ll Do". Let's extract sentences: - Collaborate with clients to understand their business requirements and integration needs. - Conduct assessments of existing system and API Portfolio, identify challenges, and recommend solutions. - Facilitate workshops and meetings with client stakeholders to gather requirements and present solutions. - Develop customized integration and API gateway architecture blueprints tailored to client needs. - Design and build scalable, reliable, and secure integration solutions. - Design and build scalable, reliable, and secure integrations/API solutions and help migrate existing APIs to new API platforms. - Create detailed technical specifications, including API designs, message schemas, and data mappings. - Lead the implementation of integration & API solutions using appropriate middleware and integration tools. - Capable of working independently or as part of a team with minimal supervision. - Oversee the development, testing, and deployment of integration, and API components, ensuring alignment with client expectations. - Provide hands-on support and troubleshooting during the implementation phase. - Offer technical guidance and mentorship to client project teams. - Act as a subject matter expert in integration and API technologies, providing leading practices and recommendations. - Assist clients in optimizing and maintaining their integration solutions. - Proactively escalate risks and issues to project and client teams. Note there is duplicate "Design and build scalable, reliable, and secure integration solutions." and "Design and build scalable, reliable, and secure integrations/API solutions and help migrate existing APIs to new API platforms." Slightly different; keep both. Now Requirements/Qualifications/Skills: from "What You’ll Bring". Let's parse: - 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. - 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. - Certification in relevant integration technologies or platforms. - Experience with microservices architecture and containerization (Docker, Kubernetes). - Knowledge of enterprise service buses (ESBs) and service-oriented architecture (SOA). - Willingness to travel up to 30% as needed and/or be in person at client site in your home city. - Preferred Expertise: 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 We could split into Requirements (education, years, consulting experience) and Skills (technical proficiencies). But we have headings: Requirements, Qualifications, Skills. Could use Requirements for education/experience, Qualifications for certifications, Skills for technical. But to keep few sections, maybe combine into Requirements and Skills. Let's decide: Use

    Requirements

    for education, years, consulting experience, willingness to travel. Use

    Skills

    for technical proficiencies, certifications, etc. Or we could have Requirements and Qualifications. But we need to preserve all info; we can put all in one

    Requirements

    with a list; that's acceptable. However instruction says prefer few substantive sections over many thin ones. So maybe one section for Requirements/Qualifications/Skills combined. But we have headings allowed; we could still use just one heading like

    Requirements

    and put all items there. That would be fewer sections. But we also need Benefits and Pay sections. Thus final sections: About the role, Responsibilities, Requirements, Pay, Benefits. We'll not include Qualifications or Skills separately. Now Pay: need to include salary ranges per location, bonus statement, maybe contact email. We have: "Compensation and BenefitsSlalom 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. Slalom is committed to fair and equitable compensation practices. For this role, we are 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,000Principal: $174,000-213,000 All other locations:Senior Consultant: $129,000-$158,000Principal: $160,000-195,000 In addition, individuals may be eligible for an