Workday Software Developer – Student Financial Systems

University of the Cumberlands
US flag
Remote, US
Full-timeTechnical
SalaryTurbin est.
$85k–115k
Seniority
Mid-level
Hands-on configuration
90%of the role is configuring in the tenant
Systems
Workday only
Travel
Occasional

Good to know. Applicants must be authorized to work in the U.S. without visa sponsorship. The role includes occasional travel to the main campus and reports to the Manager of Enterprise Applications and Development.

Overview

Turbin's analysis on the role ·

Hands-on Workday integrations developer role.Higher ed domain experience is not required.

Daily work centres on designing, building, and supporting Workday integrations using Studio, EIB, Orchestrate, Core Connectors, and APIs, alongside WQL and business process support. The posting explicitly welcomes strong developers without prior student financials experience and offers domain training.

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
  • Workday Studio
  • EIB
  • Orchestrate
  • Core Connectors
4 skills
Working knowledge

Expected, but not what you are hired for.

  • Reporting
  • WQL
  • Business processes
  • XSLT
4 skills
Only mentioned

Named in the posting. Safe to skip.

  • Student Financials
  • Financial Aid
  • Workday Extend
  • Title IV reporting

What you'll do

8 responsibilities
  • Design, build, test, and deploy Workday integrations using Studio, EIB, Orchestrate, Core Connectors, and SOAP or REST APIs
  • Write and maintain maintainable integration transformation logic using XSLT, XML, JSON, and scripting languages
  • Support and monitor existing Student Financials, Student Accounts, and Financial Aid integrations, including release testing
  • Configure and enhance Workday functionality, business processes, and rules for student financial processes

Do you fit?

Tick what you have. Only you see this.
0 of 5 must-havesTick what you have to see your match.
Must have · 5

Nice to have

  • Experience supporting Workday Student, Student Financials, Student Accounts, Financial Aid, or comparable higher education systems
  • Knowledge of Title IV federal financial aid regulations and Department of Education reporting such as FISAP, NSLDS, or COD
  • Workday Pro certification in Integrations, Student, Financial Aid, or a related area
  • Experience with Workday Extend, XSLT, or general-purpose languages such as Python, Java, or JavaScript

How to pitch yourself

Turbin's advice

Lead with your hands-on integration builds in Studio, EIB, Orchestrate, Core Connectors, and SOAP or REST APIs, backed by solid software engineering practices. Keep Workday reporting and Extend brief if you have them, since integration engineering is the main bar.

  1. Detail 2 to 3 end-to-end Workday integrations you built, naming the tools such as Studio, EIB, or Core Connectors, data formats like XSLT or JSON, and volume or error-handling scope
  2. Highlight software engineering practices the posting calls out, such as version control, peer code reviews, release testing, and structured deployment processes
  3. If you have supported Student Financials, Financial Aid, or Title IV feeds, connect that work to secure data exchange, and only mention WQL or Extend if you have used them