Delivery Operations Analyst

We run the operational engine behind a fast-growing cybersecurity SaaS delivery business - resource planning, scheduling, capacity and utilization, governance reporting and delivery performance across four global segments.

Why this role is worth your time

Unusual visibility for the level. The weekly delivery and operations report you produce is read by delivery leads, project management, customer success and leadership, including CEO COO. Very few analyst roles put your work in front of that audience every week.

You see the whole pipeline. Not one account or one region - every pentest engagement moving through scoping, validation and scheduling across SMB, Mid Enterprise, US Strategic and ROW Strategic. That breadth is the fastest operations education available, and it is hard to get in a larger, more siloed company.

You will build, not just maintain. The reporting cadence, the escalation rules and the tracking model are still being shaped. If you spot a manual step worth automating or a report worth rebuilding, you will be asked to do it rather than told to leave it alone.

A growing industry. Penetration testing and offensive security services are expanding, and operations experience in this space transfers well. The domain knowledge you build here holds its value.

What you will own

• Hygiene and accuracy of the pentest scheduling board - stage progression, ownership, dates and dependency flags

• Tracking every scope validation card from request through to scheduling, keeping aging visible by tower

• The weekly Delivery Ops report - deck and email - to a fixed cadence and a fixed metric set

• Week-on-week trend data, so movement is visible rather than re-reported

• Daily follow-up with technical SMEs, project managers and customer success managers on anything pending

• Escalation of cards with no activity for more than three business days

• Capacity and utilization tracking by segment, and flagging where intake is outpacing throughput

• Support for access governance reviews and the associated sign-off tracking

• The integrity of the numbers the function publishes

Your first 90 days

Days 1-30. Learn the board, the stages and who owns what across both towers. Run the weekly reporting cycle with review.

Days 31-60. Reporting runs without prompting. You are chasing aging cards proactively and raising data discrepancies before publication rather than in the meeting.

Days 61-90. You have improved one part of the process - a template, an automation, a dashboard, a manual step removed - and the delivery leads come to you for the numbers rather than waiting to be

Who we are looking for

This is a hands-on execution role, not a strategy one. The three non-negotiables:

1. Real spreadsheet depth - pivot tables, lookups, and the ability to turn a messy export into a clean summary without hand-holding.

2. Has owned a recurring report for a management audience. Cadence discipline matters more than polish.

3. Comfortable chasing senior people politely and persistently without being prompted.

No security or technical testing background is required. Exposure to a technical services or SaaS delivery environment is a plus, not a filter.

We are not looking for a specialist in penetration testing, or a people manager. This role has no direct reports and no technical testing component.

Work model. [Hybrid]

Disclaimer : This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.