Jamil:
IN GENERAL
Jamil has a solid knowledge of the areas needed, he scored 8 out of 11 in the pre-screening test, when we went through the incorrect questions he needed a little coaching with some of them, nonetheless he is a good solid candidate and he would fit in without any problems as an intermediate developer
The interview was quite conversational and he seemed very enquiring when we came across something he was not aware of. We spent some time on these areas and he always asked appropriate questions when he didn't understand something. In addition it seems he has a keen ability to learn new things and was able to do so quickly and within the framework of modern software development theory. A good sign for the training course. His skills as they stand are fine, however if he wanted to focus on learning more he could do with improving his knowledge of maven and build tools in general.
JAVA & OBJECT ORIENTED PRINCIPLES
Jamil knew the fundamentals of deployment in java and of object oriented principles and uses design patterns on a regular basis. He has used several frameworks including Spring. He is aware of all of the fundamentals and has easily sufficient experience.
He didin't get the hardest question I ask correct (about the persistence of the singleton design pattern) but seemed fascinated when I told him the answer and fully understood the explanation.
JAVASCRIPT
Jamil has used javascript for front end validation. In addition he has used the JQuery javascript framework. This is a good basis for the training course. His knowledge fits into the "old fashioned" category that is true of many of the candidates. He was aware of some of the recent changes in Javascript and it's applicability to wider problems.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
Jamil's knowledge of TDD and testing in general was excellent. He was aware of Mike Cohen's test pyramid. He has done some hard-core TDD testing, often practicing code "kata's" at home. He was aware of the phrase red-green-refactor and of how TDD should be performed. In addition to this he was aware of all of the different types of testing used in a modern professional environment. There would be no problems at all here.
AGILE METHODOLOGY
Jamil had worked in an agile environemnt, was very well aware of what occurs at a standup and mentioned the other ceremonies, like story pointing at a planning session. I have no doubt he'd fit in to an agile team, however he did struggle, as many have on some of the deeper concepts of agile. He was unsure what agile says about documentation and had not come across the concept of an MVP
RESTFUL WEB SERVICES
Jamil has used restful web services allong side the spring framework. He understood verbs and end points and was able to correctly identify when each should be used. he's have no problems here.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
Jamil is well aware of how continuous integration works. He got the initial pre-screening question wrong but after a little promptin for the kind of info I was looking for, he was able to accurately describe it's purpose and point out that he had used it before, although he hasn't created any jobs in it. This is fine for the type of working environemnt he will be exposed to.
SOURCE CONTROL MANAGEMENT
Jamil was a little shaky where it came to source control technology. He said he had used GIT but struggled a little with some of the finer concepts. Nonetheless he would still be able to work well in a team.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
Jamil pointed out that he had used maven on several occasions which I accept, however he struggled to explain the basic maven directory structure and why it exists, when questioned further it seemed his knowledge of the subject was weak to moderate. Not everyone is good at everythin of course. I'd say this was his weakest area. It think Jamil has used maven but doesn't at this stage know it well. Given his good performance elsewhere this should not be a show stopper.
CSS + HTML5
Jamil has used HTML and CSS in the older fasioned versions.
Jamil has a solid knowledge of the areas needed, he scored 8 out of 11 in the pre-screening test, when we went through the incorrect questions he needed a little coaching with some of them, nonetheless he is a good solid candidate and he would fit in without any problems as an intermediate developer
The interview was quite conversational and he seemed very enquiring when we came across something he was not aware of. We spent some time on these areas and he always asked appropriate questions when he didn't understand something. In addition it seems he has a keen ability to learn new things and was able to do so quickly and within the framework of modern software development theory. A good sign for the training course. His skills as they stand are fine, however if he wanted to focus on learning more he could do with improving his knowledge of maven and build tools in general.
JAVA & OBJECT ORIENTED PRINCIPLES
Jamil knew the fundamentals of deployment in java and of object oriented principles and uses design patterns on a regular basis. He has used several frameworks including Spring. He is aware of all of the fundamentals and has easily sufficient experience.
He didin't get the hardest question I ask correct (about the persistence of the singleton design pattern) but seemed fascinated when I told him the answer and fully understood the explanation.
JAVASCRIPT
Jamil has used javascript for front end validation. In addition he has used the JQuery javascript framework. This is a good basis for the training course. His knowledge fits into the "old fashioned" category that is true of many of the candidates. He was aware of some of the recent changes in Javascript and it's applicability to wider problems.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
Jamil's knowledge of TDD and testing in general was excellent. He was aware of Mike Cohen's test pyramid. He has done some hard-core TDD testing, often practicing code "kata's" at home. He was aware of the phrase red-green-refactor and of how TDD should be performed. In addition to this he was aware of all of the different types of testing used in a modern professional environment. There would be no problems at all here.
AGILE METHODOLOGY
Jamil had worked in an agile environemnt, was very well aware of what occurs at a standup and mentioned the other ceremonies, like story pointing at a planning session. I have no doubt he'd fit in to an agile team, however he did struggle, as many have on some of the deeper concepts of agile. He was unsure what agile says about documentation and had not come across the concept of an MVP
RESTFUL WEB SERVICES
Jamil has used restful web services allong side the spring framework. He understood verbs and end points and was able to correctly identify when each should be used. he's have no problems here.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
Jamil is well aware of how continuous integration works. He got the initial pre-screening question wrong but after a little promptin for the kind of info I was looking for, he was able to accurately describe it's purpose and point out that he had used it before, although he hasn't created any jobs in it. This is fine for the type of working environemnt he will be exposed to.
SOURCE CONTROL MANAGEMENT
Jamil was a little shaky where it came to source control technology. He said he had used GIT but struggled a little with some of the finer concepts. Nonetheless he would still be able to work well in a team.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
Jamil pointed out that he had used maven on several occasions which I accept, however he struggled to explain the basic maven directory structure and why it exists, when questioned further it seemed his knowledge of the subject was weak to moderate. Not everyone is good at everythin of course. I'd say this was his weakest area. It think Jamil has used maven but doesn't at this stage know it well. Given his good performance elsewhere this should not be a show stopper.
CSS + HTML5
Jamil has used HTML and CSS in the older fasioned versions.