Engineering Manager, Platform

About The Role We’re looking for a Platform Engineering Manager to lead our small but growing platform team. The platform team at Knock are responsible for building, scaling, and maintaining the core services and infrastructure that run Knock. This is the first engineering manager hire we’re making at Knock, and this person will report directly to Chris, our CTO. You will have a high degree of ownership and autonomy over the platform team’s roadmap, the people on it, and how we operate. We’re an engineer‑led team that obsesses over the reliability and availability of our service, and we’re looking for a leader who will help us raise that bar even further. What you’ll be doing in this role As an early stage company, everyone (including you) is involved in building every part of the company from the product and the infrastructure that it runs on, to how we get work done internally. Here are a collection of hats we need you to be OK with wearing: Hiring and building a high‑performing platform team over the next year, identifying engineers who can balance craft with pragmatism and growing the team from where it is today to 2–4 additional ICs. Owning the platform team’s roadmap and prioritization, making sure we’re aimed at the highest‑priority business problems and balancing platform investments (reliability, scalability, developer experience) against feature delivery. Coaching and developing the engineers on the team through regular 1‑on‑1s, stretch projects, and consequential decisions—rewarding outputs and impact, not inputs or theater. Contributing to architecture decisions and design reviews for our platform services and infrastructure, and writing code strategically to unblock critical paths and set standards through example. Leading and participating in incident response—debugging production issues, running post‑mortems, and driving reliability improvements off the back of them. Partnering with the product engineering team to manage cross‑team dependencies, establish support models, and define the SLAs and metrics that actually measure platform success. Helping shape Knock’s broader engineering culture, standards, and tooling choices alongside the CTO. This position is both high autonomy and high accountability: you will have a lot of room to set direction and raise our standards, while also bringing the rest of the team along for the ride and being accountable for the team’s outcomes and culture. What we’re looking for in this role 3+ years of experience as an engineering manager in a startup or mid‑sized company, leading a platform or infrastructure team that operates at scale. Strong technical foundations to own an inherently deeply technical area of our service. You should be capable of making strong technical contributions, even though you should seldom be spending time doing so. A track record of hiring, growing, and retaining excellent engineers, and of building team cultures where people do their best work. The judgment to delegate decision making and expertise to the team, and the instincts to know when to step in to move a decision along. Comfort owning prioritization without a dedicated Product Manager partner—able to say no to protect the team’s focus, but pragmatic enough to know when to drop things to get high‑priority work done. Experience leading on‑call rotations, incident response, and the operational maturity that comes with running a high‑availability service. Enough experience with fast‑growing, well‑structured engineering organizations to bring strong ideas in, without following any of them as dogma. Strong communication skills, with the ability to work in a fully distributed, remote‑first team. We love to write long‑form documents for us, our future selves, and our AI companions. A note on AI at Knock We’re a team that has fully embraced AI tools to help us in our day‑to‑day. We use these tools to accelerate us, but remain clear‑eyed about where they shine and where the pitfalls lie. We’re not overly prescriptive about the tools you can use, and we encourage experimentation as we embrace this new method of working. We have a collaborative culture of figuring out together what works and what doesn’t — sharing what we’ve learned, comparing notes, and iterating on our workflows as the tooling landscape evolves. We’re not overly prescriptive about the tools you can use in your day‑to‑day. As a member of the Knock team, we expect you to be familiar with tools like Cursor, Claude Code, Codex, or similar to assist you in your job. You’ll be allowed to use these tools in some parts of your interview loop, but there will be times where we’ll ask that you refrain. #J-18808-Ljbffr Knock