[Hiring] Senior Engineer, Platform Services @Stord

Role Description

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.

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.
• 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 that allow agents to do reliable work without a human intervening at every step.
• Developer Experience as a Product: Internal engineers are your customers. Understand their friction deeply and ship tooling, golden paths, and scaffolding with the same rigor and iteration speed as customer-facing products.
• 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.

Qualifications

• Platform depth — You have spent meaningful time at the infrastructure or platform layer and have strong opinions formed from that experience.
• Agentic development in practice, not theory — You have run agents in production-adjacent workflows and understand at a technical level what infrastructure changes move those walls.
• Product manager instincts — You define problems before solutions and communicate clearly with non-technical stakeholders.
• High agency — You thrive without a detailed brief.
• CLI-native workflow — Claude Code, Cursor, Codex, or equivalent is your primary development environment.

Requirements

• Ownership & Accountability — You own features end-to-end and take pride in what you ship.
• Strong Communication — You can explain technical decisions and trade-offs to engineers, PMs, and stakeholders.
• Collaborative Approach — You work well with others and actively seek input from teammates.
• Production Mindset — You prioritize reliability and user impact.
• Learning Agility — You're comfortable with rapidly evolving AI/ML technologies and tools.
• Directed AI-Assisted Development — You know how to use AI coding tools as a productivity multiplier.

Nice to Have

• Domain context in logistics, supply chain, or operations software.
• 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.

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 into the hands of other engineers.
• By 90 days, you have measurably improved how the org operates.
• By six months, the platform you have built is the default infrastructure other engineers build on.