Professional Experience
This engagement represents my most significant professional cybersecurity experience to date.
As part of a Wipro consulting team, I supported the delivery of a ServiceNow Vulnerability Response implementation for a client operating under a demanding timeline. Although I joined the engagement early in my career, I was given ownership responsibilities that extended beyond what I expected as a recent graduate.
The experience taught me that successful cybersecurity projects depend as much on communication, ownership, stakeholder alignment, and delivery discipline as they do on technical implementation.
Project Summary#
Overview#
This engagement involved supporting the implementation of ServiceNow Vulnerability Response for a client environment.
The project team consisted of an engagement partner, a lead consultant/developer, two offshore developers, and client stakeholders. While technical implementation work was performed across the team, I was given responsibility for coordinating project activities, maintaining delivery visibility, tracking progress, and helping ensure the engagement remained aligned with project objectives.
One of the most valuable aspects of this experience was seeing how cybersecurity delivery works in a real consulting environment. Success depended not only on technical implementation but also on communication, planning, documentation, stakeholder alignment, and execution discipline.
Responsibilities#
My responsibilities included:
- maintaining the RAID log
- coordinating project activities
- scheduling meetings and stakeholder sessions
- tracking development progress
- participating in daily standups
- creating approximately half of the project user stories
- reviewing story progress through delivery
- supporting UAT preparation and execution
- supporting end-user training activities
- contributing to go-live readiness
- helping maintain overall project quality
These responsibilities provided exposure to both cybersecurity implementation work and project leadership activities.
Delivery Workflow#
Requirements & Planning#
Business requirements, process expectations, and implementation objectives were defined with client stakeholders.
Planning
Story Development#
Requirements were translated into user stories and tracked throughout implementation.
User Stories
Daily Coordination#
Development progress, blockers, dependencies, and stakeholder alignment were managed through recurring coordination activities.
Coordination
User Acceptance Testing#
The solution was reviewed and validated through structured UAT activities.
UAT
Biggest Challenge#
The most difficult part of the engagement was not technical implementation.
The most difficult challenge was stakeholder alignment.
As someone relatively new to the industry, I quickly learned that project success often depends on coordinating people with different priorities, schedules, expectations, and responsibilities.
At various points, the project required alignment between client stakeholders, offshore developers, consultants, and leadership. Information did not always arrive when expected, requirements evolved, and dependencies needed to be managed carefully.
One of the practices that helped most was maintaining daily communication and recurring standups. Consistent communication reduced uncertainty and kept the project moving forward even when challenges emerged.
What I Learned#
This engagement changed how I think about cybersecurity consulting.
Before joining the project, I assumed that technical implementation would be the most difficult part of delivery.
Instead, I learned that stakeholder alignment is often harder than technology.
Most implementation challenges eventually have technical solutions. Coordinating people, expectations, priorities, schedules, and communication requires a different skill set.
I was also surprised by how much ownership I was given early in my career. Being responsible for project tracking, user-story management, stakeholder coordination, and delivery support forced me to become more organized, proactive, and detail-oriented than I had been previously.
The biggest lesson I took away from this project is that successful cybersecurity implementations are not purely technical achievements. They are delivery achievements. Technology, communication, planning, accountability, and execution all have to work together for a project to succeed.
That perspective continues to influence how I approach ServiceNow SecOps, cybersecurity consulting, and project delivery today.
Capability-to-Evidence Map#
Professional Relevance#
This is the strongest professional-experience page in the portfolio.
It represents:
- real client delivery
- real stakeholders
- real deadlines
- real ownership
- real implementation work
The experience directly supports conversations around:
- ServiceNow SecOps
- Vulnerability Response
- cybersecurity consulting
- project leadership
- stakeholder management
- security operations
- implementation delivery
and serves as the clearest example of how my academic foundation translated into professional execution.
Portfolio-Safe Redaction Notes#
This page intentionally excludes:
- client names
- screenshots
- implementation configurations
- internal documentation
- architecture diagrams
- proprietary workflows
- customer data
- confidential project materials
The purpose is to demonstrate professional experience while protecting client confidentiality.
Related Portfolio Areas#
ServiceNow SecOps Lab Hub#
Personal ServiceNow SecOps lab work and Vulnerability Response workflow concepts.
Primary Focus
ServiceNow Vulnerability Response Lab#
Portfolio-safe Vulnerability Response workflow demonstration.
Workflow
Capabilities#
Capability-to-evidence mapping across consulting, SecOps, vulnerability management, and cybersecurity operations.
Evidence Map