How to make your application count.
We assess every application properly, which takes real time on both sides. This page is what we wish every applicant knew beforehand: what we are actually looking for, how to present your experience, and what happens once you have applied. None of it is a trick, and none of it is hidden from you.
What we are looking for
We are not scoring you against a checklist of technologies. We are trying to work out what you are genuinely good at, so we can match you to work where you will do well.
Depth in one stack, not a list of twenty
We would rather see three years of real work in TypeScript and Node than a profile listing eleven languages. Clients hire for the thing you are genuinely strong at, and that is what we match on.
Work you can talk about
Not every project can be shared, and that is normal. What matters is that you can describe what you built, the decisions you made, and what you would do differently now.
Clear written English
Every engagement is remote and international. You do not need perfect grammar. You do need to explain a technical idea so a teammate in another timezone understands it without a follow-up call.
Finishing things
Shipped, tested, maintained. A smaller project you took all the way through is stronger evidence than a large one you started.
Your application, field by field
The form is short on purpose. Because it is short, each answer carries weight.
The role you are applying for
Choose the one you want to be matched on, not the widest one. Applying as a fullstack engineer when your real strength is backend puts you against a different comparison set and rarely helps.
If you are genuinely split between two, pick the one you would want to be doing in a year.
Years of experience
Count professional engineering work. Do not round up. We assess your level ourselves during the process and set it from what you demonstrate, so an inflated number here only creates a mismatch later.
Skills
List what you would be comfortable being tested on tomorrow. This is used for matching, so a skill you added because it looked good is a skill you may be asked about.
Five you know well beats fifteen you have touched.
GitHub, portfolio and LinkedIn
At least one link that shows real work. A GitHub with a pinned repository you can explain is worth more than an empty profile. If most of your work is private, a portfolio page or a short written description of a project does the same job.
Pin two or three repositories you are actually proud of, and make sure each has a README that says what it does.
Your CV
One or two pages, in English. Lead with what you built and the impact it had, not a list of responsibilities. Include the stack for each role, because that is what we read most closely.
What happens after you apply
You do everything in one place, and you can see where you are at every point. There are four steps: a written and spoken English exercise, a practical technical assessment in our own environment, a conversation with an experienced reviewer about how you build, and a secure identity check.
You are assessed once. You do not repeat it for every client, which is the part most engineers tell us they are tired of elsewhere.
Read what each step involvesWhat usually holds an application back
Worth saying plainly, because most of it is fixable before you press send.
- A profile with no link to any work at all, and nothing written to stand in for it.
- A stated level that the technical assessment does not support.
- Applying for a role well outside the experience described in the application.
- An application written so briefly that there is nothing to assess.
Ready when you are.
Take the time to get your links and CV right, then apply once and properly. We read every application.
Apply as an engineer