Most technology projects fail in the gap between what someone asked for and what they actually needed. The work here is closing that gap early, when it is still cheap to close.
You would sit between the client and the people building, translating in both directions. That means understanding the client’s constraints — funding cycles, procurement rules, the systems they already run, the staff they actually have — well enough to know when a stated requirement is the real one.
What you would work on
Requirements gathering with school districts, nonprofits, municipalities and small organizations, where the person you are talking to often is not technical and does not have time to be.
Documenting current-state environments: what is running, what it costs, what depends on what.
Writing the specification that an engineer builds from and a procurement decision is made against.
Vendor and product evaluation, including reading licensing terms closely enough to find what they actually commit the client to.
Occasionally, helping a client work out whether they need the thing they are about to buy.
What we look for
You can write. Not decoratively — clearly, in a way that survives being read by someone who was not in the room.
You are comfortable saying you do not understand something yet, and then going and finding out.
Some background in public sector, education or nonprofit environments is useful, because the constraints are genuinely different from commercial work.
Familiarity with Microsoft 365, identity, or cloud platforms is helpful but not required. Judgment is harder to teach than tooling.
Other roles
INFRASTRUCTURE
IT Specialist
Hands on the systems. Identity, endpoints, networks, and the day-to-day that has to work.
ARTIFICIAL INTELLIGENCE
AI/ML Engineer
Building systems that use models responsibly inside real constraints.
DATA
Data Scientist
Finding what the data actually supports, and saying so plainly.
Register your interest
No cover letter. We will read it and we will reply either way.