Work that gets finished
Projects have a defined end and a proper handover. You see the result of what you built.
Careers at Inovex
No openings right now, but read on
We hire a few people at a time, when the work needs them. If this page sounds like you, we would still like to hear from you.
No vacancies right now
We do not have an open role at the moment. When we do, it will be listed here first, and people who have already written to us hear about it before it goes anywhere else.
If you are an engineer, administrator or delivery lead who likes finishing things, send a short note about work you are proud of. A person reads every one.
Working here
What the job is actually like
Senior colleagues within reach
You work next to people who have done this for years and will explain their reasoning.
Remote-first, with overlap
Work from where you work best. A few shared core hours mean nobody waits a day for an answer.
Breadth across the stack
Code, cloud, security and support sit in one team, so you can learn the parts next to yours.
Time to do it properly
Estimates include testing and documentation. Nobody is asked to skip them to hit a date.
On-call that is fair
24/7 cover is shared on a published rota, with time back after a rough night.
Who we look for
Five habits we look for
Skills can be taught. These are harder to teach, so we hire for them.
- 01You write things down
Decisions, runbooks, handover notes. If it only exists in your head, it does not exist.
- 02You say when you are stuck
Early and plainly. A problem raised on Monday is cheap; one raised on Friday is not.
- 03You finish the boring part
Tests, cleanup, the last ten percent. That is where most of the value is.
- 04You explain without jargon
Clients should understand what you did and why, without needing a glossary.
- 05You care what happens after
You build things expecting to support them, because you might.
Application process
How hiring runs, step by step
- 01Application review
We read what you send. If your experience lines up with what we need, you hear back either way, because a rejection with a reason beats silence.
- 02Initial interview
A video call about your background, what you have shipped and what you want to be doing in two years. Bring questions; we would rather answer them now.
- 03Technical assessment
For most roles, a scoped exercise or a walk through work you have already done. Time-boxed, relevant to the job, and never unpaid work we would otherwise bill for.
- 04Team interview
You meet the people you would work with day to day, and they meet you. Both sides are deciding at this point.
- 05Offer and onboarding
A written offer with the terms spelled out, then a structured first month: a real project, a named person to ask, and clear expectations for ninety days.
Day to day
What a normal week looks like
Client work
Most of the week is spent on one or two engagements, with the same team and the same client contacts.
Support rota
A share of service desk or on-call time, so everyone knows how the systems behave in real use.
Learning time
A few hours for certifications, reading or improving internal tools, booked like any other work.
Be first in line for the next role
Send a note now and you will hear about the next opening before it is advertised.