A movement for displaced engineers
The layoffs have scattered thousands of skilled engineers into the wind. But though we are masterless, our skilled blades can still be of use.
The Moment
AI-driven automation. Overcorrected hiring sprees. Macroeconomic whiplash. The industry that once absorbed every ambitious programmer now discards them by the tens of thousands.
The traditional path — send résumés, wait for recruiter calls, compete with hundreds for each surviving role — has become a lottery with terrible odds and months of demoralizing silence.
While we can continue to search for powerful lords, we can weild the tools to help others. Because while engineers are being shown the door, the institutions that run our cities are drowning — in legacy software, opaque budgets, and decisions made without technical literacy at the table. While we wait out the storm, we can help.
"The ronin who wanders without purpose is merely masterless. The one who walks into the village — and asks how they can help — has learned to be the master of self." — The premise of this movement
The Village
Every city, county, and municipal district is struggling with problems that engineers solve before breakfast. Most have no one to ask.
City budgets are public documents. Most citizens — and many council members — cannot parse them. A skilled engineer can build dashboards, automate anomaly detection, and surface the story the numbers are telling.
Permit portals built in 2003. 311 systems that crash on mobile. Water billing code no one understands. Cities run on software that a junior engineer could modernize in an afternoon — but there is no junior engineer in the room.
Municipalities collect enormous datasets — crime, traffic, permits, utilities — and do almost nothing with them. Analytical skills that corporations pay six figures for can transform civic decision-making.
Ransomware attacks on cities have become routine. Most small municipalities have no security posture at all. A few hours of honest audit work can protect critical public infrastructure.
Find Your City
Most city council meetings are open to the public and include a "public comment" period. You do not need an appointment. You need five minutes and something useful to say.
Municipal codes and meeting agendas for thousands of US cities and counties.
Legislative data for all 50 US states — bills, votes, lawmakers, and schedules.
The professional org for city/county managers. A direct channel to the people who run municipal operations day-to-day.
Covers tech initiatives and RFPs across state and local government — good signal for where help is needed.
Open-source projects from US federal agencies. A starting point for understanding government software culture.
An existing network of civic tech brigades in cities across the country. Find your local chapter and plug in.
Ways to Serve
Walk in with one of these proposals. Each is concrete, bounded, and delivers visible value quickly — which is how you earn the next conversation.
Offer to parse the annual budget and build a plain-language summary or interactive dashboard. Most council members will be quietly relieved. Ask for the PDF and a two-week timeline.
Request a 30-minute walkthrough of public-facing digital services: the city website, permit portal, payment systems. Deliver a written findings report with prioritized, actionable recommendations.
Offer a volunteer security posture review — phishing exposure, patch levels on public-facing systems, MFA adoption. Frame it as a gift, not a critique. Deliver findings privately to city leadership first.
Ask what datasets they have but never analyze. 311 call logs, traffic incident data, permit turnaround times — these tell stories that can shift budget priorities and improve services.
City IT contracts are often written by vendors for vendors. Offer to review upcoming RFPs or evaluate bids. A few hours of expert review can save six figures in bad purchases.
Sit in on vendor presentations and help council members ask the right questions. A technically literate advocate in the room changes every conversation with a sales team.
The Exchange
Volunteer work opens doors. Contract work and bounty micropayments keep them open — and let both sides plan around real commitments.
How Bounty Micropayments Work
City describes a specific, verifiable task. Sets a payment amount. Posts it publicly on a bounty board or GitHub issue.
An engineer claims the task, does the work, and submits a pull request or deliverable for review.
City staff (or a designated technical volunteer) verifies the work meets the stated criteria.
Bounty releases automatically (crypto) or via a purchase order. No RFP. No six-month procurement cycle.
Join the Movement
You were not laid off. You were freed — to do work that actually matters to the people who live where you live.
The three commitments of a wandering engineer
I will show up to one public meeting this month and listen before I speak.
I will offer one concrete deliverable before I ask for anything in return.
I will share what I learn so the next wanderer walks in a little less alone.