Description du poste
Strong technical judgment: comfortable in architecture reviews, able to evaluate proposals critically, and able to spot when a technical decision is being made for the wrong reasons US work authorization required. Dispel requires comprehensive background checks for all employees A prior career as a software engineer with enough depth to understand what good engineering looks like. You do not need to write code in this role, but you need to have written it professionally and to have strong intuitions about quality, complexity, and technical risk Strong written communication. In a fully remote company, writing is your primary leadership surface: 1:1 notes, status updates, feedback, and engineering-wide contributions all need to be clear, specific, and worth reading Experience managing engineers on security-critical, reliability-critical, or infrastructure-adjacent software. The stakes are different when the thing you ship cannot go down 4 or more years managing software engineering teams of 5+ ICs in a product engineering environment Experience with multi-quarter planning: you have owned delivery commitments spanning multiple sprint cycles and know how to track them, communicate about them, and recover when plans diverge from reality Demonstrated track record of growing engineers’ careers. You can point to specific people you have leveled up, describe how you identified their gaps, and explain what you did to close them Comfortable using coding agents (e.g., GitHub Copilot, Claude Code) as part of your daily workflow. Addy Osmani’s article roughly describes Dispel’s stance on AI usage by engineers Demonstrated ability to operate remote-first. You have managed distributed teams and understand what remote management requires that in-person does not Experience at a company with a security-first product or customers in regulated industries (critical infrastructure, defense, industrial control systems, financial services, healthcare) Familiarity with compliance frameworks such as SOC 2, FedRAMP, or IEC 62443. Not as a practitioner, but as a manager who understands what compliance costs a team and how to resource it Exposure to Dispel’s core technology areas: cloud-native infrastructure on AWS or Azure, Terraform, backend services in Python, TypeScript, or Go, and React/TypeScript frontends Experience driving improvements to release infrastructure, CI/CD pipelines, or developer tooling. You got the build time cut in half or got automated testing enforced as a gate, and you know what that takes organizationally Familiarity with structured hiring and leveling practices: rubrics, evaluation frameworks, or calibration processes that make hiring and promotion decisions more consistent Prior experience working alongside a Technical Program Manager or equivalent. You understand how program management and engineering management divide responsibilities An ability to communicate clearly and succinctly both in-person and over team chat A passion for learning new disciplines and gaining a deep understanding of how others on the team do their work A willingness to accept failure and feedback, learn and try again
Dispel builds network isolation and access infrastructure for critical industries, where a breach is an operational failure with real-world consequences Our customers include critical infrastructure operators, defense contractors, and industrial enterprises that hold their software vendors to an exceptionally high bar. The Senior Engineering Manager is accountable for making that standard real This is a people-first, delivery-focused leadership role. You will manage 6–12 engineers across one or two teams, owning the full management lifecycle: hiring, onboarding, career development, performance management, and the hard conversations that come with it You will co-own how engineering works at Dispel, participating in decisions about org structure, engineering-wide practices, and multi-quarter delivery strategy. Technical judgment is non-negotiable. You will read pull requests, join architecture discussions, and flag technical risk. You must understand what your teams are building to fully enable them Engineering at Dispel is a collaborative effort and those that show up trying to get things done and help others will receive support from the team Dispel has high aspirations and we are growing quickly. We have noticed that people that have been in such environments before tend to adapt better. If you have not been in an environment like this before you would do well to try and convince us that you can handle it during your interviews Own delivery health across all active work: track project status, identify blockers early, remove obstacles, and escalate risks to the VP of Engineering with context and a proposed path forward Run effective team rituals (sprint planning, retrospectives, standups, reviews) calibrated to what your teams actually need, not a fixed process template Conduct regular, substantive 1:1s with every dire