Senior DoD Staff Writing SME

$40–80/hrrate as listed

Write authentic DoD staff products — WARs, SITREPs, executive summaries, performance reports — as reference answers that AI models are trained and graded against. You'll also build the grading rubrics reviewers use to score model output for accuracy, tone, and compliance.

Summary, eligibility guidance and screening preparation are prepared by Sidequest from the platform's posting. Check the source listing before applying.

What the work involves

micro1 is staffing a customer project that needs real DoD staff writing, not approximations of it. Day to day you'll receive or design task scenarios — a weekly activity roll-up for a program office, a SITREP under a compressed timeline, an executive summary for a general officer, an NCOER or civilian performance narrative — and produce the input artifacts plus the golden response a competent staff officer would actually submit. Alongside each item you write grading guidance: what counts as a factual error, where BLUF discipline breaks down, which tone or classification-handling misses are disqualifying versus merely weak.

The second half of the job is evaluation. You'll read model attempts against your own rubric, score them, and explain the delta in writing that another reviewer can apply consistently. Expect feedback cycles — rubrics get challenged, prompts get rewritten when they turn out to be ambiguous, and calibration disagreements are surfaced rather than smoothed over.

What the platform screens for

Verifiable provenance. Which command or agency, which reporting chain, which formats you personally drafted and who signed them. Vague "supported DoD programs" answers do not survive follow-up.
Format fluency under probing. You should be able to describe the difference between a SITREP and a commander's update brief, or explain why a WAR bullet gets rejected, without hedging.
Rubric thinking. Screeners look for whether you can convert taste into criteria — thresholds, weights, examples of near-misses — rather than only asserting that something reads wrong.
Judgment on compliance. Handling of markings, OPSEC, PII, and the line between authentic style and disclosing anything real matters here more than on most writing projects.

Logistics

Contractor engagement, fully remote, US-based only. Work is asynchronous with defined batch deadlines; most contributors treat it as part-time alongside other commitments, though throughput expectations tighten during review sprints. Observed pay for this listing has been $40–60/hr, typically banded by seniority and format breadth — as reported, not guaranteed. No prior AI or ML background is required or expected.

What they look for

military writing
federal documentation standards
report generation and evaluation
grading rubric development
written and verbal communication
department of defense procedures
collaborative remote work
compliance best practices

Before you apply

Would you pass this screen?

Drawn from what this listing actually requires. Answered in your browser — nothing is sent to us, and we do not store your answers.

Have you spent at least 3 years producing staff writing outputs (such as WARs, SITREPs, executive summaries, or similar reports) in a Department of Defense or federal military role?
DoD staff writing experience · required
Have you served in one of the six branches of the U.S. military or in a federal DoD position?
U.S. military background · required
Are you a U.S. citizen or authorized to work in the United States, and do you reside in the United States?
U.S. citizenship and location · required
Do you have practical experience producing DoD or federal briefings, reports, or summaries using PowerPoint, Excel, Word, or similar back-office tools?
Back-office tool proficiency · preferred

0 of 4 answered

Included with this listing

Interview prep — 11 questions

Matched to what this platform's screening actually measures. Answer each out loud in 60–90 seconds: claim → concrete example → implication.

What it tests: Whether the candidate has hands-on experience authoring the actual report formats the project needs, not just familiarity with their existence or structure.
A strong answer: The answer should name a concrete scenario (unit, timeframe, operational context), describe the specific sections and data types included (e.g., personnel status, mission progress, resource constraints), and explain the judgment calls made about what to emphasize for the intended audience and classification level.
Where people lose it: Candidates often describe reading or reviewing reports instead of writing them, or speak in generic terms about 'reporting standards' without anchoring to an actual document they produced under real DoD conditions.