Developer Recruiting Guide: “Backend-Developer”
While the word "backend" certainly seems amusing in the job listing, it describes the role very well. This type of developer, unlike the front-end developer, does not work in the front, visible part of the store, but in the back room of the store, but just for software. The work that backend programmers do, writing code, is not visible to users or customers. That is, the code does not affect the user interface (UI), or the part of the software that can be seen.
Backend developers develop code in the form of APIs, or interfaces, which are then used by others, such as front-end developers.
Backend developers typically work with data (stored in files or the database), or APIs, to transform it and make it usable by other parts of the system. These developers are often closest to the system, web services, and hardware.
To recruit for the role of "backend developer," we have prepared three appropriate interview questions:
What strategies connect the back end of a system to the front end?
There is no right answer for this question, yet it should be reasonable. A valid answer could be APIs or callbacks, for example. If you don't know what the term means exactly, ask for an analogy. This will allow you to check the developer's communication skills right away.
How do you choose the right database for your project?
Don't be surprised if a candidate answers that it depends on the project. If this is the case, you can give the candidate an example, such as a website you like and use, or you can narrow down based on other criteria. The candidate should think critically about how the data will be used by the client on the website or in the application.
What is your favorite programming language? - and why?
This question is a good and "safe" opener to start the conversation. It also gives the developer a chance to talk freely about their work experience and preferences, and more importantly, it gives you a chance to gauge how enthusiastic the applicant is. In my opinion, the best developers are those who can passionately explain to you why PHP or Ruby are better suited for certain tasks than others.
