!Good to know. Requires working in the office three or more days per week. Subject to financial industry background checks and regulatory compliance requirements.
Overview
Turbin's analysis on the role ·
Technical Workday Financials integrations role.Financials experience is a hard requirement.
The responsibilities use a generic software engineering template, while the technical requirements focus on building production Workday Financials integrations. Core Financials and integration tools like Studio and APIs define the daily work, with Extend, Prism, and sub-modules listed as supporting scope.
Skills, by how much you'll use them
From Turbin's read of the posting
4 skills
Every day
The core of the job. Lead with these.
Integrations
Workday Studio
Core Financials
Workday APIs
6 skills
Working knowledge
Expected, but not what you are hired for.
Workday Extend
Orchestrate
Prism Analytics
Accounting Center
Fixed Assets
Accounts Receivable
4 skills
Only mentioned
Named in the posting. Safe to skip.
Integration security
CI/CD
ETL and batch processing
Python scripting
What you'll do
6 responsibilities
Design, develop, test, operate, and maintain production-grade software and Workday integration solutions
Write testable, production-ready code adhering to architectural, security, and reliability best practices
Analyze system failures, propose design changes, and drive operational and monitoring improvements
Conduct and incorporate feedback from code reviews to uphold engineering standards and compliance
Do you fit?
Tick what you have. Only you see this.
0 of 3 must-havesTick what you have to see your match.
Must have · 3
Nice to have
Hands-on experience with Workday Integrations including EIB, Core Connectors, Studio, Orchestrate, and Extend
Experience with Workday APIs and technologies including WWS, REST, SOAP, RaaS, XML, XSLT, JSON, SFTP, and PGP
Proficiency in Python, JavaScript, PowerShell, or Shell scripting for integration and automation
Knowledge of enterprise data integration, ETL or ELT, data mapping, and high-volume batch processing
Experience with CI/CD, GitHub or GitLab, UDeploy, automated deployment, and change management
Experience with integration security including OAuth 2.0, Workday ISUs, certificates, and secrets
Experience supporting production financial integrations with monitoring, reconciliation, and error recovery
How to pitch yourself
Turbin's advice
Lead with production-grade Workday Financials integrations you have built and supported end to end, highlighting engineering rigor like error handling and reconciliation. Treat Extend, Orchestrate, and sub-modules like Prism as supporting breadth if you have them.
1Show full-lifecycle integration ownership with scale, such as "Built Studio and EIB financial feeds for GL and AP processing 50k+ daily journals with automated control totals"
2Call out software engineering practices the posting emphasizes, including CI/CD pipelines, GitHub or GitLab version control, automated testing, and restart or recovery design
3Detail your integration security setup with OAuth 2.0, Workday ISUs, certificates, and PGP or SFTP, since banking controls are central to this team
4Mention Extend, Accounting Center, Prism, or scripting languages like Python briefly only where you have real hands-on delivery