[Remote] Software Engineering Manager (US - Remote)

Note The job is a remote job and is open to candidates in USA. KnowBe4 empowers the modern workforce to make smarter security decisions every day. As a Software Engineering Manager, you will lead a team responsible for building the infrastructure that supports various product teams, focusing on messaging and events platforms that enhance communication across services and customers. Responsibilities 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, EventBridge, 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 proposals for both engineers and executives Lead a software team that develops software using the KnowBe4 Software Development Lifecycle and Agile Methodologies Recommend solutions to engineering problems Provide genuine recommendations as to the hiring, firing, promotion, and discipline of subordinate employees to which the Company gives significant weight Skills 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, EventBridge, 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 proposals for both engineers and executives Lead a software team that develops software using the KnowBe4 Software Development Lifecycle and Agile Methodologies Recommend solutions to engineering problems Provide genuine recommendations as to the hiring, firing, promotion, and discipline of subordinate employees to which the Company gives significant weight Prior individual contributor experience in messaging, eventing, or platform engineering before moving into management Go production experience comfort with the concurrency model and the kind of high-throughput service work this team does day to day Rust exposure enough familiarity with the async ecosystem (tokio, axum, reqwest, serde) to follow and guide technical discussion Email infrastructure AWS SES or third-party ESPs (such as SendGrid or Postmark), plus SMTP and the deliverability standards SPF, DKIM, and DMARC Third-party messaging integrations Slack API, Microsoft Graph and Teams, Google Chat API, and webhook delivery patterns AWS EventBridge and SNS or SQS at scale event bus design, schema management, and routing across bounded contexts C# and .NET (8+) or Python both show up in this layer for services and event-processing tooling Terraform at scale multi-account, multi-region IaC and CI deploy patterns Observability tooling structured logging, tracing, and delivery metrics for systems where 'did it actually arrive' is the core question Experience managing a platform or infrastructure team whose customers are other internal engineering teams Prior individual contributor experience in identity, auth, or platform engineering before moving into management Rust exposure enough familiarity with the async ecosystem to follow and guide technical discussion C# and .NET (8+) Lambda AOT compilation, ASP.NET Core, Native AOT targeting linux-arm64 Auth0 and Keycloak tenant and realm administration, SAML, OIDC, and OAuth app configuration Terraform at scale multi-account, multi-region IaC and CI deploy patterns GitLab CI/CD pipeline design and multi-environment deployment Security engineering concepts threat modeling, zero-trust principles, secrets management, and credential rotation Experience managing a platform or infrastructure team whose customers are other internal engineering teams Benefits Company-wide bonuses based on monthly sales targets Employee referral bonuses Adoption assistance Tuition reimbursement Certification reimbursement Certification completion bonuses Company Overview KnowBe4 is a security platform for security awareness training and simulated phishing attacks. It was founded in 2010, and is headquartered in Clearwater, Florida, USA, with a workforce of 1001-5000 employees. Its website is http//www.KnowBe4.com.

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...