Senior Platform Engineer (DevOps)

June 9, 2026

Other Jobs To Apply

No other job posts for this day.

Company OverviewActiveProspect is on a mission to make consent-based marketing the best channel for online customer acquisition. We provide marketers the products they need to acquire qualified customers at scale. Our platform is trusted by thousands of companies engaged in direct-to-consumer marketing, helping them save wasted spend, comply with ever-changing regulations, and manage a constantly evolving partner landscape. Our flagship product, TrustedForm, is used to certify over 1 billion opt-in digital customer leads every year and is the gold standard for documenting prior express written consent for TCPA compliance.Job SummaryYou own outcomes for the engineers you serve, not tickets. You find the friction slowing teams down and remove it for everyone at once — and you do it with the autonomy and judgment to decide what's worth building, what isn't, and when to say no. Platform is a force multiplier. We build self-service tooling, paved roads, and automation that any team can adopt without us in the loop. The systems you build and run power products that serve hundreds of millions of requests per day, and the abstractions you ship determine how fast every product engineer at ActiveProspect can build and deploy. When you build something well here, one change makes dozens of engineers faster. The technical bar is high, but raw skill is the floor here, not the ceiling. What sets this role apart is judgment: knowing which friction is worth removing, when a smaller fix beats a bigger one, when to build a reusable capability instead of a one-off, and when AI output is good enough versus when to dig in yourself. You'll set technical direction for how we deploy, observe, secure, and operate our infrastructure — and raise the bar for the engineers around you.Responsibilities:<ul><li style="list-style-type:disc;">Own outcomes end-to-end. Frame the problem, design the solution, ship it, and own whether it actually moved the metric. Descope to the cheapest version that works, and prototype in days, not weeks.</li><li style="list-style-type:disc;">Build for self-service, not for tickets. Treat the platform as a product and internal engineers as your customers. Understand their friction, then solve it with reusable, well-documented tooling that teams adopt on their own — so the fix scales to everyone, not just the team that asked.</li><li style="list-style-type:disc;">Own and evolve the paved road. Set the direction for our GitOps, Kubernetes (AWS EKS / ArgoCD), and serverless (AWS Lambda) patterns so the easy path is also the secure, reliable, and cost-aware one — and lead the migrations that get us there.</li><li style="list-style-type:disc;">Own reliability. Lead incident response for the systems you own, drive blameless postmortems, and turn what you learn into durable fixes. Set the on-call practices that keep us meeting our SLAs without burning people out.</li><li style="list-style-type:disc;">Architect AI-driven leverage. Design and operate AI agents and automation that hold up in production — auto-triage, auto-remediation, agent-assisted CI/CD — and set the guardrails, evals, and cost controls that keep them safe. Evolve the team’s practices as the tooling changes. We expect everyone here to build with AI, not just be aware of it.</li><li style="list-style-type:disc;">Own access, security, and compliance. Design how we manage credentials and permissions for developers and automated processes. Consent and PII handling are central to customer trust, so security is built into every system you own. Lead our SOC 2 and GDPR work and the remediation that follows.</li><li style="list-style-type:disc;">Make things cheaper. Own initiatives that measurably reduce infrastructure cost.</li><li style="list-style-type:disc;">Multiply the team. Mentor on judgment and systems thinking, not just syntax. Write decision memos and ADRs, set standards, and bring patterns and hard-won context back to the wider org instead of hoarding them.</li></ul> Qualifications and Skills<ul><li style="list-style-type:disc;">5+ years building, operating, and owning production infrastructure at scale, with a track record of platform work that made many engineers faster.</li><li style="list-style-type:disc;">Deep expertise in a cloud environment (AWS) and with containers and orchestration (Docker, Kubernetes / EKS, Helm).</li><li style="list-style-type:disc;">Strong command of CI/CD and GitOps (GitHub Actions, ArgoCD) and Git-based workflows.</li><li style="list-style-type:disc;">Hands-on expertise with Infrastructure as Code (Terraform) and configuration automation.</li><li style="list-style-type:disc;">Solid grasp of Linux (Ubuntu), production databases (PostgreSQL/RDS, DynamoDB, MySQL, MongoDB), and networking (load balancers, firewalls, routing, VPN).</li><li style="list-style-type:disc;">A track record of shipping something you cared about end-to-end and owning the outcome — and the instinct to solve a problem once, reusably, rather than the same problem over and over.</li><li style="list-style-type:disc;">Treats developer experience as a product — measures adoption and delivery metrics (e.g., DORA) and iterates on tooling the way a PM iterates on a feature.</li><li style="list-style-type:disc;">Strong systems-design judgment in ambiguous contexts, and the ability to descope well and push back on low-value work.</li><li style="list-style-type:disc;">Experience leading incidents and operating customer-facing production environments with a focus on uptime and service quality.</li><li style="list-style-type:disc;">Uses AI agents and coding tools as a daily driver — reads their output critically and builds automation on top of them, not just consumes them.</li><li style="list-style-type:disc;">Clear written and verbal communication, plus mentorship experience — you make the people around you more productive.</li><li style="list-style-type:disc;">A security and reliability mindset that fits working with sensitive consumer data.</li><li style="list-style-type:disc;">A 4-year degree in engineering or computer science</li></ul> <h3 style="line-height:1.38;margin-top:21px;margin-bottom:5px;">How to Stand Out</h3><ul><li style="list-style-type:disc;">Experience building an internal developer platform or paved-road tooling adopted across multiple teams.</li><li style="list-style-type:disc;">Deep observability and telemetry experience (OpenTelemetry, Datadog), including SLOs and alerting strategy.</li><li style="list-style-type:disc;">Experience operating microservices, serverless (AWS Lambda), or event streaming (Apache Kafka / Confluent) at scale.</li><li style="list-style-type:disc;">Secrets management at scale (AWS Secrets Manager, Doppler).</li><li style="list-style-type:disc;">Experience with multi-account AWS, distributed database systems, or high-throughput data pipelines.</li><li style="list-style-type:disc;">Programming experience with Elixir, Ruby, JavaScript/Node.js, or Python.</li><li style="list-style-type:disc;">Ownership of compliance frameworks (SOC 2, GDPR) end-to-end.</li></ul><h3 style="line-height:1.38;margin-top:21px;margin-bottom:5px;">How It Works</h3>You'll report to an Engineering Manager who owns delivery health and stakeholder alignment, while you own technical direction for the platform — often acting as the player-coach Tech Lead for the work in flight. We partner with product teams to understand their needs and deliver through self-service tooling and automation. Success looks like product teams that ship faster on tooling you built, friction removed for many teams at once, incidents handled calmly, decisions made fast, and engineers who level up because they worked with you.Reports to:<ul><li style="list-style-type:disc;">Engineering Manager</li></ul>

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

DISCLAIMER