Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso OrderDynamics
Colloquio
Recruiter phone screening then invited for an in-person interview, covering a variety of full stack topics ... You need to be solid in the fundamentals ... Some questions were hard, otherwise straightforward
Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto una settimana. Ho sostenuto un colloquio presso OrderDynamics
Colloquio
A phone interview was arranged with the Development Manager. It was to be followed with an in-person interview. The interview was arranged by a recruiting firm. They were looking for a senior level ASP.Net development resource.
Domande di colloquio [1]
Domanda 1
The interviewer asked .Net C# related questions mostly and some relational database questions.
1. What are abstract classes?
2. What are interfaces?
3. What are static classes? Can we instantiate an instance of these classes?
4. What are nullable types?
5. Do C# support multiple inheritance?
6. What is polymorphism?
7. What are indexes? Why do we need them?
8. Why do we use group by clause?
9. Have you worked using Design Patterns?
10. Name any two design patterns and for what purpose they are used?.
Ho presentato la mia candidatura tramite segnalazione di un dipendente. La procedura ha richiesto 3 giorni. Ho sostenuto un colloquio presso OrderDynamics (Richmond Hill, ON) nel mese di ago 2013
Colloquio
The Hiring process was one of the best, if not THE BEST, process I have been through. What made it stand out from the rest was the interview itself. I ended up meeting with, and interviewing with the Development Manager and the Vice President of R & D.
What was great about the interview was that rather than asking a bunch of "HR" type questions, mixed in with standard work history questions and textbook questions, the interview was broken down into distinct parts that were meant to show me exactly what type of working environment this was and what kind of things would be expected of me.
The first part was the standard HR / Work history questions - This was meant to get an idea of where I was coming from and breaks the ice in terms of nervousness.
The second part was an actual hands on test (using a real computer) - This part of the test is great because it forced me to show my skills in action. It really separates candidates that say they know how to do something, and the ones who ACTUALLY know what they are doing.
The third part was related to the development process itself and it gave a really good insight into the thought process of the candidate.
The last part was another hands on test with a different focus - This test and the test in the second part are different enough that they look to showcase different skills.
Overall the interview process itself is the best one I've seen. The questions force candidates to showcase their skills and doesn't let people get away with saying they know something when they actually don't. If you say you can do something, the interview will force you to prove it!
Domande di colloquio [1]
Domanda 1
The most unexpected question was when I was asked to review a User Story and come up with QA tasks and estimations on it.