Workday Technical Analyst
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to extract substantive content: Job Summary paragraph, Position Responsibilities (list), Qualifications (list maybe), Competencies & Skills (list), About Nclh (company description). Also maybe "About Nclh" is about the company; we can treat as "About the company" heading.
We must not include boilerplate like "EQUAL OPPORTUNITY EMPLOYER", "Learn More About Our Company At a Glance Brand Overview ..."? Actually there is "Learn More About Our Company At a Glance Brand Overview Norwegian Cruise Line Oceania Cruises Regent Seven Seas Cruises New Releases". That seems like navigation; we should remove. Also "APPLY ONLINE" etc. Remove application instructions.
We need to keep all substantive info: The job summary paragraph, responsibilities list, qualifications list, competencies & skills list, about NCLH description.
We need to format with
headings. Which headings? The posting has sections: Job Summary, Position Responsibilities, Qualifications, Competencies & Skills, About Nclh. We can map to headings: "Job Summary" maybe not in list but we can use "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings if they match content? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we can use those headings if appropriate. For Job Summary we could use "About the role". For Position Responsibilities we can use "Responsibilities". For Qualifications we can use "Qualifications". For Competencies & Skills we can use "Skills". For About Nclh we could use "About the company" but not in examples; maybe we can still use "About the role"? Actually "About Nclh" is about the company, not role. Could use "About the company". The instruction didn't forbid other headings, just gave examples. Safer to use headings that match content: "About the role", "Responsibilities", "Qualifications", "Skills", "About the company". Use for each.
Now content:
Job Summary paragraph: "The Workday Technical Analyst is a hands-on HR technology professional responsible for designing, developing, testing, deploying, and supporting secure, scalable Workday solutions. The role combines expertise in Workday integrations, reporting, security, data conversion, and Core HCM to maintain reliable data exchanges and improve the employee and manager experience. The ideal candidate can translate business requirements into technical designs, troubleshoot complex production issues, and partner effectively with People Excellence, Payroll, Finance, IT, security teams, vendors, and external consultants in a complex global enterprise environment."
We'll put that in
.
Responsibilities: list of bullet points from "Position Responsibilities". Need to extract each bullet. The text after "Position Responsibilities" is a long sentence with many items separated by periods? Actually it's a paragraph with many items separated by periods but not bullet list. We need to convert to
- . We should split by each distinct responsibility. Let's parse:
"Serve as a technical subject matter expert for Workday HCM integrations, reporting, security, data conversion, and production support.
Design, build, configure, and maintain integrations using Enterprise Interface Builder (EIB)
Support integrations across varying solutions such as Core Connectors, Workday Studio, Report-as-a-Service (RaaS), Workday Web Services, REST/SOAP APIs, and secure file transfer methods.
Create and maintain technical design documents, business process flow diagrams, data mappings, transformation rules, integration schedules, dependencies, error handling, and operational support procedures.
Partners with Reporting and Analytics subject matter experts to troubleshoot and test Workday custom reports, advanced and matrix reports, calculated fields, dashboards, and data extracts that support operational, audit, and analytical needs.
Partner with functional teams and business stakeholders to gather requirements, assess impacts, and translate business needs into scalable technical solutions.
Plan and execute unit, system integration, regression, and user acceptance testing; prepare test cases and test data, document results, and manage defects through resolution.
Support Workday implementations, tenant updates/releases, enhancements, data conversions, deployments, and post-production stabilization activities.
Monitor scheduled integrations and production processes; triage incidents, perform root-cause analysis, implement corrective actions, and communicate status in accordance with service-level expectations.
Validate inbound and outbound data for accuracy, completeness, reconciliation, and compliance across Workday and connected systems.
Collaborate across Core HCM, Recruiting, Talent, Compensation, Benefits, Absence, Time Tracking, Payroll, Finance, and identity management processes.
Maintain technical documentation, runbooks, configuration records, testing evidence, and audit-ready support artifacts.
Audit, SOX & Compliance Support consolidating audit evidence materials for project phases and ongoing Production Support activities to present to Audit panels in fulfillment of internal and external audit requests
Identify opportunities to automate manual processes, strengthen controls, improve maintainability, and enhance system performance and user experience.
Provide knowledge transfer and technical guidance to analysts, support teams, and business partners.
Perform other duties as assigned."
We need to ensure each bullet is a
- . We'll keep the text as is.
Qualifications: The section includes "DEGREE TYPE: Bachelor's Degree FIELD(S) OF STUDY: Information Systems, Computer Science, Human Resources, Business Administration, or a related field. Experience 4+ years of Workday or HRIS/IT technical experience supporting integrations, reporting, security, data conversion, or related platform capabilities. Hands-on experience with Workday integration technologies such as EIB, Core Connectors, Workday Studio, RaaS, Workday Web Services, REST/SOAP APIs, XML, XSLT, JSON, and SFTP. Experience with Workday reports and calculated fields and analyzing data using Microsoft Excel; SQL experience is strongly preferred. Working knowledge of Workday Core HCM, business process framework, organization structures, foundational data, and security concepts. Experience supporting the full solution lifecycle, including requirements, design, build, testing, deployment, documentation, monitoring, and production support. Strong analytical, troubleshooting, data validation, and root-cause analysis skills with high attention to accuracy and detail. Ability to communicate complex technical concepts clearly to technical and non-technical stakeholders and manage multiple priorities independently. Experience with ticketing and delivery tools such as ServiceNow, JIRA, or Smartsheet and with Agile or Waterfall methodologies."
We can turn into list items. Could also keep as paragraphs but instruction: use
- for any list of duties/requirements/benefits. So we should list each qualification as
- . Let's split by sentences.
List:
- Bachelor's Degree in Information Systems, Computer Science, Human Resources, Business Administration, or a related field.
- 4+ years of Workday or HRIS/IT technical experience supporting integrations, reporting, security, data conversion, or related platform capabilities.
- Hands-on experience with Workday integration technologies such as EIB, Core Connectors, Workday Studio, RaaS, Workday Web Services, REST/SOAP APIs, XML, XSLT, JSON, and SFTP.
- Experience with Workday reports and calculated fields and analyzing data using Microsoft Excel; SQL experience is strongly preferred.
- Working knowledge of Workday Core HCM, business process framework, organization structures, foundational data, and security concepts.
- Experience supporting the full solution lifecycle, including requirements, design, build, testing, deployment, documentation, monitoring, and production support.
- Strong analytical, troubleshooting, data validation, and root-cause analysis skills with high attention to accuracy and detail.
- Ability to communicate complex technical concepts clearly to technical and non-technical stakeholders and manage multiple priorities independently.
- Experience with ticketing and delivery tools such as ServiceNow, JIRA, or Smartsheet and with Agile or Waterfall methodologies.
Competencies & Skills: list:
- Workday Pro certification or equivalent Workday integration, reporting, security, or HCM training desired.
- Experience supporting Workday in a publicly traded, global organization with a large and diverse workforce preferred.
- Experience integrating Workday with payroll, benefits, finance, recruiting, timekeeping, identity management, and third-party vendor systems preferred.
- Knowledge of data governance, privacy, audit controls, and secure integration design preferred.
About Nclh: paragraph: "Norwegian Cruise Line Holdings Ltd. (NYSE: NCLH) is a leading global cruise company which operates the Norwegian Cruise Line®, Oceania Cruises® and Regent Seven Seas Cruises® brands. The combined brands currently operate 32 ships, employ over 35,000 shipboard crew from more than 110 different countries and visit approximately 700 different port destination each year."
We can also include "Learn More About Our Company At a Glance Brand Overview Norwegian Cruise Line Oceania Cruises Regent Seven Seas Cruises New Releases" but that seems like navigation; we should drop.
Now produce HTML fragment:
About the role
The Workday Technical Analyst is a hands-on HR technology professional responsible for designing, developing, testing, deploying, and supporting secure, scalable Workday solutions. The role combines expertise in Workday integrations, reporting, security, data conversion, and Core HCM to maintain reliable data exchanges and improve the employee and manager experience. The ideal candidate can translate business requirements into technical designs, troubleshoot complex production issues, and partner effectively with People Excellence, Payroll, Finance, IT, security teams, vendors, and external consultants in a complex global enterprise environment.
Responsibilities
- Serve as a technical subject matter expert for Workday HCM integrations, reporting, security, data conversion, and production support.
- Design, build, configure, and maintain integrations using Enterprise Interface Builder (EIB)
- Support integrations across varying solutions such as Core Connectors, Workday Studio, Report-as-a-Service (RaaS), Workday Web Services, REST/SOAP APIs, and secure file transfer methods.
- Create and maintain technical design documents, business process flow diagrams, data mappings, transformation rules, integration schedules, dependencies, error handling, and operational support procedures.
- Partners with Reporting and Analytics subject matter experts to troubleshoot and test Workday custom reports, advanced and matrix reports, calculated fields, dashboards, and data extracts that support operational, audit, and analytical needs.
- Partner with functional teams and business stakeholders to gather requirements, assess impacts, and translate business needs into scalable technical solutions.
- Plan
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to extract substantive content: Job Summary paragraph, Position Responsibilities (list), Qualifications (list maybe), Competencies & Skills (list), About Nclh (company description). Also maybe "About Nclh" is about the company; we can treat as "About the company" heading. We must not include boilerplate like "EQUAL OPPORTUNITY EMPLOYER", "Learn More About Our Company At a Glance Brand Overview ..."? Actually there is "Learn More About Our Company At a Glance Brand Overview Norwegian Cruise Line Oceania Cruises Regent Seven Seas Cruises New Releases". That seems like navigation; we should remove. Also "APPLY ONLINE" etc. Remove application instructions. We need to keep all substantive info: The job summary paragraph, responsibilities list, qualifications list, competencies & skills list, about NCLH description. We need to format with
headings. Which headings? The posting has sections: Job Summary, Position Responsibilities, Qualifications, Competencies & Skills, About Nclh. We can map to headings: "Job Summary" maybe not in list but we can use "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings if they match content? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we can use those headings if appropriate. For Job Summary we could use "About the role". For Position Responsibilities we can use "Responsibilities". For Qualifications we can use "Qualifications". For Competencies & Skills we can use "Skills". For About Nclh we could use "About the company" but not in examples; maybe we can still use "About the role"? Actually "About Nclh" is about the company, not role. Could use "About the company". The instruction didn't forbid other headings, just gave examples. Safer to use headings that match content: "About the role", "Responsibilities", "Qualifications", "Skills", "About the company". Use for each.
Now content:
Job Summary paragraph: "The Workday Technical Analyst is a hands-on HR technology professional responsible for designing, developing, testing, deploying, and supporting secure, scalable Workday solutions. The role combines expertise in Workday integrations, reporting, security, data conversion, and Core HCM to maintain reliable data exchanges and improve the employee and manager experience. The ideal candidate can translate business requirements into technical designs, troubleshoot complex production issues, and partner effectively with People Excellence, Payroll, Finance, IT, security teams, vendors, and external consultants in a complex global enterprise environment."
We'll put that in
for each. Now content: Job Summary paragraph: "The Workday Technical Analyst is a hands-on HR technology professional responsible for designing, developing, testing, deploying, and supporting secure, scalable Workday solutions. The role combines expertise in Workday integrations, reporting, security, data conversion, and Core HCM to maintain reliable data exchanges and improve the employee and manager experience. The ideal candidate can translate business requirements into technical designs, troubleshoot complex production issues, and partner effectively with People Excellence, Payroll, Finance, IT, security teams, vendors, and external consultants in a complex global enterprise environment." We'll put that in
. Responsibilities: list of bullet points from "Position Responsibilities". Need to extract each bullet. The text after "Position Responsibilities" is a long sentence with many items separated by periods? Actually it's a paragraph with many items separated by periods but not bullet list. We need to convert to
- . We should split by each distinct responsibility. Let's parse: "Serve as a technical subject matter expert for Workday HCM integrations, reporting, security, data conversion, and production support. Design, build, configure, and maintain integrations using Enterprise Interface Builder (EIB) Support integrations across varying solutions such as Core Connectors, Workday Studio, Report-as-a-Service (RaaS), Workday Web Services, REST/SOAP APIs, and secure file transfer methods. Create and maintain technical design documents, business process flow diagrams, data mappings, transformation rules, integration schedules, dependencies, error handling, and operational support procedures. Partners with Reporting and Analytics subject matter experts to troubleshoot and test Workday custom reports, advanced and matrix reports, calculated fields, dashboards, and data extracts that support operational, audit, and analytical needs. Partner with functional teams and business stakeholders to gather requirements, assess impacts, and translate business needs into scalable technical solutions. Plan and execute unit, system integration, regression, and user acceptance testing; prepare test cases and test data, document results, and manage defects through resolution. Support Workday implementations, tenant updates/releases, enhancements, data conversions, deployments, and post-production stabilization activities. Monitor scheduled integrations and production processes; triage incidents, perform root-cause analysis, implement corrective actions, and communicate status in accordance with service-level expectations. Validate inbound and outbound data for accuracy, completeness, reconciliation, and compliance across Workday and connected systems. Collaborate across Core HCM, Recruiting, Talent, Compensation, Benefits, Absence, Time Tracking, Payroll, Finance, and identity management processes. Maintain technical documentation, runbooks, configuration records, testing evidence, and audit-ready support artifacts. Audit, SOX & Compliance Support consolidating audit evidence materials for project phases and ongoing Production Support activities to present to Audit panels in fulfillment of internal and external audit requests Identify opportunities to automate manual processes, strengthen controls, improve maintainability, and enhance system performance and user experience. Provide knowledge transfer and technical guidance to analysts, support teams, and business partners. Perform other duties as assigned." We need to ensure each bullet is a
- . We'll keep the text as is.
Qualifications: The section includes "DEGREE TYPE: Bachelor's Degree FIELD(S) OF STUDY: Information Systems, Computer Science, Human Resources, Business Administration, or a related field. Experience 4+ years of Workday or HRIS/IT technical experience supporting integrations, reporting, security, data conversion, or related platform capabilities. Hands-on experience with Workday integration technologies such as EIB, Core Connectors, Workday Studio, RaaS, Workday Web Services, REST/SOAP APIs, XML, XSLT, JSON, and SFTP. Experience with Workday reports and calculated fields and analyzing data using Microsoft Excel; SQL experience is strongly preferred. Working knowledge of Workday Core HCM, business process framework, organization structures, foundational data, and security concepts. Experience supporting the full solution lifecycle, including requirements, design, build, testing, deployment, documentation, monitoring, and production support. Strong analytical, troubleshooting, data validation, and root-cause analysis skills with high attention to accuracy and detail. Ability to communicate complex technical concepts clearly to technical and non-technical stakeholders and manage multiple priorities independently. Experience with ticketing and delivery tools such as ServiceNow, JIRA, or Smartsheet and with Agile or Waterfall methodologies."
We can turn into list items. Could also keep as paragraphs but instruction: use
- for any list of duties/requirements/benefits. So we should list each qualification as
- . Let's split by sentences.
List:
- Bachelor's Degree in Information Systems, Computer Science, Human Resources, Business Administration, or a related field.
- 4+ years of Workday or HRIS/IT technical experience supporting integrations, reporting, security, data conversion, or related platform capabilities.
- Hands-on experience with Workday integration technologies such as EIB, Core Connectors, Workday Studio, RaaS, Workday Web Services, REST/SOAP APIs, XML, XSLT, JSON, and SFTP.
- Experience with Workday reports and calculated fields and analyzing data using Microsoft Excel; SQL experience is strongly preferred.
- Working knowledge of Workday Core HCM, business process framework, organization structures, foundational data, and security concepts.
- Experience supporting the full solution lifecycle, including requirements, design, build, testing, deployment, documentation, monitoring, and production support.
- Strong analytical, troubleshooting, data validation, and root-cause analysis skills with high attention to accuracy and detail.
- Ability to communicate complex technical concepts clearly to technical and non-technical stakeholders and manage multiple priorities independently.
- Experience with ticketing and delivery tools such as ServiceNow, JIRA, or Smartsheet and with Agile or Waterfall methodologies.
Competencies & Skills: list:
- Workday Pro certification or equivalent Workday integration, reporting, security, or HCM training desired.
- Experience supporting Workday in a publicly traded, global organization with a large and diverse workforce preferred.
- Experience integrating Workday with payroll, benefits, finance, recruiting, timekeeping, identity management, and third-party vendor systems preferred.
- Knowledge of data governance, privacy, audit controls, and secure integration design preferred.
About Nclh: paragraph: "Norwegian Cruise Line Holdings Ltd. (NYSE: NCLH) is a leading global cruise company which operates the Norwegian Cruise Line®, Oceania Cruises® and Regent Seven Seas Cruises® brands. The combined brands currently operate 32 ships, employ over 35,000 shipboard crew from more than 110 different countries and visit approximately 700 different port destination each year."
We can also include "Learn More About Our Company At a Glance Brand Overview Norwegian Cruise Line Oceania Cruises Regent Seven Seas Cruises New Releases" but that seems like navigation; we should drop.
Now produce HTML fragment:
About the role
The Workday Technical Analyst is a hands-on HR technology professional responsible for designing, developing, testing, deploying, and supporting secure, scalable Workday solutions. The role combines expertise in Workday integrations, reporting, security, data conversion, and Core HCM to maintain reliable data exchanges and improve the employee and manager experience. The ideal candidate can translate business requirements into technical designs, troubleshoot complex production issues, and partner effectively with People Excellence, Payroll, Finance, IT, security teams, vendors, and external consultants in a complex global enterprise environment.
Responsibilities
- Serve as a technical subject matter expert for Workday HCM integrations, reporting, security, data conversion, and production support.
- Design, build, configure, and maintain integrations using Enterprise Interface Builder (EIB)
- Support integrations across varying solutions such as Core Connectors, Workday Studio, Report-as-a-Service (RaaS), Workday Web Services, REST/SOAP APIs, and secure file transfer methods.
- Create and maintain technical design documents, business process flow diagrams, data mappings, transformation rules, integration schedules, dependencies, error handling, and operational support procedures.
- Partners with Reporting and Analytics subject matter experts to troubleshoot and test Workday custom reports, advanced and matrix reports, calculated fields, dashboards, and data extracts that support operational, audit, and analytical needs.
- Partner with functional teams and business stakeholders to gather requirements, assess impacts, and translate business needs into scalable technical solutions.
- Plan