Senior Engineer, Platform Services

Role overview

A senior engineering position on a Platform Services team focused on building the internal infrastructure that multiplies the productivity of the entire engineering organization. Rather than shipping customer-facing features, this role creates the agentic development tooling, MCP integrations, skill registries, and shared services that other engineers depend on. The work is highly autonomous: there is no pre-existing backlog, and the engineer is expected to identify what needs to be built, make architectural calls, and own the outcome end-to-end.

Responsibilities

- Identify gaps in shared development infrastructure and design the systems needed to fill them, including agent-ready tooling, harness engineering, and skill registries. - Translate high-level architectural direction from principal engineering leadership into reliable, production-grade software. - Establish ownership patterns for shared services so product teams can integrate with minimal friction. - Build and standardize MCP integrations that turn informal experimentation into consistent, org-wide acceleration. - Operate with strong reliability instincts, designing for failure modes, monitoring, and operational concerns from the start. - Embed with internal product teams, map workflows end-to-end, and ship working improvements quickly.

Requirements

- Strong engineering fundamentals and demonstrated problem-solving ability over specific technology checklists. - Comfort working in ambiguous problem spaces where technical direction and ownership patterns still need to be defined. - High ownership mentality with the ability to operate independently and drive outcomes without external scaffolding. - A production mindset that treats reliability, observability, and user impact as first-class design concerns. - Learning agility with rapidly evolving AI and ML tooling, staying current without chasing hype. - Practical experience using AI-assisted development tools as a productivity multiplier while maintaining quality and independent judgment.

Nice to have

- Domain familiarity with logistics, supply chain, or operations software. - Experience with Elixir/Phoenix, TypeScript, Kafka, or GCP-based infrastructure. - Background building or significantly contributing to an internal developer platform. - Familiarity with orchestration tools such as Temporal, Prefect, or Airflow. - Open source contributions or active participation in agentic developer communities. - Experience with authentication and authorization systems, event-driven architectures, M&A integration, or working in high-growth environments undergoing rapid organizational scaling.