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="Adil" data-source="post: 469619" data-attributes="member: 3031"><p>I've done one technical interview for someone who was tasked with maintaining some software we had built. In that technical interview I went over basic concepts, such as:</p><ul> <li data-xf-list-type="ul">HTTP</li> <li data-xf-list-type="ul">JS/CSS</li> <li data-xf-list-type="ul">What do you know about technology X?</li> <li data-xf-list-type="ul">Can you tell me how you'd go about process Y?</li> </ul><p></p><p>My general findings when interviewing for a position I'm applying to:</p><ul> <li data-xf-list-type="ul">Phone screen covering basics about tech stack (e.g. what's a class in Python, what does XYZ do in JS, etc)</li> <li data-xf-list-type="ul">Technical assessment (sometimes done in step 3)</li> <li data-xf-list-type="ul">Technical interview onsite (or remote)</li> <li data-xf-list-type="ul">Offer</li> </ul><p></p><p>The technical interviews are usually very gnarly and really test aspects of my understanding. In one recent interview they wanted me to describe in detail how I debug bugs in production and the design decisions behind my assessment.</p><p></p><p>One thing I have noticed - it's good to ask for specifics on a language but the more fruitful path is asking about technical problems that are language/framework agnostic. Those are the most enjoyable for me anyway</p></blockquote><p></p>
[QUOTE="Adil, post: 469619, member: 3031"] I've done one technical interview for someone who was tasked with maintaining some software we had built. In that technical interview I went over basic concepts, such as: [LIST] [*]HTTP [*]JS/CSS [*]What do you know about technology X? [*]Can you tell me how you'd go about process Y? [/LIST] My general findings when interviewing for a position I'm applying to: [LIST] [*]Phone screen covering basics about tech stack (e.g. what's a class in Python, what does XYZ do in JS, etc) [*]Technical assessment (sometimes done in step 3) [*]Technical interview onsite (or remote) [*]Offer [/LIST] The technical interviews are usually very gnarly and really test aspects of my understanding. In one recent interview they wanted me to describe in detail how I debug bugs in production and the design decisions behind my assessment. One thing I have noticed - it's good to ask for specifics on a language but the more fruitful path is asking about technical problems that are language/framework agnostic. Those are the most enjoyable for me anyway [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Software Development
Programming
Programming Q&A
How do you perform technical interviews for developers?
Top