FSO - Risk Consulting - Non-Financial Risk - Manager - Archer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, EEO, etc. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes salary range (Pay). Benefits: "Total Rewards package includes medical and dental coverage, pension and 401(k) plans, and a wide range of paid time off options." So Benefits section exists. Schedule: not mentioned. So we should not include Schedule section. Also maybe "Location" list is metadata; we can fold into a short p or drop. The location list is many cities; we could include as a short p: "Locations: New York, Atlanta, Baltimore, Boston, Charlotte, Chicago, Hartford, Hoboken, McLean, Metropark, Philadelphia, Providence, Raleigh". That's minor metadata; we can put in a p. Now we need sections: About the role (intro paragraph). Responsibilities (list). Requirements (maybe qualifications). Skills (maybe Skills And Attributes For Success). Qualifications (maybe "To qualify for the role, you must have..."). But we need to avoid duplication. The posting has sections: "Your Key Responsibilities", "Skills And Attributes For Success", "To qualify for the role, you must have", "Ideally, you’ll also have", "What We Look For", "What We Offer You". Also earlier paragraphs about EY etc. We need to map to headings: About the role (intro). Responsibilities (Your Key Responsibilities). Requirements (maybe combine qualifications and experience). Skills (Skills And Attributes For Success). Benefits (What We Offer You includes benefits). Pay (salary range). Possibly also "Qualifications" separate from Skills? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content distinct. But we must not create thin sections. Let's see content: - Requirements: maybe the "To qualify for the role, you must have" list includes Bachelor's degree, 4-6 years Archer implementation experience, etc. That's qualifications. - Qualifications: maybe also "Ideally, you’ll also have" list (additional preferred qualifications). Could be separate. - Skills: "Skills And Attributes For Success" list includes Application and Tool Analysis, Complex Problem-Solving, etc. Also later list of technical skills (Archer etc). Might be overlapping. We need to decide how to split without duplication. Perhaps combine all skill/requirement info under Skills, and Requirements for basic qualifications (degree, years). But we need to follow instruction: include a section only when posting has real specific content. So we can have: About the role: intro paragraphs (first few paragraphs up to "Your Key Responsibilities"). Responsibilities: bullet list from "Your Key Responsibilities". Requirements: bullet list from "To qualify for the role, you must have" (basic qualifications). Qualifications: bullet list from "Ideally, you’ll also have" (preferred qualifications). Skills: bullet list from "Skills And Attributes For Success" plus maybe the detailed technical skills list (Archer form and layout design etc). But that list is also part of qualifications? Actually the "To qualify for the role, you must have" includes a long list of technical skills after "Proficiency with Agile...". That seems like qualifications as well. Hmm. Let's parse the posting text: After "Skills And Attributes For Success To excel as a Manager in Solution Architecture, you will need a robust set of technical and business skills. Your success will be driven by your proficiency in: Application and Tool Analysis Complex Problem-Solving and Critical Thinking Building and Managing Relationships Communicating With Impact" Then "To qualify for the role, you must have A Bachelor’s degree required (4-year degree)Typically, no less than 4 - 6 years relevant experience of Archer implementation experience with IRM (GRC) implementations in a client consulting environmentExcellent communication skills, with the ability to communicate with impact A track record of Complex Problem-Solving, Critical Thinking, and Digital Fluency Leadership qualities, including Driving Outcomes, Emotional Agility, and Leading Teams Adaptability and Learning Agility, with experience in Managing Change and Negotiation and Influencing Proficiency with Agile project management and delivery methodologies.Demonstrated hands-on experience in technical consulting and client-facing roles requiredExpertise with Archer form and layout design configuration, development of field updates, advanced workflow, troubleshooting, complex calculations, different datafeeds, data imports, scheduled jobs, various notifications, data driven events, reports, dashboard, workspaces, Appearance, Access Control (Roles, Groups, Users), Record Permissions, deployment (package creation and installation), Platform upgrades, on-prem to SaaS migration.Certifications such as Archer Certified Administrator – Specialist, Archer Certified Administrator - ExpertIndustry Certifications, including SAFe Product Owner, SAFe Implementer, SAFe Agilist, and Scrum Master, are also preferred.Maintain all certifications and continual progression in developer learning plans.Excellent oral and written communication skills with the ability to present and articulately explain technical information.Ability to understand and interpret business needs and identify appropriate business and technical solutions to meet those needs.Demonstrated ability to influence and consult (providing options with pros, cons, and risks) around all critical technical decisions during project delivery.Prior experience with mentoring junior team members and managing end-to-end project quality and seamless delivery" Then "Ideally, you’ll also have Experience managing & delivering multiple projects at the same time.Experience providing business/operations/technical consulting to senior leaders of organizations.Experience with Evolv Compliance, RMIS, Archer InsightExperience with Archer Control panel, data publication, Web Services, REST API, Content API, MS SQL, report objects, broadhead, custom objects, HTML, JavaScript/jQuery, ASP .net.Experience with SDLC, Agile Scrum, SAFe, and Kanban methodologies.Excellent communication skills, team player, drives processes, and actively owns deliverables.Deep understanding of Archer Platform end-to-end delivery processes; advanced functional and technical knowledge of the Archer IRM/GRC best practices.Strong interest in cloud computing and related technologies, including SaaS, PaaS, and IaaS." Thus the "To qualify..." includes both basic qualifications and many technical skills. The "Ideally..." includes additional preferred experience. Thus we could treat: - Requirements: Bachelor's degree, 4-6 years Archer implementation experience, excellent communication skills, track record of problem solving, leadership qualities, adaptability, proficiency with Agile, hands-on technical consulting, Archer expertise (maybe that's too detailed). But that's a lot. - Qualifications: Certifications, maintain certifications, communication skills, ability to interpret business needs, influence, mentoring, etc. But that seems messy. Alternative: Combine all into Skills section, and have Requirements just for degree and years experience. But we risk losing detail. Given instruction: "Prefer a few substantive sections over many thin ones." So maybe we have About the role, Responsibilities, Requirements (combining qualifications and skills), Benefits, Pay. That's 5 sections. Avoid Qualifications and Skills separate. But the instruction list includes Qualifications and Skills as possible headings; we can omit if not needed. However we must preserve all substantive info. If we put everything under Requirements, we need to ensure it's not too thin? It will be substantive. Let's craft: About the role: intro paragraphs (first few paragraphs up to "Your Key Responsibilities"). Responsibilities: bullet list from "Your Key Responsibilities". Requirements: combine all qualification/skill details: degree, years experience, Archer expertise, certifications, technical skills, soft skills, etc. Benefits: bullet list from "What We Offer You": medical and dental coverage, pension and 401(k) plans, wide range of paid time off options. Pay: salary ranges as given. We should not include Schedule. We need to format:

About the role

then

...

. For lists:

• ...

. We must not repeat job title. Must not include Job ID etc. We must remove boilerplate: EEO, legal, application instructions, etc. Also remove navigation, cookie, etc. The posting includes a lot of fluff at end about EY building better working world, EEO, accommodation, etc. Remove those. Also remove duplicated lines. Now craft content. First, extract About the role: The paragraphs before "Your Key Responsibilities". Let's copy: "Location: New York, Atlanta, Baltimore, Boston, Charlotte, Chicago, Hartford, Hoboken, McLean, Metropark, Philadelphia, Providence, Raleigh 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”) 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 are passionate about rallying together to solve the most complex challenges in the financial services industry, join our dynamic FSO team! You’ll get to work on cutting-edge, disruptive technologies and assist with building and implementing new technology solutions and products to address challenges faced by the banking industry. The opportunity Our Risk Technology Consulting practice helps clients modernize systems, processes, and products to enhance business and customer-facing platforms and services to support high performance in a rapidly changing, competitive environment. The team leverages eGRC platforms, Microservices, Cloud, API Management, and open-source technologies to enable end-to-end automation with safe and sound architecture at optimum cost. As a Manager in Solution Architecture, you will play a pivotal role in bridging the gap between complex business problems and innovative technical solutions. You will be instrumental in understanding business requirements and defining the solution architecture that translates these requirements into effective, workable solutions. Your expertise will guide technical decisions to ensure they align with business outcomes, offering recommendations that propel the business forward." We need to keep location maybe as a short p: "Locations: New York, Atlanta, Baltimore, Boston, Charlotte, Chicago, Hartford, Hoboken, McLean, Metropark, Philadelphia, Providence, Raleigh". Could be included in About the role or separate minor metadata. We'll include as a p after the intro? Probably better to include as a short p within About the role? But we can put it as a separate p before the intro? The instruction: fold minor metadata into a short

or drop it. So we can add a p with locations. Thus About the role section will have a p for locations, then p for the descriptive text. Now Responsibilities: bullet list from "Your Key Responsibilities". The text: "Your Key Responsibilities In this role, you will focus on the effective management and delivery of technology solutions, ensuring quality and risk management. Your responsibilities will include: Leading project implementations and developing, investing, and maintaining thought leadership with deep subject matter expertise related to the Archer platform, product capabilities, and complementary technologies in a client-consulting environment, including Integrated Risk Management (Policy Management, Enterprise Management, Risk Management, Compliance Management, Audit Management, Regulatory Change Management), Third-party Risk Management (TPRM), Business Continuity Management (BCM), Environmental, Privacy Management, Vulnerability and SecOps Management, Social and Governance (ESG).Leading all technical aspects of offering development, project delivery, and solution delivery on the Archer platform.Be the Subject Matter Expert on the delivery of Archer GRC solutions.Ensuring technical deliverables are complete, consistent, high quality, on time, and deliver valued outcomes." We need to split into sensible bullet points. The original seems to have missing punctuation. We'll create bullets: - Lead project implementations and develop, invest, and maintain thought leadership with deep subject matter expertise related to