Pi Shaped Platform Developer IRC

The Pi Shaped Software Engineer / Platform Developer builds and maintains the components of the central platform that all software engineering teams consume to accelerate delivery and reduce friction. We operate as a high-value technology consultancy, meaning our developers are versatile, “Pi-shaped” practitioners with deep roots in Software Engineering alongside a second deep leg in Platform/Dev Ops.

We are proudly building an AI-Native culture, leveraging modern AI tooling to flex across languages and supercharge delivery. Working directly with clients, the developer treats platform engineering as a product, ensures exceptional communication, and helps embedded delivery squads integrate platform assets into product teams.

Pi-shaped engineering fundamentals:
Strong software engineering background with a natural evolution into Dev Ops, Test, and Platform Engineering.

Modern language proficiency:
Solid experience in at least one modern language (Type Script, Python, or Java preferred). Language requirements can be flexed for AI power-users who use AI assistance to rapidly adapt to new stacks.

Hands-on experience with Claude Code (or equivalent agentic CLI tooling — Cursor, Codex CLI, Cline, Aider): writing skills, configuring MCP servers, and using AI tooling as part of daily development workflow.

Understanding of AI-native development practices: prompt-first workflows, AI pair programming, agent-assisted development, and the ability to speak confidently about AI value to clients.

Genuine interest in developer experience: designs documentation, examples, and defaults so consuming teams can self-serve rather than raise tickets.

Working knowledge of Git Lab CI or comparable (Git Hub Actions, Jenkins) — able to build and debug pipeline configurations.

Familiarity with infrastructure-as-code concepts (Terraform, Cloud Formation, or similar) and container technologies (Docker, Kubernetes basics).

Consultative mindset & spot-on communication: able to communicate effectively with client stakeholders, explain complex architecture simply, and identify commercial/value-add opportunities.

Good documentation skills: able to write clear guides, READMEs, and integration instructions for other engineers.

Collaborative working style: comfortable asking questions, pairing with senior engineers, and supporting client teams consuming your output.

Experience with developer portal tooling (Spotify Backstage, or similar) is a massive plus.

Exposure to platform-as-a-product practices — thinking of templates, APIs, and tooling as products with users, not just artefacts to publish.

Background in Dev Ops or site reliability (monitoring, alerting, incident response).

Experience with package management and publishing (npm, PyPI, internal registries).

Previous experience in a platform team, consultancy, or shared services engineering function.

Build and maintain CI/CD templates, pipeline components, and automation scripts that are made centrally available to engineering teams.

Implement Claude Code (or equivalent agentic CLI tooling) skills and MCP servers based on designs from senior team members — testing, documenting, and iterating based on squad feedback.

Support the golden path tooling: maintaining project templates, updating scaffolding tools, and ensuring templates stay current with evolving standards.

Keep platform assets centrally available: publishing new versions across the relevant channels (component repos, package registries, deployed agent services), running compatibility checks, updating documentation, and triaging integration issues reported by delivery squads.

Assist delivery squads and client teams with platform integration questions — helping them consume platform assets correctly and debugging issues at the platform boundary.

Act as a trusted consultant: engaging with client stakeholders to articulate technical value, support technical discoveries, and deliver consultative value-add.

Write and maintain documentation for all platform components, ensuring delivery squads can self-serve where possible.

Participate in design reviews and contribute to the architectural evolution of the platform.