eCommerce Product Engineering Lead

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: There's a description paragraph about Princess, then "The Lead, Product Engineering for Salesforce Commerce Cloud (SFCC) teams serves as the primary technical expert..." That's about the role. So we can put that in About the role. Responsibilities: there is a list under "Responsibilities:" with bullet points (SFCC Architecture & Hands-on Development, Platform Integrations, Code Quality & Mentorship, Business & Release Collaboration, Administrative). So we need a

• for each. Knowledge & Skills: there is a section "Knowledge & Skills:" with subparts: Scope, Problem solving, Impact, Leadership, Knowledge, Skills, Abilities. This could map to Requirements, Qualifications, Skills sections. We need to decide which headings to use. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. We have "Essential/Minimum Qualifications:" with bullet list: Bachelor's degree, 5+ years, 3+ years dedicated SFCC, certification preferred, essential experience required (list). That's qualifications. We have "Knowledge & Skills:" which includes Knowledge, Skills, Abilities. Could be split into Requirements (maybe knowledge) and Skills. But we have separate headings for Requirements, Qualifications, Skills. We need to avoid duplication. Let's think: Requirements could be the knowledge and abilities needed (like expert knowledge, abilities). Qualifications could be education/experience/certifications. Skills could be technical skills (C#/.NET, Node.js, SFCC cartridge development, etc.). The posting lumps them together but we can separate. We need to preserve all substantive info, not invent. So we must extract each piece and place under appropriate heading. Let's parse: After "Knowledge & Skills:" we have: Scope: Technical leadership of the Salesforce Commerce Cloud development pod. Technical ownership of e-commerce storefront functionality, checkout pipelines, and third-party platform integrations. Problem solving: Resolves complex e-commerce engineering challenges around checkout concurrency, cartridge architecture, OCAPI/SCAPI customization, payment gateway security, and third-party API integration latency. Impact: Directly drives online guest bookings, revenue generation, promotional campaign execution, e-commerce stability, and digital checkout conversion rates. Leadership: Requires strong hands-on technical authority, developer mentorship, effective task breakdown/estimation, and collaborative technical guidance. For all roles: Knowledge: Expert knowledge of Salesforce Commerce Cloud B2C platform architecture (SFRA, OCAPI, SCAPI, Business Manager, Jobs, Pipelines, Custom Objects), e-commerce integrations, and frontend web technologies. Skills: Technical lead expertise in C#/.NET or Node.js integration, SFCC cartridge development, code review governance, API architecture, performance profiling. Abilities: Ability to lead technical delivery within Agile pods, translate business requirements into efficient SFCC architectures, guide junior/mid-level developers, and maintain high code quality. Then "Essential/Minimum Qualifications:" list. Thus we can map: - About the role: initial paragraph(s) describing role and company. - Responsibilities: the list under Responsibilities. - Requirements: maybe the Knowledge, Problem solving, Impact, Leadership? Or we could treat Requirements as the knowledge and abilities needed. But we also have Skills heading for technical skills. Qualifications for education/experience. Let's decide: Section "Requirements": could contain the Knowledge, Problem solving, Impact, Leadership (these are more like expectations/requirements). Or we could combine Knowledge and Abilities under Requirements, and Skills under Skills. Qualifications: Education, experience, certification. Skills: Technical lead expertise in C#/.NET or Node.js integration, SFCC cartridge development, code review governance, API architecture, performance profiling. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. We also have Travel, Work Conditions, Physical Demands, Hybrid schedule info. That could go under Schedule? The posting mentions Travel: Less than 25% with shoreside travel likely; Work Conditions: Work primarily in a climate-controlled environment... Physical Demands: Must be able to remain in a stationary position... This position is classified as “hybrid.” As an in-office role, it requires employees to work from a designated Princess location Mondays through Thursdays. Fridays you can work from home. Thus we have schedule info (hybrid, Mon-Thu in-office, Fri remote). Also travel info. Could put under Schedule section (maybe include travel). The instruction: include a section ONLY when posting has real, specific content for it. So we can create a Schedule section with that info. Benefits: The posting lists benefits under "Princess provides comprehensive and innovative benefits to meet your needs, including:" then a list: Cruise and Travel Privileges for You and Your Family, Health Benefits, 401(k) Employee Stock Purchase Plan, Training & Professional Development, Tuition & Professional Certification Reimbursement, Rewards & Incentives. So we can create Benefits section with those as
  • . Pay: No salary info given. So we should NOT create Pay section. Now we need to output HTML fragment only, no /. Use

    for each section heading. Use

    for prose. Use

    • for lists. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines. We need to preserve all substantive info. Let's extract. First, About the role: The initial paragraph(s) before Responsibilities. Text: "Job Description One of the best-known names in cruising, Princess is the world’s leading international premium cruise line and tour company, carrying millions of guests each year to hundreds of destinations around the globe. We give our guests the Medallion Class experience others simply can’t. The Love Boat promises something for everyone. The Lead, Product Engineering for Salesforce Commerce Cloud (SFCC) teams serves as the primary technical expert and lead developer for the e-commerce web platform. In this role, you will guide the design, customization, implementation, and integration of SFCC (B2C Commerce / SFRA / Headless), leading a pod of engineers to deliver optimized shopping, merchandising, catalog, and checkout experiences. Here’s a summary of what Princess is looking for in a Lead, Product Engineering for Salesforce Commerce. Is this you?" We can combine into a paragraph. Might be a bit long but okay. We should not include "Job Description" maybe as part of prose? It's okay. Now Responsibilities: list items: - SFCC Architecture & Hands-on Development: Lead the technical design, cartridge development, and implementation of SFCC solutions using SFRA, controllers, ISML/JavaScript, and headless APIs (OCAPI/Commerce API). - Platform Integrations: Architect and build robust integrations between SFCC and enterprise backend platforms, including GraphQL APIs, .NET microservices, payment gateways, tax engines, OMS, and CRM systems. - Code Quality & Mentorship: Perform rigorous code reviews, establish development standards, optimize page load speed and site performance, and mentor software developers within the e-commerce pod. - Business & Release Collaboration: Work closely with Product Owners, Merchandisers, and DevOps to configure Business Manager settings, customize promotional engines, support code deployments, and resolve technical blockers. - Administrative: Perform all other administrative and organizational duties as required (time keeping, training, travel, collaboration and correspondence, etc.) Now Requirements: we need to decide content. Let's take the "Knowledge & Skills" sections: Scope, Problem solving, Impact, Leadership, Knowledge, Abilities. Possibly also "For all roles:" but that's same. We could structure as a
      • each bullet summarizing each area. But we need to preserve specifics, not summarize away detail. So we should keep each point as a sentence. We could create a
        with items: - Scope: Technical leadership of the Salesforce Commerce Cloud development pod. Technical ownership of e-commerce storefront functionality, checkout pipelines, and third-party platform integrations. - Problem solving: Resolves complex e-commerce engineering challenges around checkout concurrency, cartridge architecture, OCAPI/SCAPI customization, payment gateway security, and third-party API integration latency. - Impact: Directly drives online guest bookings, revenue generation, promotional campaign execution, e-commerce stability, and digital checkout conversion rates. - Leadership: Requires strong hands-on technical authority, developer mentorship, effective task breakdown/estimation, and collaborative technical guidance. - Knowledge: Expert knowledge of Salesforce Commerce Cloud B2C platform architecture (SFRA, OCAPI, SCAPI, Business Manager, Jobs, Pipelines, Custom Objects), e-commerce integrations, and frontend web technologies. - Abilities: Ability to lead technical delivery within Agile pods, translate business requirements into efficient SFCC architectures, guide junior/mid-level developers, and maintain high code quality. That seems good. Now Skills: Technical lead expertise in C#/.NET or Node.js integration, SFCC cartridge development, code review governance, API architecture, performance profiling. We could put as a
        • each? It's a single sentence with multiple items separated by commas. Could break into list items for clarity but must preserve info. Could keep as a

          or

          . The instruction: Use
          • for any list of duties/requirements/benefits. This is a list of skills, so we should use
            • . We can split: - Technical lead expertise in C#/.NET or Node.js integration - SFCC cartridge development - Code review governance - API architecture - Performance profiling Now Qualifications: Essential/Minimum Qualifications list: - Bachelor's degree in Computer Science, Software Engineering, or equivalent experience. - 5+ years of full-stack web software engineering experience. - 3+ years of dedicated technical experience developing on Salesforce Commerce Cloud (B2C Commerce). - Salesforce Certified B2C Commerce Developer or Architect credential strongly preferred. - Essential experience required: - Hands-on expertise building enterprise e-commerce solutions on SFCC (SFRA / Composable Commerce). - Demonstrated track record integrating SFCC with external enterprise services (GraphQL, microservices, payment gateways). - Proven experience serving as a Senior/Lead developer guiding team code delivery and technical architecture. We could format as
              • each bullet, with sub-bullets for essential experience required maybe as nested list? But we can just list them as separate items, preserving the sub-bullets as separate items. Thus: - Bachelor's degree in Computer Science, Software Engineering, or equivalent experience. - 5+ years of full-stack web software engineering experience. - 3+ years of dedicated technical experience developing on Salesforce Commerce Cloud (B2C Commerce). - Salesforce Certified B2C Commerce Developer or Architect credential strongly preferred. - Hands-on expertise building enterprise e-commerce solutions on SFCC (SFRA / Composable Commerce). - Demonstrated track record integrating SFCC with external enterprise services (GraphQL, microservices, payment gateways). - Proven experience serving as a Senior/Lead developer guiding team code delivery and technical architecture. Now Benefits: list: - Cruise and Travel Privileges for You and Your Family - Health Benefits - 401(k) Employee Stock Purchase Plan - Training & Professional Development - Tuition & Professional Certification Reimbursement - Rewards & Incentives Now Schedule: includes Travel less than 25% with shoreside travel likely, Work Conditions, Physical Demands, Hybrid schedule (Mon-Thu in-office, Fri remote). We could combine into a

                or

                . Since it's multiple pieces, maybe a
                with items: - Travel: Less than 25% with shoreside travel likely. - Work Conditions: Work primarily in a climate-controlled environment with minimal safety/health hazard potential. - Physical Demands: Must be able to remain in