Title: Workday Integration & Test Automation Architect
Location : Remote/ Chicago
Target Start Date : End of August
Type: (C, CTH, D) Contract, 3 month possibility extended
Pay Rate / Salary (Ranges OK) : $100/hour
Position Summary
We are seeking a senior Workday Integration & Test Automation Architect to assess the client's current integration landscape and design an automated testing strategy that improves the reliability, scalability, and maintainability of integrations feeding data into Workday.
The client's primary challenge is not simply UI test automation. The critical gap is integration quality: ensuring that data flowing from upstream applications and services into Workday is complete, accurate, timely, and processed correctly — while minimizing integration failures, manual validation, and lengthy regression cycles.
The architect will assess the current integration ecosystem, identify where and why failures occur, and establish a practical automated integration testing framework and strategy. The focus will be on creating repeatable automated validation that can be incorporated into development and CI/CD processes, enabling defects to be identified before they reach downstream environments or production.
This role requires someone who understands both Workday integrations and modern automated integration/API testing and can translate that knowledge into an enterprise-scale testing architecture.
Core Mission
The successful candidate will establish an approach that allows the client to confidently answer:
- Is the data being sent to Workday correct?
- Is the integration sending all required records and fields?
- Is Workday receiving and processing the data correctly?
- Are errors, rejected records, and exceptions detected automatically?
- Can integrations be regression-tested without extensive manual effort?
- Can failures be identified early in the development lifecycle?
- Can integration tests run reliably and repeatedly as part of CI/CD?
- Can the organization make integration changes without introducing unexpected downstream impacts?
Key Responsibilities 1. Assess the Workday Integration Landscape
- Map and understand the systems, applications, APIs, middleware, files, and processes that feed data into Workday.
- Assess the different integration patterns used to deliver data to Workday, including APIs, web services, files, batch processes, and scheduled integrations.
- Identify critical integration points and business-critical data flows.
- Understand dependencies between upstream systems, integration layers, Workday, and downstream consumers.
- Identify the highest-risk integrations and failure points.
- Document where testing currently occurs and where significant gaps exist.
2. Design an Automated Integration Testing Strategy
Develop a comprehensive strategy for automatically validating integrations into Workday.
The strategy should address:
- API and web-service validation.
- Request and response validation.
- Schema and field-level validation.
- Business-rule validation.
- Data transformation validation.
- Source-to-Workday reconciliation.
- Record counts and completeness.
- Required/optional fields.
- Data-type and format validation.
- Error and exception handling.
- Negative testing.
- Boundary and edge cases.
- Duplicate and missing records.
- Integration sequencing and dependencies.
- Batch and scheduled integration testing.
- Regression testing.
- End-to-end integration validation.
The objective is to move the organization from "run the integration and manually check whether it worked” toward automated, repeatable validation of integration behavior and data quality.
3. Establish a Workday-Focused Test Automation Architecture
Define how automated testing should interact with Workday and the surrounding integration ecosystem.
The architect will determine:
- Which tests should occur at the API/integration layer.
- Which scenarios require Workday validation.
- Which scenarios require UI testing.
- Where mocks, stubs, or service virtualization should be used.
- How upstream systems can be simulated when unavailable.
- How integration test data should be created and managed.
- How asynchronous Workday processing should be validated.
- How integration status and error conditions should be automatically detected.
- How source-system data can be reconciled against Workday results.
The target architecture should minimize unnecessary end-to-end UI testing and establish integration/API testing as the primary quality layer.
4. Evaluate Current Automation Tools
Assess the existing use of:
- Playwright
- Selenium
- Cucumber
- Artillery
- API testing tools/frameworks
- CI/CD tooling
Determine where each technology provides value and where the current toolset creates unnecessary duplication or maintenance.
The architect should make recommendations based on the testing problem, rather than assuming that every existing tool needs to be retained or replaced.
For example:
- UI automation should be reserved for scenarios that genuinely require UI validation.
- API/integration automation should provide the majority of integration regression coverage.
- Cucumber should be used selectively where business-readable scenarios provide value.
- Artillery or equivalent tooling should be used where performance and throughput testing are required.
5. Automate Integration Regression Testing
Design an automated regression approach capable of validating critical Workday integrations whenever changes are introduced.
This should include:
- Automated test execution.
- Automated data setup.
- Automated integration triggering.
- Automated monitoring of integration completion.
- Automated validation of Workday responses/results.
- Automated detection of rejected or failed records.
- Automated source-to-target reconciliation.
- Automated reporting.
- Repeatable execution across environments.
The goal is to create a regression safety net for Workday integrations rather than relying on manual testing before releases.
6. Test Data & Environment Strategy
Assess how integration test data is currently generated and maintained.
Develop recommendations for:
- Synthetic test data.
- Reusable integration test datasets.
- Data-driven testing.
- Test data refresh.
- Data masking where required.
- Environment-specific configuration.
- Parallel test execution.
- Data cleanup and reset.
The strategy should make it possible to execute integration tests repeatedly without extensive manual preparation.
7. Failure Detection & Observability
A major component of the assessment should be determining how integration failures are detected and diagnosed.
Evaluate the ability to automatically identify:
- Failed integrations.
- Rejected records.
- Missing records.
- Unexpected data transformations.
- Partial processing.
- Incorrect mappings.
- Duplicate records.
- Timing/latency issues.
- Downstream processing failures.
Recommend automated reporting and monitoring that provides sufficient information for engineering and QA teams to quickly determine what failed, where it failed, and why.
8. CI/CD Integration
Design an approach for integrating automated Workday integration testing into the software delivery lifecycle.
The target approach should support appropriate automated quality gates such as:
Code change → Automated integration tests → Workday validation → Results/reconciliation → Quality gate → Deployment
The architect will identify which tests should run:
- On every code change.
- During build/deployment pipelines.
- As nightly regression.
- Before major releases.
- As scheduled integration health checks.
9. Target-State Architecture & Roadmap
Deliver a practical target-state architecture and implementation roadmap.
The roadmap should identify:
- Immediate quick wins.
- High-risk integrations requiring priority attention.
- Automation opportunities.
- Tooling changes.
- Framework requirements.
- Test data improvements.
- CI/CD integration.
- Monitoring and reporting improvements.
- Longer-term maturity improvements.
Recommendations should be prioritized according to business criticality, integration risk, effort, and expected reduction in manual testing/failure risk.
Primary Deliverables Current-State Integration Assessment
A detailed assessment of how data currently flows into Workday, how integrations are tested, and where the largest reliability and testing gaps exist.
Integration Risk & Failure Analysis
Identification of critical integrations, common failure modes, testing gaps, and areas where failures are currently difficult to detect.
Automated Integration Testing Strategy
A defined strategy for automated API, integration, data, reconciliation, negative, regression, and end-to-end testing.
Target-State Test Architecture
A reference architecture showing how integration testing, Workday validation, automation frameworks, test data, service virtualization, CI/CD, and reporting should work together.
Automation Framework Recommendation
Recommendations for the appropriate use of Playwright, Selenium, Cucumber, Artillery, and API/integration testing technologies.
Test Data Strategy
A repeatable approach for generating, managing, masking, and resetting integration test data.
CI/CD & Regression Strategy
A recommended approach for embedding automated integration testing into the delivery pipeline and establishing automated quality gates.
Implementation Roadmap
A prioritized roadmap showing what the client should implement first, what can follow, and the expected benefits.
Required Qualifications
- 10+ years in QA, test automation, integration testing, or quality architecture.
- Significant experience designing enterprise integration testing strategies.
- Strong experience with Workday integrations and Workday data flows.
- Strong understanding of Workday APIs/Web Services, integration patterns, and data processing.
- Strong API testing and automation experience.
- Experience validating data transformations and source-to-target reconciliation.
- Experience designing automated regression frameworks.
- Experience with asynchronous integrations, batch processing, scheduled jobs, and distributed systems.
- Experience with Playwright and/or Selenium.
- Experience with Cucumber/Gherkin and BDD approaches.
- Experience with performance/load testing tools such as Artillery, JMeter, Gatling, or equivalent.
- Experience integrating automated testing into CI/CD pipelines.
- Strong understanding of test data management, mocking, stubbing, and service virtualization.
- Ability to assess existing automation frameworks and develop a pragmatic target-state architecture.
- Strong stakeholder communication and executive presentation skills.
Highly Preferred
- Deep hands-on experience with Workday integration testing.
- Experience with Workday Studio, EIB, Web Services, REST/SOAP APIs, or related Workday integration technologies.
- Experience with enterprise HR/ERP integrations.
- Banking or financial-services experience.
- Experience establishing automated source-to-target reconciliation.
- Experience implementing integration testing as part of DevOps/CI/CD.
- Experience reducing manual integration regression testing through automation.
What Success Looks Like
At the end of the engagement, the client should have a clear and actionable answer to:
"How can we automatically prove that the data flowing into Workday is correct and that our integrations continue to work whenever something changes?”
The architect should leave the client with more than a list of tools or testing recommendations. They should have a repeatable integration quality model that enables automated testing, earlier failure detection, faster regression cycles, reduced manual effort, and greater confidence when making changes to systems that integrate with Workday.
Welcome to ConsultNet, a premier national provider of technology talent and solutions. Our expertise spans across project services, contract-to-hire, direct search, and managed services onshore, nearshore, and hybrid. For over 25 years, we have connected thousands of consultants with meaningful roles through a personal, communication-driven approach, partnering with a diverse client base to build high-performing teams and create lasting impact. Our comprehensive service offerings cover a wide range of technology and engineering positions across key markets nationwide. Learn more at www.consultnet.com .
We champion equality and inclusivity, proudly supporting an Equal Opportunity Employer policy. We welcome applicants regardless of Race, Color, Religion, Sex, Sexual Orientation, Gender Identity, National Origin, Age, Genetic Information, Disability, Protected Veteran Status, or any other status protected by law.
