Technical Candidate Review - tCView
tCView helps technical software recruiters - independent or within a hiring organization - verify candidates’ technical skills and technical claims on their resume. We offer several options - all aligned with recruiters needs:
Notes:
Get started today - call +1 416-809-1453 or Contact us here.
Sample Report
Here is an excerpt of a tCView report as a result of a technical interview:
| Candidate | Erik W. |
| Date of Interview | April 6 |
| Candidate's Phone number | +1 416-555-1212 |
| Start Time | 11:45 |
| End Time | 12:30 |
| Total Minutes | 45 minutes |
| Interview Style | Resume based - conversational |
Comments:
Candidate was on-time for interview and presented as an experienced developer early in the interview process. I reviewed his most recent project with him - on asking him to describe it, the candidate was vague about the project’s purpose and deliverables. On discussing further, the candidate explained that he was under a non-disclosure agreement regarding precise details but was willing to cover general comments.
The candidate’s comments about the BizTalk aspect of the solution revealed that a consulting firm provided the overall architecture, a proof of concept application, and guidance. The candidate’s development efforts extended the proof of concept application and use of the guidance - patterns included the use of many custom components to implement business rules, mapping, and other major functionality.
I asked the candidate how he would design the system on his own, given that he had worked with it for about a year. He again became very vague by giving very general comments about using mapping within BizTalk and Orchestrations. As I was listening, I was reading through the BizTalk documentation and some other broadly available sources and found some of his answers matched the exact text in the sources.
The Candidate was more specific about another project and, in fact, volunteered a lot of details including architecture, design, and implementation. The customer he worked for at the time was one that I had also worked for in the past. Oddly enough, he claimed to be there at the same time I was there and working in a similar capacity on the same project. I can confirm that the team was made up of four people, including myself, and the candidate was not part of the team.
At that point, I concluded the interview citing the vague answers and alleged lying about the preceding position (the one he claimed to be on, when I was in fact there at the same time on the same project with a team of four people).
| Quality of responses | Poor |
| Clarity of responses | Vague |
| Technical capabiltiies | Junior/Junior Intermediate |
| Command of English | Good |
| Suggestion | Candidate may be suitable in a highly-supervised environmnet and with clear direction. I suggest regular follow-ups with client to ensure that candidate is consistent and that the customer is not exceeding the candidate's capabiltiies (the candidate will not inform your customer that he does not know how to complete something and will instead work at the expense of the project as opposed to finding assistance. |