John:
IN GENERAL
John is a very competent developer who would operate at fairly senior level in any organisation. He has extensive experience in nearly all of the areas covered. He has experience of Javascript that he is looking to build on and already has a good knowledge of Node.js - a key component of the MEAN course. He is a very good candidate. A firm Yes.
JAVA & OBJECT ORIENTED PRINCIPLES
He was familiar with .war files and what to do with them. he has used strutts in the past and more recently Spring Boot, so was no stranger to frameworks and what they are, however he did not profess to be an expert in Java frameworks. Given the breadth of his knowledge in other areas, and that the prime technology fort this role will be the MEAN software stack, this should not be an issue. He was very familiar with design patterns, and we discussed the disadvantages of this way of doing things. His views were relevant and defensible in the light of current technology. No issues here.
JAVASCRIPT
Most of his experience has been with old fashioned Javascript, but recently he has been learning and becoming experienced with modern full OO Javascript.He has recently used frameworks with this, including JQuery and has been recently learning Angular.js. This places him in an excellent position to expand upon this learning with the MEAN course. He is clearly very keen to do so and very competent.
Uniquely, John has experience of Node.js (server side javascript), he has used it recently and already understands the concepts. This places him far ahead of most candidates for the MEAN course.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
He answered incorrectly in the pre screening, however when we went through this it was clear that he did know the answer after all but did not listen to the question properly the first time around. He was able to explain both TDD and traditional forms of testing in depth. He has extensive experience of unit testing and has done integration testing. There should be no problems here.
AGILE METHODOLOGY
He knows Agile extensively, he is aware of the ceremonies and we discussed each one at length. He has used "proper" agile. He understands both the theory and the practice. There should be not issues from John regarding this. Very good.
RESTFUL WEB SERVICES
John has used REST extensively in his experience of both Java and Node.js. HE knew the answers to all questions put to him, he is aware of verbs and end points and knows how to intelligently apply the concepts he knows. He is exceptionally experienced here.
SOURCE CONTROL MANAGEMENT
He has used subversion and GIT. He was confident answering specific questions regarding GIT commands and the location of repositories with this technology. No problems here.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
He has used jenkins a lot, he is aware of the concepts and regularly creates Jenkins jobs both using the standard Jenkins user interface and using the xml configuration scripts. He could easily take over as the Jenkins admin for any team.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
Is very familiar with this. Has used ant very extensively and has used Maven too but did not profess significant expertise in it. He has used it mainly for only one of its characteristics. This level of knowledge is easily fine for the role. No problems.
CSS + HTML5
He has used CSS and HTML extensively and has touched on some of the newer HTML 5 recently. So only marginally better than most here.
John is a very competent developer who would operate at fairly senior level in any organisation. He has extensive experience in nearly all of the areas covered. He has experience of Javascript that he is looking to build on and already has a good knowledge of Node.js - a key component of the MEAN course. He is a very good candidate. A firm Yes.
JAVA & OBJECT ORIENTED PRINCIPLES
He was familiar with .war files and what to do with them. he has used strutts in the past and more recently Spring Boot, so was no stranger to frameworks and what they are, however he did not profess to be an expert in Java frameworks. Given the breadth of his knowledge in other areas, and that the prime technology fort this role will be the MEAN software stack, this should not be an issue. He was very familiar with design patterns, and we discussed the disadvantages of this way of doing things. His views were relevant and defensible in the light of current technology. No issues here.
JAVASCRIPT
Most of his experience has been with old fashioned Javascript, but recently he has been learning and becoming experienced with modern full OO Javascript.He has recently used frameworks with this, including JQuery and has been recently learning Angular.js. This places him in an excellent position to expand upon this learning with the MEAN course. He is clearly very keen to do so and very competent.
Uniquely, John has experience of Node.js (server side javascript), he has used it recently and already understands the concepts. This places him far ahead of most candidates for the MEAN course.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
He answered incorrectly in the pre screening, however when we went through this it was clear that he did know the answer after all but did not listen to the question properly the first time around. He was able to explain both TDD and traditional forms of testing in depth. He has extensive experience of unit testing and has done integration testing. There should be no problems here.
AGILE METHODOLOGY
He knows Agile extensively, he is aware of the ceremonies and we discussed each one at length. He has used "proper" agile. He understands both the theory and the practice. There should be not issues from John regarding this. Very good.
RESTFUL WEB SERVICES
John has used REST extensively in his experience of both Java and Node.js. HE knew the answers to all questions put to him, he is aware of verbs and end points and knows how to intelligently apply the concepts he knows. He is exceptionally experienced here.
SOURCE CONTROL MANAGEMENT
He has used subversion and GIT. He was confident answering specific questions regarding GIT commands and the location of repositories with this technology. No problems here.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
He has used jenkins a lot, he is aware of the concepts and regularly creates Jenkins jobs both using the standard Jenkins user interface and using the xml configuration scripts. He could easily take over as the Jenkins admin for any team.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
Is very familiar with this. Has used ant very extensively and has used Maven too but did not profess significant expertise in it. He has used it mainly for only one of its characteristics. This level of knowledge is easily fine for the role. No problems.
CSS + HTML5
He has used CSS and HTML extensively and has touched on some of the newer HTML 5 recently. So only marginally better than most here.