Job search
NIST SURF for Computing Students: Choose the Campus and Build the Right Fellowship Application
Use the current campus announcement to connect computing experience to research interests and build a complete, accurately scoped SURF application packet.
For a computing student, NIST SURF starts with two decisions: which campus you can attend and which research interests your coursework or projects can support. Gaithersburg asks for first and second preferred host laboratories; Boulder asks for first through fourth preferred projects. Applying to both requires separate applications, even when you reuse documents.
This public-documentation review was checked October 23, 2026. The 2027 announcements were accepting applications, with a January 26, 2027 closing date. Several laboratory pages still displayed earlier project examples, so the guide separates current application rules from historical research descriptions. LandOffer publishes this guide; its recent job search can support a parallel search, but it does not replace NIST's fellowship application.

Start with the current campus announcement
The current USAJOBS records are Gaithersburg, SURF-2027-0001 and Boulder, SURF-2027-0002. Both show an opening date of October 16, 2026 and a closing date of January 26, 2027. Their instructions require electronic submission by 11:59 p.m. Eastern Standard Time on the closing date. These are documented dates for this cycle, not a prediction for later years.
Both announcements require working at the named campus throughout the appointment. Both mark remote work and telework as unavailable. An older virtual project or a previous summer's arrangement therefore cannot establish remote access to the 2027 program.
The announcements describe an eleven-week main program, June 2–August 13, 2027, with alternative schedules for academic calendars. Each lists a nine-week June 14–August 13 option. Their later eleven-week options have different printed end dates: August 27 in Gaithersburg and August 28 in Boulder. Preserve the campus-specific wording and resolve the actual appointment dates before making travel commitments.
Both list a student stipend range of $6,390–$7,810 and possible housing and travel support subject to eligibility. That range does not establish your award or total summer budget. The FAQ still discusses anticipated 2026 funding; use the current announcement and eventual award terms for the 2027 financial decision.
Guest researcher status and student requirements
SURF uses USAJOBS, but its participants are guest researchers rather than federal employees. Both announcements state this explicitly. NIST's Grade 0 FAQ explains that agreeing to Grade 0 acknowledges that arrangement; it does not remove particular SURF projects from consideration. Do not translate the listing into a permanent federal engineering job or assume ordinary employee benefits.
The current announcements describe full-time, degree-seeking undergraduates at accredited two-year or four-year institutions in the United States or its territories. First-year students and graduating seniors are encouraged to apply. STEM study and a GPA of at least 3.0 are described as preferred, rather than turning every preference into an absolute cutoff.
Other listed conditions include proof of U.S. citizenship or permanent residency, health insurance, being at least eighteen by June 2, 2027, passing the background process and receiving payments through direct deposit. The FAQ expressly excludes F-1 student visa holders. Read the detailed conditions alongside the broad USAJOBS public hiring-path label; that label alone does not establish SURF eligibility.
This guide does not determine any reader's immigration, insurance or educational status. When records do not clearly match a requirement, use the program's published assistance route before relying on an assumption. Strong research writing still needs the required supporting documents.
Computing opportunities extend beyond one laboratory
The Gaithersburg research page identifies ITL, CTL, EL, MML/NCNR and PML, alongside participating offices. Its 2027 introduction says applicants choose first and second preferred hosts, and that individual projects are still being finalized. The announcement says the application is considered primarily by the first-choice host. Put the strongest connection between your existing work and the host's research in that first choice.
ITL is a natural starting point for information technology measurement, testing, mathematics, statistics and systems research. It is not a complete catalog of computing work. The Gaithersburg announcement specifically points computing students toward CTL, PML and EL as well. A simulation, instrument-data or scientific-software interest can cross organizational labels.
Boulder also lists ITL, CTL, MML and PML in its announcement. Its application requests four project preferences, with consideration primarily for the first three. The Boulder research page says 2027 opportunities are being finalized and labels the detailed list as 2026 research opportunities. That older list includes signal processing and statistical consulting: useful clues about the work, not confirmed 2027 openings.
Read an example for the underlying task, preparation and scientific setting. A Python preference on a measurement project does not turn it into a general software internship. Conversely, a physical-science laboratory name does not rule out substantial computation. Avoid choosing a host solely from an old acceptance percentage; historical applicants and available projects do not establish this year's personal odds.
Worked example: reconcile a campus and research shortlist
Original fictional example. Leona Vale is a computing student planning a possible summer application. Her fictional coursework includes probability and linear algebra. Her class project compares simulated sensor readings with deliberately added noise. She has no instrument-laboratory experience and has not reproduced a NIST experiment. This example demonstrates research planning, not a determination that she qualifies.
Her completed shortlist record reads:
| Decision field | Leona's recorded conclusion |
|---|---|
| Campus constraint | Can investigate an in-person summer in either location; housing remains unpriced. |
| Work she can evidence | Python simulation, plotting residuals and explaining a class comparison. |
| Gaithersburg first host | ITL, because measurement and testing connect to the work she can explain. |
| Gaithersburg second host | CTL, because network or communications measurement offers a related scientific direction. |
| Boulder research lead | Historical signal-processing example, to investigate when 2027 choices are finalized. |
| Boulder selection status | Four current project preferences are not yet reconciled; an old project number is not treated as current. |
| Unsupported claims removed | Instrument calibration experience, an agreed mentor and a guaranteed assignment. |
| Application consequence | Prepare a Gaithersburg narrative; keep Boulder as a separate, unfinished research decision. |
Her completed draft interest paragraph is:
I want to study how a measurement method's assumptions affect the conclusions drawn from its output. In a class project, I used Python to compare simulated sensor readings under several deliberately added noise conditions and plotted residuals. The work taught me to separate a cleaner-looking graph from evidence that a method is appropriate. My first host preference is ITL, with CTL second, because I want to develop that reasoning in a measurement or communications setting. I have not worked with laboratory instruments and would need training in the relevant experimental procedures.
The paragraph links an existing experience to a learning goal without claiming NIST access or results. Leona's finding is narrower than “apply everywhere”: one campus narrative is coherent, while the second requires current project choices. She can reuse factual coursework descriptions across applications, but cannot copy two host preferences into Boulder's four-project selection fields.

Build the packet in the system the announcement names
The SURF application page directs applicants to separate campus applications and permits reuse of documents. The current announcements add an important handoff detail: they do not accept resumes or documents transferred from USAJOBS. Their prompts direct applicants to upload documents in the application system. A file sitting in your USAJOBS profile is not evidence that SURF received it.
The required packet includes online responses, two recommendation letters, a resume, an undergraduate transcript, citizenship or permanent-residency documentation, insurance evidence and a personal statement. PDF is preferred. The transcript must support current enrollment as well as identify the institution, completed coursework and cumulative GPA. Follow the specified removal of Social Security numbers and birth dates from the transcript and citizenship or residency evidence.
Keep identity and insurance materials out of a public portfolio, shared writing sample or general job-search document. Prepare the application copies through the official route. An article or editing tool does not need to receive these sensitive records to help improve your research narrative.
The personal statement should connect relevant coursework or research, prioritized interests, participation commitment, expected learning and career goals. A resume should support those statements rather than simply list programming languages. An unfinished course is different from completed training; a classroom exercise is different from independent research.
The announcements describe a submission confirmation followed by a return to USAJOBS and a Track this application view. That view reports received documentation and recommendation status; uploaded documents may take hours to clear scanning. The FAQ permits updates before closing but says references cannot be edited after submission without program assistance. Check those names and addresses before committing the packet.
Worked example: find the incomplete item before submission
Second original fictional example. Mateo Reed has assembled a Gaithersburg packet in a local planning exercise. No account, upload, recommendation request or application was made for this guide. The statuses below are invented to demonstrate a reconciliation; they are not observations of the live application interface.
| Packet component | Fictional review finding | Completed correction or disposition |
|---|---|---|
| Campus identity | Folder says Gaithersburg; notes mention Boulder. | Set the cover record to SURF-2027-0001 and remove the Boulder selection notes. |
| Research preferences | Statement names ITL; response draft puts EL first. | Retain ITL first and EL second after reviewing his stated interests. |
| Resume | Says a database course is complete. | Change it to current coursework; retain a completed SQL class exercise separately. |
| Transcript | Older copy does not establish current enrollment. | Mark replacement documentation required; do not call the packet ready. |
| Sensitive documents | Application-only evidence is separate. | Keep it outside public writing files; required redaction remains a pre-upload check. |
| Personal statement | Generic wish to work at a famous lab. | Replace it with the specific paragraph below. |
| Recommendations | Two intended writers, no verified portal receipt. | Keep both pending in the planning record; no fictional portal receipt has been supplied. |
| Second campus | No separate application record. | Record Boulder as not submitted, regardless of document reuse. |
His revised statement excerpt reads:
My completed SQL class exercise involved separating inconsistent category labels from missing values in a small teaching dataset. I wrote the queries and documented cases where the categories still required a human decision. I am currently taking a database course; I have not completed it or managed a production research database. I would like to learn how a laboratory defines data quality requirements before choosing a tool. ITL is my first host preference and EL my second, subject to the research opportunities available. I hope this experience will help me decide whether graduate study in scientific data systems fits my interests.
His finished review memo is: “The narrative and host order now agree. The packet remains unready because current enrollment evidence and recommendation receipts are unresolved. Preparing one location's files does not establish a Boulder application. No submission confirmation exists.”
Recommendation timing needs its own check. Gaithersburg specifies three days after closing. Boulder's Required Documents section also says three days, but its How to Apply text says four. Treat the extra day as unresolved rather than as a usable extension. Seek clarification for Boulder and arrange letters early; the applicant's own submission deadline remains separate.
Make the next decision small and verifiable
Save the current campus announcement first. Record whether it requests hosts or projects, then draft one paragraph connecting work you can explain to work you want to learn. Reconcile the packet against that same announcement before submitting. A complete application can still receive no offer, and a preferred host or project is not a promised placement.
Keep fellowship preparation alongside your other opportunities. Browse recent roles on LandOffer.ai, then compare each employer's actual qualifications and application route with your available evidence.


