The intro call defines the seat
You talk with Ana Pastor about the stack, the seniority, full-time or part-time, and the term. That conversation produces a quote and a search, not a generic resume drop. If the role is a poor fit for the pool, you hear that on the call.
Bring the tools you use and an example ticket. A clear picture of the first month of work makes the shortlist sharper.
A shortlist, then your interviews
We introduce two or three developers who already passed the degree check and the English screen, and whose experience matches the stack. You meet them on video. You are choosing a teammate, so the interview is a normal technical and working-style conversation.
This is the step that most often sets the start date. A team that can interview within a few days can have a person in the repo the following week. A team that needs two rounds of committee review will take longer, and that time is on the calendar you control.
The contract, then the first day
When you choose someone, we send the contractor agreement. It covers IP, confidentiality, the hours, the term, and the rate. After it is signed, the developer joins the Slack, the board, and the repositories you open.
The first 14 days are the replacement window. Use them to give a real task. A good match is visible quickly when the person is in your tools and your hours.
What 'days, not months' assumes
The phrase on our site means you are not opening a local req, waiting on applicants, and running a six-week process for one seat. It assumes you can describe the role and attend the interviews.
The pool covers the roles on the site: frontend developer, backend developer, full-stack developer, mobile developer, qa engineer, devops engineer. An unusual stack can take longer because the shortlist has to be real, not padded.