We are building the teamthat community colleges deserve.

Kenii is a small team building modern software for an institution that has been sold legacy tools for too long. We are growing deliberately, in step with the colleges we serve, and we hire people who want to build something real rather than something big for its own sake.

We would rather grow at the speed our customers trust us than the speed a headcount slide demands.

Small on purpose, for now.

Who we build for

The most overlooked institution in higher ed software.

They serve the most students

Community colleges enroll more students than any other sector of higher education, and they do it on the leanest staff and the tightest budget in the industry. The software market has not kept pace with what they actually need.

They were sold the wrong tools

The catalog and curriculum platforms built for large research universities got resold to community colleges at university prices, with university complexity, hosted on somebody else’s server. We think that trade was never fair.

They are where mobility happens

A community college catalog is often the first real decision a student makes about their future. Get that page right, on the college’s own site, in language a working adult can act on, and the impact compounds for a whole region.

People who would rather ship
than talk about shipping.

Kenii is still a small team, which means everyone here writes code, talks to customers, or both. We look for people who can hold a real institution’s problem in their head, build the smallest thing that solves it, and put it in front of the college fast enough to learn something.

People who take a coordinator’s
time as seriously as we do.

Every feature we ship touches a catalog coordinator publishing on a deadline with no developer on call. We hire people who design and build with that person in the room, not an abstraction of them.

The team today

Small, direct, and close to the customer.

Everyone talks to a real college

There is no layer between the people who build Kenii and the people who use it. Product decisions get made after a conversation with a coordinator or an administrator, not a roadmap meeting in isolation.

North Carolina roots, built with a partner college

Kenii was built alongside a real community college from the start, not designed in a vacuum and pitched afterward. That habit, building with a customer rather than for one, stays as we grow.

We hire for the next stage we are actually in

We are not staffing up ahead of a growth curve we are hoping for. We hire when a real need shows up, for a role we can describe honestly, on a team small enough that the work you do is visible.

Right now

We do not have open roles posted today.

Kenii is growing in step with the colleges that run it, so hiring happens in bursts tied to real demand, not on a fixed calendar. When a role opens, it will be specific, honestly described, and posted here first. If you want to build modern software for community colleges and do not see a fit yet, reach out anyway. We keep a short list and go back to it first.

Want to build thiswith us?

Send us a note about what you would want to work on and why community colleges. We read every message ourselves, and if nothing is open today, we will tell you honestly and keep you in mind for what is next.