Process Architect
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, legal, navigation, cookie, etc). Must not include sections with placeholder text like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes "Compensation and financial well-being – Competitive base salary, excellent bonus program, 401k, & Employee ownership program." That's compensation info, so we can include a Pay section? The instruction: "Prefer a few substantive sections over many thin ones." Also "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The posting does have compensation details: "Competitive base salary, excellent bonus program, 401k, & Employee ownership program." That's specific enough. So we can have a Pay section with that content. Benefits: The posting mentions "Our Investment in you: We believe that Benefits should connect you to the support you need when it matters most, and should help you care for those who matter most. That’s why we provide an array of options (including medical, dental, and vision insurance plans), expert guidance, and always-on tools, that are personalized to meet the needs of your reality – to help support you physically, financially, and emotionally through the big milestones and in your everyday life." Also later: "At Skanska, we Care for Life. And we’re committed to supporting your whole health and peace of mind through inclusive and personalized total rewards." So we have benefits content: medical, dental, vision insurance plans, expert guidance, always-on tools, inclusive total rewards. So we can have Benefits section. Schedule: Not mentioned. So no Schedule section. Qualifications: There's "Process Architect Required Qualifications:" with bullet list? Actually it's a paragraph: "5+ years of experience in construction operations, project delivery, process improvement, or operational workflow redesign.Working knowledge of AI, automation, agentic workflows or digital solution design sufficient to identify where technology can reshape a workflow and where human judgement remains essential.Demonstrated ability to translate complex, operational workflows into clear future-state designs, decision maps, or process architecture outputs. Bachelor’s degree in construction management, engineering or related field or 8 years equivalent experience plus minimum 5 years prior relevant experience. Currently the company is not offering sponsorship on this role." That's qualifications. Could also include "Skills"? Might be overlapping. We could have Requirements and Qualifications separate? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have About the role: The initial paragraph describing Skanska and the role: "Skanska is searching for a dynamic Process Architect. This is a great opportunity to start a career with a company that builds things that matter and values its team. We are proud to share our culture of diversity and inclusion. Our work makes a clear contribution to society and the environment around us. We build in many different verticals. Whether we are building schools to provide inspiring spaces for learning, roads to connect communities or hospitals to care for patients, it all contributes to our purpose – we build for a better society. Skanska's values —Be Better Together, Act Ethically and Transparently, Commit to Customer and Care for Life—are deeply engrained in how we work, which is why our values support and drive our D&I efforts. The Process Architect plays a key role in redesigning critical business workflows to support automation, AI, and agentic AI-enabled ways of working. This position is responsible for ensuring that business processes are thoughtfully evaluated, mapped, and improved before technology solutions are introduced, so that automation is applied in practical, scalable, and value-driven ways rather than layered onto inefficient or inconsistent workflows. The Process Architect will work closely with cross-functional stakeholders across the business to understand how work is actually performed, identify sources of friction in decision-making and information flow, and design future-state processes that improve consistency, efficiency, and business outcomes." That's about the role and responsibilities. Could split into About the role and Responsibilities. But we can combine? The instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role (includes overview) and Responsibilities (list of duties). However the responsibilities are described in prose; we could put them under Responsibilities as
. But we could also just have About the role covering both overview and responsibilities. However we have a separate "Process Architect Required Qualifications:" which is qualifications. So we can have Qualifications section. We also have Benefits and Pay sections. We should not include Skills unless there is explicit skills list. Not present. Thus sections: About the role, Responsibilities (maybe we can embed responsibilities in About the role to avoid thin section). But we have enough content for Responsibilities: the bullet-like duties: "ensuring that business processes are thoughtfully evaluated, mapped, and improved before technology solutions are introduced", "work closely with cross-functional stakeholders ... understand how work is actually performed, identify sources of friction ... design future-state processes". That's enough for a Responsibilities section. We could also have Requirements (maybe same as Qualifications). But we have Qualifications section with the list. Could also have Requirements (like experience, knowledge, ability). But to avoid thin sections, we could combine Requirements and Qualifications into one Qualifications section. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It's okay to omit some. Thus final HTML:
About the role
... (overview)
Responsibilities
- Ensure that business processes are thoughtfully evaluated, mapped, and improved before technology solutions are introduced, so that automation is applied in practical, scalable, and value‑driven ways rather than layered onto inefficient or inconsistent workflows.
- Work closely with cross‑functional stakeholders across the business to understand how work is actually performed, identify sources of friction in decision‑making and information flow, and design future‑state processes that improve consistency, efficiency, and business outcomes.
Qualifications
- 5+ years of experience in construction operations, project delivery, process improvement, or operational workflow redesign.
- Working knowledge of AI, automation, agentic workflows or digital solution design sufficient to identify where technology can reshape a workflow and where human judgement remains essential.
- Demonstrated ability to translate complex, operational workflows into clear future‑state designs, decision maps, or process architecture outputs.
- Bachelor’s degree in construction management, engineering or related field or 8 years equivalent experience plus minimum 5 years prior relevant experience.
- Currently the company is not offering sponsorship on this role.
Benefits
- Medical, dental, and vision insurance plans
- Expert guidance and always‑on tools personalized to support physical, financial, and emotional wellbeing
- Inclusive and personalized total rewards supporting whole health and peace of mind
Pay
Competitive base salary, excellent bonus program, 401(k), and employee ownership program.
We must ensure we didn't include any boilerplate like EEO, legal, etc. We removed those. Also we must not repeat job title as heading. We didn't. We didn't include Job ID. Good. Check that we preserved all substantive information: The overview about Skanska culture, values, purpose, D&I, role description. We captured that in About the role paragraph. Did we miss any specifics? The overview includes: "Skanska is searching for a dynamic Process Architect. This is a great opportunity to start a career with a company that builds things that matter and values its team. We are proud to share our culture of diversity and inclusion. Our work makes a clear contribution to society and the environment around us. We build in many different verticals. Whether we are building schools to provide inspiring spaces for learning, roads to connect communities or hospitals to care for patients, it all contributes to our purpose – we build for a better society. Skanska's values —Be Better Together, Act Ethically and Transparently, Commit to Customer and Care for Life—are deeply engrained in how we work, which is why our values support and drive our D&I efforts. The Process Architect plays a key role in redesigning critical business workflows to support automation, AI, and agentic AI-enabled ways of working. This position is responsible for ensuring that business processes are thoughtfully evaluated, mapped, and improved before technology solutions are introduced, so that automation is applied in practical, scalable, and value-driven ways rather than layered onto inefficient or inconsistent workflows. The Process Architect will work closely with cross-functional stakeholders across the business to understand how work is actually performed, identify sources of friction in decision-making and information flow, and design future-state processes that improve consistency, efficiency, and business outcomes." We placed the first part in About the role paragraph. We need to ensure we included all that. Let's craft About the role paragraph to include all that content. We'll write:Skanska is searching for a dynamic Process Architect. This is a great opportunity to start a career with a company that builds things that matter and values its team. We are proud to share our culture of diversity and inclusion. Our work makes a clear contribution to society and the environment around us. We build in many different verticals — whether we are building schools to provide inspiring spaces for learning, roads to connect communities, or hospitals to care for patients, it all contributes to our purpose – we build for a better society. Skanska's values — Be Better Together, Act Ethically and Transparently, Commit to Customer and Care for Life — are deeply engrained in how we work, which is why our values support and drive our D&I efforts. The Process Architect plays a key role in redesigning critical business workflows to support automation, AI, and agentic AI‑enabled ways of working. This position is responsible for ensuring that business processes are thoughtfully evaluated, mapped, and improved before technology solutions are introduced, so that automation is applied in practical, scalable, and value‑driven ways rather than layered onto inefficient or inconsistent workflows. The Process Architect will work closely with cross‑functional stakeholders across the business to understand how work is actually performed, identify sources of friction in decision‑making and information flow, and design future‑state processes that improve consistency, efficiency, and business outcomes.
That covers overview. Now Responsibilities: we could extract the two bullet points from that paragraph (the evaluating processes and working with stakeholders). However we already included those in the overview. To avoid duplication, we could keep overview as About the role and not duplicate responsibilities. But the instruction says preserve ALL substantive information; we can keep them in About the role and not have a separate Responsibilities section if it would be duplicate. However we have to decide: The overview already includes the responsibilities description. If we also create a Responsibilities section with same content, that would be duplication. Better to keep About the role covering both overview and responsibilities, and not have a separate Responsibilities section. But we need to decide if we need a Responsibilities section at all. The instruction: "Prefer a few substantive sections over many thin ones." So we can have About the role (includes overview and responsibilities) and Qualifications, Benefits, Pay. That's four sections. Thus we will not have a separate Responsibilities section. We'll keep About the role as above. Now Qualifications: we need to capture all qualifications: 5+ years experience, working knowledge of AI/automation/agentic workflows/digital solution design, demonstrated ability to translate complex operational workflows into clear future-state designs, decision maps, or process architecture outputs, Bachelor's degree in construction management, engineering or related field or 8 years equivalent experience plus