Generalist

About FSH Technologies

FSH Tech builds modern software that just works for the public sector. When we deliver, taxpayer dollars go further, agencies move faster, and millions of Americans get tangibly better service and quality of life.

Local governments, schools, libraries, and emergency services run on brittle software that was built decades ago. This results in wasted budgets, broken workflows, and bad outcomes for the public. We believe that the institutions closest to people's daily lives deserve products as good as anything in the private sector. We're building them.

We're a small, high-agency team. The people who do their best work here are:

• Relentlessly optimistic in creating a better world now

• Driven to have the most impact they can for society

• Brilliant and creative

Role Overview

Every year, we aim to hire a few new grad generalists - people early enough in their careers that they haven't specialized yet, and good enough that we’d love to bet on their slope.

A Generalist at FSH does whatever is most pressing and important. In practice, this comes from three places:

Clients. You'll be in the room with the public servants who actually make cities run. You'll help scope what they need, configure our product to match, write the documentation, and run the training. You will own workstreams and work closely with our Client Strategists.

Growth. Public procurement is a specific and learnable process. You'll help research which agencies should be buying from us, build pipeline, and assemble bid responses that are better than what we (and the incumbents) have submitted before.

Systems. We're a small team serving institutions far larger than us, which only works if our systems are excellent. You'll build those systems. If you find yourself doing something twice by hand, we'd rather you spend the afternoon automating it than the next six months repeating it.

There is no predefined destination for this role. Some will grow into client ownership, some into operations, some into engineering. We don’t know which one you’ll be, and you’ll have an opportunity to experience them all. What we can promise is that you will see very clearly how this business is built, and the ceiling on what you do and own is set by what you demonstrate day-to-day.

What this is not:

• An assistant role

• A support ticket engineering role

What You’ll Need

We don’t care about what school you went to, your GPA, or how many internships you’ve done. We want evidence of the following:

• You've built things. A side project people actually used. An internal tool you made at an internship. A scraper, a bot, a Chrome extension, a mod, a game, a newsletter with real readers, an open source contribution. Send us the links.

• Technical fluency. You can write a script, query a database, read enough code to talk to an engineer, and use modern AI tooling as a genuine force multiplier. You will not be expected to write production code, although if you demonstrate enough engineering skill, you can.

• You write clearly. A large part of this job is explaining things in writing, both to government readers and to colleagues.

• You finish your work. We want to see that you have followed through on unglamorous work after the interesting early parts are over.

• Comfort with ambiguity and a strong bias toward action. We would rather tell you to slow down than to speed up.

Nice to Have

• A CS, engineering, math, or other technical degree — or a self-taught equivalent you can show us.

• Any experience being responsible for a real outcome with real stakes: a startup you tried, a business you ran, a team you led, a competitive pursuit you were serious about.

• Prior internship or work experience in consulting, banking, a startup, or a fast-moving operating role.

• Familiarity with local government, public procurement, or civic technology.

Employees are expected to live in New York City or Philadelphia and work out of our office in either location.