Platform Engineer

About Us

We're an AI-first company, and that starts with our own work. We automate what we can and do old-school what we must, building the tools and knowledge that teams of humans and AIs need to run construction and infrastructure projects.

Our product consists of two halves: a customer-facing platform that runs both standard and bespoke project scheduling apps, supports large-scale datasets, complex integrations and large groups of users and runs an AI copilot; and an internal AI operating system that automates and supports our own work. It dials into meetings, analyses customers' screen-shares and shared datasets, builds implementation plans, orchestrates coding agents and validation systems - and pushes PRs.

We're a small team in London (8 people), growing fast, and looking for people who see a problem and run at it - figuring things out, and not stopping at “that's not my job.” Any new joiner can make a big difference. We raised our Seed round earlier this year at a ~$25m valuation, and are now aggressively scaling the business.

Our customers are large contractors, infrastructure builders and asset owners. They build railways, highways, airports, power plants, solar farms, steel mills and more. We work with them to improve the construction schedules for these assets.

The Role

The Platform Engineer builds and improves our platform. The platform covers anything that makes customer delivery fast & high-quality. This includes our internal AI operating system (the software that is stealing our own jobs), our customer-facing AI agent (“cursor for project management”), shared component library (large-scale optimisers, rendering pipeline for large datasets, …), deployment & hosting system (single-tenant VPCs for complex customers, different infra requirements for data sovereignty, …) etc.

We welcome earlier-career through senior engineers with strong work to show, clear conceptual understanding and a willingness to tackle diverse engineering challenges. You’ll work closely with our CTO and team; your initial scope and the guidance and review you receive will reflect your experience.

Platform engineers work mostly heads-down on the platform, while supporting the customer-facing team when something requires deeper platform-level changes. As a small team, our platform engineers are expected to participate in supporting the customers when needed.

Ownership at every level

We expect ownership at every experience level. You’ll take responsibility for getting your work to a useful outcome: understanding the problem, moving it forward, raising questions or blockers early, testing and releasing it, and checking the result. Asking for help at the right time is part of good judgment. The scope and complexity of what you own—and the support you receive—will reflect your experience.

How your scope can vary

These are examples of where you might start, with room to grow. We’ll agree your initial responsibilities with you during hiring, based on the skills and judgment you demonstrate.

• Earlier career: Own a clearly scoped improvement to tooling, infrastructure or a platform component, from understanding the problem to release and follow-up. Work with our CTO and team for guidance on design, technical decisions and review.
• Experienced: Independently define and deliver solutions to broader platform problems, diagnosing across system layers and following changes into operation.
• Senior: Own ambiguous platform problems with wider consequences, make architectural trade-offs, and improve how the team builds and operates systems.

What We Offer

• Salary ranging £100k to £160k — offers reflect demonstrated skills and judgment, the scope and complexity you can own, and the support you need. We’ll discuss salary, share options and responsibilities during the interview process.
• Share options ranging from 0.25% – 0.75% (4-year vest, 1-year cliff, fully diluted)
• Nice office in London with some flexibility on hybrid
• Skilled worker visa sponsorship if needed - we’re a very international team
• Highly entrepreneurial environment
• All the equipment, software and tokens you need to do the best job
• Unlimited headroom to grow

Problem Domains

• AI agents, algorithms, scheduling optimisers, and computational logic
• Infrastructure, deployment, scaling, and system architecture
• Product-facing shared components: minimising friction, designing reusable patterns
• Internal delivery operating system: the tooling Planlab uses to run its own engineering and delivery
• All our code is strongly typed (TypeScript, some Rust), which we deploy on various infra providers

What We're Looking For

At every experience level:

• Sound engineering fundamentals, evidence that you can build working software, and curiosity about how systems fit together
• Product-minded thinking: understand the intended outcome and care whether your work helps users or colleagues
• Ownership: move work forward, communicate clearly, raise blockers early, and follow through on testing, release and operation
• Judgment about trade-offs and when a decision needs discussion or review
• A methodical approach to debugging, a willingness to learn unfamiliar layers, and the ability to explain what you find
• Comfort working across different problem domains and using AI coding tools while taking responsibility for the result

Broader independent delivery, cross-layer diagnosis and architectural decisions come with the experienced and senior scopes above. We don’t expect an earlier-career hire to arrive with deep expertise in every domain we work in.

Ideal Backgrounds

Show us systems or software you’ve built, explain your own decisions and contribution, and tell us how you tested the result and dealt with problems. Professional work, substantial personal or university projects, and internships are all welcome. Earlier-career applicants still need evidence of engineering ability. For broader roles, we’ll look for experience shipping and operating systems under real-world constraints, including what you learned after release.

Your First 90 Days

We’ll agree an initial scope with you and review it as you learn the platform. In your first three months, we’d aim for these outcomes:

• Own a useful platform improvement. Take a problem through investigation, implementation, testing and release. An earlier-career hire might improve a defined part of our coding agent sandbox or deployment tooling with guidance and review; an experienced hire might independently define and deliver a change spanning several layers.
• Check it works in practice. Follow your change into operation, resolve issues, and give colleagues the documentation or checks they need to use and maintain it.
• Build on what you learn. Identify the next improvement with the team. At senior scope, also frame a wider platform problem, work through architectural trade-offs and improve the team’s approach to building or operating it.

Success at every level means useful work in operation and clear follow-through. The size and ambiguity of the problem—and the support needed to solve it—will differ.