SDC Front End Engineer---Manager---Raleigh, NC or Dallas, TX
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into 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.
We need to parse the posting: It's a job posting for FSO Technology Service Delivery Manager (Frontend Engineer). Contains location: Anywhere in Country (maybe remote). Contains description: At EY, we’re all in to shape your future with confidence... etc. Then "The opportunity As an FSO Technology Service Delivery Manager, you’ll be based in our Service Delivery Center..." Then "We are looking for Frontend Engineers who will collaborate..." Then "Your Key Responsibilities" bullet list. Then "Skills And Attributes For Success" bullet list. Then "To qualify for the role you must have..." bullet list. Then "Ideally, you’ll also have Experience with the following technologies and practices" bullet list. Then "What We Look For" prose. Then "What We Offer You At EY..." includes compensation and benefits package, base salary ranges, total rewards includes medical/dental, pension/401(k), paid time off, flexible vacation policy, etc.
We need to decide sections: About the role (maybe intro), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Pay info (salary ranges). Benefits info (medical/dental, pension/401(k), paid time off, flexible vacation). Schedule? Not explicitly mentioned; maybe flexible vacation policy but not schedule. No explicit schedule like full-time, part-time, remote? It says location: Anywhere in Country (maybe remote). Could treat location as part of About the role? Not a schedule. So we may not include Schedule section because no explicit schedule content. Benefits we have. Pay we have.
We need to avoid filler sections. So we will include sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe combine qualifications and skills?), but we have separate sections: Requirements (maybe "To qualify for the role you must have..."), Qualifications (maybe "Ideally, you’ll also have..."), Skills (maybe "Skills And Attributes For Success"). However we need to avoid thin sections; but we have substantive content for each. Could combine some but instructions: Prefer a few substantive sections over many thin ones. But we need to follow rule: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings if content exists. We have content for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. That's many sections but each is substantive. Could we merge Requirements and Qualifications? They are distinct: Requirements = mandatory qualifications; Qualifications = preferred/additional. Both are substantive. Could keep both.
We must not include Schedule because no explicit schedule content. Benefits we have. Pay we have.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out lines like "Are you ready to shape your future with confidence? Apply today..." and the EEO statement at end, etc. Also remove "To make the most of your application experience..." etc. Also remove "EY | Building a better working world" etc. Also remove the final paragraphs about EY building a better working world, equal employment opportunities, accommodation info. Also remove "Under our flexible vacation policy..."? That's part of benefits, we keep that. But the flexible vacation policy is part of benefits; we can keep that as part of Benefits section.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the salary ranges exactly as given. Keep benefits details: medical and dental coverage, pension and 401(k) plans, wide range of paid time off options, flexible vacation policy, designated EY Paid Holidays, Winter/Summer breaks, Personal/Family Care, other leaves of absence.
We need to keep location: "Anywhere in Country". Could be placed in About the role paragraph.
We need to keep the intro paragraphs about EY, FSO, etc.
We need to keep the "Your Key Responsibilities" list.
We need to keep "Skills And Attributes For Success" list.
We need to keep "To qualify for the role you must have..." list.
We need to keep "Ideally, you’ll also have Experience with the following technologies and practices" list.
We need to keep "What We Look For" paragraph.
We need to keep "What We Offer You At EY..." paragraph plus benefits details.
We need to avoid duplication: there may be duplicated lines like repeated mention of Angular, React etc. We'll keep as is but ensure not to duplicate same bullet? Might be okay.
Now produce HTML.
Structure:
About the role
Location: Anywhere in Country. At EY, we’re all in to shape your future with confidence. We’ll help you succeed in a globally connected powerhouse of diverse teams and take your career wherever you want it to go. Join EY and help to build a better working world. EY is the only professional services firm with a separate business unit (“FSO”) that is dedicated to the financial services marketplace. Our FSO teams have been at the forefront of every event that has reshaped and redefined the financial services industry. If you have a passion for rallying together to solve the most complex challenges in the financial services industry, come join our dynamic FSO team! We help our clients transform. Together we are changing the way they interact with their Customers, Employees and Partners alike. We are modernizing their applications, creating new ones and driving business efficiency across their ever-changing platform and channel infrastructures. Everything we do centers around this simple story. The opportunity As an FSO Technology Service Delivery Manager, you’ll be based in our Service Delivery Center, which is made up of high-performing US-based colleagues who work closely with our experienced advisory professionals. We deliver Technology project-based work and managed services to our clients. Here, you’ll work as part of a project team and will be responsible for the design, build/configuration, testing, analysis, delivery and support of Technology solutions. This position is fast-paced and ever-changing, which means you’ll need to be a flexible self-starter and be able to manage changing priorities and learning new and rapidly changing technology solutions. We are looking for Frontend Engineers who will collaborate with clients to transform their business through disruptive innovation and transformational design solutions. The team supports clients in modernizing customer-facing systems, processes, and products to deliver intuitive, responsive, accessible, and high-performing digital experiences. The team leverages Angular, React, TypeScript, API integration, cloud technologies, and modern UI engineering practices to enable scalable end-to-end solutions.
That seems long but okay.
Then Responsibilities:
Responsibilities
- Help our clients solve business problems through frontend engineering solutions.
- Assist engagement teams with analyzing business and user experience requirements;
- Designing, developing, integrating, testing, deploying, and supporting responsive web applications;
- Delivering high-quality systems with a focus on usability, accessibility, reliability, performance, and excellent customer experience.
- Demonstrate in-depth technical capabilities and professional knowledge.
But the original had a paragraph then bullet list? Actually "Your Key Responsibilities The goal is to help our clients solve business problems through frontend engineering solutions. You will assist engagement teams with analyzing business and user experience requirements; designing, developing, integrating, testing, deploying, and supporting responsive web applications; and delivering high-quality systems with a focus on usability, accessibility, reliability, performance, and excellent customer experience. You will demonstrate in-depth technical capabilities and professional knowledge." That's a sentence with semicolons. We can convert to list items: maybe each clause as li. We'll keep as list.
Now Skills And Attributes For Success:
Skills And Attributes For Success
- Prior frontend software product development experience, with strong knowledge of modern UI engineering practices and a preferred understanding of DevOps tools and services.
- Strong experience leading frontend solution architecture and technical design, including micro frontend architectures, reusable component frameworks, design systems, and scalable UI engineering patterns.
- Deliver engineering solutions through all phases of the project lifecycle, including requirements definition, engineering design, development, integration, and testing; based on a proven agile methodology.
- Demonstrate hands-on technical capabilities in Angular, React, TypeScript, JavaScript, HTML5, CSS3, and responsive web development.
- Effectively work with client engagement teams with diverse skills and backgrounds fostering an innovative and inclusive work environment.
- Demonstrate understanding of current technology environment and industry trends and provide recommendations for engagement and client service issues.
- Willingness and ability to travel up to 30% of the time.
Now Requirements (mandatory qualifications):
Requirements
- Bachelor’s degree in Computer Science or other related field.
- A minimum of 6 years’ experience in technology software development.
- Strong frontend development experience using Angular, React, TypeScript, JavaScript, HTML5, CSS3, and modern responsive design practices.
- Hands-on experience designing and building reusable components, single-page applications, state management solutions, and accessible user interfaces.
- Experience leading frontend solution design, architecture decisions, and implementation of scalable enterprise applications.
- Experience integrating frontend applications with RESTful APIs and handling authentication, authorization, error handling, and asynchronous data flows.
- Experience with frontend architecture, micro frontends, performance optimization, browser compatibility, and secure coding practices.
- Experience with modern development practices including Git, npm or Yarn, code reviews, CI/CD pipelines, and automated testing frameworks.
- Experience mentoring developers, conducting technical reviews, and driving engineering best practices.
- Comfortable working in Agile delivery teams and collaborating closely with UX designers, backend engineers, product owners, QA professionals, and client stakeholders.
Now Qualifications (preferred):
Qualifications
- Experience with the following technologies and practices:
- Angular, React, TypeScript, JavaScript, HTML5, and CSS3
- State management using NgRx, Redux, Context API, or similar patterns
- Unit and component testing using Jest, Jasmine, Karma, or React Testing Library
- End-to-end test automation using Cypress or Playwright
- Responsive design, web accessibility, cross-browser compatibility, and performance optimization
- Node.js tooling, npm or Yarn, Webpack or Vite, cloud platforms, and micro frontend architecture
- Cloud technologies like AWS, or Azure
But we need to keep proper nesting: outer then - then inner
. That's fine.
Now Benefits:
Benefits
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into 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. We need to parse the posting: It's a job posting for FSO Technology Service Delivery Manager (Frontend Engineer). Contains location: Anywhere in Country (maybe remote). Contains description: At EY, we’re all in to shape your future with confidence... etc. Then "The opportunity As an FSO Technology Service Delivery Manager, you’ll be based in our Service Delivery Center..." Then "We are looking for Frontend Engineers who will collaborate..." Then "Your Key Responsibilities" bullet list. Then "Skills And Attributes For Success" bullet list. Then "To qualify for the role you must have..." bullet list. Then "Ideally, you’ll also have Experience with the following technologies and practices" bullet list. Then "What We Look For" prose. Then "What We Offer You At EY..." includes compensation and benefits package, base salary ranges, total rewards includes medical/dental, pension/401(k), paid time off, flexible vacation policy, etc. We need to decide sections: About the role (maybe intro), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Pay info (salary ranges). Benefits info (medical/dental, pension/401(k), paid time off, flexible vacation). Schedule? Not explicitly mentioned; maybe flexible vacation policy but not schedule. No explicit schedule like full-time, part-time, remote? It says location: Anywhere in Country (maybe remote). Could treat location as part of About the role? Not a schedule. So we may not include Schedule section because no explicit schedule content. Benefits we have. Pay we have. We need to avoid filler sections. So we will include sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe combine qualifications and skills?), but we have separate sections: Requirements (maybe "To qualify for the role you must have..."), Qualifications (maybe "Ideally, you’ll also have..."), Skills (maybe "Skills And Attributes For Success"). However we need to avoid thin sections; but we have substantive content for each. Could combine some but instructions: Prefer a few substantive sections over many thin ones. But we need to follow rule: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings if content exists. We have content for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. That's many sections but each is substantive. Could we merge Requirements and Qualifications? They are distinct: Requirements = mandatory qualifications; Qualifications = preferred/additional. Both are substantive. Could keep both.
We must not include Schedule because no explicit schedule content. Benefits we have. Pay we have.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out lines like "Are you ready to shape your future with confidence? Apply today..." and the EEO statement at end, etc. Also remove "To make the most of your application experience..." etc. Also remove "EY | Building a better working world" etc. Also remove the final paragraphs about EY building a better working world, equal employment opportunities, accommodation info. Also remove "Under our flexible vacation policy..."? That's part of benefits, we keep that. But the flexible vacation policy is part of benefits; we can keep that as part of Benefits section.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the salary ranges exactly as given. Keep benefits details: medical and dental coverage, pension and 401(k) plans, wide range of paid time off options, flexible vacation policy, designated EY Paid Holidays, Winter/Summer breaks, Personal/Family Care, other leaves of absence.
We need to keep location: "Anywhere in Country". Could be placed in About the role paragraph.
We need to keep the intro paragraphs about EY, FSO, etc.
We need to keep the "Your Key Responsibilities" list.
We need to keep "Skills And Attributes For Success" list.
We need to keep "To qualify for the role you must have..." list.
We need to keep "Ideally, you’ll also have Experience with the following technologies and practices" list.
We need to keep "What We Look For" paragraph.
We need to keep "What We Offer You At EY..." paragraph plus benefits details.
We need to avoid duplication: there may be duplicated lines like repeated mention of Angular, React etc. We'll keep as is but ensure not to duplicate same bullet? Might be okay.
Now produce HTML.
Structure:
About the role
Location: Anywhere in Country. At EY, we’re all in to shape your future with confidence. We’ll help you succeed in a globally connected powerhouse of diverse teams and take your career wherever you want it to go. Join EY and help to build a better working world. EY is the only professional services firm with a separate business unit (“FSO”) that is dedicated to the financial services marketplace. Our FSO teams have been at the forefront of every event that has reshaped and redefined the financial services industry. If you have a passion for rallying together to solve the most complex challenges in the financial services industry, come join our dynamic FSO team! We help our clients transform. Together we are changing the way they interact with their Customers, Employees and Partners alike. We are modernizing their applications, creating new ones and driving business efficiency across their ever-changing platform and channel infrastructures. Everything we do centers around this simple story. The opportunity As an FSO Technology Service Delivery Manager, you’ll be based in our Service Delivery Center, which is made up of high-performing US-based colleagues who work closely with our experienced advisory professionals. We deliver Technology project-based work and managed services to our clients. Here, you’ll work as part of a project team and will be responsible for the design, build/configuration, testing, analysis, delivery and support of Technology solutions. This position is fast-paced and ever-changing, which means you’ll need to be a flexible self-starter and be able to manage changing priorities and learning new and rapidly changing technology solutions. We are looking for Frontend Engineers who will collaborate with clients to transform their business through disruptive innovation and transformational design solutions. The team supports clients in modernizing customer-facing systems, processes, and products to deliver intuitive, responsive, accessible, and high-performing digital experiences. The team leverages Angular, React, TypeScript, API integration, cloud technologies, and modern UI engineering practices to enable scalable end-to-end solutions.
That seems long but okay. Then Responsibilities:Responsibilities
- Help our clients solve business problems through frontend engineering solutions.
- Assist engagement teams with analyzing business and user experience requirements;
- Designing, developing, integrating, testing, deploying, and supporting responsive web applications;
- Delivering high-quality systems with a focus on usability, accessibility, reliability, performance, and excellent customer experience.
- Demonstrate in-depth technical capabilities and professional knowledge.
Skills And Attributes For Success
- Prior frontend software product development experience, with strong knowledge of modern UI engineering practices and a preferred understanding of DevOps tools and services.
- Strong experience leading frontend solution architecture and technical design, including micro frontend architectures, reusable component frameworks, design systems, and scalable UI engineering patterns.
- Deliver engineering solutions through all phases of the project lifecycle, including requirements definition, engineering design, development, integration, and testing; based on a proven agile methodology.
- Demonstrate hands-on technical capabilities in Angular, React, TypeScript, JavaScript, HTML5, CSS3, and responsive web development.
- Effectively work with client engagement teams with diverse skills and backgrounds fostering an innovative and inclusive work environment.
- Demonstrate understanding of current technology environment and industry trends and provide recommendations for engagement and client service issues.
- Willingness and ability to travel up to 30% of the time.
Requirements
- Bachelor’s degree in Computer Science or other related field.
- A minimum of 6 years’ experience in technology software development.
- Strong frontend development experience using Angular, React, TypeScript, JavaScript, HTML5, CSS3, and modern responsive design practices.
- Hands-on experience designing and building reusable components, single-page applications, state management solutions, and accessible user interfaces.
- Experience leading frontend solution design, architecture decisions, and implementation of scalable enterprise applications.
- Experience integrating frontend applications with RESTful APIs and handling authentication, authorization, error handling, and asynchronous data flows.
- Experience with frontend architecture, micro frontends, performance optimization, browser compatibility, and secure coding practices.
- Experience with modern development practices including Git, npm or Yarn, code reviews, CI/CD pipelines, and automated testing frameworks.
- Experience mentoring developers, conducting technical reviews, and driving engineering best practices.
- Comfortable working in Agile delivery teams and collaborating closely with UX designers, backend engineers, product owners, QA professionals, and client stakeholders.
Qualifications
- Experience with the following technologies and practices:
- Angular, React, TypeScript, JavaScript, HTML5, and CSS3
- State management using NgRx, Redux, Context API, or similar patterns
- Unit and component testing using Jest, Jasmine, Karma, or React Testing Library
- End-to-end test automation using Cypress or Playwright
- Responsive design, web accessibility, cross-browser compatibility, and performance optimization
- Node.js tooling, npm or Yarn, Webpack or Vite, cloud platforms, and micro frontend architecture
- Cloud technologies like AWS, or Azure
- then
- then inner
- . That's fine.
Now Benefits:
Benefits