Senior Manager, Infrastructure & Security

<h1><strong style="background-color: transparent; color: rgb(98, 57, 235);">Senior Manager, Infrastructure & Security</strong></h1><div><br></div><div><strong style="background-color: transparent; color: rgb(0, 0, 0);">Reports to:</strong><span style="background-color: transparent; color: rgb(0, 0, 0);"> Senior Director of Engineering, Platform & Infrastructure</span></div><h2><br></h2><h2><strong style="background-color: transparent; color: rgb(153, 0, 255);">What You'll do</strong></h2><div><br></div><h3><span style="background-color: transparent; color: rgb(153, 0, 255);">Lead Cloud Infrastructure & SRE</span></h3><div><br></div><ul><li class=""><span style="background-color: transparent;">Lead Cloud Infrastructure & SRE: AWS (ECS, EKS, networking, VPCs, IAM), databases (PostgreSQL, Kafka, DynamoDB), IaC standards, SLOs, error budgets, DR/BCP, and a sustainable on-call program</span></li><li class=""><span style="background-color: transparent;">Own CI/CD & Developer Experience: GitLab CI across ~150 repos: build speed, reliability, test signal, release safety, environments, and paved roads for new services</span></li><li class=""><span style="background-color: transparent;">Drive Observability & Cloud Cost: high signal logging/metrics/tracing/alerting stack, SLO instrumentation, cloud cost attribution by team/service, FinOps practice</span></li><li class=""><span style="background-color: transparent;">Lead Application & Cloud Security end-to-end: secure SDLC, SAST/DAST/SCA, vuln triage and SLAs, secrets hygiene, IAM, CSPM</span></li><li class=""><span style="background-color: transparent;">Partner with IT to support compliance program, customer security questionnaires, and pen-test remediation</span></li><li class=""><span style="background-color: transparent;">Own Vendor & Tooling Portfolio: build-vs-buy decisions, vendor selection, POCs and lifecycle across observability, CI/CD, security, and incident management</span></li></ul><div><br></div><h2><strong style="background-color: transparent; color: rgb(153, 0, 255);">Grow and Develop the Team</strong></h2><ul><li class=""><span style="background-color: transparent;">Hire, onboard, and mentor engineers. Actively participate in recruiting; interview candidates, provide calibrated feedback, and raise the bar.</span></li><li class=""><span style="background-color: transparent;">Conduct regular 1:1s, provide actionable feedback, and support career development for each team member.</span></li><li class=""><span style="background-color: transparent;">Build a culture of urgency, ownership, customer empathy, and continuous improvement.</span></li></ul><div><br></div><h2><strong style="background-color: transparent; color: rgb(153, 0, 255);">What We're Looking For</strong></h2><h3><br></h3><ul><li class=""><strong style="background-color: transparent;">7+ years of infrastructure or SRE engineering experience</strong><span style="background-color: transparent;">, with at least </span><strong style="background-color: transparent;">3 years managing platform, infra, or SRE teams</strong><span style="background-color: transparent;"> in a product-focused SaaS environment.</span></li><li class=""><strong style="background-color: transparent;">Production AWS ownership</strong><span style="background-color: transparent;"> — you've run HA workloads on AWS at scale, covering high availability, governance, compliance, and a 24/7 on-call program.</span></li><li class=""><strong style="background-color: transparent;">Infrastructure as code</strong><span style="background-color: transparent;"> - you've built and scaled IaC practices using Terraform, and know enough about packaging tooling (Helm, Kustomize, or similar) to make good architectural decisions and hold the team to a high bar.</span></li><li class=""><strong style="background-color: transparent;">CI/CD fluency</strong><span style="background-color: transparent;"> — you've built or owned pipelines in GitLab CI, GitHub Actions, Jenkins, or similar, and know where they break under scale.</span></li><li class=""><strong style="background-color: transparent;">Observability ownership</strong><span style="background-color: transparent;"> - you've built or evolved an observability stack and made it materially better: alerting, SLOs, and distributed tracing for a real production system.</span></li><li class=""><strong style="background-color: transparent;">Incident command</strong><span style="background-color: transparent;"> - you've run customer-facing major incidents both as incident commander and as the manager supporting the team. You know the difference between those roles.</span></li><li class=""><strong style="background-color: transparent;">Application security</strong><span style="background-color: transparent;"> - you've embedded security into the SDLC: SAST/DAST/SCA, vuln management with SLAs, and threat modeling as a team practice, not a checkbox.</span></li><li class=""><strong style="background-color: transparent;">Cloud security posture</strong><span style="background-color: transparent;"> - you own IAM, secrets management, network segmentation, and CSPM. You've hardened an AWS environment and can explain the tradeoffs you made.</span></li><li class=""><strong style="background-color: transparent;">Compliance partnership</strong><span style="background-color: transparent;"> - you've worked alongside IT on compliance programs (SOC 2, ISO 27001, or similar) and know how to translate requirements into engineering work.</span></li><li class=""><strong style="background-color: transparent;">Deeply hands-on </strong><span style="background-color: transparent;">-</span><strong style="background-color: transparent;"> </strong><span style="background-color: transparent;">you've kept your technical edge as your teams have grown, and you're still close enough to the work to spot problems early and earn credibility with your engineers.</span></li><li class=""><strong style="background-color: transparent;">Bias for action </strong><span style="background-color: transparent;">-  you default to doing, not delegating. When something is broken, you dig in. When a process isn't working, you fix it. You don't wait to be told.</span></li><li class=""><strong style="background-color: transparent;">Active AI adoption</strong><span style="background-color: transparent;"> - you use AI-assisted tools (Claude Code, Copilot, Cursor, Windsurf, or similar) as part of your daily workflow for incident diagnosis, IaC authoring, runbook generation, or log and metric analysis. You can describe specifically how, not just that you do.</span></li></ul><div><br></div><h3><strong style="background-color: transparent; color: rgb(153, 0, 255);">Preferred</strong></h3><ul><li class=""><span style="background-color: transparent;">B2B SaaS experience with Salesforce coupling — managed packages, org provisioning, integration patterns</span></li><li class=""><span style="background-color: transparent;">CPQ, billing, or revenue domain — high-stakes correctness, audit-relevant data</span></li><li class=""><span style="background-color: transparent;">Experience standing up a Platform Engineering practice or internal developer platform (Team Topologies, paved roads)</span></li></ul><div><br></div><h2><strong style="background-color: transparent; color: rgb(153, 0, 255);">Tech Stack</strong></h2><ul><li class=""><strong style="background-color: transparent;">Salesforce Platform:</strong><span style="background-color: transparent;"> Apex, Lightning Web Components (LWC), SOQL, Flows, managed packages</span></li><li class=""><strong style="background-color: transparent;">Backend:</strong><span style="background-color: transparent;"> Java (Spring Boot), Node.js, REST APIs, GraphQL</span></li><li class=""><strong style="background-color: transparent;">Frontend:</strong><span style="background-color: transparent;"> React 16, TypeScript, Material-UI, Webpack</span></li><li class=""><strong style="background-color: transparent;">Database:</strong><span style="background-color: transparent;"> PostgreSQL (AWS RDS), Salesforce SOQL/SOSL</span></li><li class=""><strong style="background-color: transparent;">Infrastructure:</strong><span style="background-color: transparent;"> AWS (Lambda, SQS, S3), Kafka, Docker, GitLab CI/CD</span></li><li class=""><strong style="background-color: transparent;">AI Tooling:</strong><span style="background-color: transparent;"> Claude Code, Windsurf, Copilot (used daily across engineering)</span></li><li class=""><strong style="background-color: transparent; color: rgb(0, 0, 0);">Collaboration:</strong><span style="background-color: transparent; color: rgb(0, 0, 0);"> Jira, Slack, Gem, Fellow, Confluence</span></li></ul><div><br></div><div><br></div>

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...