UI Architect
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Job Location, Description (lots of duties), Base compensation range, Benefits description. Also there is a "Role Summary" etc. We need to parse content.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, legal, disclaimer, etc. Also remove application instructions (none). Keep substantive info.
We need sections: maybe "About the role" (role summary), "Responsibilities" (duties), "Requirements" (skills/qualifications), "Qualifications" maybe overlapping, "Skills" (technical stack), "Benefits", "Pay". Schedule not present, so omit.
We must not create sections with filler like "commensurate with experience". Pay section: we have base compensation range 96366 to 150000. That's specific, so include Pay section.
Benefits: they describe benefits package. Include Benefits section.
Skills: list of technologies: Angular 21, TypeScript, JavaScript, HTML5, CSS3/SCSS, Angular Material, RxJS, REST APIs, plus good to have: Java 17, Spring Boot, cybersecurity domain experience, vulnerability management platforms, security analytics applications, enterprise dashboard design, risk management platforms, OCSF familiarity. Also mention UX/UI Architect responsibilities etc. So we can put Skills section.
Requirements/Qualifications: maybe combine. The posting includes role summary, duties, but not explicit qualifications like years experience, degree. Not given. So maybe we skip Requirements/Qualifications if no specific content. But we need to include sections only when posting has real specific content. There's no explicit qualifications like "Bachelor's degree" etc. So we could omit Requirements and Qualifications sections.
About the role: we have role summary paragraph. Could be "About the role". Use that.
Responsibilities: we have many duties listed. Use that.
Skills: list of tech.
Benefits: description.
Pay: compensation range.
We must not include headings with empty content. Use - for any list of duties/requirements/benefits. For prose use
.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from duties, responsibilities, skills, benefits, pay.
We must not repeat job title. No markdown.
Let's extract duties exactly as in posting. They are many sentences. We'll need to put them as list items? The instruction: Use
- for any list of duties/requirements/benefits. So we should convert duties into list items. Each duty sentence can be a
- . Ensure we keep all details.
Similarly for skills: list of technologies.
Benefits: they have a paragraph describing benefits; we could keep as prose
but also could list items: Paid time off based on employee grade (A-F), defined by policy: Vacation: 12-25 days, depending on grade, Company paid holidays, Personal Days, Sick Leave, Medical, dental, and vision coverage..., Retirement savings plans..., Life and disability insurance, Employee assistance programs, Other benefits as provided by local policy and eligibility. That's a list. Use
- .
Pay: we can put as
with the range.
About the role: we can put as
with role summary paragraph.
Now need to strip boilerplate: Remove EEO, legal, disclaimer, etc. Also remove "Important Notice: Compensation..." etc? That's part of compensation details but maybe considered boilerplate? It's about compensation but still substantive? It's more legal disclaimer. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Important Notice: Compensation (including bonuses...)" is legal disclaimer about compensation. Might be considered boilerplate. However we already have Pay section with range; the notice adds context but maybe considered legal. Safer to omit that notice. Also remove "Disclaimers" section about EEO etc. Remove "Important Notice" and "Disclaimers". Also remove "Click the following link..." etc.
Also remove "Job Location : New York City, NY" maybe we can include location in About the role? Not required but could be part of About the role. 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 in About the role paragraph. But we already have role summary; we could add location as a sentence. However we must preserve ALL substantive information; location is substantive. So we should include it somewhere. Could add a
for location separate? But we have no heading for location; we could fold into About the role
. Let's include location in About the role paragraph.
Now compile.
Let's extract role summary paragraph: "Choosing Capgemini means choosing a company where you will be empowered to shape your career in the way you’d like, where you’ll be supported and inspired by a collaborative community of colleagues around the world, and where you’ll be able to reimagine what’s possible. Join us and help the world’s leading organizations unlock the value of technology and build a more sustainable, more inclusive world." That's introductory. Then later: "Role Summary The UX/UI Architect is responsible for the end-to-end modernization of the VMAD Portal user experience.This role leads Discovery, drives alignment across UX Research, UX Design, Business Analysis, Data Engineering, Backend Engineering, and Front-End Engineering teams, and is accountable for the technical quality of all UI deliverables.The role establishes the patterns, specifications, and implementation standards used to accelerate delivery through AI-assisted development while ensuring consistency, maintainability, performance, and usability across the platform."
We can combine into About the role.
Now duties list: Let's extract each duty sentence from the block after "Duties & Responsibilities". We'll list them.
I'll copy the duties text:
"Lead the UX/UI modernization effort from Discovery through UAT and production readiness.
Collaborate with business stakeholders, UX Research, UX Design, Business Analysis, Data Engineering, Java Engineering, and Angular Engineering teams to understand current-state functionality and define modernization objectives.
Analyze legacy application architecture, user workflows, database relationships, APIs, integration patterns, and technical dependencies.
Drive alignment between Hero Journeys, business requirements, technical constraints, implementation patterns, and delivery objectives.
Define and maintain specification schemas including attributes, types, required/optional elements, defaults/constraints, inheritance/composition patterns used by developers to refine specification patterns into AI-ready inputs for Devin Desktop or equivalent approved tooling.
Establish specification patterns used for screens, workflows, APIs, integrations, security, environments, and shared platform capabilities.
Create initial implementation specifications based on approved Hero Journeys and modernization objectives.
Review and approve specification updates throughout delivery.
Define the Angular 21 application architecture, repository structure, component model, routing standards, API integration patterns, security patterns, and development standards used throughout the modernization effort.
Create foundational application scaffolding and reusable implementation patterns used by engineering teams.
Define environment requirements and architecture specifications for Development, QA, UAT, Pre-Production, and Production environments.
Establish standards for reusable components, shared services, application structure, and integration approaches.
Deliver the Single Pipeline Scaffold POC with Minimal Screen Display based on an approved Hero Journey and supported by mock data and mock services. Validate the modernization approach from Hero Journey through specification, implementation, API integration, and UI presentation.
Establish baseline implementation patterns used for subsequent screen and workflow modernization activities."
Now skills list: From description: "Angular architectureComponent architectureResponsive web applicationsInformation architectureApplication integration architectureDesign system implementationAngular 21TypeScriptJavaScriptHTML5CSS3 / SCSSAngular MaterialRxJSREST APIsGood to have skills:Familiarity with Java 17 and Spring Boot architecturesCybersecurity domain experienceVulnerability management platformsSecurity analytics applicationsEnterprise dashboard designRisk management platformsOCSF familiarity"
We need to split into items. Also note there is no spacing; we need to parse.
Let's list:
- Angular architecture
- Component architecture
- Responsive web applications
- Information architecture
- Application integration architecture
- Design system implementation
- Angular 21
- TypeScript
- JavaScript
- HTML5
- CSS3 / SCSS
- Angular Material
- RxJS
- REST APIs
- Good to have skills:
- Familiarity with Java 17 and Spring Boot architectures
- Cybersecurity domain experience
- Vulnerability management platforms
- Security analytics applications
- Enterprise dashboard design
- Risk management platforms
- OCSF familiarity
We'll treat "Good to have skills:" as a heading? Not needed; just include as list items maybe with note.
Now benefits list: From benefits paragraph:
"Paid time off based on employee grade (A-F), defined by policy: Vacation: 12-25 days, depending on grade, Company paid holidays, Personal Days, Sick Leave
Medical, dental, and vision coverage (or provincial healthcare coordination in Canada)
Retirement savings plans (e.g., 401(k) in the U.S., RRSP in Canada)
Life and disability insurance
Employee assistance programs
Other benefits as provided by local policy and eligibility"
We'll make each as
- .
Pay: "The base compensation range for this role in the posted location is 96366 to 150000". Also note that it's in USD presumably. We'll output as
The base compensation range for this role in New York City, NY is $96,366 to $150,000.
maybe keep original numbers but add commas for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Adding commas could be considered summarizing? It's still same numbers, just formatting. Might be okay but safer to keep exactly as posted: "96366 to 150000". However that is hard to read. Could we keep as "96,366 to 150,000"? That's adding commas, which is a minor formatting change not altering meaning. Might be considered okay. I'd keep original to be safe: "96366 to 150000". Also mention currency? Not specified. We'll keep as is.
Now About the role paragraph: combine the introductory and role summary plus location.
Let's craft:
Choosing Capgemini means choosing a company where you will be empowered to shape your career in the way you’d like, where you’ll be supported and inspired by a collaborative community of colleagues around the world, and where you’ll be able to reimagine what’s possible. Join us and help the world’s leading organizations unlock the value of technology and build a more sustainable, more inclusive world. Job Location: New York City, NY. Role Summary: The UX/UI Architect is responsible for the end-to-end modernization of the VMAD Portal user experience. This role leads Discovery, drives alignment across UX Research, UX Design, Business Analysis, Data Engineering, Backend Engineering, and Front-End Engineering teams, and is accountable for the technical quality of all UI deliverables. The role establishes the patterns, specifications, and implementation standards used to accelerate delivery through AI-assisted development while ensuring consistency, maintainability, performance, and usability across the platform.
Now Responsibilities: Responsibilities
- ...
Skills: Skills
- ...
Benefits: Benefits
- ...
Pay: Pay
The base compensation range for this role in the posted location is 96366 to
. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from duties, responsibilities, skills, benefits, pay. We must not repeat job title. No markdown. Let's extract duties exactly as in posting. They are many sentences. We'll need to put them as list items? The instruction: Use
- for any list of duties/requirements/benefits. So we should convert duties into list items. Each duty sentence can be a
- . Ensure we keep all details.
Similarly for skills: list of technologies.
Benefits: they have a paragraph describing benefits; we could keep as prose
but also could list items: Paid time off based on employee grade (A-F), defined by policy: Vacation: 12-25 days, depending on grade, Company paid holidays, Personal Days, Sick Leave, Medical, dental, and vision coverage..., Retirement savings plans..., Life and disability insurance, Employee assistance programs, Other benefits as provided by local policy and eligibility. That's a list. Use
- .
Pay: we can put as
with the range. About the role: we can put as
with role summary paragraph. Now need to strip boilerplate: Remove EEO, legal, disclaimer, etc. Also remove "Important Notice: Compensation..." etc? That's part of compensation details but maybe considered boilerplate? It's about compensation but still substantive? It's more legal disclaimer. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Important Notice: Compensation (including bonuses...)" is legal disclaimer about compensation. Might be considered boilerplate. However we already have Pay section with range; the notice adds context but maybe considered legal. Safer to omit that notice. Also remove "Disclaimers" section about EEO etc. Remove "Important Notice" and "Disclaimers". Also remove "Click the following link..." etc. Also remove "Job Location : New York City, NY" maybe we can include location in About the role? Not required but could be part of About the role. 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 in About the role paragraph. But we already have role summary; we could add location as a sentence. However we must preserve ALL substantive information; location is substantive. So we should include it somewhere. Could add a
for location separate? But we have no heading for location; we could fold into About the role
. Let's include location in About the role paragraph. Now compile. Let's extract role summary paragraph: "Choosing Capgemini means choosing a company where you will be empowered to shape your career in the way you’d like, where you’ll be supported and inspired by a collaborative community of colleagues around the world, and where you’ll be able to reimagine what’s possible. Join us and help the world’s leading organizations unlock the value of technology and build a more sustainable, more inclusive world." That's introductory. Then later: "Role Summary The UX/UI Architect is responsible for the end-to-end modernization of the VMAD Portal user experience.This role leads Discovery, drives alignment across UX Research, UX Design, Business Analysis, Data Engineering, Backend Engineering, and Front-End Engineering teams, and is accountable for the technical quality of all UI deliverables.The role establishes the patterns, specifications, and implementation standards used to accelerate delivery through AI-assisted development while ensuring consistency, maintainability, performance, and usability across the platform." We can combine into About the role. Now duties list: Let's extract each duty sentence from the block after "Duties & Responsibilities". We'll list them. I'll copy the duties text: "Lead the UX/UI modernization effort from Discovery through UAT and production readiness. Collaborate with business stakeholders, UX Research, UX Design, Business Analysis, Data Engineering, Java Engineering, and Angular Engineering teams to understand current-state functionality and define modernization objectives. Analyze legacy application architecture, user workflows, database relationships, APIs, integration patterns, and technical dependencies. Drive alignment between Hero Journeys, business requirements, technical constraints, implementation patterns, and delivery objectives. Define and maintain specification schemas including attributes, types, required/optional elements, defaults/constraints, inheritance/composition patterns used by developers to refine specification patterns into AI-ready inputs for Devin Desktop or equivalent approved tooling. Establish specification patterns used for screens, workflows, APIs, integrations, security, environments, and shared platform capabilities. Create initial implementation specifications based on approved Hero Journeys and modernization objectives. Review and approve specification updates throughout delivery. Define the Angular 21 application architecture, repository structure, component model, routing standards, API integration patterns, security patterns, and development standards used throughout the modernization effort. Create foundational application scaffolding and reusable implementation patterns used by engineering teams. Define environment requirements and architecture specifications for Development, QA, UAT, Pre-Production, and Production environments. Establish standards for reusable components, shared services, application structure, and integration approaches. Deliver the Single Pipeline Scaffold POC with Minimal Screen Display based on an approved Hero Journey and supported by mock data and mock services. Validate the modernization approach from Hero Journey through specification, implementation, API integration, and UI presentation. Establish baseline implementation patterns used for subsequent screen and workflow modernization activities." Now skills list: From description: "Angular architectureComponent architectureResponsive web applicationsInformation architectureApplication integration architectureDesign system implementationAngular 21TypeScriptJavaScriptHTML5CSS3 / SCSSAngular MaterialRxJSREST APIsGood to have skills:Familiarity with Java 17 and Spring Boot architecturesCybersecurity domain experienceVulnerability management platformsSecurity analytics applicationsEnterprise dashboard designRisk management platformsOCSF familiarity" We need to split into items. Also note there is no spacing; we need to parse. Let's list: - Angular architecture - Component architecture - Responsive web applications - Information architecture - Application integration architecture - Design system implementation - Angular 21 - TypeScript - JavaScript - HTML5 - CSS3 / SCSS - Angular Material - RxJS - REST APIs - Good to have skills: - Familiarity with Java 17 and Spring Boot architectures - Cybersecurity domain experience - Vulnerability management platforms - Security analytics applications - Enterprise dashboard design - Risk management platforms - OCSF familiarity We'll treat "Good to have skills:" as a heading? Not needed; just include as list items maybe with note. Now benefits list: From benefits paragraph: "Paid time off based on employee grade (A-F), defined by policy: Vacation: 12-25 days, depending on grade, Company paid holidays, Personal Days, Sick Leave Medical, dental, and vision coverage (or provincial healthcare coordination in Canada) Retirement savings plans (e.g., 401(k) in the U.S., RRSP in Canada) Life and disability insurance Employee assistance programs Other benefits as provided by local policy and eligibility" We'll make each as
- .
Pay: "The base compensation range for this role in the posted location is 96366 to 150000". Also note that it's in USD presumably. We'll output as
The base compensation range for this role in New York City, NY is $96,366 to $150,000.
maybe keep original numbers but add commas for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Adding commas could be considered summarizing? It's still same numbers, just formatting. Might be okay but safer to keep exactly as posted: "96366 to 150000". However that is hard to read. Could we keep as "96,366 to 150,000"? That's adding commas, which is a minor formatting change not altering meaning. Might be considered okay. I'd keep original to be safe: "96366 to 150000". Also mention currency? Not specified. We'll keep as is. Now About the role paragraph: combine the introductory and role summary plus location. Let's craft:Choosing Capgemini means choosing a company where you will be empowered to shape your career in the way you’d like, where you’ll be supported and inspired by a collaborative community of colleagues around the world, and where you’ll be able to reimagine what’s possible. Join us and help the world’s leading organizations unlock the value of technology and build a more sustainable, more inclusive world. Job Location: New York City, NY. Role Summary: The UX/UI Architect is responsible for the end-to-end modernization of the VMAD Portal user experience. This role leads Discovery, drives alignment across UX Research, UX Design, Business Analysis, Data Engineering, Backend Engineering, and Front-End Engineering teams, and is accountable for the technical quality of all UI deliverables. The role establishes the patterns, specifications, and implementation standards used to accelerate delivery through AI-assisted development while ensuring consistency, maintainability, performance, and usability across the platform.
Now Responsibilities:Responsibilities
- ...
Skills
- ...
Benefits
- ...
Pay
The base compensation range for this role in the posted location is 96366 to
- .
Pay: we can put as