Engagement Manager

DataDrone runs a Qualys implementation practice that ships outcomes in 45 days. Not a license shop. Not a generalist consultancy. Every engagement starts with one Hero use case and ends with the client team running a Qualys deployment they actually trust - at mid-market and lower-enterprise, where Qualys's value gets stranded most often. The Engagement Manager is the rhythm-keeper. The cadence is yours. The plan is yours. The handoffs are yours. The Day-45 closure is yours. You don't touch the Qualys platform; you make sure the people who do are unblocked, aligned, and moving on a beat the client can predict. What You'll Do You run the engagement end-to-end across a 45-day arc. You lock the plan on Day 1. You orchestrate the POD - Qualys SME building, Integration Engineer wiring, QA & Validation verifying, Sales & Account Executive holding the commercial line. You hold the cadence - daily POD stand-ups, weekly client checkpoints, bi-weekly executive updates to the client sponsor, the Day-30 check-in packets, and the Day-45 closure ritual. You hold the scope wall. Every customer "while you're in here..." request gets triaged in writing - in-scope, change request, roadmap, or decline. Nothing silently absorbed. Nothing left to surprise anyone at Day 45. You will not be doing forklift PM work - chasing status from Slack threads, building elaborate Gantt charts no one reads, or running an engagement out of your head. You will be running a metronome that the client can predict, with written handoffs, surfaced slips, and a documentation hub that always matches the ground. Daily Rhythm (How You Operate) The plan lives in writing. Every handoff lives in writing. Every slip surfaced within 24 hours of the signal - never at the milestone meeting. Cultural maxim: "Rhythm. No surprises. No loose ends. The plan is the plan. Scope changes get acknowledged in writing, or they don't exist." Timezone Flexibility - clients pick NA / EMEA / APAC; we mirror. Key Responsibilities Lock the 45-day phased plan at Day 1; refresh it in writing every time the rhythm shifts. Run the daily POD stand-up. Document outcomes. Route blockers. Orchestrate every handoff between SME, Integration Engineer, and QA - every one written, none verbal. Deliver the bi-weekly executive update to the client sponsor. Short. Honest. Ahead of surprises. Send the Day-30 check-in packets (Configuration axis + Coverage & Findings axis). Confirm client alignment. Triage every scope-creep request through Sales & Account. Disposition in writing. Map the client org - stakeholders, asset owners, remediation workflow - and keep it current. Run the Day-45 closure ritual: Closure & Handoff signed, warranty window opened, documentation handed over. What We're Looking For Hands-on as a senior implementation PM with security or VM domain literacy - you can hold a CISO conversation without bluffing. Strong written communication - you document by default, not by exception. Comfortable holding the scope line without breaking the client relationship. Cadence discipline - you run a meeting every day, even when nothing is happening, because you understand cadence is the contract. Fluent across modern collaboration surfaces - Confluence / Notion / Slack / Teams / Jira / Asana / ClickUp / Trello. Co-pilot instinct - the client team is in every conversation; you advise, they decide. Bonus Points For Past delivery of multi-stakeholder vulnerability-management engagements (Qualys, Rapid7, Tenable, Nessus). Experience translating CISO-level outcomes into engineering-level execution. Contribution to a partner practice's pattern library - engagement templates, handoff artifacts, executive-update formats. The Mindset We Hire For Rhythm is the contract. A cadence the client can predict is worth more than a plan that drifts. Documented by default. If it's not written down, it didn't happen. Surface slips early. A slip surfaced in week 2 is a re-plan. A slip surfaced at Day 30 is a fire. Scope wall, friendly tone. Hold the line without breaking the relationship. Co-pilot, never contractor. The client team is in every conversation. The hub is the source of truth. If the hub is stale, the engagement is misaligned. Success in This Role 30 days: POD rhythm internalized; one engagement underway with a current hub and a held scope wall. 60 days: First engagement closed cleanly; Day-45 closure ran without a surprise. 90 days: Second engagement underway with sharper cadence and pattern contributions back to the practice. Tools You'll Use Engagement hub (Confluence / Notion / Google Workspace per client), project tracker (Jira / Asana / ClickUp / Trello per engagement), Slack / Teams per engagement, calendar discipline, the practice's Closure & Handoff template, Day-30 Check-In packet templates, Requirements Pack template, the practice's AI Copilot loaded with the Qualys practice KB. Why Join Us You're not running engagements as a status-chaser for a reseller - you're running 45-day arcs that ship deployments the client owns. The practice rewards cadence over chaos, written discipline over heroics, and a scope wall over scope creep. You pick where you land on the clock - NA / EMEA / APAC - and we mirror. Timezone Flexibility is built into the practice; you don't fit yourself into someone else's day. Self-Check Before You Apply I run the stand-up every day, even on quiet days. I document by default - the hub is the source of truth, not my head. I surface slips in writing within 24 hours of the signal. I hold the scope wall without breaking the relationship. I send the bi-weekly executive update on time, every cycle. I'd rather route a request than absorb it silently. If three or more are yes, that's you - apply. #J-18808-Ljbffr