Lead Adobe Commerce Architect
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Content:
- Intro paragraph: "Deloitte's Customer practice helps organizations build deeper customer relationships and drive sustained growth through customer and commercial strategy, data and analytics, Generative AI, digital products, marketing, commerce, sales, and service. As a Lead Business Transformation Architect specializing in Adobe Commerce, you will help clients define scalable commerce architectures that connect business priorities, content, and enterprise technology. You will collaborate with strategy, design, and engineering professionals to modernize commerce experiences and deliver measurable value for clients and their customers. Recruiting for this role ends on December 18, 2026"
- Then "Work you'll do As an Adobe Commerce Architect on the Advertising, Marketing & Commerce team, you will be responsible for:" then list of responsibilities.
- Then "A successful candidate would possess these skills:" then list of skills.
- Then "The team Deloitte's Advertising, Marketing & Commerce team creates content and experiences that inspire action. ..."
- Then "Qualifications Required:" list.
- Then "Preferred:" list.
- Then "The wage range for this role takes into account..." includes pay range.
- Then mention discretionary annual incentive program.
- Then hashtags.
We need sections: About the role (intro), Responsibilities, Skills (maybe from "A successful candidate would possess these skills"), Qualifications (Required and Preferred), Benefits? Not explicit benefits besides maybe discretionary annual incentive program (could be considered benefit). Pay section: we have wage range. Schedule? Not mentioned. So we may not include Schedule.
We need to decide headings: About the role (intro paragraph). Responsibilities (the list after "Work you'll do..."). Skills (the list after "A successful candidate would possess these skills"). Qualifications (maybe combine Required and Preferred under Qualifications). Benefits (maybe mention discretionary annual incentive program). Pay (wage range). Possibly also "Team" description could be part of About the role or separate? Could be part of About the role.
We must not create sections with filler. Ensure each heading has substantive content.
We need to use - for any list of duties/requirements/benefits, and
for prose.
Thus:
About the role
Deloitte's Customer practice helps organizations build deeper customer relationships and drive sustained growth through customer and commercial strategy, data and analytics, Generative AI, digital products, marketing, commerce, sales, and service. As a Lead Business Transformation Architect specializing in Adobe Commerce, you will help clients define scalable commerce architectures that connect business priorities, content, and enterprise technology. You will collaborate with strategy, design, and engineering professionals to modernize commerce experiences and deliver measurable value for clients and their customers. Recruiting for this role ends on December 18, 2026.
The team Deloitte's Advertising, Marketing & Commerce team creates content and experiences that inspire action. We design and implement technology platforms for personalized marketing across all digital touchpoints, specializing in customer-centric B2B and B2C solutions. Our in-house agency engages customers throughout their journey, working on projects like AdTech, MarTech, campaign automation, CRM, and lead-to-loyalty orchestration. Join us to drive impactful customer interactions and business growth.
That seems fine.
Responsibilities
- Lead the architecture and delivery of Adobe Commerce (Magento) solutions, including catalog, pricing, promotions, checkout, order management, and extensibility patterns.
- Design, deploy, and support Adobe Commerce Cloud environments, including cloud configuration, build and deployment workflows, integrations, performance optimization, and operational troubleshooting.
- Build serverless extensions, integrations, and event-driven capabilities using Adobe App Builder and Adobe I/O Runtime; orchestrate Adobe Commerce GraphQL application programming interfaces (APIs) with external services through Adobe API Mesh.
- Guide PHP (Hypertext Preprocessor) and Magento development, including module development, dependency injection, service contracts, GraphQL, Representational State Transfer (REST) APIs, database interactions, and upgrade-safe customization practices.
- Apply microservices and API-led architecture principles by defining service boundaries, designing reusable APIs, and integrating Adobe Commerce with product information management, enterprise resource planning, order management, payment, tax, and fulfillment platforms.
- Define integration patterns between Adobe Experience Manager as a Cloud Service, Edge Delivery Services, and Adobe Commerce; translate business and functional requirements into solution architecture, integration specifications, and technical design decisions.
Skills
- Ability to work independently and collaborate as part of a team
- Effective written and verbal communication skills
- Meticulous attention to detail and quality of work product
- Ability to build and sustain professional relationships
- Ability to lead projects or workstreams
- Ability to manage and prioritize multiple tasks in a fast-paced and dynamic environment
- Strong interpersonal skills and professional demeanor
- Ability to meet deadlines
- Ability to mentor and provide clear guidance to others
- Ability to design headless front-end architecture utilizing Adobe Edge Delivery Services (EDS) to serve as a unified frontend on top of Adobe Commerce (ACCS)
Qualifications
We have Required and Preferred. Could split into two sub-sections? But we only have headings for Qualifications (maybe include both required and preferred as lists). Could do:
Qualifications
Required:
- 5+ years of experience designing Adobe Commerce (Magento) solution architectures, including catalog, pricing, promotions, checkout, order management, and extensibility patterns.
- Experience designing, deploying, and supporting Adobe Commerce Cloud environments, including cloud configuration, build and deployment workflows, integrations, performance optimization, and operational troubleshooting.
- Experience building serverless extensions, integrations, and event-driven capabilities using Adobe App Builder, Adobe I/O Runtime, Adobe API Mesh, and Adobe Commerce GraphQL application programming interfaces (APIs).
- Experience developing PHP (Hypertext Preprocessor) and Magento modules using dependency injection, service contracts, GraphQL, Representational State Transfer (REST) APIs, database interactions, and upgrade-safe customization practices.
- Experience applying microservices and API-led architecture principles to integrate Adobe Commerce with product information management, enterprise resource planning, order management, payment, tax, and fulfillment platforms.
- Ability to travel up to 50%, on average, based on the work you do and the clients and industries/sectors you serve.
- Limited immigration sponsorship may be available.
Preferred:
- Experience using Adobe Commerce Optimizer to improve storefront performance and scale high-volume product discovery and shopping experiences.
- Experience integrating Adobe Experience Manager as a Cloud Service and Edge Delivery Services with Adobe Commerce, including product and category content, storefront experiences, GraphQL/API consumption, and ownership boundaries between content and commerce platforms.
- Experience translating documented business and functional requirements into Adobe Commerce solution architecture, integration specifications, and technical design decisions.
But we need to follow rule: Use - for any list of duties/requirements/benefits, and
for prose. The required/preferred headings could be
with bold? That's okay. Or we could just have two lists under Qualifications without extra heading. The rule says use
for prose, not for headings. Using
Required:
is okay as prose.
Alternatively we could separate Required and Preferred as separate sections? But we only have Qualifications heading allowed; we could have two subheadings but not in allowed list. Better to keep as above.
Now Benefits: we have discretionary annual incentive program. Also maybe mention "Limited immigration sponsorship may be available" but that's more qualification/requirement. Benefits: discretionary annual incentive program. Also maybe mention other benefits not specified. We'll include Benefits section only if we have specific content. We have: "You may also be eligible to participate in a discretionary annual incentive program, subject to the rules governing the program, whereby an award, if any, depends on various factors, including, without limitation, individual and organizational performance." That's a benefit.
Thus:
Benefits
You may also be eligible to participate in a discretionary annual incentive program, subject to the rules governing the program, whereby an award, if any, depends on various factors, including, without limitation, individual and organizational performance.
Pay: we have wage range.
Pay
The wage range for this role is $134,500 - $265,100.
We could also include note about geographic differential etc. But we should preserve all substantive information. The posting includes: "The wage range for this role takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and other business and organizational needs. The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which the position may be filled. At Deloitte, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and circumstances of each case. A reasonable estimate of the current range is $134,500 - $265,100." We should preserve all that. So we need to include that prose.
Thus Pay section: The wage range for this role takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and other business and organizational needs. The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which the position may be filled. At Deloitte, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and circumstances of each case. A reasonable estimate of the current range is $134,500 - $265,100. You may also be eligible to participate in a discretionary annual incentive program, subject to the rules governing the program, whereby an award, if any, depends on various factors, including, without limitation, individual and organizational performance.
But we already put incentive program in Benefits. Could combine but better separate. However we might duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all details. If we split incentive program into Benefits, we still need to include it there. The Pay section can omit the incentive program sentence to avoid duplication. But we must preserve all info; duplication is okay as long as we don't lose info. It's okay to repeat? Probably better not to repeat but we can include in both sections; but it's not prohibited. However to avoid redundancy, we could put incentive program in Benefits only, and Pay section only about wage range details. That still preserves all info (incentive program appears in Benefits). So we need to ensure we didn't lose any other info: The Pay paragraph includes all details about wage range etc. Good.
Now Schedule: not present, so we omit.
Now ensure we didn't include boilerplate like EEO etc. Not present.
Now output only HTML fragment.
Check that we didn't include any markdown fences.
Let's craft final HTML.
We need to ensure proper nesting.
Let's produce:
for prose. Thus:
About the role
Deloitte's Customer practice helps organizations build deeper customer relationships and drive sustained growth through customer and commercial strategy, data and analytics, Generative AI, digital products, marketing, commerce, sales, and service. As a Lead Business Transformation Architect specializing in Adobe Commerce, you will help clients define scalable commerce architectures that connect business priorities, content, and enterprise technology. You will collaborate with strategy, design, and engineering professionals to modernize commerce experiences and deliver measurable value for clients and their customers. Recruiting for this role ends on December 18, 2026.
The team Deloitte's Advertising, Marketing & Commerce team creates content and experiences that inspire action. We design and implement technology platforms for personalized marketing across all digital touchpoints, specializing in customer-centric B2B and B2C solutions. Our in-house agency engages customers throughout their journey, working on projects like AdTech, MarTech, campaign automation, CRM, and lead-to-loyalty orchestration. Join us to drive impactful customer interactions and business growth.
That seems fine.Responsibilities
- Lead the architecture and delivery of Adobe Commerce (Magento) solutions, including catalog, pricing, promotions, checkout, order management, and extensibility patterns.
- Design, deploy, and support Adobe Commerce Cloud environments, including cloud configuration, build and deployment workflows, integrations, performance optimization, and operational troubleshooting.
- Build serverless extensions, integrations, and event-driven capabilities using Adobe App Builder and Adobe I/O Runtime; orchestrate Adobe Commerce GraphQL application programming interfaces (APIs) with external services through Adobe API Mesh.
- Guide PHP (Hypertext Preprocessor) and Magento development, including module development, dependency injection, service contracts, GraphQL, Representational State Transfer (REST) APIs, database interactions, and upgrade-safe customization practices.
- Apply microservices and API-led architecture principles by defining service boundaries, designing reusable APIs, and integrating Adobe Commerce with product information management, enterprise resource planning, order management, payment, tax, and fulfillment platforms.
- Define integration patterns between Adobe Experience Manager as a Cloud Service, Edge Delivery Services, and Adobe Commerce; translate business and functional requirements into solution architecture, integration specifications, and technical design decisions.
Skills
- Ability to work independently and collaborate as part of a team
- Effective written and verbal communication skills
- Meticulous attention to detail and quality of work product
- Ability to build and sustain professional relationships
- Ability to lead projects or workstreams
- Ability to manage and prioritize multiple tasks in a fast-paced and dynamic environment
- Strong interpersonal skills and professional demeanor
- Ability to meet deadlines
- Ability to mentor and provide clear guidance to others
- Ability to design headless front-end architecture utilizing Adobe Edge Delivery Services (EDS) to serve as a unified frontend on top of Adobe Commerce (ACCS)
Qualifications
We have Required and Preferred. Could split into two sub-sections? But we only have headings for Qualifications (maybe include both required and preferred as lists). Could do:Qualifications
Required:
- 5+ years of experience designing Adobe Commerce (Magento) solution architectures, including catalog, pricing, promotions, checkout, order management, and extensibility patterns.
- Experience designing, deploying, and supporting Adobe Commerce Cloud environments, including cloud configuration, build and deployment workflows, integrations, performance optimization, and operational troubleshooting.
- Experience building serverless extensions, integrations, and event-driven capabilities using Adobe App Builder, Adobe I/O Runtime, Adobe API Mesh, and Adobe Commerce GraphQL application programming interfaces (APIs).
- Experience developing PHP (Hypertext Preprocessor) and Magento modules using dependency injection, service contracts, GraphQL, Representational State Transfer (REST) APIs, database interactions, and upgrade-safe customization practices.
- Experience applying microservices and API-led architecture principles to integrate Adobe Commerce with product information management, enterprise resource planning, order management, payment, tax, and fulfillment platforms.
- Ability to travel up to 50%, on average, based on the work you do and the clients and industries/sectors you serve.
- Limited immigration sponsorship may be available.
Preferred:
- Experience using Adobe Commerce Optimizer to improve storefront performance and scale high-volume product discovery and shopping experiences.
- Experience integrating Adobe Experience Manager as a Cloud Service and Edge Delivery Services with Adobe Commerce, including product and category content, storefront experiences, GraphQL/API consumption, and ownership boundaries between content and commerce platforms.
- Experience translating documented business and functional requirements into Adobe Commerce solution architecture, integration specifications, and technical design decisions.
- for any list of duties/requirements/benefits, and
for prose. The required/preferred headings could be
with bold? That's okay. Or we could just have two lists under Qualifications without extra heading. The rule says use
for prose, not for headings. Using
Required:
is okay as prose. Alternatively we could separate Required and Preferred as separate sections? But we only have Qualifications heading allowed; we could have two subheadings but not in allowed list. Better to keep as above. Now Benefits: we have discretionary annual incentive program. Also maybe mention "Limited immigration sponsorship may be available" but that's more qualification/requirement. Benefits: discretionary annual incentive program. Also maybe mention other benefits not specified. We'll include Benefits section only if we have specific content. We have: "You may also be eligible to participate in a discretionary annual incentive program, subject to the rules governing the program, whereby an award, if any, depends on various factors, including, without limitation, individual and organizational performance." That's a benefit. Thus:Benefits
You may also be eligible to participate in a discretionary annual incentive program, subject to the rules governing the program, whereby an award, if any, depends on various factors, including, without limitation, individual and organizational performance.
Pay: we have wage range.Pay
The wage range for this role is $134,500 - $265,100.
We could also include note about geographic differential etc. But we should preserve all substantive information. The posting includes: "The wage range for this role takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and other business and organizational needs. The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which the position may be filled. At Deloitte, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and circumstances of each case. A reasonable estimate of the current range is $134,500 - $265,100." We should preserve all that. So we need to include that prose. Thus Pay section:The wage range for this role takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and other business and organizational needs. The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which the position may be filled. At Deloitte, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and circumstances of each case. A reasonable estimate of the current range is $134,500 - $265,100. You may also be eligible to participate in a discretionary annual incentive program, subject to the rules governing the program, whereby an award, if any, depends on various factors, including, without limitation, individual and organizational performance.
But we already put incentive program in Benefits. Could combine but better separate. However we might duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all details. If we split incentive program into Benefits, we still need to include it there. The Pay section can omit the incentive program sentence to avoid duplication. But we must preserve all info; duplication is okay as long as we don't lose info. It's okay to repeat? Probably better not to repeat but we can include in both sections; but it's not prohibited. However to avoid redundancy, we could put incentive program in Benefits only, and Pay section only about wage range details. That still preserves all info (incentive program appears in Benefits). So we need to ensure we didn't lose any other info: The Pay paragraph includes all details about wage range etc. Good. Now Schedule: not present, so we omit. Now ensure we didn't include boilerplate like EEO etc. Not present. Now output only HTML fragment. Check that we didn't include any markdown fences. Let's craft final HTML. We need to ensure proper nesting. Let's produce: