Job search
Paragon Policy Fellowship Review: Unpaid Remote Projects, Weekly Hours, and Government Partners
Assess Paragon’s unpaid remote policy projects through current intake notices, government partner deliverables and two complete fictional work-and-time records.
Paragon Policy Fellowship is worth investigating if you want to turn technical knowledge into policy research for a state or local government partner and can afford a substantial unpaid commitment. Its Fall 2026 description specifies an unpaid, fully remote volunteer fellowship with 8–10 hours of work per week. The published arrangement is volunteer policy research; a government partner is not identified as your employer, and the deliverable need not be production software.
Check the intake before preparing an application. On October 22, 2026, the official Students page displayed “Applications are currently closed.” LandOffer publishes this review and also operates a job-search platform. The worked examples below are fictional planning exercises, not fellow testimonials, admission decisions or government recommendations.

Current availability: closed means prepare for a future notice
The Students page still describes the Fall 2026 cohort while marking applications closed. Its timeline FAQ describes three semester-based cohorts: spring from late January to early May, summer from late May to late August, and fall from late September to late December. It says application windows open roughly two months before a cohort starts.
That general calendar does not establish the next cohort's exact application dates. Do not calculate a deadline and present it as announced. A previous application link or description of fall projects also does not show that late submissions are accepted. Read the current notice again when deciding whether to apply.
The closed window leaves useful preparation work: read completed projects, test whether you enjoy policy writing and map the time you can actually protect. We did not create an account, submit a form, contact staff or join a mailing list for this review.
Remote work includes scheduled obligations
The time-commitment FAQ distinguishes synchronous meetings, workshops and presentations from research and writing completed asynchronously. It says fellows must accommodate government partners' and supervisors' working hours, team coordination and firm deadlines. It specifically asks applicants to consider whether they can attend meetings during business hours.
Eight to ten hours is therefore a weekly planning range, not a promise of work you can always do late at night. The same FAQ says hours can fluctuate around deadlines and presentations. For a future cohort, request the mandatory meeting slots and time zones, response expectations and a concrete account of how teams handle a deadline week.
Paragon compares the commitment to a two-credit professional seminar. That is a workload analogy; it does not establish that your university will grant credit. If course credit matters, obtain your institution's own approval and requirements. Remote participation can remove commuting while leaving substantial coordination and preparation costs.
What fellows produce for government partners
The program describes small project teams with a Project Lead and staff coordination. Fellows research a partner's policy question and draft deliverables. Published components include a literature review, demographic analysis, a midpoint presentation, final deliverables, a final presentation and a project brief for publication. Bootcamps and workshops cover policy analysis, writing, project scoping and related skills.
This work can use technical judgment without involving production code. You might compare approaches, explain operational constraints, assess evidence or turn interviews into a recommendation. Knowing whether you will research, draft, present or implement helps you choose the evidence you want to develop for your next role. Ask what your contribution would be before assuming the fellowship supplies a software portfolio project.
The government-partner page describes pro bono work with state and local government and asks partners to meet virtually with teams every two weeks to provide direction and feedback. That is the organization's published operating model. It is not evidence that a particular fellow becomes an employee of the partner, receives a paid internship or has authority to implement a recommendation.
Read an actual brief for its evidence boundaries
Paragon's Summer 2026 Fort Collins project brief describes an assessment of digital-service access and AI suitability. Its methods included secondary research, service-page walkthroughs and evidence from city staff and city data. Importantly, it says planned resident focus groups did not take place; resident experience was represented through staff and city data, with single-source observations flagged for verification.
The reported deliverables included a resident-access assessment, an AI-suitability assessment and a general evaluation framework. The brief also identifies further validation work. These are useful examples of a policy product's reasoning and limitations. The brief supports describing the team's reported work and its stated limits. We did not independently verify city adoption, resident outcomes or each fellow's contribution.
The project directory is a starting point for understanding subject matter. A past partner or project is not a current assignment menu. Use the project question, evidence, limitations and delivered work to judge its learning value. Keep later employment outcomes unresolved.
Published participation and selection rules
Paragon's general criteria list enrollment in a degree program or graduation within the last year, primary residence and authorization to work in the United States, the weekly commitment, and interest in technology policy and civic innovation. It says prior technology-policy experience is not required. Read the current full requirements and official guidance rather than inferring participation rules from the word “volunteer.”
This review does not determine anyone's educational admission, work authorization or personal eligibility. The fictional examples do not assign a protected identity, immigration status or selection outcome to their subjects. Questions about an individual's circumstances belong with the program and an appropriate qualified adviser.
The application FAQ describes non-rolling review: submitting earlier in the window does not provide an advantage under that stated process. It also describes a finalist Group Trial, a mock policy assignment completed collaboratively over three or four days, taking about seven to nine hours in total. Selection considers effort, engagement and asynchronous collaboration; Project Leads are also assessed on leadership and project management.
Treat that trial as additional selection effort, not confirmation that you have joined a cohort. Check the next intake's actual instructions before reserving dates or assuming the same format will continue. This review completed no trial or assessment.
Worked example: a complete, bounded policy note
Jo is fictional and wants to practice translating technical observations into a useful brief. The setting is an invented municipality's public workshop directory, not a real Paragon partner or a site we tested. All three page descriptions below are stipulated toy facts. Jo has no application or assignment.
| Toy evidence item | Observation in the example | What remains unknown | Implication for a draft |
|---|---|---|---|
| Workshop overview | Shows the event date and venue, but no update owner | Who maintains the page | Ask for an accountable owner before proposing a process |
| Registration page | Includes a registration link without an explanation of confirmation | What a registrant receives next | Describe the information gap; do not invent a failed registration rate |
| Help page | Lists a contact address without a response window | Actual staffing and response practice | Seek staff confirmation before publishing a service expectation |
Jo completes the following short policy note:
Decision requested: Approve a limited review of workshop information ownership and registration explanations. Evidence: The three stipulated pages show missing ownership, confirmation guidance and response expectations. These observations establish gaps in published information; they do not establish how many people are affected. Options: Leave the pages unchanged, revise the three pages with staff-approved information, or build a new portal. Recommendation: Confirm the process with the service owner and try a small content revision before scoping a portal. Owner and review: A designated page owner should approve wording and maintain an update date. Evaluation: Review whether the revised pages accurately explain the confirmed process, then obtain feedback on usefulness. No usage improvement is claimed from this example.
Their handoff memo reads: “I drafted the evidence table and options note from the supplied toy pages. Staff confirmation and user feedback remain missing. I did not interview residents, operate a public service or establish legal compliance.” That is a complete practice asset with a limited claim of authorship. It offers material to discuss in a policy interview without pretending it was government work.

Worked example: an honest weekly and total time budget
Maya is fictional and is considering a future unpaid cohort. Their eligibility and any selection remain unresolved. The following is an illustrative twelve-workweek plan, not the published Fall 2026 calendar or an assigned schedule.
| Work category | Ordinary weekly hours in Maya's plan | Constraint recorded |
|---|---|---|
| Team and partner coordination | 1.5 | Needs a feasible business-hours slot, not just an empty evening |
| Workshop or presentation preparation | 1.0 | Actual mandatory schedule is unknown |
| Reading and evidence notes | 2.5 | Requires uninterrupted time to assess sources |
| Writing and revision | 3.0 | Includes responding to feedback, not only a first draft |
| Team handoff and administration | 1.0 | Must leave a clear record for asynchronous collaborators |
| Total | 9.0 | Within the published ordinary 8–10-hour range |
Nine hours multiplied by twelve weeks is 108 hours. Adding an assumed eight-hour finalist trial gives 116 modeled hours. The eight-hour assumption sits within the published seven-to-nine-hour trial range; it is not an actual invitation or recorded participation. At the broader stated ranges, twelve weeks of eight to ten hours plus a seven-to-nine-hour trial would total 103–129 hours, excluding initial application preparation.
Maya also models one deadline week with three additional hours of revision: twelve hours that week and 119 modeled hours overall if only that week changes. This exceeds their ordinary nine-hour plan, which is why the published warning about fluctuations matters. They identify three hours of an optional personal project that could move temporarily, while keeping fixed study, work and rest commitments intact. If that flexibility disappeared, the plan would need revision.
For an opportunity-cost comparison only, 116 hours at a hypothetical available paid rate of $18 would equal $2,088. That is neither a Paragon wage nor proof that Maya could obtain paid work for those hours. It is a way to compare uses of limited time; the fellowship's published Fall 2026 compensation remains unpaid.
Maya's completed decision memo is: “Do not budget fellowship income. Keep the nine-hour plan provisional until mandatory meeting slots and peak-week expectations are known. A project with useful feedback could justify the time, but I cannot spend the same hours twice. Revisit the next published intake and choose whether the documented schedule and learning objective fit.” Their next step is preparation, not a late application to the closed cohort.
Keep support, paid fellowships and employment separate
Paragon advertises workshops, speakers, networking and alumni opportunities. Its separate mentorship program describes a four-month arrangement for current or former fellows, with matching based on interests, goals and availability and a minimum one-hour monthly commitment. At our check, that page also said applications were closed. Do not treat a fellowship description as an already assigned mentor or job referral.
A different program can have a different work arrangement. TechCongress's Congressional Innovation Fellowship, for example, describes a congressional policy fellowship with a stipend. Those terms do not transfer to Paragon, and stipend support alone does not establish ordinary government employment. Compare each route's duties, location, intake and funding on its own terms.
Paragon is most useful to investigate when you specifically want supervised policy research and a candid account of your contribution, and can support the unpaid time. If your next commitment must provide income or production engineering work, compare those requirements directly with each job description and compensation arrangement. You can browse recent roles on LandOffer.ai while evaluating which kind of work your next commitment should provide.
Sources and Further Reading
Official public pages checked October 22, 2026. No application, assessment, account, partner contact or private information submission was made.
- Paragon Students: closed intake, Fall 2026 unpaid terms, public criteria, timeline, selection and time-commitment FAQs.
- Government partners: pro bono model and partner feedback expectations.
- Project directory and Fort Collins brief: prior work and stated evidence limits, not verified employment outcomes.
- Mentorship program: separate participation conditions and closed notice.
- TechCongress fellowship description: contrasting congressional policy and stipend arrangement.


