Workday Integration Sr Analyst (Location Flexible)
RSM US LLP
Houston, TX +4Full-timeTechnical
Salary
$95k–164kper year
Seniority
Senior
Hands-on configuration
90%of the role is configuring in the tenant
Systems
Workday + Power Automate
!Good to know. Eligible for a discretionary bonus based on firm and individual performance. Entry-level candidates requiring current or future visa sponsorship, such as F-1 visa holders, are not eligible.
Overview
Turbin's analysis on the role ·
Hands-on API integrations engineering role.Raw REST and SOAP APIs matter more than Studio.
Every responsibility and requirement centers on designing, building, and debugging raw Workday REST and SOAP API integrations, XML payloads, and ISU security. Power Automate serves as the external orchestration layer with engineering teams. Candidates who rely purely on Studio abstractions will not fit.
Skills, by how much you'll use them
From Turbin's read of the posting
5 skills
Every day
The core of the job. Lead with these.
Integrations
REST and SOAP APIs
XML
Integration security
Business processes
1 skill
Working knowledge
Expected, but not what you are hired for.
Power Automate
1 skill
Only mentioned
Named in the posting. Safe to skip.
Workday Studio
What you'll do
6 responsibilities
Design and implement Workday integrations using REST APIs, SOAP web services, and business process logic
Construct and troubleshoot XML payloads, API requests, responses, authentication, and security context
Build deterministic, observable integrations with explicit pre-write validation, audit trails, and safe retry strategies
Diagnose integration failures by analyzing raw API data, Workday business process states, and cross-system sequencing
Do you fit?
Tick what you have. Only you see this.
0 of 8 must-havesTick what you have to see your match.
Must have · 8
How to pitch yourself
Turbin's advice
Lead with hands-on experience building and debugging raw Workday REST and SOAP web service integrations without relying on Studio. Mention Power Automate or external orchestration tools briefly if you have paired them with Workday APIs.
1Show raw API debugging depth with a concrete example, such as "troubleshot SOAP XML namespace errors and BP approval states across ISU-secured endpoints"
2Highlight software engineering practices the posting emphasizes, including pre-write validation, idempotent retry logic, and logging or audit trails
3Note your experience with Workday data models, object relationships, and Business Process behavior when triggered via external API calls
4Mention Power Automate or similar orchestration platforms briefly only if you have actually integrated them with Workday