U.S. Citizenship and Security Clearance Solutions

Created: May 04, 2015 03:49PM PDT      Updated: Dec 09, 2015 10:51AM PST
It can be challenging to passively source candidates who are U.S citizens or have security clearances. There are a number of reasons for this, but mainly:
  • People don't usually post their U.S. residency status information publicly online
  • People aren't supposed to publish security clearance information online...for security reasons!
Due to this, the amount of data TalentBin is able to pull back about citizenship or security clearances is minimal. Unlike an active resume database, where candidates can select options like "Willing to Relocate", "Current U.S. Citizen", etc., we rely on various clues and keywords to qualify our candidates. But, over time, we've developed a few strategies to help you find the right people:

1. The best solution is to inform the candidate of the requirement in your outreach message, so they can quickly qualify themselves as a U.S. citizen and/or having the ability to own a security clearance.

Let's take a look at a couple of example templates that you could use for these situations:

U.S. Citizenship Outreach Message

Security Clearance Outreach Message

2. You can also try building out more refined search trees:
  • Restrict US Visas and Green Card from your Search (US Citizenship)
Similar to restricting "Leadership", "Recruiting" and "Sales" roles from searches, you can also restrict the search from pulling back profiles with certain U.S. Visa keywords (H1B, H1B1, etc.) from the search. We've built in an explode term to help with this, called US Visas (Beta).

Note: You may want to also exclude terms like "Green card", etc.

To follow this strategy, make sure to use the "NOT" Boolean modifier in Advanced search by switching the green checkmark  to the red minus  symbol:

  • Use our Security Clearance Explode Terms
We've developed a number of keyword explode terms to help with security clearance positions. The terms below contain an array of different keywords we know are associated with clearance, and will help refine down searches to candidates who mention any of the terms across the web:
  • Security Clearance: National Industrial Security Program (Keyword)
  • Security Clearance: U.S. Intelligence Community (Keyword)
  • Security Clearance Terms: DoD (Keyword)
  • Security Clearance Terms: DoE (Keyword)
You may also want to try using past employment as a modifier, particularly for candidates who need security clearances. We've complied a list of companies that we know require their employees to hold a security clearance, and by using the list in your search, you can limit the results to people who have worked at those places.
  • U.S. Government Departments & Agencies (Company)
  • Security Clearance Companies: Common Hirers (Company)
  • Security Clearance Companies: DoD Contractors (Company)
For example, let's take a look at how to run a search for Java Developers in San Francisco that have worked at companies where employees need security clearances:

  • Use the US Universities Explode Term (US Citizenship)

Another way to potentially cut out candidates without U.S. citizenship is to use our education data in TalentBin. You can use our "US Universities" explode term, select "School" on the Advanced search dropdown, and pull back people who are attending or who have graduated from our comprehensive list of universities.

While this is clearly not a perfect solution (there will probably be international students included in the results), it can be a helpful strategy:

Keep in mind, even with the solutions above, the best practice will always be to reach out to as many candidates as possible to increase your chance of success!

And remember, you can always verify citizenship through standard procedures when the candidate moves from being a passive candidate to an active candidate (or applies for the position).


See Also:
Q​uestions? Thoughts? Either c​ontact your Product Specialist, reach out to us at support@talentbin.com anytime, or leave a comment below!
Comment Form is loading comments...

Contact Us