Automation/Flow Designer Specialist
Capgemini · Bristol County, MA · 1 mo ago
EngineeringFull-time
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, no summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions.
We need to parse the posting.
The posting text:
"Your role As an Automation / Flow Designer Specialist, you will be responsible for designing, developing, testing, and optimizing automations on the ServiceNow platform. This role is central to build operational processes into efficient, reusable automated workflows. You will focus on using Flow Designer and Integration Hub to build automations for incident enrichment, alert routing, request fulfilment, and automated remediation, directly contributing to our 'ZERO touch operations' goal. In this role you will play a key role in: Automation Development, Build Reusable WorkflowsCore Automation Build, Reusable ComponentsLifecycle Support andDocumentation Your profile Required Experience Experience with a strong, hands-on focus on ServiceNow automation.Expertise in ServiceNow Flow Designer, Integration-Hub, subflows, custom actions, and classic workflow automation.Proven ability to design and implement operational runbooks, enrichment actions, and onboarding accelerators.Experience with ServiceNow scripting (Business Rules, Script Includes, server-side scripts).Understanding of core ITSM processes (Incident, Problem, Change, Request, SLA).Experience in troubleshooting flow executions, integration failures, trigger logic, and data mapping issues.Experience as an L3 OSS Support Engineer or OSS Operations & Service Assurance Lead, with a deep understanding of operational challenges and automation opportunities. Preferred Certifications ServiceNow Micro-Certification – Flow Designer.ServiceNow Micro-Certification – Integration Hub.ServiceNow Certified Application Developer (CAD).Certified Implementation Specialist – IT Service Management (CIS-ITSM).ITIL 4 Foundation. If you're excited about this role but don’t meet every requirement, we still encourage you to apply, your unique experience could be just what we need. Make it real - what does it mean for you? Open access to digital learning platforms Active employee networks promoting diversity, equity and inclusion like OutFront, CapAbility or Women@Capgemini Capgemini Is Proud To Be a Disability Confident Employer (Level 2) Under The UK Government’s Disability Confident Scheme. As Part Of Our Commitment To Inclusive Recruitment, We Will Offer An Interview To All Candidates Who Declare they have a disability, and Meet the minimum essential criteria for the role. Please opt in during the application process. Capgemini. Make it real. Need to know All roles will require a level of security clearance; BPSS OR Security ClearanceOR Developed Vetting. You can bring your whole self to work. At Capgemini building an inclusivefuture is part of everyday life and will be part of your working reality. We havebuilt a representative and welcoming environment, for everyone. About Capgemini Capgemini is an AI-powered global business and technology transformation partner, delivering tangible business value. We imagine the future of organisations and make it real with AI, technology and people. With our strong heritage of nearly 60 years, we are a responsible and diverse group of over 420,000 team members in more than 50 countries. We deliver end-to-end services and solutions with our deep industry expertise and strong partner ecosystem, leveraging our capabilities across strategy, technology, design, engineering and business operations. The Group reported 2025 global revenues of €22.5 billion. Make it real | www.capgemini.com"
We need to extract sections:
- About the role: description of role responsibilities? The first paragraph describes role: designing, developing, testing, optimizing automations on ServiceNow platform, building operational processes into efficient reusable automated workflows, using Flow Designer and Integration Hub for incident enrichment, alert routing, request fulfilment, automated remediation, contributing to ZERO touch operations. Also "In this role you will play a key role in: Automation Development, Build Reusable WorkflowsCore Automation Build, Reusable ComponentsLifecycle Support andDocumentation". That seems like responsibilities.
Thus About the role could be a paragraph summarizing role.
- Responsibilities: maybe list of duties: designing, developing, testing, optimizing automations; using Flow Designer and Integration Hub; building automations for incident enrichment, alert routing, request fulfilment, automated remediation; contributing to ZERO touch ops; Automation Development; Build Reusable Workflows; Core Automation Build; Reusable Components; Lifecycle Support and Documentation.
We need to decide which sections to include. The instruction: Prefer a few substantive sections over many thin ones. So we could combine role description and responsibilities into one "About the role" section, and maybe "Requirements" for required experience, "Qualifications" for preferred certifications, "Skills" maybe not needed if covered. Benefits: we have "Open access to digital learning platforms Active employee networks promoting diversity, equity and inclusion like OutFront, CapAbility or Women@Capgemini Capgemini Is Proud To Be a Disability Confident Employer (Level 2) Under The UK Government’s Disability Confident Scheme. As Part Of Our Commitment To Inclusive Recruitment, We Will Offer An Interview To All Candidates Who Declare they have a disability, and Meet the minimum essential criteria for the role. Please opt in during the application process." Also "You can bring your whole self to work. At Capgemini building an inclusivefuture is part of everyday life and will be part of your working reality. We havebuilt a representative and welcoming environment, for everyone." Also "Need to know All roles will require a level of security clearance; BPSS OR Security ClearanceOR Developed Vetting." That could be considered a requirement? It's a requirement for security clearance. Could be part of Requirements.
Pay and Schedule: not mentioned. So we should NOT include Pay or Schedule sections.
Thus we will have sections: About the role, Responsibilities (maybe combine), Requirements, Qualifications, Benefits.
But we need to avoid duplication. Let's extract substantive content.
First, "Your role As an Automation / Flow Designer Specialist, you will be responsible for designing, developing, testing, and optimizing automations on the ServiceNow platform. This role is central to build operational processes into efficient, reusable automated workflows. You will focus on using Flow Designer and Integration Hub to build automations for incident enrichment, alert routing, request fulfilment, and automated remediation, directly contributing to our 'ZERO touch operations' goal. In this role you will play a key role in: Automation Development, Build Reusable WorkflowsCore Automation Build, Reusable ComponentsLifecycle Support andDocumentation"
We can turn that into a paragraph.
Then "Your profile Required Experience Experience with a strong, hands-on focus on ServiceNow automation.Expertise in ServiceNow Flow Designer, Integration-Hub, subflows, custom actions, and classic workflow automation.Proven ability to design and implement operational runbooks, enrichment actions, and onboarding accelerators.Experience with ServiceNow scripting (Business Rules, Script Includes, server-side scripts).Understanding of core ITSM processes (Incident, Problem, Change, Request, SLA).Experience in troubleshooting flow executions, integration failures, trigger logic, and data mapping issues.Experience as an L3 OSS Support Engineer or OSS Operations & Service Assurance Lead, with a deep understanding of operational challenges and automation opportunities."
That's required experience.
Then "Preferred Certifications ServiceNow Micro-Certification – Flow Designer.ServiceNow Micro-Certification – Integration Hub.ServiceNow Certified Application Developer (CAD).Certified Implementation Specialist – IT Service Management (CIS-ITSM).ITIL 4 Foundation."
That's qualifications.
Then benefits: "Open access to digital learning platforms Active employee networks promoting diversity, equity and inclusion like OutFront, CapAbility or Women@Capgemini Capgemini Is Proud To Be a Disability Confident Employer (Level 2) Under The UK Government’s Disability Confident Scheme. As Part Of Our Commitment To Inclusive Recruitment, We Will Offer An Interview To All Candidates Who Declare they have a disability, and Meet the minimum essential criteria for the role. Please opt in during the application process. Capgemini. Make it real. Need to know All roles will require a level of security clearance; BPSS OR Security ClearanceOR Developed Vetting. You can bring your whole self to work. At Capgemini building an inclusivefuture is part of everyday life and will be part of your working reality. We havebuilt a representative and welcoming environment, for everyone."
Also "About Capgemini ..." That's company description, maybe not needed as a section but could be part of About the role? Probably not needed. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the About Capgemini paragraph as part of maybe a section "About Capgemini"? But we only have allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About Capgemini". However we could incorporate that into Benefits or About the role? It's not exactly a benefit but company overview. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid adding other headings not in list? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples but likely they expect only those headings. Safer to stick to those headings. So we need to fit company info somewhere, maybe under Benefits? But it's not a benefit. Could be under About the role? Not really. Could be omitted? But we must preserve ALL substantive information. If we omit company description, we lose substantive info. However maybe the company description is considered boilerplate? It's not navigation/legal/EEO etc. It's substantive about the company. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company description is not those. So we should keep it.
We could create a section "About Capgemini" but not in allowed list. However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples but likely they expect only those headings. Safer to stick to those headings. So we need to fit company info somewhere, maybe under Benefits? But it's not a benefit. Could be under About the role? Not really. Could be omitted? But we must preserve ALL substantive information. If we omit company description, we lose substantive info. However maybe the company description is considered boilerplate? It's not navigation/legal/EEO etc. It's substantive about the company. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company description is not those. So we should keep it.
We could create a section "About Capgemini" but not in allowed list. However the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." implies those are examples, not an exhaustive list. So we can use other headings if needed, as long as they are . But to be safe, we could use "About Capgemini" as an . The instruction didn't forbid other headings, just gave examples. So we can include it.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, About Capgemini.
We need to avoid thin sections. Ensure each has substantive content.
Now we need to format as HTML fragment: use for each heading, then content: either
. But to be safe, we could use "About Capgemini" as an . The instruction didn't forbid other headings, just gave examples. So we can include it.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, About Capgemini.
We need to avoid thin sections. Ensure each has substantive content.
Now we need to format as HTML fragment: use for each heading, then content: either
for each heading, then content: either
for prose,
- for lists. We need to decide which content is list vs prose. Responsibilities: we have a list of duties: designing, developing, testing, optimizing automations; using Flow Designer and Integration Hub; building automations for incident enrichment, alert routing, request fulfilment, automated remediation; contributing to ZERO touch ops; Automation Development; Build Reusable Workflows; Core Automation Build; Reusable Components; Lifecycle Support and Documentation. Could be a list. Requirements: list of required experience items. Qualifications: list of preferred certifications. Benefits: list of benefits: open access to digital learning platforms; active employee networks promoting diversity, equity and inclusion like OutFront, CapAbility or Women@Capgemini; Capgemini is a Disability Confident Employer (Level 2) under UK Gov's Disability Confident Scheme; commitment to inclusive recruitment: interview offered to all candidates who declare disability and meet minimum essential criteria; you can bring your whole self to work; building an inclusive future is part of everyday life; representative and welcoming environment; security