← Search all jobs

Sr Security Engineer

Cisco IOS

Reston, VA · Posted November 7, 2026

Just laid off? Start here: a plan for the first weeks

See every open role at Cisco IOS

More in Virginia job market · Technology & Software · Security jobs

More roles at Cisco IOS

Similar jobs

Where Reston, VA ranks

Where Reston, VA placed in our monthly rankings, month by month. Each month stays online at its own address.

Rankings about security jobs

Security jobs · Top Security employers · All rankings

How AI is used in this kind of work

Among computer occupations, all other, AI is already used for a large share of the tasks. Measured exposure for computer occupations, all other: 31% (high).

Share of this job’s tasks that AI is already used for at work, from real usage. It is not a forecast of job loss, and a low number means no use seen yet. Source: Anthropic Economic Index.

Check how this applies to your own job

About the job

RECRUITER SCREENING GUIDE

Senior Security Engineer SASE and SSE

Required and preferred qualifications

Required

Substantial hands on deployment and troubleshooting experience with both Netskope and Zscaler, with deep implementation capability in at least one of the two platforms.

Consulting or professional services experience leading customers through discovery, design, implementation, migration, testing, documentation, knowledge transfer, and stabilization.

Ability to explain what the candidate personally configured rather than describing work completed by a vendor, partner, or another engineer.

Working knowledge of core SSE capabilities including secure web gateway, ZTNA or private access, traffic steering, identity, endpoint clients, tunnels, policy, logging, and operational troubleshooting.

Strongly preferred

Current professional and architect level certifications for both Netskope and Zscaler, or a credible plan to complete missing advanced certifications.

Hands on enterprise firewall experience, especially Palo Alto Networks, Fortinet, Cisco, or Check Point.

Experience integrating SSE platforms with identity providers, endpoint management, SIEM, SD WAN, cloud environments, and existing firewall infrastructure.

Mandatory recruiter questions

1 Netskope hands on deployment depth

Ask exactly Describe the most recent Netskope deployment you personally delivered. What did you configure, how large was the environment, and what problems did you have to solve?

Qualified response Red flags and likely reject

Provides a recent enterprise example and personally owned items such as tenant setup, steering, Netskope Client, GRE or IPsec, SWG policy, NPA publishers and applications, identity, certificates, logging, testing, and troubleshooting. Only supported sales calls or observed delivery; cannot name specific configuration objects, design decisions, migration steps, or issues resolved.

2 Zscaler hands on deployment depth

Ask exactly Describe the most recent Zscaler deployment you personally delivered. What did you configure in ZIA and ZPA?

Qualified response Red flags and likely reject

Provides a recent example covering items such as Client Connector, forwarding profiles, PAC or tunnels, locations, authentication, app connectors, application segments, access policy, certificates, logging, and testing. Experience is limited to product positioning, administration of a mature tenant, or one narrow feature; another engineer performed the deployment.

3 Platform balance

Ask exactly Which platform is your strongest, Netskope or Zscaler? Rate your hands on depth in each and explain what you could independently deploy tomorrow.

Qualified response Red flags and likely reject

Clearly identifies strengths and limits while demonstrating meaningful implementation capability in both platforms and senior depth in at least one. Claims equal expertise without evidence; has deep experience in one platform and only familiarity or sales exposure in the other.

4 Personal ownership

Ask exactly For the projects you described, what configuration and troubleshooting did you personally perform, and what was handled by other engineers or the manufacturer?

Qualified response Red flags and likely reject

Separates personal work from team contributions and can discuss exact technical decisions, changes, validation, and outcomes. Repeatedly uses “we” but cannot isolate personal ownership; relies on vendor professional services or escalation teams for core tasks.

5 Consulting delivery experience

Ask exactly Walk me through how you lead a customer from discovery through design, deployment, migration, stabilization, documentation, and knowledge transfer.

Qualified response Red flags and likely reject

Describes a structured consulting lifecycle, manages dependencies and risk, communicates decisions, maintains scope, documents the environment, and prepares customer operations teams. Experience is internal administration only; little customer leadership; focuses on configuration without project communication, documentation, or handoff.

6 Secure web gateway implementation

Ask exactly What are the major technical decisions and dependencies when deploying secure web gateway services for remote users and branch locations?

Qualified response Red flags and likely reject

Covers traffic steering, client and tunnel methods, identity, certificate deployment, TLS inspection, policy hierarchy, exceptions, bandwidth, egress IPs, logging, rollout, and rollback. Focuses only on URL categories or assumes installing the endpoint client completes the deployment.

7 Private access and ZTNA implementation

Ask exactly How would you migrate users from traditional VPN to Netskope Private Access or Zscaler Private Access?

Qualified response Red flags and likely reject

Addresses application discovery, segmentation, publisher or connector placement, DNS, identity, posture, dependencies, pilot groups, coexistence, testing, rollback, monitoring, and user support. Treats ZTNA as a direct VPN replacement without application discovery, dependency mapping, phased rollout, or rollback planning.

8 Traffic steering and connectivity

Ask exactly Explain when you would use an endpoint client, GRE tunnel, IPsec tunnel, proxy method, or another steering option. What commonly goes wrong?

Qualified response Red flags and likely reject

Selects methods based on user and location use cases and discusses routing, MTU, asymmetric paths, failover, authentication, certificate, PAC, bypass, and inspection issues. Cannot explain why one steering method fits a use case or has no structured troubleshooting approach.

9 Identity certificates and TLS inspection

Ask exactly Describe how identity, certificates, and TLS inspection fit into an SSE deployment. What must be coordinated with the customer?

Qualified response Red flags and likely reject

Explains IdP integration, groups and attributes, authentication flows, certificate trust, deployment method, decryption exceptions, privacy or legal considerations, testing, and break fix procedures. Treats identity and certificates as simple prerequisites and cannot explain failure modes or customer coordination.

10 Troubleshooting methodology

Ask exactly A user reports that an application stopped working after traffic was moved through the SSE platform. Walk me through your troubleshooting process.

Qualified response Red flags and likely reject

Uses a layered process covering endpoint status, steering, DNS, authentication, policy match, TLS inspection, logs, routing, connectors or publishers, application behavior, packet evidence, and controlled bypass testing. Jumps immediately to bypassing the application or opening a vendor ticket without isolating the failure domain.

11 Migration and change control

Ask exactly How do you execute a large SSE migration while limiting user disruption and maintaining a reliable rollback path?

Qualified response Red flags and likely reject

Discusses prerequisites, baselining, pilots, deployment rings, success criteria, communications, monitoring, exception handling, rollback, change control, and hypercare. Proposes a broad cutover with limited pilot testing, no measurable acceptance criteria, or no rollback plan.

12 Documentation and knowledge transfer

Ask exactly What documentation and operational handoff do you provide at the end of an SSE deployment?

Qualified response Red flags and likely reject

Produces as built documentation, architecture and traffic flows, policy and object inventories, integration details, support procedures, troubleshooting runbooks, known exceptions, and customer knowledge transfer. Documentation is limited to vendor exports or informal notes; no deliberate operational readiness or knowledge transfer process.

13 Certifications and continuing development

Ask exactly Which current Netskope and Zscaler certifications do you hold, at what levels, and how have they supported your hands on work?

Qualified response Red flags and likely reject

Ideally holds professional and architect level credentials for both vendors, gives verifiable certification names and status, and connects training to real deployments and ongoing lab work. Uses certifications as the primary proof of capability; credentials are expired or unclear; cannot connect certification knowledge to implementation examples.

14 Firewall experience and integration

Ask exactly Which enterprise firewall platforms have you personally configured or troubleshot, and how have firewalls affected your SSE designs?

Qualified response Red flags and likely reject

Has useful hands on experience with platforms such as Palo Alto, Fortinet, Cisco, or Check Point and understands routing, NAT, VPN, segmentation, egress, tunnels, and policy interactions. No firewall or routing fluency; treats the SSE platform as isolated from the customer network; cannot troubleshoot connectivity outside the SSE console.

15 Closeout confidence check

Ask exactly If assigned a Netskope or Zscaler deployment tomorrow, which workstreams could you lead independently and where would you need support?

Qualified response Red flags and likely reject

Confidently identifies multiple deployment workstreams, demonstrates realistic senior level ownership, and acknowledges bounded areas for collaboration. Response is narrow or vague, depends heavily on vendor support, or claims expert depth across every feature without credible examples.