Careers
Software where the bugs matter
Most products fail quietly when they are wrong. In lending, a rounding error compounds across three years, a missing audit entry becomes a regulatory finding, and a careless permission exposes somebody’s identity documents. If that sounds like pressure rather than appeal, this is not the team for you.
The work
What you would actually be doing
Backend engineering
Node, Express, MongoDB and TypeScript. Domain modelling, the state machine, the audit trail and the regulatory enforcement layers.
Mobile engineering
Expo React Native for borrowers on mid-range Android phones and patchy connections. Performance work that has an actual user.
Frontend engineering
Next.js for the operations console. Dense, data-heavy interfaces that credit officers use all day.
Product & design
Interfaces for people who are not enjoying themselves — a borrower who needs money, an officer with a queue.
Compliance engineering
Turning directives into constants, tests and controls. Unglamorous, and the reason the product can exist.
Customer engineering
Working directly with partner institutions on configuration, integration and training.
How we work
Correctness first, in a way that is not just a slogan
Every team says quality matters. What distinguishes one that means it is whether the tests can actually block a release, and whether anyone is allowed to skip them under deadline pressure. Here, they can and nobody is.
- Compliance-critical logic ships with tests, or it does not ship
- Architectural decisions written down and numbered, including the reversed ones
- Code review on everything, with the regulatory paths reviewed hardest
- No feature is worth quietly weakening a control for
Honestly
What this job is not
The fastest way to a bad hire is a job description that only describes the good parts.
- Not a greenfield playground — the constraints are real and mostly non-negotiable
- Not a place to try the newest framework; boring technology is a deliberate choice
- Pre-launch, which means uncertainty and changing priorities
- A domain you will have to learn — lending regulation is not optional background
Who does well here
The trait that matters most is care
We can teach the domain. What is much harder to teach is the instinct to check whether the edge case is handled before saying something is done.
- You read the whole function before changing one line of it
- You are comfortable saying “I do not know” and then finding out
- You write the comment that explains why, not the one that restates the code
- You would rather raise a problem early than deliver a surprise late
No formal openings listed right now
We would rather leave this page honest than list roles we are not actively hiring for. If the work described here is what you want to do, write to careers@khepee.com with something you have built and a note on why lending in particular. Speculative applications from people who are clearly interested in the domain get read properly — that is how small teams usually find their best hires.
Process
How hiring would work
You write to us
Something you have built, and why this domain. A CV alone tells us very little.
A conversation
About your work and about the problem, with an engineer rather than a recruiter.
A practical exercise
Realistic, time-boxed and paid if it takes real effort. No unpaid multi-day projects.
Meet the team
Including the people you would disagree with, because that is the relationship that matters.
A clear answer
Yes or no, with a reason, within a week. Silence is not an acceptable response to someone’s effort.
Get in touch
careers@khepee.com
Tell us what you have built and what you would want to work on.