How to choose from multiple developers and what to do about risks?

Question

Project management

The developer left the current project. There are 3 candidates, according to the technology stack described in the resume, they are suitable. How to choose the most qualified among them? And then every frog praises his swamp ...
And most importantly - the risks. Even if I sign a non-disclosure agreement, which prevents one of them, having gained access to the server, from stealing the project, screwing up something, taking control of the project, etc. etc.? What is usually done in such situations? How to control the introduction of the developer into the project and its subsequent actions?

Answer 1

There are 3 candidates, according to the technology stack described in the resume, they are suitable. How to choose the most qualified among them?

If I understand correctly, those. a specialist of a higher level did not interview them - you can spread them out on tarot cards, or toss a coin)) Only on the basis of a resume can you make the most basic selection. Whether the candidate is suitable - can only evaluate those. specialist.
The project code itself is useless. Yes, it can bring joy and blah blah blah, but without the work of marketers, SEOs, content specialists, and people who directly perform the services of your project, these are just lines of code, nothing more.
Do you know people who have never made mistakes?)) In order not to screw up, there is a set of measures: version control, development only on a local machine, auto testing, code analyzers, automatic database migrations, CI systems, etc. If all your work is done on a production server - do not be offended, but your project is shit from the inside.
Are you kidding?)) If the programmer does not have the rights to work with the code, he will not be able to execute it. It's like putting a straitjacket on a driver and putting him behind the wheel.
In any case, you are associated with risks, draw up a contract correctly. Pay a decent salary and on time. Trust his decisions on the implementation of the code, for this, in fact, you hired him.
Do not put a bunch of managers over him - there will be no profit from this.
Do not evaluate his work by what he does directly (writing the code itself is usually only 10% of the working time, the rest is mostly "thinking"), evaluate the result.

Answer 2

1. These are normal business risks. Draw up the correct contract, so that if anything, you can actually go to court and win.
   
2. Gather more information about the developers. Freelancers now google very well and you can find, in addition to the work performed, also reviews of past employers.
   
3. Give out for starters only some part of the work, so that you can evaluate the result.
   

Answer 3

You can also take a person to your office. Get acquainted, do a couple of interviews, talk for the family, get to know his friends. Then in case of code theft or something else, you can find and hang.