Join us
Write software that matters, from Kinshasa.
We do not hire often, and we never hire in a hurry. But we read every speculative application, and we have created a role before for someone we were not looking for.
Open roles
No open roles today.
That does not mean you should not write.
Our hires almost always come from an application received months earlier and kept on file. If your profile speaks to us we will come back to you — sometimes long afterwards, and we will tell you plainly if it is a no.
Internships
We take interns, and we put them to work.
An academic placement required by your institution, or a professional internship on your own initiative: either way you leave with code in production and a certificate that says what you actually did.
Academic placement
For students whose course requires a formal placement. We sign the agreement, appoint a supervisor, and complete your institution's paperwork on time.
Professional internship
For those who want to learn the craft outside any course. Length is agreed according to your availability and what you want to pick up.
What you will actually do
- Code that ships to production, reviewed line by line by a developer on the team.
- One feature you own from start to finish, not scraps of other people's work.
- A visit to a client site, to meet the people who use what you write.
- A weekly code review, run to teach rather than to police.
What we do not promise
Neither guaranteed payment nor a job at the end: that depends on timing and budget, and we would rather say so upfront. That said, several people on the team started here as interns.
How to apply
Write to us with your institution, the period you want, the length your course requires if any, and above all what you have already built — a class project counts, even an unfinished one. We answer every request.
Apply for an internshipWorking here
What is different from elsewhere.
Your platforms serve real people
Three hundred and fifty thousand students depend on what we write. When an examination board goes down, it is not a ticket: it is a session at a standstill.
You see the outcome
There are twelve of us. Nobody builds a feature without knowing who it is for, or without spending a day on the client's site.
Constraints you will not find elsewhere
Making an application work without internet, on an old phone, through a power cut in the middle of an examination board. You do not learn those problems from a tutorial.
You are allowed to learn
Systematic code review, not to police but to pass on. The youngest people on the team joined with no professional experience.
How it goes
Three steps, not ten.
A one-hour conversation with no trick questions. We want to understand what you have already built and what you want to learn.
A short exercise on a real case from our projects, done at home in a few hours. We never ask for free work we could use.
Half a day with the team in our offices. You see how we work, you meet the people you would work with, and you get to decide too.
We answer every application, including to say no. It takes us time, but being met with silence after applying is something we do not want to inflict on anyone.
Profiles that interest us
Applying
A CV, and a few lines about something you have built that you are proud of. The rest we will talk about in person.
contact@enywork.com