HRIS Architect
First American · Santa Ana, CA · 3 wk ago
Engineering$85k–$113k/yrFull-time
We need to output only HTML fragment, no html/body tags, no markdown fences. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting.
The posting includes:
- Who We Are (company description) - not a required heading but could be "About the role"? Actually "About the role" is a heading we can use for description of role? The posting includes "What We Do" which describes responsibilities. Also "Essential Functions" list of duties. Also "Knowledge and Skills / Technology Used". Also "Typical Education". Also "Licenses or Certificates". Also "Typical Range of Experience". Also "What We Offer" includes benefits and pay range.
We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We should not repeat job title as heading (not present). We should not include Job ID etc.
We need to decide which sections to include based on content.
- About the role: Could include the "Who We Are" and maybe "What We Do" summary? But "About the role" maybe a brief description of the role. The posting includes "What We Do" which is essentially role description. So we can put that under About the role.
- Responsibilities: The "Essential Functions" list is responsibilities. So we can put that under Responsibilities.
- Requirements: Could include education, experience, certifications? Might be split into Qualifications and Skills. The spec says we can have sections for Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements could be education and experience; Qualifications could be certifications; Skills could be technical skills. But we need to follow instruction: use headings only when posting has real specific content for it. We can include multiple sections if they have content.
We have:
- Typical Education: Bachelor's degree ... or equivalent.
- Licenses or Certificates: Workday certifications preferred but not required; Workday training or demonstrated hands-on Workday development experience desirable; Workday Extend training or certification considered a plus; Integration, cloud, software development, or related technical certifications considered a plus.
- Typical Range of Experience: 2–4 years of HRIS or Workday technical experience; hands-on experience supporting or developing Workday integrations, reporting, or related technical solutions; experience with Workday EIB, Web Services, Reporting, and Calculated Fields preferred; experience with Workday Studio and Cloud Connect preferred; experience troubleshooting production issues and supporting business-critical integrations preferred; experience collaborating with functional HRIS teams, business stakeholders, vendors, and technical teams; Workday Extend experience a plus but not required; demonstrated interest and ability to learn Workday Extend and other emerging Workday development technologies; demonstrated ability and desire to grow technical expertise across Workday integrations, reporting, security, application development, and related platform technologies.
- Knowledge and Skills / Technology Used: list of technical skills: Working knowledge of Workday integration technologies such as EIB, Workday Studio, Cloud Connect, Web Services, and APIs; Hands-on experience developing, maintaining, or troubleshooting Workday integrations; Experience with Workday Reporting and Calculated Fields; Working knowledge of XML, XSLT, XPath, JSON, REST APIs, SOAP Web Services, and related integration technologies; Familiarity with object-oriented programming concepts; Understanding of Workday Security concepts is preferred; Familiarity with software development lifecycle, source control, deployment processes, and change management practices; Strong analytical, troubleshooting, and problem-solving skills; Ability to systematically investigate technical issues and identify potential root causes; Strong attention to detail, particularly when working with integrations and sensitive HR data; Strong written and verbal communication skills; Ability to communicate technical concepts to both technical and non-technical stakeholders; Ability to manage multiple assignments and prioritize work effectively; Demonstrated ability and willingness to learn new Workday technologies and development tools; Intermediate to advanced Microsoft Excel skills.
Thus we have overlapping content: Experience and skills.
We could structure:
- About the role: combine Who We Are and What We Do? But "Who We Are" is company description, not role. Might be okay as About the role includes company overview? The instruction: "use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting.
The posting includes:
- Who We Are (company description) - not a required heading but could be "About the role"? Actually "About the role" is a heading we can use for description of role? The posting includes "What We Do" which describes responsibilities. Also "Essential Functions" list of duties. Also "Knowledge and Skills / Technology Used". Also "Typical Education". Also "Licenses or Certificates". Also "Typical Range of Experience". Also "What We Offer" includes benefits and pay range.
We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We should not repeat job title as heading (not present). We should not include Job ID etc.
We need to decide which sections to include based on content.
- About the role: Could include the "Who We Are" and maybe "What We Do" summary? But "About the role" maybe a brief description of the role. The posting includes "What We Do" which is essentially role description. So we can put that under About the role.
- Responsibilities: The "Essential Functions" list is responsibilities. So we can put that under Responsibilities.
- Requirements: Could include education, experience, certifications? Might be split into Qualifications and Skills. The spec says we can have sections for Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements could be education and experience; Qualifications could be certifications; Skills could be technical skills. But we need to follow instruction: use headings only when posting has real specific content for it. We can include multiple sections if they have content.
We have:
- Typical Education: Bachelor's degree ... or equivalent.
- Licenses or Certificates: Workday certifications preferred but not required; Workday training or demonstrated hands-on Workday development experience desirable; Workday Extend training or certification considered a plus; Integration, cloud, software development, or related technical certifications considered a plus.
- Typical Range of Experience: 2–4 years of HRIS or Workday technical experience; hands-on experience supporting or developing Workday integrations, reporting, or related technical solutions; experience with Workday EIB, Web Services, Reporting, and Calculated Fields preferred; experience with Workday Studio and Cloud Connect preferred; experience troubleshooting production issues and supporting business-critical integrations preferred; experience collaborating with functional HRIS teams, business stakeholders, vendors, and technical teams; Workday Extend experience a plus but not required; demonstrated interest and ability to learn Workday Extend and other emerging Workday development technologies; demonstrated ability and desire to grow technical expertise across Workday integrations, reporting, security, application development, and related platform technologies.
- Knowledge and Skills / Technology Used: list of technical skills: Working knowledge of Workday integration technologies such as EIB, Workday Studio, Cloud Connect, Web Services, and APIs; Hands-on experience developing, maintaining, or troubleshooting Workday integrations; Experience with Workday Reporting and Calculated Fields; Working knowledge of XML, XSLT, XPath, JSON, REST APIs, SOAP Web Services, and related integration technologies; Familiarity with object-oriented programming concepts; Understanding of Workday Security concepts is preferred; Familiarity with software development lifecycle, source control, deployment processes, and change management practices; Strong analytical, troubleshooting, and problem-solving skills; Ability to systematically investigate technical issues and identify potential root causes; Strong attention to detail, particularly when working with integrations and sensitive HR data; Strong written and verbal communication skills; Ability to communicate technical concepts to both technical and non-technical stakeholders; Ability to manage multiple assignments and prioritize work effectively; Demonstrated ability and willingness to learn new Workday technologies and development tools; Intermediate to advanced Microsoft Excel skills.
Thus we have overlapping content: Experience and skills.
We could structure:
- About the role: combine Who We Are and What We Do? But "Who We Are" is company description, not role. Might be okay as About the role includes company overview? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use About the role for a brief description of the role and maybe company. We'll include the "Who We Are" paragraph and "What We Do" paragraph as prose.
- Responsibilities: list of Essential Functions (bulleted). Use - .
- Requirements: maybe education and typical experience? Could combine education and experience. But we also have Qualifications (certifications) and Skills (technical). Let's decide:
- Requirements: Education and Experience (Typical Education + Typical Range of Experience). Could be separate sections but we can combine into Requirements.
- Qualifications: Licenses or Certificates.
- Skills: Knowledge and Skills / Technology Used.
- Benefits: What We Offer includes benefits description (medical, dental, vision, 401k, PTO/paid sick leave, employee stock purchase plan). Also inclusive culture description. We'll put benefits there.
- Pay: Pay Range: $85,000.00 - $113,300.00 Annually. Also note about hiring range. We'll include that.
- Schedule: Not mentioned. So we omit Schedule section.
We must not include sections with filler like "commensurate with experience". We have real content.
We must not include boilerplate like EEO etc. The posting includes a Fair Chance statement for Los Angeles County unincorporated area. That's likely boilerplate/legal; we should remove it. Also the statement about "Note that the following statements only apply to candidates who will be working from an unincorporated area within Los Angeles County." and the following paragraphs about criminal history. That's legal boilerplate; remove.
Also remove "First American is an equal opportunity employer..." etc. That's EEO boilerplate; remove.
Also remove "For more information, please visit www.careers.firstam.com." maybe not needed but it's not boilerplate? It's a link; could be considered navigation? Probably safe to keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to careers site is not navigation? It's a reference; but could be considered navigation. Safer to remove.
Also remove "Based on eligibility, First American offers a comprehensive benefits package including medical, dental, vision, 401k, PTO/paid sick leave and other great benefits like an employee stock purchase plan." That's benefits; we keep.
Now craft HTML.
We need to output only HTML fragment, no or . We'll output headings and content.
Structure:
About the role
Who We Are ...
What We Do ...
But we need to ensure we don't duplicate content. We'll combine.
Let's extract the Who We Are paragraph:
"Join a team that puts its People First! Since 1889, First American (NYSE: FAF) has held an unwavering belief in its people. They are passionate about what they do, and we are equally passionate about fostering an environment where all feel welcome, supported, and empowered to be innovative and reach their full potential. Our inclusive, people-first culture has earned our company numerous accolades, including being named to the Fortune 100 Best Companies to Work For® list for eleven consecutive years. We have also earned awards as a best place to work for women, diversity and LGBTQ+ employees, and have been included on more than 50 regional best places to work lists. First American will always strive to be a great place to work, for all."
Then What We Do:
"Participates in the design, development, configuration, testing, debugging, deployment, and maintenance of technical solutions supporting Human Resources business applications. Supports enterprise-wide Workday implementations and integrations with vendor and company-specific applications. The HRIS Architect works as part of the HRIS technical team supporting Workday technical administration, integrations, reporting, security, and related technical solutions. The role provides hands-on development opportunities across technologies including Enterprise Interface Builder (EIB), Workday Studio, Cloud Connect, Web Services, Workday Reporting, and other Workday platform capabilities. This position requires a strong technical foundation, curiosity, problem-solving ability, and a desire to continuously expand technical knowledge within the Workday ecosystem. The individual may also have opportunities to learn and develop applications using Workday Extend. Previous Workday Extend experience is beneficial but is not required for the position. Candidates should demonstrate an interest and ability to learn new Workday development technologies as the platform evolves."
We'll put both as under About the role.
Now Responsibilities: list of Essential Functions. We'll extract each sentence that starts with a verb. We'll make
- for each.
List:
- Support and maintain Workday integrations, reporting, security, and related technical components.
- Develop and maintain Workday integrations using Enterprise Interface Builder (EIB), Workday Web Services, Cloud Connect, and Workday Studio.
- Develop technical solutions based on business and functional requirements with guidance from senior team members when appropriate.
- Create and maintain Cloud Connect integrations.
- Support Workday Security configuration and maintain related technical documentation.
- Prepare and execute migrations and deployments across Workday Sandbox, Preview, and Production environments following established change management procedures.
- Develop and maintain Workday reports using the Workday Reporting Platform, Calculated Fields, and Workday Report Designer.
- Write high-quality, maintainable, reusable, and well-documented code according to established development standards.
- Perform unit testing, integration testing, troubleshooting, and debugging of integrations, reports, and related technical solutions.
- Schedule and monitor integrations and reports and configure appropriate notifications for failures and other operational events.
- Monitor integration activity and proactively investigate failures, performance issues, and data discrepancies.
- Analyze, prioritize, troubleshoot, and resolve technical issues, escalating complex issues when appropriate.
- Participate in root-cause analysis and contribute to solutions that prevent recurring production issues.
- Collaborate with HRIS functional teams, business stakeholders, vendors, and other technical teams to understand requirements and translate them into effective technical solutions.
- Participate in technical design discussions and contribute recommendations based on Workday capabilities and established development practices.
- Create and maintain technical documentation, design specifications, support procedures, and troubleshooting documentation.
- Participate in the ongoing development, maintenance, and improvement of Knowledge Base and FAQ repositories.
- Stay current with Workday releases, integration enhancements, reporting capabilities, and emerging Workday development technologies.
- Participate in technical peer reviews, testing, and knowledge-sharing sessions.
- Continuously develop technical skills across the Workday ecosystem.
- Develop familiarity with Workday Extend and other emerging Workday development capabilities as opportunities arise.
We'll put each as
- .
Now Requirements: Education + Experience.
Education paragraph: "Typical Education Bachelor’s degree in Computer Science, Information Systems, Engineering, Human Resources Information Systems, or a related field, or an equivalent combination of education and relevant professional experience."
Experience paragraph: "Typical Range of Experience 2–4 years of HRIS or Workday technical experience.Hands-on experience supporting or developing Workday integrations, reporting, or related technical solutions.Experience with Workday EIB, Web Services, Reporting, and Calculated Fields is preferred.Experience with Workday Studio and Cloud Connect is preferred.Experience troubleshooting production issues and supporting business-critical integrations is preferred.Experience collaborating with functional HRIS teams, business stakeholders, vendors, and technical teams.Workday Extend experience is a plus but not required.Demonstrated interest and ability to learn Workday Extend and other emerging Workday development technologies.Demonstrated ability and desire to grow technical expertise across Workday integrations, reporting, security, application development, and related platform technologies"
We'll combine into maybe two
under Requirements.
Now Qualifications: Licenses or Certificates.
- .
- Requirements: maybe education and typical experience? Could combine education and experience. But we also have Qualifications (certifications) and Skills (technical). Let's decide:
- Requirements: Education and Experience (Typical Education + Typical Range of Experience). Could be separate sections but we can combine into Requirements.
- Qualifications: Licenses or Certificates.
- Skills: Knowledge and Skills / Technology Used.
- Benefits: What We Offer includes benefits description (medical, dental, vision, 401k, PTO/paid sick leave, employee stock purchase plan). Also inclusive culture description. We'll put benefits there.
- Pay: Pay Range: $85,000.00 - $113,300.00 Annually. Also note about hiring range. We'll include that.
- Schedule: Not mentioned. So we omit Schedule section.
We must not include sections with filler like "commensurate with experience". We have real content.
We must not include boilerplate like EEO etc. The posting includes a Fair Chance statement for Los Angeles County unincorporated area. That's likely boilerplate/legal; we should remove it. Also the statement about "Note that the following statements only apply to candidates who will be working from an unincorporated area within Los Angeles County." and the following paragraphs about criminal history. That's legal boilerplate; remove.
Also remove "First American is an equal opportunity employer..." etc. That's EEO boilerplate; remove.
Also remove "For more information, please visit www.careers.firstam.com." maybe not needed but it's not boilerplate? It's a link; could be considered navigation? Probably safe to keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to careers site is not navigation? It's a reference; but could be considered navigation. Safer to remove.
Also remove "Based on eligibility, First American offers a comprehensive benefits package including medical, dental, vision, 401k, PTO/paid sick leave and other great benefits like an employee stock purchase plan." That's benefits; we keep.
Now craft HTML.
We need to output only HTML fragment, no or . We'll output headings and content.
Structure:
About the role
Who We Are ...
What We Do ...
But we need to ensure we don't duplicate content. We'll combine. Let's extract the Who We Are paragraph: "Join a team that puts its People First! Since 1889, First American (NYSE: FAF) has held an unwavering belief in its people. They are passionate about what they do, and we are equally passionate about fostering an environment where all feel welcome, supported, and empowered to be innovative and reach their full potential. Our inclusive, people-first culture has earned our company numerous accolades, including being named to the Fortune 100 Best Companies to Work For® list for eleven consecutive years. We have also earned awards as a best place to work for women, diversity and LGBTQ+ employees, and have been included on more than 50 regional best places to work lists. First American will always strive to be a great place to work, for all." Then What We Do: "Participates in the design, development, configuration, testing, debugging, deployment, and maintenance of technical solutions supporting Human Resources business applications. Supports enterprise-wide Workday implementations and integrations with vendor and company-specific applications. The HRIS Architect works as part of the HRIS technical team supporting Workday technical administration, integrations, reporting, security, and related technical solutions. The role provides hands-on development opportunities across technologies including Enterprise Interface Builder (EIB), Workday Studio, Cloud Connect, Web Services, Workday Reporting, and other Workday platform capabilities. This position requires a strong technical foundation, curiosity, problem-solving ability, and a desire to continuously expand technical knowledge within the Workday ecosystem. The individual may also have opportunities to learn and develop applications using Workday Extend. Previous Workday Extend experience is beneficial but is not required for the position. Candidates should demonstrate an interest and ability to learn new Workday development technologies as the platform evolves." We'll put both asunder About the role. Now Responsibilities: list of Essential Functions. We'll extract each sentence that starts with a verb. We'll make
- for each. List: - Support and maintain Workday integrations, reporting, security, and related technical components. - Develop and maintain Workday integrations using Enterprise Interface Builder (EIB), Workday Web Services, Cloud Connect, and Workday Studio. - Develop technical solutions based on business and functional requirements with guidance from senior team members when appropriate. - Create and maintain Cloud Connect integrations. - Support Workday Security configuration and maintain related technical documentation. - Prepare and execute migrations and deployments across Workday Sandbox, Preview, and Production environments following established change management procedures. - Develop and maintain Workday reports using the Workday Reporting Platform, Calculated Fields, and Workday Report Designer. - Write high-quality, maintainable, reusable, and well-documented code according to established development standards. - Perform unit testing, integration testing, troubleshooting, and debugging of integrations, reports, and related technical solutions. - Schedule and monitor integrations and reports and configure appropriate notifications for failures and other operational events. - Monitor integration activity and proactively investigate failures, performance issues, and data discrepancies. - Analyze, prioritize, troubleshoot, and resolve technical issues, escalating complex issues when appropriate. - Participate in root-cause analysis and contribute to solutions that prevent recurring production issues. - Collaborate with HRIS functional teams, business stakeholders, vendors, and other technical teams to understand requirements and translate them into effective technical solutions. - Participate in technical design discussions and contribute recommendations based on Workday capabilities and established development practices. - Create and maintain technical documentation, design specifications, support procedures, and troubleshooting documentation. - Participate in the ongoing development, maintenance, and improvement of Knowledge Base and FAQ repositories. - Stay current with Workday releases, integration enhancements, reporting capabilities, and emerging Workday development technologies. - Participate in technical peer reviews, testing, and knowledge-sharing sessions. - Continuously develop technical skills across the Workday ecosystem. - Develop familiarity with Workday Extend and other emerging Workday development capabilities as opportunities arise. We'll put each as
- .
Now Requirements: Education + Experience.
Education paragraph: "Typical Education Bachelor’s degree in Computer Science, Information Systems, Engineering, Human Resources Information Systems, or a related field, or an equivalent combination of education and relevant professional experience."
Experience paragraph: "Typical Range of Experience 2–4 years of HRIS or Workday technical experience.Hands-on experience supporting or developing Workday integrations, reporting, or related technical solutions.Experience with Workday EIB, Web Services, Reporting, and Calculated Fields is preferred.Experience with Workday Studio and Cloud Connect is preferred.Experience troubleshooting production issues and supporting business-critical integrations is preferred.Experience collaborating with functional HRIS teams, business stakeholders, vendors, and technical teams.Workday Extend experience is a plus but not required.Demonstrated interest and ability to learn Workday Extend and other emerging Workday development technologies.Demonstrated ability and desire to grow technical expertise across Workday integrations, reporting, security, application development, and related platform technologies"
We'll combine into maybe two
under Requirements. Now Qualifications: Licenses or Certificates.