States more explicitly that these are open-ended questions

Author: Martini Arialdo

README.md

@@ -7,11 +7,15 @@ I started writing down this list for a very personal goal, as a reminder of topi
 
 I'm not a big fan of asking technical questions in job interviews: I'd rather prefer to sit together with candidates in front of some real code, facing a real problem, and have a full day of pair programming rotating with all the team members. Yet, some technical questions could be used to start a deep and nice conversation, and this can be useful to get a deeper knowledge of each other.
 
-This repo contains a number of backend interview questions that can be used when vetting potential candidates. It is by no means recommended to use every single question here on the same candidate (that would take hours). Choosing a few items from this list should help you vet the intended skills you require.
+This repo contains a number of backend interview questions that can be used when vetting potential candidates. It is by no means recommended to use every single question here on the same candidate: that would take hours, and would have no sense at all, as they cover a too broad set of topics no single developer would probably have such a broad knowledge. Choosing a few selected items from this list should help you vet the intended skills you require.
+
+** Note** Most of the questions are open-ended, and they just don't have a **right** answer. On the contrary, they are intended to be used as the starting point for a conversation that hopefully tell you more about the person's capabilities than a straight answer would.
+
+Again, I stress that just asking questions is hardly sufficient. Complete the interview with a long pair programming session with your candidates: it is one of the best opportunities to know each other's style and approach and to let candidates know some details about their future day job.
 
 This project is admittedly inspired by [Front-end Job Interview Questions](https://github.com/darcyclarke/Front-end-Developer-Interview-Questions) by [@darcyclarke](https://github.com/darcyclarke)
 
-**Note:** Keep in mind that many of these questions are open ended and could lead to interesting discussions that tell you more about the person's capabilities than a straight answer would. Again, I stress that just asking question is hardly sufficient. Complete the interview with a long pair programming session with your candidates: it is one of the best opportunities to know each other's style and approach and to let candidates know some details about their future day job.
+
 
 
 ### Where are the answers?