Lead Platform Engineer

About Us FeedMe is building the operating system for restaurants. Our product teams work across point of sale, kitchen, ordering, inventory, payments, CRM, HR and reporting, with applications running in the cloud and on restaurant devices. We are looking for a Lead Platform Engineer to make those teams faster. This is a hands-on technical leadership role spanning two connected areas: the Kubernetes and delivery foundation on which our services run, and the shared platform engines used to build our products—including Flutter, K8s, Web foundation. You will treat the platform as an internal product. You will work closely with Product Leads to identify recurring capability gaps, turn them into simple and reusable platform capabilities, and drive adoption across product teams. You will also partner closely with SRE on reliability, observability, capacity and cloud-cost optimisation. The goal is not to centralise every engineering decision; it is to provide clear contracts, paved roads and self-service tools that let domain teams ship independently with less cognitive load. What You Will Own Platform Direction and Developer Productivity Own the technical vision, architecture and roadmap for FeedMe’s internal platform, balancing product-development speed, reliability, maintainability and cost. Meet regularly with Product Leads and engineers to identify repeated friction, missing capabilities and opportunities for shared solutions. Turn validated needs into opinionated but extensible platform APIs, SDKs, templates, tooling and golden paths. Drive adoption through excellent documentation, examples, migration support and direct collaboration—not mandates alone. Measure the platform as a product using outcomes such as lead time, deployment frequency, onboarding time, adoption, reliability, developer satisfaction and reduced toil. Kubernetes and Delivery Foundation Lead the evolution and optimisation of our Kubernetes ecosystem, including workload architecture, scheduling, autoscaling, resource management, networking, ingress, security, upgrades and lifecycle management. Improve our GitOps and continuous-delivery workflows so teams can provision, deploy, observe and roll back services safely through self-service paths. Partner with SRE to establish practical service standards for health checks, observability, SLOs, resilience, capacity planning and incident learnings. Use production evidence to improve performance and cloud efficiency, including workload rightsizing, utilisation, scaling behaviour and cost attribution. Keep infrastructure and platform changes reproducible through versioned configuration and Infrastructure as Code. Shared Product Platform Engines Provide technical stewardship for shared engines such as GooDB, FooDB, feature flags and Flutter foundations that support cloud services and offline-first restaurant devices. Design stable, well-documented contracts that work across FeedMe’s TypeScript, Dart/Flutter and Go ecosystem. Strengthen the path from domain entities to generated schemas, SDKs and runtime integrations while preserving backward compatibility for data already deployed to customer devices. Keep core logic independent of frameworks and infrastructure, with clear boundaries between entities, use cases and delivery mechanisms. Evaluate build-versus-buy decisions pragmatically and evolve shared capabilities without forcing unnecessary migrations on product teams. Technical Leadership and Collaboration Lead architecture and design reviews for cross-cutting platform changes, making trade-offs explicit and decisions easy to understand. Stay close to implementation: build critical components, prototypes and reference implementations, and help teams through difficult integrations and migrations. Coach platform and product engineers in systems thinking, clean architecture, domain boundaries, testing and operational ownership. Create clear ownership boundaries with Product and SRE, and lead ambiguous initiatives from discovery through adoption and measurable improvement. Raise engineering quality through reusable patterns, automation and sound judgement rather than adding process for its own sake. What Success Looks Like Product teams can start, deploy and operate services through reliable paved roads with less manual support. The most important platform capability gaps are visible, prioritised with Product Leads and addressed through a coherent roadmap. Flutter, Golang foundations have clear ownership, stable contracts, useful documentation and growing adoption. Kubernetes workloads become more reliable and cost-efficient, with improvements demonstrated through agreed operational and financial metrics. Platform and SRE work as complementary partners: Platform improves the developer-facing system and reusable runtime capabilities; SRE improves production reliability and operational health. What You Bring To The Table Strong experience leading platform engineering, infrastructure engineering, developer productivity or a comparable cross-cutting technical function. Deep, hands-on Kubernetes experience in production, including workload optimisation, autoscaling, networking, security, observability and cluster lifecycle. Strong software-engineering skills in Go or another systems/backend language, with the ability to design maintained products—not only scripts and configuration. Experience building shared libraries, SDKs, frameworks, internal developer platforms or self-service capabilities used by multiple engineering teams. Experience with GitOps, CI/CD, Infrastructure as Code and modern observability practices. Our environment includes Argo CD, GitHub Actions, Terraform, Prometheus and Grafana or equivalent tools. Sound knowledge of distributed systems, data consistency, API and schema evolution, compatibility and failure-mode design. Product judgement: you can discover the real developer problem, design the smallest useful abstraction and measure whether it creates