Strengthened screen update: 0 of 9 retained leads fully pass — 6 of the original 15 removed

Asked (summary)

Find 15 highly qualified public candidates for a Cyber Threat Engineer role in Vienna, VA and Pensacola, FL — 5–10 years of cybersecurity experience, hybrid 3 days onsite, with mandatory hands-on evidence of 3+ years Python scripting/automation, direct CTI, threat hunting, YARA and SIGMA rule development, MITRE ATT&CK, and security-automation / threat-intel ingestion and enrichment workflows — separated by location with experience, technical evidence, certifications and match percentage, without assuming missing qualifications.

Asked (follow-up, summary)

Tighten the screen: candidates must be U.S.-based in the specified areas, hold established profiles with verifiable history dating to 2019 or earlier, show complete and consistent dated employment timelines, and have technical skills verified through actual documented project experience rather than keyword matches; exclude profiles that cannot meet these verification standards.

This stricter update re-screened the original 15 public leads (drawn from 2,308 unique web results — 1,204 Northern Virginia/DC-area and 1,104 Pensacola-area). 9 profiles were retained for possible recruiter validation — 4 in the Vienna/Northern Virginia/DC commuting pool and 5 in the Pensacola pool — and 6 were removed because identity, current location, or adequate profile evidence could not be cleanly re-established. Zero profiles pass every strengthened public-evidence check, so no profile should be called a qualified candidate.

Compliance boundary: candidates were not screened, ranked, or inferred by citizenship, immigration status, or any protected characteristic. Work authorization was not assessed and must be verified separately by the employer through a lawful, consistent process; nothing here implies any person lacks authorization. Three-day onsite willingness also remains unverified. Blank or grey cells mean not publicly evidenced — never absence of skill.

Public-evidence matrix: ten strengthened checks, nine retained leads

Each column is one equally weighted check behind the documented-evidence score. Hover or tap a cell for the exact project evidence or the specific item still unresolved. No row completes all ten.

Concrete public evidence found Not publicly evidenced / requires clarification (not a negative claim)

What the matrix cannot say alone

Chinonso Nwangwu is the closest DC-pool lead at 80% evidence coverage, with 40+ documented federal threat hunts and YARA/SIGMA/ATT&CK projects — but only two dated Python years are publicly established and his certification IDs and timeline need clarification. theorg.com

Troy Karpinsky also reaches 80% with three dated Python years and strong YARA, CTI, hunting and ATT&CK project evidence from FBI work — but no practical SIGMA project was verified and two current Kaseya roles list overlapping “Present” dates. linkedin.com

Ramon Villareal shows the deepest dated Python record of the nine (8 years automating security on Naval networks), yet no YARA, SIGMA, CTI or ATT&CK project is publicly documented. linkedin.com

Only one of the nine profiles, Fidelle W., shows a fully consistent dated timeline — but her verifiable history begins in 2021, short of the 2019-or-earlier requirement. linkedin.com

Methodology

Score = documented public-evidence completeness across ten equally weighted checks: history to 2019 or earlier; 5–10 cybersecurity years; 3+ dated Python years; and concrete YARA, SIGMA, CTI, threat-hunting, MITRE ATT&CK and security-automation/CTI-workflow projects; plus a complete, consistent dated employment history.
Work authorization and onsite willingness are excluded from scoring and from every check.
Evidence had to name an actual project in a dated role; keyword mentions did not count.
Timeline overlaps are described neutrally as items requiring clarification, not as misconduct.
Independent corroboration succeeded for Chinonso Nwangwu (CISA org chart) and Jarrad Pemberton (speaker/GitHub record); a same-name GitHub match for Tyler Smith was set aside as insufficiently established.

Recruiter validation checklist

Confirm identity and current commuting-area location directly with each profile owner.
Verify work authorization through the employer’s lawful, consistent process — it was not assessed here.
Confirm willingness to work hybrid, 3 days onsite per week, in Vienna, VA or Pensacola, FL.
Ask for dated detail on each grey cell: Python years, SIGMA/YARA artifacts, CTI and automation workflow work.
Request clarification on overlapping or dual-“Present” roles and certification IDs before advancing anyone.

All nine retained leads, by location pool

Every row carries the result “Does not pass strengthened public-evidence screen”. Score shown only where a documented-requirements percentage was computed.

Lead	Pool	Current role	Hist. from	Cyber yrs	Py yrs	Score	Certifications	Unresolved items	Source

Method: 9 strengthened-screen public leads (one row per person) from a search of 2,308 unique web results (1,204 Northern Virginia/DC, 1,104 Pensacola) that first produced 15 leads; 6 were removed when identity, location or evidence could not be re-established. Score is the share of ten equally weighted public-evidence checks met; blank means not computed or not publicly evidenced. Work authorization and onsite willingness excluded. Long project descriptions and full dated histories trimmed for space; sources: LinkedIn, The Org, AllBSides. Compiled October–November 2026 search snapshot.

This report was generated automatically by Keenable SELECT at a user's request, from publicly available web sources linked herein. Keenable does not review, verify, or endorse its contents and makes no representation as to accuracy, completeness, or timeliness; AI-based extraction may contain errors. Nothing in this report is investment, legal, financial, or other professional advice. All trademarks and referenced content remain the property of their respective owners; no affiliation or endorsement is implied. To report an error, rights concern, or request removal: legal@keenable.ai.