Summary of a programmer: how to make it comfortable?
Our team is developing a product to search for remote developers. Meaning it is not an analog upWork (ex-oDesk), but rather, Uber: the service for the minimum time is on the project the programmer that is suitable in location, language, competencies and cost.
Developers enter the system undergo a very serious testing procedure and confirm your professional experience: thus on the basis of the service formed a community of top developers who prefer to work remotely, and open to new projects. We make the product for programmers who can be trusted with key projects as platforms for freelancers, small performing non-core tasks exist in sufficient quantity.
Having vast experience of "selection" of developers, we have systemized their knowledge and were faced with the task of the ideal profile of a programmer, really convenient not only to us but to a wider audience.
So...
It needs to be:
a) Reliable and informative for the employer
b) Simple and easy to fill for the developer
In contrast to hiring offline, in our case the customer decides to invite the developer to the project, in fact, guided only by the information in the profile and our recommendation. Service, for its part, guarantees authenticity (check the data on the jobs, projects and tasks conducts in-depth testing of all skills, communication skills in a team of other developers, and confirms the knowledge of foreign languages). informative answers profile structure, on which we work. We in any case do not want to complicate and overload the profile: it needs to be such that it can be easy to fill, quick to evaluate, and in the case of interest – to obtain the necessary additional information.
We analyzed popular online form. They were written not for programmers, so, of course, good for its versatility, but for our purposes correspond to small. We took on the adaptation of the standard questionnaire to the specifics of the IT industry and, in particular, programmers working remotely.
Ultimately, we need to include a profile of 4 main entities:
1. Formal data. Strict criteria, which enables the customer and the contractor to work at a place usually two: time (time zone) and language for workplace communication. Therefore, the profile needs to provide information on where the contractor lives, what hours are suitable to him which language his mother, and what he is able to communicate without any problems.
2. Skills. It should not be excessive the list of languages, platforms, and technologies with which the contractor has ever worked or about which you have read/heard. It is sufficient to choose those that he considers himself an expert, and from them — those with whom he wants to continue to work, and related skills. To display skills in summary we offer a structured form.
3. Experience. The most important section which is very easy to ruin a lack of or excess of information. We propose to list the projects in which the developer has participated, to specify the composition of the team and his role in it, and also to describe exactly what tasks he performed. The most interesting projects can be described more ordinary — just to mention.
Thus, we move away from a standard enumeration of all technologies that relate to or have seen the developer, and a shifting emphasis on its role in the project and cases that seemed interesting to him (i.e. ask you to answer the questions asked by the interviewer in the interview).
4. The code example. Code is the product that ultimately gets the customer a programmer, so his quality and style is often a key criterion when selecting a contractor. In this regard, we believe it is necessary to add to the questionnaire a link to GitHub or the opportunity to attach files with code that the developer is ready to show as your portfolio.
There is also the possibility to insert links to articles on professional resources, as well as to share information about primary and secondary education, courses, trainings received the certificates.
At the moment we have managed to form such a structure that we continue to work:
To make a really quality product, we need your help.
What items you need to add/expand/elaborate on that?
Maybe some items seem unnecessary?
Article based on information from habrahabr.ru
Developers enter the system undergo a very serious testing procedure and confirm your professional experience: thus on the basis of the service formed a community of top developers who prefer to work remotely, and open to new projects. We make the product for programmers who can be trusted with key projects as platforms for freelancers, small performing non-core tasks exist in sufficient quantity.
Having vast experience of "selection" of developers, we have systemized their knowledge and were faced with the task of the ideal profile of a programmer, really convenient not only to us but to a wider audience.
So...
It needs to be:
a) Reliable and informative for the employer
b) Simple and easy to fill for the developer
In contrast to hiring offline, in our case the customer decides to invite the developer to the project, in fact, guided only by the information in the profile and our recommendation. Service, for its part, guarantees authenticity (check the data on the jobs, projects and tasks conducts in-depth testing of all skills, communication skills in a team of other developers, and confirms the knowledge of foreign languages). informative answers profile structure, on which we work. We in any case do not want to complicate and overload the profile: it needs to be such that it can be easy to fill, quick to evaluate, and in the case of interest – to obtain the necessary additional information.
We analyzed popular online form. They were written not for programmers, so, of course, good for its versatility, but for our purposes correspond to small. We took on the adaptation of the standard questionnaire to the specifics of the IT industry and, in particular, programmers working remotely.
Ultimately, we need to include a profile of 4 main entities:
1. Formal data. Strict criteria, which enables the customer and the contractor to work at a place usually two: time (time zone) and language for workplace communication. Therefore, the profile needs to provide information on where the contractor lives, what hours are suitable to him which language his mother, and what he is able to communicate without any problems.
2. Skills. It should not be excessive the list of languages, platforms, and technologies with which the contractor has ever worked or about which you have read/heard. It is sufficient to choose those that he considers himself an expert, and from them — those with whom he wants to continue to work, and related skills. To display skills in summary we offer a structured form.
3. Experience. The most important section which is very easy to ruin a lack of or excess of information. We propose to list the projects in which the developer has participated, to specify the composition of the team and his role in it, and also to describe exactly what tasks he performed. The most interesting projects can be described more ordinary — just to mention.
Thus, we move away from a standard enumeration of all technologies that relate to or have seen the developer, and a shifting emphasis on its role in the project and cases that seemed interesting to him (i.e. ask you to answer the questions asked by the interviewer in the interview).
4. The code example. Code is the product that ultimately gets the customer a programmer, so his quality and style is often a key criterion when selecting a contractor. In this regard, we believe it is necessary to add to the questionnaire a link to GitHub or the opportunity to attach files with code that the developer is ready to show as your portfolio.
There is also the possibility to insert links to articles on professional resources, as well as to share information about primary and secondary education, courses, trainings received the certificates.
At the moment we have managed to form such a structure that we continue to work:
To make a really quality product, we need your help.
What items you need to add/expand/elaborate on that?
Maybe some items seem unnecessary?
Комментарии
Отправить комментарий