A senior engineer screens every candidate

Senior Python and ML engineer who has been building production software since 2008. Stack evolved from .NET to PHP/Symfony and now Python, including ML and LLM systems in production. Maintains open-source projects on PyPI and GitHub. Personally runs every senior technical interview, so you get a real engineer's hire/no-hire, not a recruiter's guess.

Senior Python engineer focused on machine learning and LLM systems. Has built and shipped data and ML pipelines in production, from feature work to model serving, and spent the last few years deep in retrieval, RAG and LLM applications. On the panel runs the Python and ML interviews: async and API design, data modelling, and whether a candidate can reason about evaluation, latency and cost rather than just call an API. Looks for engineers who understand why a system behaves the way it does, write tested code, and can explain the tradeoffs behind their choices under real time pressure.

Senior backend engineer specialising in Go and distributed systems. Has designed and operated high-throughput services, message-driven pipelines and the kind of concurrent code that only shows its flaws under load. On the panel runs the Go and systems interviews: concurrency, channels and backpressure, failure modes, idempotency and data consistency across services. Cares less about syntax trivia and more about whether a candidate can design something that stays correct when traffic spikes and a dependency goes down. Pushes on the hard parts, race conditions, retries and partial failure, and listens for first-hand experience rather than rehearsed answers.

Senior frontend engineer working in React and TypeScript. Has built and maintained large component systems, design-system work and performance-sensitive interfaces used by real users every day. On the panel runs the frontend interviews: component design and state, rendering performance, accessibility, and the practical TypeScript that keeps a growing codebase sane. Looks past framework buzzwords for engineers who understand the browser, reason about re-renders and bundle size, and write components other people can actually extend. Pairs live on a small problem to see how a candidate thinks, debugs and handles feedback, not just whether they memorised an API.

Senior DevOps and platform engineer working across Kubernetes and the major clouds. Has built CI/CD pipelines, infrastructure-as-code and the observability that tells you what broke at 3am. On the panel runs the DevOps and cloud interviews: container orchestration, networking and IAM, deployment strategies, and incident response. Probes whether a candidate can reason about blast radius, rollbacks and cost, and whether they have actually run things in production rather than only read about them. Values engineers who automate the boring parts, write infrastructure others can read, and stay calm when a system is on fire.

Senior mobile engineer with production experience across iOS, Android and React Native. Has shipped and maintained apps through real release cycles, store reviews, crashes, performance regressions and OS upgrades. On the panel runs the mobile interviews: app architecture, state and navigation, offline behaviour, memory and battery, and the platform-specific gotchas that bite teams later. Looks for engineers who think about the full lifecycle of an app, not just the happy path in a demo, and who can reason about native tradeoffs even when working cross-platform. Pairs on a focused problem to see how they structure code and handle edge cases.