Composable Commerce Solution Architect

We need to output only HTML fragment, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. The posting includes Salary: $150,000 to $160,000 per Annum => Pay section. No explicit Benefits, Schedule. There's a lot of qualifications and responsibilities. We need to parse. Job description: It starts with "San Francisco, CA Apply for this job Job Description Salary: $150,000 to $160,000 per Annum Required Qualifications ..." Then a long list of qualifications. Then "Professional Skill Requirements" then bullet list of skills. Then "Tell us about you" then fields (email, name, mobile, country list) then "Application Instructions". We need to remove boilerplate: navigation, cookie, legal, EEO, etc. Also remove duplicated lines, application instructions. Also remove the "Tell us about you" fields? That seems like application instruction/form fields; likely considered boilerplate to remove. Also the long list of country codes is part of that form; remove. We need to preserve substantive information: role description, qualifications, responsibilities, professional skill requirements. The posting didn't have explicit "About the role" heading but we can infer a section. We can create sections: About the role (maybe a brief paragraph summarizing). Responsibilities (maybe from qualifications? Actually qualifications list includes responsibilities like architecting, leading platform selection, etc). Requirements (maybe the qualifications). Skills (professional skill requirements). Pay (salary). No Benefits or Schedule. We must not repeat job title as heading. No Job ID. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all the qualification bullet points as list items. Also the professional skill requirements as list items. We need to avoid filler like "commensurate with experience". Not present. We need to ensure we don't create empty sections. Let's extract content. First, after "Job Description Salary: $150,000 to $160,000 per Annum Required Qualifications". So we have salary line. Then list of qualifications (starting with "Minimum 12+ years in eCommerce technology, with 5+ years as a Solution Architect owning end-to-end commerce architecture." etc). It's a long paragraph with many sentences separated by periods. We need to turn each distinct duty/requirement into list items? The instruction: Use

  • for any list of duties/requirements/benefits. The posting currently is not formatted as list but as sentences. We could treat each sentence as a list item. But we need to preserve ALL substantive information; we can keep as paragraphs? The instruction says use
    • for any list of duties/requirements/benefits. If the content is not already a list, we could still format as list for clarity. Probably acceptable. We'll create sections:

      About the role

      maybe a short paragraph: The role is a Solution Architect focusing on eCommerce technology, requiring extensive experience. But we need to avoid inventing. Could we just not include About the role if no explicit content? The instruction: "Prefer a few substantive sections over many thin ones." We could combine About the role and Responsibilities into one? But we need headings only when posting has real specific content for it. The posting does not have an explicit "About the role" section, but we could infer from the description. However, to be safe, maybe we omit About the role and start with Responsibilities (or Requirements). But we need to follow the allowed headings list; we can use any of them if content exists. The posting includes qualifications and responsibilities; we could treat "Responsibilities" as the list of duties (architecting, leading platform selection, etc). And "Requirements" as the qualifications (minimum years, etc). However the qualifications list already includes many responsibilities. Might be overlapping. Better: Use "Requirements" for the bullet list of qualifications (minimum years, experience). Use "Responsibilities" for the professional skill requirements? Actually professional skill requirements are more like skills. Could be "Skills". Let's map: - Pay: salary. - Requirements: the list starting with "Minimum 12+ years..." etc. - Responsibilities: maybe the duties like "architected at least one from-scratch or full-replatform enterprise eCommerce implementation through to production", "Expert across commerce subsystems", etc. But those are also in the qualifications list. Hmm. Maybe we treat the long block as "Requirements" and the "Professional Skill Requirements" as "Skills". Then we don't need a separate Responsibilities section. That seems okay. Thus sections: Requirements, Skills, Pay. We need to ensure we include all substantive info from the qualifications block and the professional skill block. Let's extract qualifications block text exactly as given (starting after "Required Qualifications" up to before "Professional Skill Requirements"). The text: "Minimum 12+ years in eCommerce technology, with 5+ years as a Solution Architect owning end-to-end commerce architecture.5+ years architecting on composable/MACH platforms — hands-on depth in at least two of Salesforce Commerce Cloud, Commercetools, Shopify (Plus/Hydrogen/Functions), SCAYLE, VTEX, Spryer, Fabric or Elastic Path, including their real constraints, not just certifications.Recommended to have led at least one platform selection/assessment end to end — KPI-based scoring model, RFP, vendor deep-dives, and a recommendation presented to executive leadership.Must have architected at least one from-scratch or full-replatform enterprise eCommerce implementation through to production.Expert across commerce subsystems: Profile, Product/Catalog & PIM, Browse & Search, Cart/Order/Checkout, Pricing & Promotions, Payments, Inventory, Returns and Back Office.Strong foundation in enterprise Java Springboot microservices — enough to review the offshore team's designs and challenge an ISV's technical claims in a deep-dive.Event-driven and reactive architecture: event modelling, orchestration vs choreography, idempotency, and eventual consistency in order and inventory flows.PBC integration architecture across search & discovery (Constructor, Bloomreach, Algolia, Coveo), CMS (Contentstack, Contentful, Amplience), personalization/recommendations (Adobe Target, Dynamic Yield), loyalty, OMS and payment/fraud/tax providers.Ability to assess true modularity — swap-ability per domain, lock-in surface, event coverage, extension model and data export rights.Expert in one CSP (AWS/Azure/GCP) with in-depth knowledge of its services; strong on API gateways, serverless, containers and messaging (EventBridge/SQS/SNS/Kinesis/Kafka).Infrastructure-as-code with Terraform or equivalent (CloudFormation/ARM/Deployment Manager).SQL and NoSQL data architecture (MySQL, Oracle, Postgres, MongoDB, Cassandra, Cosmos, DynamoDB), plus product data modelling, catalog unification and search-index strategy.Strong API architecture: REST, GraphQL (incl. federation), JSON, OpenAPI/Swagger, versioning and contract governance.Headless storefront architecture — React/Next.js, edge rendering, BFF patterns, caching (Redis/Hazelcast/CDN), Core Web Vitals and SEO continuity through a phased migration.Observability and performance engineering with New Relic, Datadog or equivalent; NFR rigour across capacity, resilience, PCI-DSS, CCPA/GDPR and WCAG 2.1 AA.Must be able to build and defend a TCO model — licence/consumption cost, implementation and run cost, CAPEX/OPEX, and the cost of capability gaps.Experience defining phased, strangler-pattern roadmaps that absorb an incumbent platform slice by slice, with parity gates and no big-bang cutover.Good Retail domain knowledge; apparel/fashion preferred.Exposure to subscription or curated/stylist-led commerce models is a strong plus.Agentic commerce readiness — governed, machine-consumable access to catalog, inventory, pricing and order data — is an added advantage.Proficient in Agile methodologies and JIRA." Note there are some missing spaces after periods (like "architecture.5+ years"). We'll keep as is but maybe add space for readability? We must not invent or summarize away detail; we can keep the exact text. However, to make list items readable, we could split at each sentence. But we must preserve all info; splitting sentences does not lose info. It's okay. We'll create
      • each sentence. Similarly for Professional Skill Requirements block: "Proven ability to work creatively and analytically in a problem-solving environment, creating structure where the client has none.This is a client-facing onsite role — exceptional written and verbal communication skills, with the ability to communicate effectively with business partners, technology partners, peers and senior management.Executive presence —able to deliver an unwelcome finding without triggering defensiveness, and to hold a position under pressure from a vendor or an internal advocate.Workshop facilitation — able to run a room with competing agendas and leave with a decision.Exceptional written output — assessment charters, architecture blueprints, scoring narratives and board-ready readouts.Vendor/ISV management — runs RFPs firmly and fairly, extracts written commitments, and distinguishes roadmap promises from shipped capability.Able to lead and quality-gate an offshore pod across a significant timezone offset, personally reviewing every artefact before it reaches the client.Strong interpersonal skills and the ability to work with multiple stakeholders across engineering, product, merchandising and finance to drive success." Again missing spaces after periods. We'll keep. Now Pay: "Salary: $150,000 to $160,000 per Annum". We'll put in

        . We must not include boilerplate like "San Francisco, CA Apply for this job Job Description". Also remove "Tell us about you" and the country list and application instructions. Thus final HTML:

        Requirements

        • Minimum 12+ years in eCommerce technology, with 5+ years as a Solution Architect owning end-to-end commerce architecture.
        • 5+ years architecting on composable/MACH platforms — hands-on depth in at least two of Salesforce Commerce Cloud, Commercetools, Shopify (Plus/Hydrogen/Functions), SCAYLE, VTEX, Spryer, Fabric or Elastic Path, including their real constraints, not just certifications.
        • Recommended to have led at least one platform selection/assessment end to end — KPI-based scoring model, RFP, vendor deep-dives, and a recommendation presented to executive leadership.
        • Must have architected at least one from-scratch or full-replatform enterprise eCommerce implementation through to production.
        • Expert across commerce subsystems: Profile, Product/Catalog & PIM, Browse & Search, Cart/Order/Checkout, Pricing & Promotions, Payments, Inventory, Returns and Back Office.
        • Strong foundation in enterprise Java Springboot microservices — enough to review the offshore team's designs and challenge an ISV's technical claims in a deep-dive.
        • Event-driven and reactive architecture: event modelling, orchestration vs choreography, idempotency, and eventual consistency in order and inventory flows.
        • PBC integration architecture across search & discovery (Constructor, Bloomreach, Algolia, Coveo), CMS (Contentstack, Contentful, Amplience), personalization/recommendations (Adobe Target, Dynamic Yield), loyalty, OMS and payment/fraud/tax providers.
        • Ability to assess true modularity — swap-ability per domain, lock-in surface, event coverage, extension model and data export rights.
        • Expert in one CSP (AWS/Azure/GCP