Job search
ClearanceJobs Review: Who Can Join, Profile Visibility, and Cleared Tech Roles
Review ClearanceJobs registration rules, public technical listings, profile visibility and Premium trial terms before sharing a resume or starting paid access.
ClearanceJobs is useful for a cleared technology search when you meet its candidate-registration rules and want to investigate work requiring government security clearance. Check whether you can accurately meet the network's entry requirements, then assess the role and choose the audience for any profile you create. Public job browsing, candidate registration, employer discovery and an optional Premium subscription are separate decisions. None grants a clearance or establishes that you meet a vacancy's requirements.
LandOffer publishes this review and offers job-search tools, giving us a commercial interest in the category. We checked official pages on October 13, 2026, opened public software results and read an Amentum job detail. We inspected the unfilled registration page and documentation without creating an account. We did not upload files, change visibility, contact recruiters, start a trial or apply. The candidate records below are fictional. Compare a suitable lead with recent roles on LandOffer while keeping its actual requirements attached.

Check the published candidate-entry rules
ClearanceJobs' eligibility page restricts registration to US citizens with active or current federal security clearance. It defines active through present work requiring clearance and current through work requiring it within the past two years. These are the site's published registration definitions, not an independent verification of your status. A date in your work history alone cannot verify the government record or a particular job's access conditions.
The page also permits interim clearance, with that status noted, and final clearance approved before the associated job has started. Read those specific explanations when relevant. Do not replace uncertain status with a more favorable label.
The registration page displayed the citizenship requirement and asked whether the person currently holds active or current clearance. We left both radio choices unselected. Its existence does not provide a route for an uncleared person to obtain clearance by joining.
The candidate eligibility help says registration has no candidate cost. That is separate from optional paid tools. The site terms, dated December 3, 2025, also require users to be at least 18.
If your record is uncertain, seek verification through the appropriate authorized security contact before making a declaration. This article cannot inspect that record or decide what an employer will accept. A previous government worksite, badge or project name does not supply the missing verification.
A public search does not waive registration conditions
We followed the homepage's Software Engineer link to a public result page. After loading, it displayed role cards and controls for experience, city, state, clearance and posting recency. This establishes the public view we observed without signing in; we did not test all filters or personalized search.
Read the actual work and each complete security condition. A broad software result can include architecture leadership, embedded engineering, research and other responsibilities. Shared technologies do not make those jobs interchangeable.
The homepage also linked a Public Trust category. That category label does not redefine the registration requirement. The current USAJOBS background-check explanation explicitly distinguishes Public Trust investigations from security clearances. Check the complete role and platform instructions when their labels appear inconsistent.
ClearanceJobs says it cannot obtain clearance for a candidate. A search result, account or subscription cannot replace the authorized employer or government process. If you cannot establish a required status, keep the role pending while you clarify that condition.
Read past the short clearance field
One observed listing was Amentum's Senior Enterprise Architect, job 9174705. Its structured requirements displayed Secret, while the narrative repeatedly required active Top Secret. The description concerned Java technical leadership and enterprise architecture in Washington, DC, with an onsite schedule.
Preserve both clearance statements and ask about the actual requirement. Do not quietly select the less restrictive field or declare that one must be a harmless mistake. We did not contact Amentum or independently establish which field governs its hiring process.
The platform displayed Posted three weeks ago, while the narrative gave an original September 10, 2026 posting date. These are different displayed date fields. Neither alone establishes that a particular candidate can still be considered; reopen the current employer information before acting.
The page showed Apply Now, I'm Interested and a sign-in prompt for Match Insights. We selected none of those actions. Reading the job detail did not create an application, express interest or establish personalized match quality.
Tariq completes a network-and-role check
Tariq is a fictional Java engineer. For this exercise, assume his US citizenship and current Secret status have been verified through the appropriate records. He can consider onsite Washington work. His technical record supports maintaining Java integration tests and investigating failed service interactions with a team lead.
His original supported sentence is: “Maintained Java integration tests, investigated failed service interactions and reviewed corrective changes with the team lead.” It does not claim that he led an enterprise engineering organization.
He uses the observed Amentum detail for the following original screening exercise. His facts and decisions are fictional; we have not assessed a real person's clearance or hiring eligibility.
| Check | Evidence in the exercise | Completed decision |
|---|---|---|
| Candidate-network declaration | Verified current status under the stated fictional facts | Review the registration instructions accurately; no account created here |
| Actual role's clearance | Short field says Secret; narrative repeatedly requires active Top Secret | Hold the role for clarification; do not assume his Secret status meets it |
| Work arrangement | Description specifies onsite Washington work | This condition fits his stated preference, subject to current confirmation |
| Technical responsibility | His supported contribution is testing and investigation; role includes enterprise leadership | Assess the full leadership requirements without expanding his experience |
His completed result is a role held for two reasons: the unresolved clearance discrepancy and the breadth of technical leadership. A supported declaration for the network does not resolve either issue. He has no application recorded.
He prepares: “For Senior Enterprise Architect job 9174705, the structured clearance field says Secret and the narrative requires active Top Secret. Which status is required for consideration, and is that requirement current for this opening?” This is an unsent example using public job wording.
If the employer confirms the narrative requirement, Tariq does not claim a higher status to continue. If it clarifies a different requirement, he records the exact reply and then separately reviews leadership scope. A reply about clearance would not establish his technical qualification.
Tariq now has one clearance-requirement question and a separate comparison of his Java testing contribution with the role's enterprise leadership duties. It avoids spending time tailoring around a short field that conflicts with the full description.
Decide whether your profile should be searchable
The profile setup guide describes a Profile Searchability toggle. It says turning it off prevents employers and recruiters from finding or viewing the profile information and limits certain features. That is the documented global control; we did not operate it in an account or test the employer view.
The Premium feature page separately advertises hiding a profile from specific employers, recruiter-view information, salary estimates and job insights. Selective employer hiding and turning global searchability off serve different purposes. The public descriptions do not establish alias coverage, subsidiary matching or what happens to information already received elsewhere.
The privacy policy, updated March 27, 2026, describes customer sharing and the choice to make a profile and resume unsearchable. It advises posting those materials when you want customers to view them. Read that policy alongside the actual settings and any application-specific disclosure.
A closed recruiting network still involves sharing professional information with recipients. Choose the information and audience deliberately. Do not infer that a visibility change removes a previous application or retracts a copy already delivered; this review did not test either behavior.
Mae completes a visibility and materials decision
Mae is a fictional DevSecOps engineer who meets the site's registration conditions. She is considering a future search while employed and wants to understand discovery controls before making a professional profile searchable. Her record supports checking Terraform drift and documenting remediation tickets with platform owners.
Her original supported sentence is: “Checked Terraform configuration drift and documented remediation tickets with platform owners.” It names her technical work without revealing a customer's architecture, restricted deployment details or confidential incident information.
She completes the following preparation record. These are her proposed choices, not settings changed or files uploaded during this review.
| Decision | Mae's completed choice | Boundary she records |
|---|---|---|
| General recruiter discovery | Keep global searchability off until she understands the available controls | The documented trade-off includes restricted features |
| Hide only her current employer | Investigate the advertised selective Premium control | Exact legal-entity, alias and subsidiary matching remain untested |
| Resume contents | Use the supported Terraform sentence and permitted professional context | Exclude confidential operational material and unnecessary identity data |
| Application to a selected employer | Review the materials and consent for that specific submission | Discovery settings do not prove withdrawal of earlier disclosures |
| Paid evaluation | Defer starting a trial until its charge and cancellation terms are clear | No card entered and no subscription started |
The resume-upload guide describes a resume as enabling searchability and IntelliSearch features, with options for attachments. It specifically advises removing sensitive identity information such as birth dates and Social Security numbers. We did not upload a document or test parsing, attachments or matching.
Mae keeps a private source record for the facts behind her work sentence. She does not use a recruiting attachment area to distribute clearance-investigation records or restricted customer material. Any later authorized verification follows the recipient's designated process.

Her completed decision is to postpone searchable discovery and any paid trial until the control questions are answered. She has a specific control question to resolve and keeps any previously shared material outside the claim about future searchability. If she later accepts the discovery trade-off, she can review the materials and actual account controls before changing them.
Treat Premium as an optional paid task
The current Premium FAQ describes a monthly subscription and a seven-day trial requiring a credit card. It says cancellation is available at any time, access continues through the paid period and refunds are not offered. It also says the Premium candidate features are not yet available in the native mobile apps.
Those are published terms and limitations, not billing or cancellation tests. We did not establish the exact monthly charge in an account or checkout. Verify the amount, trial end and renewal timing before entering payment information; a trial reminder is not your own cancellation record.
The feature page advertises increased recruiter-search visibility and Premium branding. Evaluate those claims against the task you want. More discovery is not Mae's immediate goal while she is still resolving audience controls. An estimated salary also needs its source and role context; it is not an employer offer.
Begin with a named task and a way to judge whether the tool helps complete it. Keep free registration when it meets your needs. Consider a paid feature only when its actual scope and cost fit a task you have identified, without assuming a badge produces interviews.
Choose one recent role on LandOffer or a public ClearanceJobs lead. Record the full clearance requirement, technical scope and location, then resolve any conflicting condition. Before sharing materials, confirm the status declaration you can make, choose the profile audience and decide whether a named paid feature is needed.
Sources and Further Reading
- ClearanceJobs candidate eligibility and special registration cases
- Candidate registration cost and conditions
- Observed unfilled candidate registration page
- Observed public software-engineer results
- Amentum Senior Enterprise Architect, job 9174705
- Profile setup and global searchability
- Resume uploads and attachments
- Premium advertised features
- Premium FAQ: trial, cancellation, refund and mobile limits
- Privacy policy, updated March 27, 2026
- Terms of Service, updated December 3, 2025
- USAJOBS: Public Trust and security clearances are different


