Careers
Klyvant is building a senior team where nobody is a resource on a plan. If you have spent your career being handed other people's designs to implement, this is the other side of that.
The premise
The company runs on a structural promise to clients: the person who scopes the work is accountable for it running. That promise only holds if the people making it have personally lived with the consequences of a bad architecture decision.
So the hiring bar is frontline experience rather than credential count. We would rather have someone who has restored a production platform under pressure than someone who has read extensively about doing it.
In return the work is unmediated. You talk to the client, you hold the technical position, and you are not asked to defend a recommendation you did not make.
Open positions
These are the functions being built out as the practice scales. Each is a single accountable position rather than a seat in a team.
We read speculative applications properly, because the roles above are the ones we have written down rather than the only ones we need. If you are a senior infrastructure, recovery or energy engineer, send what you have worked on and what went wrong on it. That second part is the more useful half.
What the work is actually like
Client conversations are not filtered through an account manager. You hear the constraint directly, which is also why you cannot blame the brief afterwards.
Every engagement starts with discovery that contradicts the asset register. If undocumented infrastructure frustrates you rather than interests you, this will be a long few years.
Recommending the incumbent platform, or refusing a cutover date, is part of the job. The company only works if the people doing it are willing to hold that line.
Cutovers land at night and at weekends because that is when the operation can absorb them. It is not constant, but it is real and we would rather say so now.
Terms