The degree we require
Every developer in the pool holds a bachelor's degree in computer science, software engineering, or a closely related program such as systems engineering, from a university. We verify the credential before a candidate is introduced to you.
The degree is a consistent filter across Ecuador, Colombia, and Peru, where job titles and bootcamp paths vary. It is how we keep the pool comparable. It is not a claim that a diploma replaces years of shipping software.
What we check besides the diploma
English has to carry a standup, a Slack thread, and a pull request description. We screen for that before you spend time on a call. We also match the stack you named, so a Python API role is not filled with a frontend profile that merely lists Python.
Seniority on the rate card follows the kind of responsibility the person has held. Mid-level means they can ship a well-specified feature. Senior means they can own the design of the work and be the only engineer in that seat.
What you check yourself
You interview the shortlist on video. Communication, taste, and whether you want this person in your standup are your decision. We do not skip that step and assign someone you have not met.
A sample profile on the site shows the shape of a match. It is an example, not a promise that a specific named person is waiting. The shortlist you receive is built for your stack and your term.
If the screen was wrong
The first 14 days are the practical test. If the degree, the English, or the skills are not what you were shown, we replace the developer at no extra charge.
Use that window. A contract that runs six or twelve months should start with a person you have both interviewed and worked with.