Java Senior Developer
For someone with years of building enterprise systems who wants to use AI to go further, not just to do the same thing faster.
Open positions come and go.
What does not change is that we always want to meet good developers.
Building software today looks nothing like it did two years ago. We use AI across the whole cycle: design, code, review and testing. That moved where the hard work actually is. Writing the lines stopped being the bottleneck. Understanding the client's domain, choosing an architecture that will hold up for years, and reviewing what gets produced with real judgement matter more than ever.
So when we look at a CV, the list of technologies is what tells us the least. We care more about how you think, how you approach a problem with no obvious answer, and how comfortable you are learning something that did not exist last week.
We look for people who care about the problem, not just the tool. Who can say "I don't understand this yet" without it costing them anything. Who can read someone else's code, generated or not, and spot what is wrong before production does. And who want to get into whatever comes next: two years ago nobody had experience wiring language models into enterprise applications, and today it is a good part of what we do.
English helps, quite a bit: we work with clients and with the open source community abroad.
These are not job ads. They are the profiles we most often hire for, so you can tell whether it is worth writing to us.
For someone with years of building enterprise systems who wants to use AI to go further, not just to do the same thing faster.
For someone starting out who wants to learn to build enterprise software properly, at a moment when the profession is being rewritten.
There does not have to be a posting open. We keep it on file and get in touch when something comes up that fits your profile. If you like, tell us what you have been working on lately and what you would like to do next.
Send my CV