Look for a question you can answer with evidence.

A useful preparation question is: what would I need to see before accepting this claim? Start with a modest example from a course, job or volunteer role. Perhaps a report says a service improved, but its measure changed. Perhaps a spreadsheet shows spending below budget, but several invoices have not arrived. Describe how you established what the data actually covered.

Your application should make the chain of reasoning visible. Name the question, sources, method, finding and unresolved limitation. A conclusion should not be stronger than its support. A small analysis with reproducible calculations and a careful definition can demonstrate more than an ambitious report built around numbers you cannot trace.

Choose the actual announcement’s emphasis. A technical role may need programming or systems evidence; an operational role may value process coordination; a research assignment may require quantitative or written analysis. This guide does not prescribe a universal work sample for all GAO units. Read the tasks first, then select the evidence that matches them.

Six missing records are not automatically a 30% agency-wide failure rate.

Original fictional exercise: an analyst examines 20 files from an office with 100 total files. Six of the reviewed files lack a required approval record under the exercise’s stated rule. A draft says 30% of all files are noncompliant. Assess what the supplied evidence supports. This is not a GAO audit procedure or assessment.

Fictional evidence review
QuantityValueInterpretation
All files100Population named in the scenario
Files reviewed20Selection method not supplied
Documentation exceptions6Observed count in reviewed files
Reviewed-set proportion30%Not automatically a population estimate

The observed proportion is 6/20, or 30%, in the reviewed set. If those 20 were chosen because they looked problematic, the sample does not support a simple estimate for the other 80. Even with random selection, a population estimate would need the sampling design and uncertainty, not just a percentage copied into the conclusion. The prompt supplies no such design.

The immediate supported count is six reviewed files with the specified documentation issue. A missing approval record also needs a precise definition: does it mean approval never occurred, or that the requested evidence was not found? Those are different findings. State which one the review established, preserve the exceptions and ask for the missing material or a documented explanation.

A better draft is: “Six of the 20 files examined lacked the approval record required by our review criteria. The selection method does not support estimating a rate across all 100 files. We recommend resolving those exceptions and determining whether a broader, appropriately designed review is warranted.” This communicates the problem without minimizing it or inventing scope.

For a portfolio extension, use fictional files with an explicit selection column and evidence status. Show how your summary changes when records are added or an exception is resolved. Keep the data, criteria and final statement together so a reader can inspect whether the conclusion still matches the evidence.

Translate total hours into a feasible semester plan.

GAO’s stated 400–640-hour range is a total commitment, not a single universal internship length. At an assumed 40 hours weekly, it corresponds to ten to sixteen weeks. At 20 hours, it corresponds to twenty to thirty-two weeks. These are arithmetic planning scenarios, not schedules GAO has offered you.

For example, a student available for nine full weeks at 40 hours can offer 360 hours, below the program’s described range. Do not solve that mismatch by calling the placement ten weeks on a form. Ask whether a different start, end or approved schedule is possible. Conversely, twenty weeks at twenty hours reaches 400 hours mathematically but may not match the team’s needs. The agreed appointment determines the schedule, not a spreadsheet you prepared alone.

Sources[1]

Use the announcement to decide what to submit.

Keep the required documents and assessment questions together. A resume, transcript or writing sample should demonstrate the qualifications the announcement asks you to establish. Do not send a long unsolicited report simply because you prepared one. When a writing sample is requested, select material you are permitted to share and explain your contribution to any joint work.

Evidence-to-conclusion preparation sheet

Claim I investigated: Population and period: Records I actually examined: How those records were selected: Finding supported by the evidence: What remains unproven: Document or test I would request next: GAO posting requirement this example supports: Weekly availability and total hours:

Prepare a concise account of revising a conclusion. Describe what you initially believed, the evidence that challenged it and the change you made. This is not the same as saying you are detail-oriented. It gives an interviewer a concrete decision to examine and shows that you can respond constructively when the first explanation fails.

Keep conversion out of a guaranteed-outcome calculation. Satisfying a program condition does not, by itself, produce a permanent offer. Judge the internship by the actual work, supervision, compensation and academic fit, while treating any later employment decision as separate. Your next step is a complete application to an actual announcement, not a request for a promised career path.