Software Engineering Manager; US - Remote
Los Angeles, Los Angeles County, California, 90079, USA
Listed on 2026-07-08
-
Software Development
Backend Developer, DevOps, Cloud Engineer - Software, Software Architect
Software Engineering Manager (US - Remote)
Remote
KnowBe4 empowers the modern workforce to make smarter security decisions every day. Trusted by more than 70,000 organizations worldwide, KnowBe4 is the pioneer of digital workforce security, securing both AI agents and humans. The KnowBe4 Platform provides attack simulation and training, collaboration security, and agent security powered by AIDA (Artificial Intelligence Defense Agents) and a proprietary Risk Score. The platform leverages 15‑years of behavioral data to combat advanced threats including social engineering, prompt injection, and shadow AI.
By securing humans and agents, KnowBe4 leads the industry in workforce trust and defense.
Remote positions open to the US only.
Role SummaryKnowBe4's Platform Services group builds the infrastructure that every product team depends on. As a Software Engineering Manager, you own the team that shapes that foundation. You'll lead at the intersection of identity, platform reliability, and building and growing the engineers who solve problems with direct impact on every engineer and every customer at Know Be
4.
The messaging and events platform your team owns underpins bespoke email delivery, event publish and subscribe (pub/sub, the pattern where services broadcast events and other services subscribe to the ones they care about), and outbound notification delivery across Microsoft Teams, Slack, Google Chat, and other channels for the entire KnowBe4 product suite. Decisions made here ripple across every engineering team at KnowBe4 and the inboxes and channels of a global customer base.
We need a manager who can think at that scale, communicate across organizational boundaries, and stay close enough to the technology to make sound calls without writing every line themselves.
- High‑throughput email delivery (legacy & new) services in Golang & Rust deployed as AWS ECS Tasks & Lambda functions: low‑latency send pipelines handling batching, deliverability, and bounce processing across multiple AWS regions
- Outbound channel integrations: connectors for Microsoft Teams, Slack, Google Chat, and webhook‑based delivery, including the rate limiting, retry, and per‑channel formatting logic each provider demands
- Event publish and subscribe infrastructure: DFS (Data Foundation Service) subscribers, backed by AWS Eventbridge, and the message routing layer that coordinates state changes across bounded contexts
- Delivery reliability and observability: idempotency, dead‑letter queues, retry and backoff strategy, and end‑to‑end delivery tracking so teams can see whether a message actually landed
- Cross‑team messaging SDKs: libraries in Rust, C#, and Python that let other engineering teams emit events and send notifications, where design quality and backward compatibility matter deeply
- IaC at scale: multi‑account, multi‑region Terraform provisioning and governing the messaging and events layer across development, staging, and production
- People leadership experience: you have managed engineers directly, run hiring loops, handled performance conversations, and grown people into larger roles
- Enough backend depth to lead credibly: working fluency in a typed, compiled language (Go, Rust, C#, or equivalent) and the judgment to evaluate designs, not necessarily to be the top coder on the team
- AWS messaging and compute stack: ECS, Lambda, Event Bridge, SQS, SNS, DynamoDB, SSM, and IAM at a level where you can reason about the systems your team designs
- Event‑driven architecture: pub/sub, fan‑out, eventual consistency, idempotency, dead‑letter handling, and delivery guarantees (at‑least‑once versus exactly‑once and the tradeoffs between them)
- Messaging and delivery domain literacy: you understand what it takes to actually get a message delivered, whether that is email reputation and bounce handling or the rate limits and retry semantics of a third‑party chat API
- Delivery management: roadmap planning, dependency management, and predictable shipping in a discovery‑heavy platform context
- Technical communication: design docs, RFCs, and architecture reviews, plus the ability to synthesize complexity into clear…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).