Who We Are Looking For
We hire for judgement more than for a specific framework. Frameworks change every few years; the ability to understand a business problem, choose a proportionate solution and finish it does not.
In practice that means people who can read someone else’s code without complaining about it, who write things down, who say when an estimate has moved rather than hoping, and who care whether the thing they built actually works for the person using it.
We are not looking for heroics. Sustainable pace, tested code and honest status reports produce better software than late nights, and they are also considerably more pleasant.
Roles We Recruit For
- Backend engineers: PHP and Laravel, Node.js, Python, .NET
- Frontend engineers: React, Vue, Next.js, TypeScript
- Mobile engineers: Swift, Kotlin, Flutter, React Native
- DevOps and cloud engineers
- QA engineers, manual and automation
- UI and UX designers
- Business analysts and project managers
- SEO specialists, performance marketers and content writers
- Video producers and motion designers
- Internships for final-year students and recent graduates
How We Work
Two-week cycles, a working build at the end of each one, code review on everything, and a written definition of done. Projects have a named technical lead who is accountable, so responsibility is clear rather than diffuse.
You will work on real client systems rather than on internal proofs of concept: warehouse systems handling thousands of orders, applications used daily by field teams, platforms where a bad release is somebody’s bad afternoon. That is more pressure than a sandbox and considerably more satisfying.
Because we work with clients in Europe and the Gulf, English is used daily. You do not need to be fluent on day one, but you will use it.
What We Offer
Hybrid and remote arrangements depending on the role, a defined career track rather than vague promises, a training budget and time to use it, conference and certification support, and hardware you choose rather than inherit.
We also offer something less common: you will know what your work is for. Every project has an identifiable client with an identifiable problem, and you will hear whether it worked.
How to Apply
Send your CV and, if you have them, links to code, projects or anything you have built. A GitHub profile, a live application or a case study tells us more than a list of technologies.
Our process is short: a first conversation about what you want to work on, a technical discussion based on real problems rather than puzzle questions, and a meeting with the team you would join. We give a decision within a week and we tell you the reason either way.
If there is no open role that fits, we still keep good applications on file and we will say so honestly rather than leaving you waiting.