Menu
Forums
All threads
Latest threads
New posts
Trending threads
New posts
Search forums
Trending
What's new
New posts
New profile posts
Latest activity
Members
Current visitors
New profile posts
Search profile posts
Upgrades
Log in
Register
What's new
Search
Search
Search titles only
By:
All threads
Latest threads
New posts
Trending threads
New posts
Search forums
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Software Development
Programming
Programming Q&A
How do you perform technical interviews for developers?
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Mythraus" data-source="post: 470075" data-attributes="member: 20012"><p>I've been interviewing candidates for some time now.</p><p></p><p>We auto-send a very basic coding challenge to create a set of classes/methods to implement basic program (Shopping Cart, Tweet Parser, etc) with specific styling/linting requirements which acts as a nice sieve.</p><p></p><p>Once a candidate passes through the challenge we will do a phone screen where we ask about their experience with a variety of things including:</p><p></p><ul> <li data-xf-list-type="ul">Version Control Systems and their benefits along with strategies you may employ when working across a project.</li> <li data-xf-list-type="ul">IDE's and Editors and their benefits when developing software in addition to the candidates favourite one and why that is.</li> <li data-xf-list-type="ul">Functional programming paradigms and why they can be beneficial.</li> <li data-xf-list-type="ul">Outside hobbies, projects, interests to determine if they're likely to be a culture fit.</li> </ul><p></p><p>Following the screener we will do a one on one which will include some more technical questions surrounding Concurrency, API's, Security to grasp the candidates overall development knowledge as well as key things that we're looking for in the role. Additionally if a candidate had supplied a Github we would ask questions about one of their most active projects and the inspirations for it alongside any technical challenges they faced.</p><p></p><p>I find it works pretty well for getting the right people through as most of the content we require can be taught or picked up fairly easily depending on the developers experience and motivation. I've also been against interview with large stages or drawn out technicals since they enourage regurgitation of information rather than having a general understanding of the concepts.</p></blockquote><p></p>
[QUOTE="Mythraus, post: 470075, member: 20012"] I've been interviewing candidates for some time now. We auto-send a very basic coding challenge to create a set of classes/methods to implement basic program (Shopping Cart, Tweet Parser, etc) with specific styling/linting requirements which acts as a nice sieve. Once a candidate passes through the challenge we will do a phone screen where we ask about their experience with a variety of things including: [LIST] [*]Version Control Systems and their benefits along with strategies you may employ when working across a project. [*]IDE's and Editors and their benefits when developing software in addition to the candidates favourite one and why that is. [*]Functional programming paradigms and why they can be beneficial. [*]Outside hobbies, projects, interests to determine if they're likely to be a culture fit. [/LIST] Following the screener we will do a one on one which will include some more technical questions surrounding Concurrency, API's, Security to grasp the candidates overall development knowledge as well as key things that we're looking for in the role. Additionally if a candidate had supplied a Github we would ask questions about one of their most active projects and the inspirations for it alongside any technical challenges they faced. I find it works pretty well for getting the right people through as most of the content we require can be taught or picked up fairly easily depending on the developers experience and motivation. I've also been against interview with large stages or drawn out technicals since they enourage regurgitation of information rather than having a general understanding of the concepts. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Software Development
Programming
Programming Q&A
How do you perform technical interviews for developers?
Top