Engineers across the org are experimenting with agentic workflows and seeing real results, but that work is informal, inconsistent, and unowned. The MCP integrations, shared skill registries, harness engineering, and agent-ready infrastructure that turn individual experimentation into org-wide acceleration are not built yet. That is the job.

As an engineer on the Platform Services team, you are not building features for customers. You are building the system that determines how fast and how well every other Stord engineer can move. Your customers are internal. Your metrics are org-wide. Your leverage is higher than almost any other engineering role at the company.

You will operate with a high degree of agency. There is no backlog to execute against. You will identify what needs to be built, make the calls, and own the outcomes. If that requires external scaffolding to feel productive, this is the wrong role. If that sounds like the only way you would want to work, keep reading.
You will work alongside our Principal Engineering Group, who will provide architectural direction and roadmap prioritization. Your job is to translate that direction into working software, establish ownership patterns for shared services, and ensure product teams can integrate with your services reliably and with minimal friction.

We are looking for engineers who are smart, adaptable, and comfortable with adversity. The shared services space at Stord involves ambiguity-services that need ownership, technical direction that needs to be established, and integration patterns that need to be defined. If you thrive when given a hard problem and the autonomy to solve it, and you learn new technologies quickly when the situation demands it, this role is built for you.

We care more about your engineering fundamentals, problem-solving ability, and ownership mentality than checking every box on a technology list.

Why This Role

• A genuinely hard, genuinely unsolved problem - agentic development across two product lines, multiple acquired codebases, and a complex domain is not a tutorial problem
• Real leverage - three engineers owning the system that multiplies the output of the entire engineering organisation is a different kind of impact than shipping features
• The right moment - the tools are good enough to build on, the patterns are emerging but not commoditised, and there is a narrow window to define this function rather than inherit it
• Ownership and visibility - direct visibility with engineering and product leadership, meaningful equity, and the kind of technical ownership most engineers do not encounter until much later in their careers
• AI investment is a company-level mandate - you will have organizational support and visibility

What You'll Work On
Product Unification

Contribute to the technical strategy for unifying Stord's product suite into a composable set of shared services. Identify where common capabilities are duplicated across product-specific implementations, drive their extraction into well-defined platform services, and ensure those services support multi-product integration cleanly - with particular attention to consolidation challenges from acquired products.

Cross-Team Enablement

Be the go-to technical resource for product teams integrating with platform services. Proactively identify friction in how teams consume shared infrastructure, close the feedback loop between platform decisions and product team outcomes, and collaborate with SRE on infrastructure concerns that affect shared service reliability.

Agent-Ready Infrastructure

Build the MCP integrations, shared skill libraries, and automated feedback loops - type systems, test harnesses, linters, pre-commit hooks - that allow agents to do reliable work without a human intervening at every step. The goal is a codebase where agents have the context, tools, and backpressure they need to operate autonomously on meaningful work.

Developer Experience as a Product

Internal engineers are your customers. Understand their friction deeply - through direct conversation, not inference - and ship tooling, golden paths, and scaffolding with the same rigour and iteration speed as customer-facing products. Every hour saved per engineer per week compounds across the org. You will measure it.

Agentic Workflows

Evaluate tools, design the patterns that embed them into everyday engineering practice, and push the ceiling of what is possible when agents have full access to a well-instrumented environment. You will know where agents fail and build the infrastructure changes that make them succeed.

Product Unification

Contribute to the technical strategy for unifying Stord's product suite into a composable set of shared services. Identify where common capabilities are duplicated across product-specific implementations, drive their extraction into well-defined platform services, and ensure those services support multi-product integration cleanly - with particular attention to consolidation challenges from acquired products.

Cross-Team Enablement

Be the go-to technical resource for product teams integrating with platform services. Proactively identify friction in how teams consume shared infrastructure, close the feedback loop between platform decisions and product team outcomes, and collaborate with SRE on infrastructure concerns that affect shared service reliability.

What We're Looking For
Required

• Platform depth - You have spent meaningful time at the infrastructure or platform layer and have strong opinions formed from that experience - about what makes a codebase maintainable, what makes agents fail, and what distinguishes a developer platform that gets adopted from one that gets worked around.
• Agentic development in practice, not theory - You are not exploring this space - you are working in it. You have run agents in production-adjacent workflows, hit the walls, and understand at a technical level what infrastructure changes move those walls. You have a CLAUDE.md or equivalent in at least one repo and a view on what belongs in it.
• Product manager instincts - You define problems before solutions. You ship, measure, and iterate rather than design indefinitely. You communicate clearly with non-technical stakeholders - not to translate, but because you understand that alignment is load-bearing infrastructure too.
• High agency - You thrive without a detailed brief. This team is being built from scratch. The shape of the work will evolve as you do it. The right person reads that as latitude, not ambiguity.
• CLI-native workflow - Claude Code, Cursor, Codex, or equivalent is your primary development environment. This is a hard requirement.

Required Soft Skills

• Ownership & Accountability - You own features end-to-end and take pride in what you ship. You follow through from design to production and don't drop things.
• Strong Communication - You can explain technical decisions and trade-offs to engineers, PMs, and stakeholders. You ask good questions and listen well.
• Collaborative Approach - You work well with others, give constructive code review feedback, and actively seek input from teammates.
• Production Mindset - You prioritize reliability and user impact. You think about failure modes, monitoring, and operational concerns as part of your design process.
• Learning Agility - You're comfortable with rapidly evolving AI/ML technologies and tools. You stay current without chasing hype.
• Directed AI-Assisted Development - You know how to use AI coding tools as a productivity multiplier while maintaining quality and your own technical judgment.

Nice to Have

• Domain context in logistics, supply chain, or operations software - accelerates good infrastructure decisions in ways that are hard to replicate quickly
• Familiarity with Stord's stack: Elixir/Phoenix, TypeScript, Kafka, GCP
• Experience building or significantly contributing to an internal developer platform
• Experience with workflow orchestration tools (Temporal, Prefect, Airflow, or similar)
• Open source contributions or active participation in agentic developer communities (Claude Code, Cursor, etc.)

What Success Looks Like

In your first 30 days, you have embedded with at least one internal team, mapped a workflow or codebase end-to-end, and shipped something - however small - into the hands of other engineers. By 90 days, you have measurably improved how the org operates: an agent workflow is running reliably in production-adjacent conditions, at least one golden path exists that did not before, and engineering leadership can point to numbers that moved. By six months, the platform you have built is the default infrastructure other engineers build on, and the team you helped stand up is operating with the kind of coherence and velocity that makes the next hire easier than the first.
About Stord

Stord is a cloud-based supply chain platform that enables brands to compete and grow through end-to-end logistics solutions. We process over $10B in commerce annually and operate across Order Management (OMS), Warehouse Management (WMS), Transportation Management (TMS), Consumer Experience, and Demand Planning. We are backed by leading investors and are rapidly scaling our engineering organization to match our ambitions.

Bonus

• Experience with authentication/authorization systems (OAuth, OIDC, RBAC/ABAC patterns)
• Experience with event-driven architectures and messaging systems at scale
• Familiarity with GCP services or Terraform (our SRE team owns this layer, but exposure helps)
• Experience in logistics, supply chain, or commerce domains
• History of working in high-growth environments with rapid organizational scaling
• Experience with M&A integration-consolidating acquired systems into a unified platform