SDC Senior Business Analyst, Banking Platforms---Charlotte

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, etc. Must not invent or summarize away detail. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Pay: base salary ranges for various locations. So we can include Pay section with that detail. Benefits: they mention comprehensive compensation and benefits package, medical and dental coverage, pension and 401(k) plans, wide range of paid time off options, flexible vacation policy, designated holidays, etc. So Benefits section can be included. Schedule: not mentioned explicitly; no schedule info. So we should not include Schedule heading. About the role: we have description of role, opportunity, etc. Could be under About the role. Responsibilities: list of responsibilities. Requirements: maybe combine qualifications and skills? The posting includes "To qualify for the role you must have ..." then list of qualifications. Also "Ideally, you’ll also have ..." then list of preferred. Also "What We Look For" includes personal attributes. Could treat Requirements as mandatory qualifications, Skills as preferred/technologies, Qualifications maybe overlapping. But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only if there is real specific content. We have content for About the role, Responsibilities, Requirements (mandatory), Skills (preferred/tech), Qualifications maybe could be same as Requirements? But we can treat Qualifications as education/degree requirement? The posting includes "Bachelor’s degree in business or other related field" as part of qualifications. Could put that under Qualifications. Requirements could be experience etc. But we need to avoid duplication. Let's parse: - About the role: description of EY, FSO, opportunity, etc. - Responsibilities: list after "Your Key Responsibilities:" bullet list. - Requirements: maybe the mandatory qualifications: Bachelor's degree, 3 years experience, back-end experience, front-end development, API experience, cloud native, collaborative tools, testing frameworks, Agile/TDD. - Qualifications: maybe the "Ideally, you’ll also have" list (preferred tech). Or could treat that as Skills. - Skills: maybe the "What We Look For" personal attributes: intellectually curious, self-starter, quick learner, strong background in computer science. But we need to avoid filler. Let's decide: Section About the role: include paragraph(s) describing EY, FSO, opportunity, role context. Section Responsibilities: ul list of responsibilities. Section Requirements: ul list of mandatory qualifications (degree, 3 years experience, back-end, front-end, API, cloud native, collaborative dev tools, testing frameworks, Agile/TDD). Section Skills: ul list of preferred technologies (Akka/Scala, Kafka/RabbitMQ, ElasticSearch, AngularJS/ReactJS, Hadoop/Spark/Flume, Mongo/Cassandra/Any NoSQL DB). Also maybe include "What We Look For" as personal traits but could be part of Skills? Might be better to put personal traits under Qualifications? However Qualifications heading maybe for education/degree? But we already used degree in Requirements. Could treat Qualifications as education (Bachelor's degree) but we already have that. Might be better to not have Qualifications section if content overlaps. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine some. Let's think: we have About the role, Responsibilities, Requirements (mandatory), Skills (preferred tech + personal attributes), Benefits, Pay. That's 6 sections. That seems reasonable. We must not include Schedule. No schedule info. We must not include filler like "commensurate with experience". Not present. We must output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

... paragraphs ...

Responsibilities

• ...
...

Requirements

• ...
...

Skills

• ...
...

Benefits

• ...
...

Pay

... salary ranges ...

We need to preserve all substantive information. Let's extract details. About the role: The posting includes: "Location: Charlotte, Dallas 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 Business Analyst, 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 Business Analysts who will collaborate with clients to transform their business through disruptive innovation enablement and transformational design solutions. The team supports our clients in modernizing systems, processes and products to enhance business and customer-facing platforms and services to support high performance in a rapidly changing and competitive environment. The team leverages Microservices, Cloud, Omni channel integration, API Management and open source technologies to enable end to end automation." We need to preserve all that. Remove location line? Location is metadata but not a heading; we can fold minor metadata into a short

or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Location is minor metadata; we could include a short p at start:

Location: Charlotte, Dallas

but maybe better to drop it as it's not substantive? It's location info, but maybe considered minor. However we should preserve ALL substantive information; location is substantive for job posting. But they said fold minor metadata into a short

or drop it. Location is minor metadata? Could be considered minor. I'd include a short p:

Location: Charlotte, Dallas

before About the role section. But the About the role section already includes location? Not exactly. We'll include a short p. Now Responsibilities list: after "Your Key Responsibilities:" we have sentences separated by periods. Let's extract each: - Collaborate with stakeholders to gather and document business requirements. - Analyze current business processes and identify opportunities for improvement. - Develop detailed functional specifications and use cases. - Facilitate workshops and meetings to elicit requirements and validate solutions. - Work closely with IT teams to ensure that business requirements are translated into technical specifications. - Conduct data analysis to support decision-making and strategic planning. - Monitor project progress and ensure alignment with business objectives. - Provide training and support to end-users on new systems and processes. - Prepare reports and presentations for stakeholders to communicate findings and recommendations. We'll put each as

. Requirements (mandatory): after "To qualify for the role you must have" list: - Bachelor’s degree in business or other related field - A minimum of 3 years of experience - Back-end experience using modern technologies like Java, Python, Node.js, REST, NoSQL, Microservices, Serverless, and Cloud technologies like AWS, or Azure - Front-end development with modern frameworks and practices like React, Angular, or Responsive web design - Experience in designing, building and consuming RESTful APIs - Hands-on experience building applications/platforms with cloud native/Microservices architecture. Includes experience with IaaS, PaaS, container deployment. - Experience with modern collaborative development tools (e.g. Git, CI/CD pipelines) - Experience working with testing frameworks and tools for unit and integration testing and knowledge of TDD or BDD software development techniques - Comfortable working in an Agile and TDD environment We'll put each as

. Note some are long sentences; keep as is. Skills (preferred): after "Ideally, you’ll also have" list: - Experience with the following technologies - Akka/Scala - Kafka/RabbitMQ - ElasticSearch - AngularJS/ReactJS - Hadoop/Spark/Flume - Mongo/Cassandra/Any NoSQL DB Also "What We Look For" includes personal attributes: intellectually curious, passion for finding new and innovative ways to make things better, self-starter, quick learner, strong background in computer science from both theoretical and practical points of view. Could include those as skills as well. We'll add them. Thus Skills ul items: - Experience with Akka/Scala - Experience with Kafka/RabbitMQ - Experience with ElasticSearch - Experience with AngularJS/ReactJS - Experience with Hadoop/Spark/Flume - Experience with Mongo/Cassandra/Any NoSQL DB - Intellectually curious with a passion for finding new and innovative ways to make things better - Self‑starter and quick learner - Strong background in computer science (theoretical and practical) We could also include "What We Look For" as separate bullet. Benefits: after "What We Offer You At EY, we harness our collective strength..." paragraph plus details: - Comprehensive compensation and benefits package where you’ll be rewarded based on your performance and recognized for the value you bring to the business. - Base salary range (but that's Pay, we will handle separately) - Total Rewards package includes medical and dental coverage, pension and 401(k) plans, and a wide range of paid time off options. - Under our flexible vacation policy, you’ll decide how much vacation time you need based on your own personal circumstances. - You’ll also be granted time off for designated EY Paid Holidays, Winter/Summer breaks, Personal/Family Care, and other leaves of absence when needed to support your physical, financial, and emotional well-being. We should keep the paragraph about professional growth etc. We'll put as

maybe then ul for specific benefits. Pay: The posting includes base salary range details: - New York City, Boston, and Washington DC Metro Areas, Washington State, and Southern California offices – $80,300 to $149,100 - Bay Area California offices – $83,700 to $155,300 - All other offices locations in the US, including Sacramento – $67,000 to $136,800 - Individual salaries within these ranges are determined through a wide variety of factors including but not limited to education, experience, knowledge, skills and geography. We'll put that as

maybe with

but it's not a list of items? Could be

with sentences. We'll keep as

. We must not include Schedule