Sr. SAP Commerce Platform Engineer

Legrand North America has a remote opportunity for a Senior SAP Commerce Platform Engineer to join our Enterprise Digital Systems team. This is a deep platform engineering role (not a maintenance role). 

You will build and extend the SAP Commerce backend, integrate it with upstream enterprise systems through middleware, and own problems end to end — from the storefront request down through the service and persistence layers to the integration boundary. The platform serves multiple brands and storefronts and is evolving toward a composable, headless architecture, so your work at the core is consumed by every team that builds on top of it.

We are seeking engineer who can operate independently inside the platform: reason through the full stack, diagnose production issues by working directly through SAP Commerce and Dynatrace logs, and resolve them at the root.
 

At a Glance 

• Work inside a centralized SAP Commerce backend that powers multiple brand storefronts. Some storefronts are owned by the platform team; others are owned by business-unit teams who consume what you build. Decisions you make in the core propagate outward to all of them.
• Hands-on backend engineering: building and maintaining custom SAP Commerce extensions — type system, service layer, interceptors, cron jobs, ImpEx, integration logic — and on the integrations that connect commerce to upstream enterprise systems (ERP, PIM/Stibo, CRM) through middleware.
• Independent troubleshooting through SAP Commerce Cloud and Dynatrace is a daily expectation. You should be the person who can take an ambiguous production symptom and trace it through logs, traces, and code to a root cause without escalation.
• The platform is moving toward headless / composable (OCC APIs, headless content, search). Sound API and contract judgment matters and is valued — but it sits on top of, and depends on, real depth in the backend itself.
• This role reports into Platform Engineering and partners with the platform architect on design and estimate validation. You'll be expected to operate with independent technical direction and full ownership of outcomes in your domain.
   

Build and extend the SAP Commerce backend

• Design, build, and maintain custom SAP Commerce extensions — data models, service layer, facades, interceptors, cron jobs, and platform logic — following sound architecture for a multi-brand, multi-storefront environment.
• Work fluently across the SAP Commerce stack: type system and persistence, the Spring-based service layer, ImpEx, FlexibleSearch, and the build/deploy model on Commerce Cloud.
• Develop new platform capabilities against business requirements, and maintain and refactor the existing codebase, including the accelerator-based storefront that runs today.
   

Integrate with upstream systems

• Build and maintain integrations between SAP Commerce and upstream enterprise systems (ERP, PIM/Stibo, CRM) — through middleware where appropriate — using standard, resilient integration patterns.
• Reason clearly about data ownership and authority: which system is the source of truth under which conditions, and how the platform behaves when an upstream system is slow, stale, or unavailable.
• Where the architecture calls for it, design and build OCC / commerce APIs with consistent semantics and stable versioning so downstream storefronts can integrate without bespoke work.
   

Diagnose and resolve — independently

• Take ownership of production issues and drive them to permanent resolution: reproduce, isolate, root-cause, fix, and verify.
• Work directly through SAP Commerce Cloud logs and the Dynatrace observability stack — traces, service flow, log analysis, performance metrics — to diagnose issues across a multi-layered, integrated architecture. This is a core, daily skill, not an occasional one.
• Communicate root cause and impact clearly to the team and to stakeholders and follow through on action items to closure.

Raise the floor of the team

• Conduct PR reviews for domain correctness and architectural adherence — and use review as a mechanism to grow other developers, not just to gate merges.
• Produce documentation that is ahead of the team's needs. Knowledge, you hold must be transferable, not tribal — the platform should not stall when any one person is unavailable.
• Be present at the solutioning and design stage, catching design risks before they enter a sprint as defects.

Operate in delivery

• Participate in requirements and scope definition, providing credible estimates grounded in real platform constraints.
• Work in an Agile delivery model (Kanban / sprint-based) with disciplined feature flagging, fallback logic, error handling, and test coverage on all new code.
   

Required:

• Backend depth: strong, demonstrable SAP Commerce Cloud (Hybris) backend experience — typically 6+ years — with full, independent ownership of non-trivial extension and platform work. Evaluated on the scope you have owned.
• Extension development: you build extensions confidently across the type system, persistence layer, Spring service layer, interceptors, ImpEx, and FlexibleSearch, and apply sound design patterns and OOD principles in a layered architecture.
• Full-stack reasoning: you can reason through the full stack — from a storefront or API request, through the service and persistence layers, to the integration boundary — and locate a problem without being walked to it.
• Observability & troubleshooting: you are highly comfortable diagnosing issues directly through SAP Commerce Cloud logs and Dynatrace. Given an ambiguous production symptom, you can trace it to root cause independently.
• Integration: you have built and maintained integrations between SAP Commerce and upstream systems (ERP, PIM, CRM), including through middleware, and can reason about authority, resilience, and failure behavior across system boundaries.
• Independence: you own outcomes end to end can work idependently while making consistent progress. You communicate root cause and impact clearly to technical and non-technical audiences.

Preferred:

• Data & search: strong SQL and Solr; comfort with the data and search layers underneath commerce.
• Headless mindset: experience with, or clear ability to reason about, a headless / composable model where the storefront is decoupled from the backend (OCC consumed by Spartacus/Composable Storefront or a custom React frontend).
• Engineering leadership: a track record of making the engineers around you more capable through documentation, design input, and review.
  Familiarity with composable / MACH architecture, Contentful (or another headless CMS), Algolia, and Cloudinary.
• Bachelor's degree in computer science, software engineering, or a related field — or equivalent demonstrated experience.