Onsite Role : Imperva Security Engineer (VA, 12 Months)

Role : Sr Database Imperva Security Engineer with Hands on Imperva DAM/Secure sphere exp
Location: Richmond, VA
Duration of the project is 12 months.

Job Description:

1. Direct ownership of Imperva DAM.
Confirm the exact product and what the candidate personally configured, maintained, and troubleshot. An Imperva keyword or WAF-only background does not establish the database-monitoring experience required here. We need someone who has worked inside the platform and taken responsibility for its operation.

2. Strong database knowledge.
The JD names SQL Server, DB2, Oracle, and Teradata, including architecture, querying, logging mechanisms, and system catalogs. Capture hands-on depth and recency for each. We still need confirmation of the required depth across all four; do not assume a missing platform is acceptable.

The key is whether candidates understand databases well enough to investigate missing activity, identify monitoring gaps, and work effectively with platform DBAs.

3. Monitoring coverage and troubleshooting experience.
Look for examples of reconciling database inventories against DAM coverage, identifying unmonitored assets, and resolving agent outages or logging drops. A database appearing in the platform does not automatically prove its activity is being recorded.

Candidates should explain a specific failure, their diagnostic steps, what they changed, and how they confirmed monitoring was restored.

4. Practical automation.
Ask about a health check, monitoring-verification process, report, or operational workflow they personally automated. Establish what it checked, how it handled failures, and what improved. Python, PowerShell, Bash, and REST APIs are examples in the JD, not four separately required skills.

5. Security judgment and follow-through.
Obtain examples of identifying policy drift or weaknesses in security baselines, recommending adjustments, and validating the results. Also establish whether candidates have driven complex vendor escalations, upgrades, or bug fixes through resolution.

Where to focus sourcing

Target Imperva DAM Engineers, Database Security Engineers, Database Activity Monitoring Engineers, Secure Sphere Administrators, and DBAs with direct Imperva DAM ownership.

Prioritize the combination of database knowledge, platform engineering, troubleshooting, and automation. Profiles limited to general infrastructure, SOC alert review, governance, or traditional DBA duties will leave important requirements unproven.