Staff Software Engineer - Digital Platform
Western Union · Austin, TX · 3 wk ago
HybridFinance$135k–$160k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications?, Skills?, Benefits, Pay, Schedule. Use . Ensure we keep content.
Next "Role Requirements" then list of requirements. Let's extract:
"BS in Computer Science or related fields with 5+ years of professional experience or MS with 5+ years of experience; Equivalent work experience in lieu of a degree.
2+ Demonstrated experience in modern programming languages and frameworks (Java Spring boot, DynamoDB/Postgres, Kafka, Redis, Apache Camel) and standard design patterns for implementing microservices.
2+ years of hands-on technical lead with demonstrated experience in designing and implementing large scale microservices.
2+ years of experience with agile development methodologies with Test Driven Development (TDD) and CI (Continuous Integration)/CD (Continuous Delivery).
1+ years of experience with architecture design concepts and techniques and the ability to communicate and evangelize those concepts to a broad-based team.
1+ years hands-on experience in building microservices based architecture and platform developed and deployed at scale.
1+ years hands-on experience building enterprise scale APIs used by web and mobile applications.
1+ years of experience in Cloud (AWS) based architecture designs and implementations.
6 months hands-on experience using AI coding agents to build or accelerate end-to-end software delivery."
We need to keep each as . Also note "2+ Demonstrated experience" maybe missing a word but keep as is.
Next "Preferred Qualifications" then list:
"Experience in FinTech industry.
Experience in building external customer-facing applications with open-source. technologies and understanding of front-end tech stack"
We need to include as under maybe a "Preferred Qualifications" heading? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have a heading "Qualifications" for both required and preferred? Or separate? The instruction says use those headings; we can have a "Qualifications" section that includes both required and preferred? But they said "Prefer a few substantive sections over many thin ones." Could combine Requirements and Preferred Qualifications under Qualifications? However they also have separate headings for Requirements and Qualifications in the list. The posting has "Role Requirements" and "Preferred Qualifications". We could map "Role Requirements" to
for headings. Only include sections if posting has real specific content. Need to preserve all substantive info, no boilerplate, no navigation, no EEO, no application instructions, no cookie/legal, no duplicated lines. We must extract content: Job title line: "JR0130059 Position location: Austin, TX". The job ID and location can be folded into a short
or dropped. We can include a
with location maybe. Then "The Staff Software Engineer will lead the design and delivery of scalable, cloud-native microservices powering Western Union’s digital platform. This role serves as a hands-on technical expert and service owner, partnering with distributed engineering teams to ensure reliability, performance, and architectural excellence. Applicants must be currently authorized to work in the United States on a full-time basis. Western Union will not sponsor applicants for work visas for this position." That's about the role. So we can have
About the role
thenwith that paragraph. Next "Role Responsibilities" then a list of responsibilities. Need to extract bullet points. The responsibilities are a long paragraph with sentences separated by no punctuation? Let's parse: "Develop and implement new software, maintain and improve existing software Ensure that software functionality is implemented with a focus on code optimization and organization. Build applications, workflow automation’s, internal tools, and basic agents using AI coding agents within Western Union’s product and platform areas. Recommend improvements to existing software programs. Troubleshoot application issues and coordinate issue resolution with operations, functional, and technical teams. Work as service lead with development team across geographically distributed structure Review design and code from different scrum teams and ensure service level standards are enforced. Responsible for maintaining quality and engineering metrics of specific microservices as a services owner. Provide coaching to Junior engineers on the team. Works independently on complex projects. Assess business needs while providing creative and effective solutions in conformance to emerging technology standards. Perform strong decision-making, communication, and collaboration skills. Perform computer science fundamentals, data structures, algorithms, OOPs, and OOA/D." We need to turn each line into
Requirements
and "Preferred Qualifications" toQualifications
. That seems appropriate. Next "Workplace Option HYBRID ..." This is schedule info. So we can have aSchedule
with that paragraph. Next "Benefits" then list of benefits. We'll haveBenefits
with- each benefit.
Benefits list:
"You will also have access to short-term incentives, multiple health insurance options, accident and life insurance, and access to best-in-class development platforms, to name a few (https://careers.westernunion.com/global-benefits/). Please see the location-specific benefits below and note that your Recruiter may share additional role-specific benefits during your interview process or in an offer of employment. Your United States – Specific Benefits Include Paid Time Off Medical, Dental and Life Insurance Tuition Assistance Program Student Loan Repayment (below manager level only) Parental Leave One day volunteer time off $0 Money Transfer Fee Discount Code – Quarterly Recognition Program “Game Changers” Employee Discount Program Global Adoption Assistance Global Scholarship Awards Program 401K plan"
We need to parse into items. The text is messy. We'll extract each benefit separated by commas or line breaks? Let's try to split:
- short-term incentives
- multiple health insurance options
- accident and life insurance
- access to best-in-class development platforms
- Paid Time Off
- Medical, Dental and Life Insurance (maybe combined)
- Tuition Assistance Program
- Student Loan Repayment (below manager level only)
- Parental Leave
- One day volunteer time off
- $0 Money Transfer Fee Discount Code – Quarterly Recognition Program “Game Changers”
- Employee Discount Program
- Global Adoption Assistance
- Global Scholarship Awards Program
- 401K plan
Also there is mention of location-specific benefits for certain states but we can ignore as boilerplate? It's location-specific benefits but it's still substantive. However it's a conditional statement: "For residents of Colorado, California, Connecticut, Delaware, Minnesota, and Pennsylvania: Please do not respond to any questions on this initial application that may seek age-identifying information..." That's EEO/legal boilerplate, should be removed. So we discard that.
Also "Please see the location-specific benefits below and note that your Recruiter may share additional role-specific benefits during your interview process or in an offer of employment." That's generic, maybe we can keep as part of benefits intro? But it's not a specific benefit. We could keep a short paragraph before list.
We need to avoid boilerplate like EEO, legal, etc. The benefits section includes some generic sentences; we can keep the introductory sentence: "You will also have access to short-term incentives, multiple health insurance options, accident and life insurance, and access to best-in-class development platforms, to name a few." That's substantive. Then we can list specific benefits.
We also have "Please see the location-specific benefits below and note that your Recruiter may share additional role-specific benefits during your interview process or in an offer of employment." That's somewhat generic; maybe we can keep as part of intro but it's not a specific benefit. Might be considered boilerplate? It's not EEO but it's still generic. I'd keep it as part of intro paragraph.
Now Pay: "Salary Annual base salary range is $135,000 – 160,000 USD per year. Total on-target compensation includes a base salary and short-term that align with individual and company performance. Actual salaries will vary based on candidates’ qualifications, skills, and competencies." That's pay info. We'll put under
Pay
with. We also have "As part of the application process, all applicants are required to take assessments..." That's application instructions, should be removed. Also "Estimated Job Posting End Date 10-09-2026 ..." that's metadata, can be dropped. Now we need to ensure we don't repeat job title as heading. We'll not. We'll output HTML fragment. Structure:
Position location: Austin, TX
maybe. ThenAbout the role
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Benefits
Intro sentence
- ...
Pay
...
Schedule
...
We must not include empty sections. Check for any duplicated content: ensure we didn't include EEO etc. Now craft the HTML. Let's write the About the role paragraph: "The Staff Software Engineer will lead the design and delivery of scalable, cloud-native microservices powering Western Union’s digital platform. This role serves as a hands-on technical expert and service owner, partnering with distributed engineering teams to ensure reliability, performance, and architectural excellence. Applicants must be currently authorized to work in the United States on a full-time basis. Western Union will not sponsor applicants for work visas for this position." Now Responsibilities list items: - Develop and implement new software, maintain and improve existing software - Ensure that software functionality is implemented with a focus on code optimization and organization. - Build applications, workflow automation’s, internal tools, and basic agents using AI coding agents within Western Union’s product and platform areas. - Recommend improvements to existing software programs. - Troubleshoot application issues and coordinate issue resolution with operations, functional, and technical teams. - Work as service lead with development team across geographically distributed structure - Review design and code from different scrum teams and ensure service level standards are enforced. - Responsible for maintaining quality and engineering metrics of specific microservices as a services owner. - Provide coaching to Junior engineers on the team. - Works independently on complex projects. - Assess business needs while providing creative and effective solutions in conformance to emerging technology standards. - Perform strong decision-making, communication, and collaboration skills. - Perform computer science fundamentals, data structures, algorithms, OOPs, and OOA/D. Note: some lines have weird apostrophe (automation’s). Keep as is. Now Requirements list: - BS in Computer Science or related fields with 5+ years of professional experience or MS with 5+ years of experience; Equivalent work experience in lieu of a degree. - 2+ Demonstrated experience in modern programming languages and frameworks (Java Spring boot, DynamoDB/Postgres, Kafka, Redis, Apache Camel) and standard design patterns for implementing microservices. - 2+ years of hands-on technical lead with demonstrated experience in designing and implementing large scale microservices. - 2+ years of experience with agile development methodologies with Test Driven Development (TDD) and CI (Continuous Integration)/CD (Continuous Delivery). - 1+ years of experience with architecture design concepts and techniques and the ability to communicate and evangelize those concepts to a broad-based team. - 1+ years hands-on experience in building microservices based architecture and platform developed and deployed at scale. - 1+ years hands-on experience building enterprise scale APIs used by web and mobile applications. - 1+ years of experience in Cloud (AWS) based architecture designs and implementations. - 6 months hands-on experience using AI coding agents to build or accelerate end-to-end software delivery. Now Preferred Qualifications list: - Experience in FinTech industry. - Experience in building external customer-facing applications with open-source. technologies and understanding of front-end tech