Principal Software Engineer

Stord is The Consumer Experience Company, powering seamless checkout through delivery for today's leading brands. Stord is rapidly growing and is on track to double our revenue in the next 18 months. To meet and exceed this target, Stord is strategically scaling teams across the entire company, and seeking energetic experts to help us achieve our mission.

By combining comprehensive commerce-enablement technology with high-volume fulfillment services, Stord provides brands a platform to compete with retail giants. Stord manages over $10 billion of commerce annually through its fulfillment, warehousing, transportation, and operator-built software suite including OMS, Pre- and Post-Purchase, and WMS platforms. Stord is leveling the playing field for all brands to deliver the best consumer experience at scale.

With Stord, brands can increase cart conversion, improve unit economics, and drive sustained customer loyalty. Stord’s end-to-end commerce solutions combine best-in-class omnichannel fulfillment and shipping with leading technology to ensure fast shipping, reliable delivery promises, easy access to more channels, and improved margins on every order.

Hundreds of leading DTC and B2B companies like AG1, True Classic, Native, Seed Health, quip, goodr, Sundays for Dogs, and more trust Stord to deliver industry-leading consumer experiences on every order. Stord is headquartered in Atlanta with facilities across the United States, Canada, and Europe. Stord is backed by top-tier investors including Kleiner Perkins, Franklin Templeton, Founders Fund, Strike Capital, Baillie Gifford, and Salesforce Ventures.

You will partner directly with the Principal UI/UX Lead as a peer—they own the design specification, you own the technical implementation. Together, you will co-own the design system and component strategy that unifies the platform experience. You will work alongside the broader Principal Engineering Group, who cover backend and platform domains, contributing to organization-wide technical strategy.

• Own the frontend architectural vision across all product teams, covering React/TypeScript patterns, state management conventions, API integration approaches, and build/deploy tooling

• Establish and maintain frontend engineering standards through Technical Design Documents, design reviews, and direct collaboration with team leads

• Drive decisions on shared libraries, tooling, and patterns—ensuring teams converge rather than diverge

• Identify and resolve technical debt in frontend systems that slows product team velocity

• Partner with the Principal UI/UX Lead to co-own the design system strategy. You own the technical implementation; they own the design specification

• Build, maintain, and govern a shared component library that all product teams consume, ensuring consistency in look, feel, and behavior across the platform

• Define contribution models so team-level engineers can extend the design system without fragmenting it

• Ensure the component library supports multi-product scenarios cleanly, particularly as acquired products are consolidated

• Act as the go-to technical authority for frontend engineering decisions across the organization

• Provide architectural guidance and review across all teams shipping frontend code—not as a gatekeeper, but as a force multiplier

• Identify and drive resolution of systemic frontend issues: performance bottlenecks, accessibility gaps, testing strategy inconsistencies, and developer experience friction

• Build reference implementations that demonstrate how teams should adopt shared patterns and components

• Set the bar for frontend testing strategy (unit, integration, end-to-end) and ensure teams have the right frameworks and patterns to ship with confidence

• Drive improvements to frontend developer experience: build times, local development workflows, CI/CD pipelines, and debugging tooling

• Champion frontend performance, accessibility (WCAG compliance), and security best practices across the organization

• Contribute to developer experience initiatives where they intersect with frontend tooling adoption

• Report to the Head of Engineering alongside other Principal Engineers

• Operate as a member of the Principal Engineering Group, contributing to organization-wide technical strategy alongside backend and platform Principals

• Partner directly with the Principal UI/UX Lead (who reports outside of Engineering) as a peer on design system strategy and execution

• Coordinate with product team Engineering Managers and tech leads on frontend standards adoption and architectural alignment

• Participate in recurring architectural reviews and Technical Design Document reviews

• Operate with significant autonomy on implementation decisions within the architectural guardrails set by the Principal Group

• 8+ years of professional frontend engineering experience, with deep expertise in React and TypeScript

• Demonstrated experience operating at a Staff or Principal level with cross-team architectural influence—not just within a single product team

• Proven track record of building and maintaining shared design systems or component libraries consumed by multiple teams

• Strong opinions on frontend architecture (state management, API layers, rendering strategies, monorepo vs. multi-repo) backed by experience shipping at scale

• Experience defining and driving frontend standards across an engineering organization

• Deep understanding of frontend testing strategies and tooling (Jest, React Testing Library, Playwright/Cypress)

• Clear technical communication—ability to write effective design documents, present to engineering leadership, and facilitate cross-team technical discussions

• Ability to influence without authority—driving alignment through technical credibility and collaboration rather than org chart power

We are looking for an engineer who thinks in systems, not features. The frontend landscape at Stord involves real complexity—multiple product teams shipping UI across different domains, acquired products being consolidated, and a component ecosystem that needs intentional stewardship. If you see a fragmented frontend as a problem you’re eager to solve, and you can drive alignment through technical credibility and clear communication, this role is built for you.

We care more about your architectural judgment, ability to influence across teams, and track record of building shared systems than checking every box on a technology list.

• Experience in logistics, supply chain, or commerce domains

• Previous startup or high-growth environment experience with rapidly scaling frontend teams

• Experience with GraphQL, particularly in federated or stitched schema contexts

• Background in accessibility (WCAG 2.1+) at an organizational level

• Experience with AI-assisted development tools and workflows

• Familiarity with Elixir/Phoenix backends (our primary backend stack)

• History of M&A integration—consolidating acquired frontend experiences into a unified platform