Data Integration Consultant

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. The posting starts with some fluff: "Technology is our how...". That's about the company, maybe "About the role"? Actually that's generic company description. Could be considered "About the role" or "About the company". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe includes company description). Then Responsibilities: list of duties. Then Requirements: maybe qualifications. Then Qualifications: maybe required qualifications. Then Skills: maybe specific skills. Then Benefits: benefits described. Pay: not mentioned explicitly (no salary). So we should not include Pay section. Schedule: mentions onsite 3 days a week in NYC office under Qualifications Required: "Onsite 3 days a week in New York City office". That's schedule info. So we can include Schedule section with that. We must not create sections with filler like "commensurate with experience". Not present. We need to preserve all substantive info. Let's extract. Company description paragraph: "Technology is our how. And people are our why. For over two decades, we have been harnessing technology to drive meaningful change. By combining world-class engineering, industry expertise and a people-centric mindset, we consult and partner with leading brands from various industries to create dynamic platforms and intelligent digital experiences that drive innovation and transform businesses. From prototype to real-world impact - be part of a global shift by doing work that matters." That's about the company; could go under About the role. Job Description: "Support enterprise integration initiatives across the Boomi platform and custom-built integration solutions. Design, develop, enhance, and support data integrations using the Boomi platform, application-specific tools and APIs, and custom integration code developed in C# and Python. Enterprise data flows, integration patterns, API-based development, data transformation, error handling, production support, and the movement of sensitive HR, Finance, and operational data across systems. Design, build, test, deploy, and support integrations using the Boomi platform. Develop Boomi processes for data extraction, transformation, routing, validation, and delivery across enterprise systems. Configure Boomi connectors, maps, profiles, decision logic, document properties, process properties, and exception handling. Build integrations using REST APIs, SOAP web services, SFTP, flat files, XML, JSON, CSV, databases, and other common integration endpoints. Monitor Boomi process executions, investigate failures, and resolve integration errors. Improve existing processes for reliability, maintainability, performance, and operational visibility. Implement logging, alerting, retry logic, and error-handling frameworks for production integrations. Design, develop, and support seamless integrations involving Workday HCM, Finance, Payroll, Benefits, Recruiting, Security, and Reporting data to allow for efficient data exchange and accurate reporting. Work with Workday integration technologies such as Workday Web Services, EIB, Core Connectors, RaaS reports, custom reports, Workday Studio, and Workday BIRT Reports where applicable. Design, develop, and maintain user-provisioning integrations that originate from Workday and flow into Google Workspace and other downstream enterprise systems. Extract, transform, analyze, and deliver Workday data to downstream systems through Boomi, APIs, files, or custom services. Troubleshoot integration issues related to data availability, security access, report output, transformation logic, and downstream system errors, providing primary integration support for all users. Develop and validate business logic, workflow, field mappings, supervisory organizations, cost centers, worker data, finance data, contracts, and approval-related data in Workday. Develop custom integration components, utilities, APIs, scripts, and services using C#, Python, and Java to ensure technical capability across platforms. Build lightweight services or tools to support data validation, API orchestration, file processing, exception handling, and integration automation. Develop scripts and utilize technical tools for data cleansing, reconciliation, transformation, XSLT comparison, and troubleshooting. Work with SQL databases, APIs, and file-based data sources to maintain robust documentation and ensure integration implementation is successful." That's responsibilities. Qualifications Required: list: - Onsite 3 days a week in New York City office - Strong hands-on experience on designing and supporting Workday integrations. - Working knowledge of Workday Web Services, EIBs, Core Connectors, RaaS reports, and Workday security concepts. - Experience with Workday HCM, Workday Finance, Payroll, Benefits, or Procurement integrations. - Strong experience with REST APIs, SOAP services, JSON, XML, CSV, SFTP, and database integrations. - Experience with cloud platforms such as Google Cloud Platform, AWS, or Azure. - Hands-on development experience with C# and Python. - Strong SQL skills for data validation, troubleshooting, reconciliation, and reporting. - Experience with integration testing, deployment, monitoring, and production support. - Ability to troubleshoot complex data and integration issues across multiple systems. - 4-years or more experience in the fields Preferred: "Strong hands-on experience with Boomi integration development." Additional Information: Benefits list: "Discover some of the global benefits that empower our people to become the best version of themselves: Finance: Competitive salary package, share plan, company performance bonuses, value-based recognition awards, referral bonus; Career Development: Career coaching, global career opportunities, non-linear career paths, internal development programmes for management and technical leadership; Learning Opportunities: Complex projects, rotations, internal tech communities, training, certifications, coaching, online learning platforms subscriptions, pass-it-on sessions, workshops, conferences; Work-Life Balance: Hybrid work and flexible working hours, employee assistance programme; Health: Global internal wellbeing programme, access to wellbeing apps; Community: Global internal tech communities, hobby clubs and interest groups, inclusion and diversity programmes, events and celebrations." Additional Employee Requirements: list of physical requirements etc. That seems like boilerplate but maybe we should keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Additional Employee Requirements" seems like generic physical requirements; could be considered boilerplate? It's not EEO but it's generic job requirements. Might be considered boilerplate? The instruction says remove boilerplate, but not explicitly to remove physical requirements. However they are generic and not specific to role. Might be considered boilerplate. Safer to omit them? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't say to remove generic physical requirements. But they are not specific to role; still they are part of posting. However they might be considered boilerplate (standard). I'd lean to keep them? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we remove them, we might be removing substantive info (though generic). But they are not specific to role; still they are part of posting. The instruction about boilerplate is limited to certain types. So we can keep them. Then USA Benefits (Full time roles only, does not apply to contractor positions) list: robust healthcare etc. Then EEO statement etc: we must remove EEO/equal-opportunity/scam-warning boilerplate. So remove the paragraph starting "At Endava, we’re committed to creating an open, inclusive, and respectful environment..." etc. Thus we need sections: - About the role: company description paragraph. - Responsibilities: the long job description paragraph(s) maybe split into

• for list of duties? The instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. The responsibilities are a paragraph with many sentences; could be considered prose. Could also break into list items for each duty. But we can keep as

    with the whole block. However it's long; maybe better to split into

    • each sentence? That would be a list. The instruction says use
      • for any list of duties/requirements/benefits. The responsibilities are effectively a list of duties. So we should convert to
        • . We'll break each distinct duty into a list item. However we must preserve all info; we can split by sentences. Similarly Requirements: maybe combine Qualifications Required and Preferred? The instruction has separate sections for Requirements, Qualifications, Skills. We need to decide what goes where. We have "Qualifications Required:" list (including onsite schedule). Then "Preferred:" one item. Then "Additional Information" benefits. Then "Additional Employee Requirements" (physical). Then "USA Benefits". We need to map to sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have schedule info: Onsite 3 days a week in New York City office. That's schedule. We have qualifications: maybe the list of required experience etc. Skills: maybe specific technical skills (Boomi, Workday, APIs, C#, Python, SQL, cloud). Could separate. But we must not create sections with filler. We'll include sections that have real content. Let's define: - About the role: company description paragraph. - Responsibilities:
          • each duty sentence. - Requirements: maybe the "Qualifications Required:" list (excluding schedule? but schedule is separate). Could include the required experience items. - Qualifications: maybe the "Preferred:" item? Or we could treat Qualifications as the required qualifications, and Skills as specific technical skills. But we have both. Better: Use Requirements for the mandatory qualifications (including onsite schedule). Use Qualifications for the preferred qualification (Boomi experience). Use Skills for the technical skills list (REST APIs, SOAP, etc., C#, Python, SQL, cloud platforms). Benefits: combine the global benefits and USA Benefits. Schedule: separate section for onsite 3 days a week. We must not repeat job title. Let's extract each piece. About the role paragraph: as above. Responsibilities: break into list items. Let's parse sentences: 1. Support enterprise integration initiatives across the Boomi platform and custom-built integration solutions. 2. Design, develop, enhance, and support data integrations using the Boomi platform, application-specific tools and APIs, and custom integration code developed in C# and Python. 3. Enterprise data flows, integration patterns, API-based development, data transformation, error handling, production support, and the movement of sensitive HR, Finance, and operational data across systems. 4. Design, build, test, deploy, and support integrations using the Boomi platform. 5. Develop Boomi processes for data extraction, transformation, routing, validation, and delivery across enterprise systems. 6. Configure Boomi connectors, maps, profiles, decision logic, document properties, process properties, and exception handling. 7. Build integrations using REST APIs, SOAP web services, SFTP, flat files, XML, JSON, CSV, databases, and other common integration endpoints. 8. Monitor Boomi process executions, investigate failures, and resolve integration errors. 9. Improve existing processes for reliability, maintainability, performance, and operational visibility. 10. Implement logging, alerting, retry logic, and error-handling frameworks for production integrations. 11. Design, develop, and support seamless integrations involving Workday HCM, Finance, Payroll, Benefits, Recruiting, Security, and Reporting data to allow for efficient data exchange and accurate reporting. 12. Work with Workday integration technologies such as Workday Web Services, EIB, Core Connectors, RaaS reports, custom reports, Workday Studio, and Workday BIRT Reports where applicable. 13. Design, develop, and maintain user-provisioning integrations that originate from Workday and flow into Google Workspace and other downstream enterprise systems. 14. Extract, transform, analyze, and deliver Workday data to downstream systems through Boomi, APIs, files, or custom services. 15. Troubleshoot integration issues