Context before action
You should understand the service, user and constraint behind the ticket — not inherit a queue with the meaning removed.
Careers / Work with Aevis
Join a technology practice that values calm operations, clear decisions and useful outcomes. The work is complex. The way we work together should not be.
The employee promise
Good technology work needs context, trust and enough space to think. We are building an environment where quality is expected and the conditions for it are taken seriously.
You should understand the service, user and constraint behind the ticket — not inherit a queue with the meaning removed.
You join a discipline with peers, patterns and people to ask, even when your day-to-day work is embedded with a client.
Development is connected to delivery: pairing, reviews, ownership and time to turn experience into reusable knowledge.
Role scope, decisions and feedback should be explicit. Ambiguity in the work is real; ambiguity about where you stand should not be.
Open roles
Search by role or capability, then narrow the register by discipline and working pattern. Every opening leads to a complete role brief.
Openings appear here as they are published. In the meantime, tell us which practice interests you and we will get in touch when something fits.
How work feels here
The operating model matters as much for a team as it does for a client. These are the habits that make independent work sustainable.
The people closest to the work have room to decide, with a named outcome and an understood boundary.
Important choices do not disappear into meetings. The reason, owner and consequence remain available to the next person.
Peers question the work to strengthen it. Feedback should be direct, specific and safe to use.
Learning from delivery only matters when the next delivery changes, so practice work is planned rather than left to spare time.
What supports you
The employee experience focuses on the conditions that make strong work repeatable.
Time to review patterns, teach, learn and improve the system around delivery.
A development path tied to the capabilities you want to build and the work available.
Hybrid, remote or client-site expectations stated on the role before you enter a process.
Useful conversations throughout the work, not a verdict stored up for an annual meeting.
Hiring process
You should know what each conversation is meant to establish, who you will meet and what happens next. The process is designed to finish in four purposeful stages.
Thirty minutes with our talent team to compare the role, your experience and what you want next.
A working session with people from the discipline, grounded in decisions you have made rather than trivia.
A concise scenario discussed live. We are interested in how you frame the work, not unpaid production output.
Scope, team, ways of working and offer are made explicit so both sides can make a considered decision.
Candidate questions
Apply for the work that fits best. If another opening is a stronger match, the talent team can discuss it with you rather than making you restart.
The four-stage shape is shared, but the practice conversation and exercise change with the role. Any variation is explained before you invest time in it.
The working pattern is stated on each role because it differs by team and client context.
Talent community
Tell us which practice interests you and we will get in touch when the work matches.