Job search
Open to the Public or Federal Employees Only? Screen USAJOBS Eligibility First
A completed three-candidate eligibility tree and two actual Army announcements show why familiar duties do not establish an available hiring path.
Check a USAJOBS announcement's applicant groups before tailoring your resume. Read This job is open to, the agency's clarification, and any Who May Apply language together. Then establish which listed route your own records support. Relevant technical experience cannot replace eligibility for an accepted hiring path, and an eligible route does not establish that you meet the job's qualifications.
You can compare federal openings with recent roles on LandOffer.ai, but use the official announcement to determine the federal application route. This guide draws on public USAJOBS and OPM guidance and two Army announcements inspected October 12, 2026. The three candidate cases and sample inquiry are fictional teaching examples; the hiring agency makes the actual eligibility decision.

Separate eligibility from qualifications
Eligibility answers whether the announcement permits someone in your applicant group to compete through a particular route. Qualifications concern whether your education, experience and other evidence meet the position's requirements. USAJOBS explains hiring paths as the groups an agency accepts for an announcement.
A private-sector developer could have relevant software experience yet lack the employee status required by an internal announcement. A current civilian employee could have an accepted hiring path yet lack the specialized experience for the advertised grade. These cases call for different next actions: find an available route in the first case; assess the qualification gap in the second.
Keep employment conditions separate as well. Citizenship, work location, schedule, travel and any security requirements can introduce additional gates. Passing the applicant-group check does not resolve all of them. Record the accepted route, qualification evidence and unresolved employment conditions in separate fields.
Avoid a percentage rule such as “I match most requirements.” Hiring-path status is a factual declaration that needs support. A strong project portfolio can explain your technical contribution, but it cannot establish that you currently hold a qualifying federal appointment.
Understand what the main labels let you investigate
A public announcement provides a route for applicants outside federal employment, subject to its stated citizenship and other conditions. Read the specific wording rather than interpreting “public” as unrestricted worldwide access. The Army public example below expressly requires proof of U.S. citizenship.
An employee announcement needs a closer examination of service, appointment and agency scope. The USAJOBS federal employees page explains that federal employment does not make someone eligible for every federal job. Competitive service, excepted service and internal agency opportunities have different routes.
For an excepted-service employee, a competitive-service icon is not enough to establish eligibility. USAJOBS identifies interchange agreements as a possible route in appropriate circumstances. Verify that the applicable agreement and announcement cover your situation; do not treat the existence of interchange agreements generally as permission for every excepted-service employee.
“Internal to an agency” also needs its actual agency definition. A person employed by one federal organization should not assume that every other organization's internal announcement accepts them. Agency clarification may narrow the pool to a component, location or stated category. Copy that scope into your private search record so the next review does not restart from the broader icon.
Other listed paths may provide a separate route even when an employee route does not. Read their particular conditions and proof requirements. Do not assume all listed icons must apply to you, or that a broad icon grants every authority within that category.
Compare two actual announcements before merging them
On October 12, 2026, Army Transportation had two applications-software announcements for Scott AFB, Illinois, with closely matching duties and GS-13 grades. Both displayed an October 5–14 application period. Their distinct control numbers and applicant instructions make them separate application routes to inspect.
Control 887512900, announcement MCGT-26-13071372-MP, lists competitive-service employees and several other broad hiring paths. Its agency clarification directs readers to Who May Apply in Qualifications. That section lists specific authorities, including current Army civilian employees, current non-Army DoD civilian employees and several named special authorities.
This matters for someone who sees only the competitive-service label. The detailed list is narrower than a casual reading of “any federal employee.” A competitive-service employee at an unrelated agency cannot establish an accepted route merely by pointing to the broad icon; they must find a supported listed authority or seek clarification.
Control 887513000, announcement MCGT-26-13071372-DHA, identifies a Direct Hire Authority solicitation and displays the public hiring path. Its additional information requires proof of citizenship. It also contains generic Who May Apply wording referring to categories “below,” although the public page did not display a corresponding category list.
That inconsistency is a reason for a focused agency inquiry, not permission to invent missing categories. Record both the public signal and the unresolved template language. The announcement supplies an Army Applicant Help Desk contact; use the current contact on the exact announcement when clarification is necessary.
| Field inspected | Merit-promotion announcement 887512900 | Public DHA announcement 887513000 |
|---|---|---|
| Applicant route | Named employee and special-authority categories | Public hiring path; citizenship proof stated |
| Detail that changes screening | Who May Apply specifies particular authorities | Generic category reference lacks a visible list |
| Eligibility proof | Required for the authority claimed | Read public announcement's actual document instructions; clarify conflicting text |
| Qualifications | Specialized experience and competencies remain required | Similar technical requirements remain; public access does not waive them |
| Candidate's next action | Identify and document an accepted authority | Review public conditions; ask about the unresolved category wording if material |
This comparison documents what the pages showed that day. It does not establish that the two control numbers represent two independently available seats or that submitting both improves your chances. Preserve separate route records until their instructions establish how to proceed.
Follow a three-candidate decision tree
The following completed examples use invented candidates and limited stated facts. They demonstrate screening logic, not official determinations. Assume each candidate is a U.S. citizen; no additional special hiring authority is assumed.
Nora works for a private software company and has never held a federal civilian appointment. Eli is a current Army competitive-service civilian employee whose appointment records support that description. Sam works for a private contractor supporting the same Army office; Sam is employed by the contractor and has no separate federal appointment.
Their shared interest in applications software does not give them the same hiring route. Apply the tree in this order:
- Does the exact announcement list a public path? If so, read its citizenship and other conditions, retaining any conflicting instructions for clarification.
- If relying on an employee path, do service, appointment and agency facts match a specific accepted category?
- If that category does not fit, is there another listed authority supported by the candidate's own facts and documents?
- If no supported route exists, remove that announcement from active preparation. If a material rule is unclear, hold it with a specific question.
| Fictional candidate | Merit-promotion route decision | Public announcement decision | What remains |
|---|---|---|---|
| Nora, private employee | Skip under the assumed facts; no listed authority established | Retain for review, with the generic-category wording unresolved | Technical qualifications, conditions and document instructions |
| Eli, Army civilian | Retain for documented authority review | Public route also available to investigate | Exact appointment proof, applicable grade rules and qualifications |
| Sam, contractor employee | Skip under the assumed facts; agency support work does not establish civilian status | Retain for public-route review | Same public conditions and unresolved wording as Nora |
Eli's result is “retain for review,” based only on the fictional employment facts stated above. The assumed Army employment fact does not prove every appointment condition, time-in-grade rule or qualification. Nora and Sam likewise have a possible public route to examine, rather than a favorable hiring decision.
Keep contractor experience accurate
Sam's technical work may be highly relevant to the job. The employment relationship still belongs to the private contractor in this example. OPM's contractor-employment distinction identifies the contractor as the employer of outside contractor employees.
A government worksite, agency email address or familiar mission does not itself establish a federal civilian appointment. Keep the actual employer, client and work setting clear in your resume and declarations. If you separately held federal employment, examine that record on its own; contractor work does not erase a different valid route either.
This distinction protects useful experience from becoming an unsupported status claim. Sam can describe software developed for the agency through the contracting employer while choosing an application route supported by Sam's actual circumstances.

Match proof to the authority you actually claim
The merit-promotion Army announcement says required documents vary with the authority used. It requires supporting eligibility documents and warns that an incomplete package can end consideration. Read its linked checklist for the selected authority rather than collecting a generic folder of every possible federal form.
For an employee route, an SF-50 may be relevant, but its presence alone does not settle every question. The example announcement explains that a recent SF-50 may fail to show an applicable full year of time in grade and identifies additional personnel actions that can establish the period. Read the specific request before choosing files.
Do not attach documents for an authority you are not claiming simply because they appear in a checklist. Conversely, do not assume a resume sentence can replace required proof. Keep the document, fact it supports and destination together in a private preparation note.
Personnel and supporting documents can contain sensitive information. Follow the agency's upload instructions and any permitted sanitization guidance; the Army example discusses removing another person's information and possible later requests for an unsanitized version. Do not use public portfolio links to distribute these records.
Send a question that can resolve the actual uncertainty
A useful inquiry names the control number, identifies the conflicting passages and asks a bounded process question. It should give the recipient enough context to locate the issue without turning an initial email into an unnecessary personnel-record upload.
For Nora, the completed fictional draft inquiry is:
Subject: Eligibility wording clarification — control 887513000
I am reviewing announcement MCGT-26-13071372-DHA. This job is open to lists the public, while Qualifications refers to employment-authority categories below that I cannot locate on the page. I am a U.S. citizen employed in the private sector, without a federal civilian appointment. Does this announcement accept applicants through the public route under those circumstances, and is there an additional eligibility category or document instruction I should review?
No inquiry was sent for this article, and no agency answer is invented. Nora records the question as unresolved. If the deadline arrives before a response, the authority remains unresolved. Continue only preparation that does not require an unsupported status declaration.
If a response arrives, retain its date, announcement identifier and scope. Clarification for one control number should not silently change eligibility notes for every similar job. Recheck the live announcement before applying because amended instructions can change the relevant decision.
Build the shortlist around an available route
For each federal lead, record the control number, accepted hiring path, detailed authority, supporting appointment or status fact, required proof, unresolved question and next action. A row marked “qualifications review” should have an established or explicitly pending route rather than an unchecked employee icon.
LandOffer publishes this guide and has an interest in job-search tools. An existing private document or spreadsheet can hold the same screening record. Neither a discovery platform nor an application organizer can grant an appointment status or determine the agency's eligibility decision.
Choose one federal announcement and record its control number, accepted authority and your supporting evidence before tailoring a resume. Then compare your technical evidence and employment conditions separately. If you also search private employers, browse recent roles on LandOffer.ai and keep each opportunity's actual application requirements attached to its source.
Sources and Further Reading
- USAJOBS: What jobs am I eligible to apply for? — hiring paths and applicant groups.
- USAJOBS: Federal employees — service, appointment, interchange and internal routes.
- Army Transportation: Control 887512900 — dated merit-promotion example and authority-specific proof.
- Army Transportation: Control 887513000 — dated public DHA example, including unresolved generic eligibility wording.
- OPM: Can an award program cover contract employees? — contractor employment relationship; used only for that distinction.


