Lead Software Engineer
for each section heading.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information, not invent or summarize away detail.
Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to drop things like "To be considered for this position, please submit an application..." etc. Also drop "Employees may be eligible for a discretionary bonus..."? That's benefits info, we keep benefits. But we need to remove duplicated lines.
We need to include Pay section only if posting actually states them. The posting includes salary ranges per location. So we can include Pay section with that info.
Schedule: The posting mentions "Hybrid work environment, with defined in-person presence requirements. Occasional travel and extended hours may be required." That's schedule info. So we can include Schedule section.
Benefits: The posting includes many benefits: health, dental, vision insurance, basic life, AD&D, supplemental life, spouse/domestic partner and dependent life, spouse/domestic partner and dependent AD&D, short- and long-term disability, long-term care, business travel accident, disability and legal, 401(k) with match, additional FINRA-funded retirement contribution, tuition reimbursement, commuter benefits, adoption assistance, backup family care, surrogacy benefits, employee assistance, wellness programs. Also time off: 15 days PTO, 5 personal days, 9 sick days, two volunteer service days, other paid leave (military, jury duty, bereavement, voting, care of family member after 90 days, childbirth/parental after 90 days), nine paid holidays. So we can include Benefits section.
Requirements: Education/Experience Requirements: Bachelor’s degree in Computer Science, Information Systems or related discipline with at least 7 years of related experience, or equivalent training and/or work experience. Then list of strong experience items: Strong system design experience, Strong experience in object-oriented development, Strong experience with cloud technologies, Strong experience in data storage technologies, Strong experience in performance tuning and optimization, Strong experience in DevOps and CI/CD technologies, Strong experience test automation and unit testing, Strong experience software security. Also earlier there were "Software QA experience as well as being in a lead capacity role setting testing direction and mentoring others." etc. Also "Deep, hands-on expertise designing, building, and maintaining test automation frameworks using tools (such as Playwright, Cucumber, or Selenium). Strong coding skills (Java preferred) with ability to develop, review, and maintain automation code. Experience defining and implementing comprehensive test strategies covering functional, integration, regression, and performance testing, including test data management and shift-left testing practices." Also "Workday testing experience across HCM and/or Finance functional areas (Kainos Smart Test or Opkey)". Also "Experience building test automation/frameworks and test data management for closed SaaS ecosystems." Also "Experience with AWS and CI/CD pipelines for test automation (Jenkins and GitLab)."
We need to avoid duplication: there are repeated lines later.
We need to include Skills section? The posting mentions "Strong communication and influence skills", "strong communication skills", "Mentor engineers", etc. Could be part of Requirements or Skills. We can create a Skills section for soft skills: communication, influence, mentoring, leadership, stakeholder management. But we need to ensure we don't create thin sections. Perhaps combine skills into Requirements or Qualifications. However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have both Requirements and Qualifications if content distinct. But we can also just have Requirements and maybe Skills.
We need to avoid filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /, no markdown fences.
Let's structure:
About the role
... prose describing role ...
Responsibilities
- ... each responsibility ...
Requirements
- ... each requirement ...
Maybe also Skills
for soft skills.
But we need to ensure we don't duplicate content.
Let's extract About the role: first paragraph: "We're seeking an experienced lead developer with strong Java development and test lead skills to drive our testing automation strategy across FINRA's enterprise applications. This hands-on role (approximately 40% QA strategy/leadership, 50% automation and test case development, 10% code reviews) combines quality leadership with advanced technical capabilities to champion best practices, implement automation frameworks, and influence stakeholders at all levels. The ideal candidate will bring extensive experience with test automation tools and a passion for building quality into our diverse application portfolio, including Workday HCM and Finance systems."
That's good.
Next description: "This position supports multiple Corporate Systems application teams across FINRA's enterprise, working with a diverse portfolio including SaaS, COTS, and custom-built software. The successful candidate will provide both direct hands-on support and influence-based leadership to 10+ analysts and developers across multiple peer teams, requiring strong communication skills to drive outcomes and champion quality practices. Key technical requirements include advanced hands-on development capabilities, deep quality assurance practice knowledge, and the ability to understand application architectures to assess risk, set strategy, and communicate priorities effectively."
That could be part of About the role or Responsibilities. But we already have About the role; we could incorporate that into About the role as more prose. However we need to avoid duplication. We'll keep About the role as a single paragraph maybe combining both.
But we need to preserve all substantive information; we can split into multiple paragraphs under About the role.
Now Responsibilities: list from "Responsibilities:" section.
Responsibilities bullet points:
- Define, implement, and evolve test automation strategy across multiple application teams.
- Lead Workday test automation and tool evaluation for HCM and Finance functional areas.
- Develop and maintain automated test cases and frameworks for both custom-built applications and Workday systems.
- Mentor engineers and developers on testing best practices.
- Collaborate with application teams to integrate quality practices throughout the development lifecycle.
- Establish and track quality metrics, presenting findings to executive leadership.
- Drive cultural change around quality practices and shift-left testing adoption.
We need to ensure each as - .
Now Requirements: combine education/experience and technical requirements.
Education/Experience: Bachelor’s degree in Computer Science, Information Systems or related discipline with at least 7 years of related experience, or equivalent training and/or work experience.
Then list of strong experience items:
- Strong system design experience
- Strong experience in object-oriented development
- Strong experience with cloud technologies
- Strong experience in data storage technologies
- Strong experience in performance tuning and optimization
- Strong experience in DevOps and CI/CD technologies
- Strong experience test automation and unit testing
- Strong experience software security
Also earlier technical requirements: "Software QA experience as well as being in a lead capacity role setting testing direction and mentoring others." (duplicate later). "Deep, hands-on expertise designing, building, and maintaining test automation frameworks using tools (such as Playwright, Cucumber, or Selenium)." "Strong coding skills (Java preferred) with ability to develop, review, and maintain automation code." "Experience defining and implementing comprehensive test strategies covering functional, integration, regression, and performance testing, including test data management and shift-left testing practices." "Workday testing experience across HCM and/or Finance functional areas (Kainos Smart Test or Opkey)". "Experience building test automation/frameworks and test data management for closed SaaS ecosystems." "Experience with AWS and CI/CD pipelines for test automation (Jenkins and GitLab)."
We need to avoid duplication: there is repeated block later. We'll consolidate.
Thus Requirements list items:
- Bachelor’s degree in Computer Science, Information Systems or related discipline with at least 7 years of related experience, or equivalent training and/or work experience.
- Strong system design experience
- Strong experience in object-oriented development
- Strong experience with cloud technologies
- Strong experience in data storage technologies
- Strong experience in performance tuning and optimization
- Strong experience in DevOps and CI/CD technologies
- Strong experience in test automation and unit testing
- Strong experience in software security
- Software QA experience in a lead capacity role setting testing direction and mentoring others
- Deep, hands-on expertise designing, building, and maintaining test automation frameworks using tools such as Playwright, Cucumber, or Selenium
- Strong coding skills (Java preferred) with ability to develop, review, and maintain automation code
- Experience defining and implementing comprehensive test strategies covering functional, integration, regression, and performance testing, including test data management and shift-left testing practices
- Workday testing experience across HCM and/or Finance functional areas (Kainos Smart Test or Opkey)
- Experience building test automation/frameworks and test data management for closed SaaS ecosystems
- Experience with AWS and CI/CD pipelines for test automation (Jenkins and GitLab)
We could also include "Strong communication and influence skills" but that's more Skills.
Now Skills section: maybe include:
- Strong communication and influence skills
- Ability to mentor engineers and developers
- Stakeholder management and leadership
- Collaboration across teams
But we need to see if there is any explicit skill list. The posting mentions "strong communication skills to drive outcomes and champion quality practices." Also "Mentor engineers and developers on testing best practices." Also "Collaborate with application teams". Also "influence stakeholders at all levels". So we can create Skills section.
Now Benefits: list all benefits.
We need to format as
- each benefit.
But there are many; we can group maybe but need to preserve all substantive information. We'll list each distinct benefit.
Benefits from posting:
- Comprehensive health, dental and vision insurance
- Basic life insurance
- Accidental death and dismemberment (AD&D)
- Supplemental life insurance
- Spouse/domestic partner and dependent life insurance
- Spouse/domestic partner and dependent accidental death and dismemberment
- Short- and long-term disability
- Long-term care
- Business travel accident insurance
- Disability and legal (maybe "disability and legal" as a benefit? Actually phrase: "short- and long-term disability, long-term care, business travel accident, disability and legal". We'll treat as separate items: short-term disability, long-term disability, long-term care, business travel accident, disability and legal.
- 401(k) plan with company match
- Additional FINRA-funded retirement contribution
- Tuition reimbursement
- Commuter benefits
- Adoption assistance
- Backup family care
- Surrogacy benefits
- Employee assistance
- Wellness programs
- Time off: 15 days of paid time off
- 5 personal days
- 9 sick days (pro-rated first year)
- Two volunteer service days (based on full-time schedule)
- Other paid leave: military leave, jury duty leave, bereavement leave, voting and election official leave for federal, state or local primary and general elections, care of a family member leave (available after 90 days of employment), childbirth and parental leave (available after 90 days of employment)
- Nine paid holidays (full-time schedule)
We need to avoid duplication: there is also "Employees may be eligible for a discretionary bonus in addition to base pay." That's a benefit (bonus). Also "Non-exempt employees are also eligible for overtime pay". That's also a benefit.
We'll include those.
Now Pay: we have salary ranges per location.
We need to present Pay section. Could be a
summarizing ranges,
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to drop things like "To be considered for this position, please submit an application..." etc. Also drop "Employees may be eligible for a discretionary bonus..."? That's benefits info, we keep benefits. But we need to remove duplicated lines. We need to include Pay section only if posting actually states them. The posting includes salary ranges per location. So we can include Pay section with that info. Schedule: The posting mentions "Hybrid work environment, with defined in-person presence requirements. Occasional travel and extended hours may be required." That's schedule info. So we can include Schedule section. Benefits: The posting includes many benefits: health, dental, vision insurance, basic life, AD&D, supplemental life, spouse/domestic partner and dependent life, spouse/domestic partner and dependent AD&D, short- and long-term disability, long-term care, business travel accident, disability and legal, 401(k) with match, additional FINRA-funded retirement contribution, tuition reimbursement, commuter benefits, adoption assistance, backup family care, surrogacy benefits, employee assistance, wellness programs. Also time off: 15 days PTO, 5 personal days, 9 sick days, two volunteer service days, other paid leave (military, jury duty, bereavement, voting, care of family member after 90 days, childbirth/parental after 90 days), nine paid holidays. So we can include Benefits section. Requirements: Education/Experience Requirements: Bachelor’s degree in Computer Science, Information Systems or related discipline with at least 7 years of related experience, or equivalent training and/or work experience. Then list of strong experience items: Strong system design experience, Strong experience in object-oriented development, Strong experience with cloud technologies, Strong experience in data storage technologies, Strong experience in performance tuning and optimization, Strong experience in DevOps and CI/CD technologies, Strong experience test automation and unit testing, Strong experience software security. Also earlier there were "Software QA experience as well as being in a lead capacity role setting testing direction and mentoring others." etc. Also "Deep, hands-on expertise designing, building, and maintaining test automation frameworks using tools (such as Playwright, Cucumber, or Selenium). Strong coding skills (Java preferred) with ability to develop, review, and maintain automation code. Experience defining and implementing comprehensive test strategies covering functional, integration, regression, and performance testing, including test data management and shift-left testing practices." Also "Workday testing experience across HCM and/or Finance functional areas (Kainos Smart Test or Opkey)". Also "Experience building test automation/frameworks and test data management for closed SaaS ecosystems." Also "Experience with AWS and CI/CD pipelines for test automation (Jenkins and GitLab)." We need to avoid duplication: there are repeated lines later. We need to include Skills section? The posting mentions "Strong communication and influence skills", "strong communication skills", "Mentor engineers", etc. Could be part of Requirements or Skills. We can create a Skills section for soft skills: communication, influence, mentoring, leadership, stakeholder management. But we need to ensure we don't create thin sections. Perhaps combine skills into Requirements or Qualifications. However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have both Requirements and Qualifications if content distinct. But we can also just have Requirements and maybe Skills. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Let's structure:
About the role
... prose describing role ...
Responsibilities
- ... each responsibility ...
Requirements
- ... each requirement ...
Skills
for soft skills. But we need to ensure we don't duplicate content. Let's extract About the role: first paragraph: "We're seeking an experienced lead developer with strong Java development and test lead skills to drive our testing automation strategy across FINRA's enterprise applications. This hands-on role (approximately 40% QA strategy/leadership, 50% automation and test case development, 10% code reviews) combines quality leadership with advanced technical capabilities to champion best practices, implement automation frameworks, and influence stakeholders at all levels. The ideal candidate will bring extensive experience with test automation tools and a passion for building quality into our diverse application portfolio, including Workday HCM and Finance systems." That's good. Next description: "This position supports multiple Corporate Systems application teams across FINRA's enterprise, working with a diverse portfolio including SaaS, COTS, and custom-built software. The successful candidate will provide both direct hands-on support and influence-based leadership to 10+ analysts and developers across multiple peer teams, requiring strong communication skills to drive outcomes and champion quality practices. Key technical requirements include advanced hands-on development capabilities, deep quality assurance practice knowledge, and the ability to understand application architectures to assess risk, set strategy, and communicate priorities effectively." That could be part of About the role or Responsibilities. But we already have About the role; we could incorporate that into About the role as more prose. However we need to avoid duplication. We'll keep About the role as a single paragraph maybe combining both. But we need to preserve all substantive information; we can split into multiple paragraphs under About the role. Now Responsibilities: list from "Responsibilities:" section. Responsibilities bullet points: - Define, implement, and evolve test automation strategy across multiple application teams. - Lead Workday test automation and tool evaluation for HCM and Finance functional areas. - Develop and maintain automated test cases and frameworks for both custom-built applications and Workday systems. - Mentor engineers and developers on testing best practices. - Collaborate with application teams to integrate quality practices throughout the development lifecycle. - Establish and track quality metrics, presenting findings to executive leadership. - Drive cultural change around quality practices and shift-left testing adoption. We need to ensure each as- each benefit.
But there are many; we can group maybe but need to preserve all substantive information. We'll list each distinct benefit.
Benefits from posting:
- Comprehensive health, dental and vision insurance
- Basic life insurance
- Accidental death and dismemberment (AD&D)
- Supplemental life insurance
- Spouse/domestic partner and dependent life insurance
- Spouse/domestic partner and dependent accidental death and dismemberment
- Short- and long-term disability
- Long-term care
- Business travel accident insurance
- Disability and legal (maybe "disability and legal" as a benefit? Actually phrase: "short- and long-term disability, long-term care, business travel accident, disability and legal". We'll treat as separate items: short-term disability, long-term disability, long-term care, business travel accident, disability and legal.
- 401(k) plan with company match
- Additional FINRA-funded retirement contribution
- Tuition reimbursement
- Commuter benefits
- Adoption assistance
- Backup family care
- Surrogacy benefits
- Employee assistance
- Wellness programs
- Time off: 15 days of paid time off
- 5 personal days
- 9 sick days (pro-rated first year)
- Two volunteer service days (based on full-time schedule)
- Other paid leave: military leave, jury duty leave, bereavement leave, voting and election official leave for federal, state or local primary and general elections, care of a family member leave (available after 90 days of employment), childbirth and parental leave (available after 90 days of employment)
- Nine paid holidays (full-time schedule)
We need to avoid duplication: there is also "Employees may be eligible for a discretionary bonus in addition to base pay." That's a benefit (bonus). Also "Non-exempt employees are also eligible for overtime pay". That's also a benefit.
We'll include those.
Now Pay: we have salary ranges per location.
We need to present Pay section. Could be a
summarizing ranges,