2 ms·
1/2/3 - Shows a knowledge of basic, modern CSS. 4 - Somewhat advanced IMHO, and how often do you need this? 5/6/7 - Tedious. 8 - Okay, showing some knowledge
by debacle 8y ago
1/2/3 - Shows a knowledge of basic, modern CSS.
4 - Somewhat advanced IMHO, and how often do you need this?
5/6/7 - Tedious.
8 - Okay, showing some knowledge of JavaScript.
9 - Showing the ability to write a control structure.
10/11 - Showing the ability to interact with the DOM and modify someone else's code.
Why would you give this code test after the interview? Why not give it to the potentially viable applicants first?
What kind of salary are you looking at? Anyone over 2-3 years of experience should be able to answer most/all of these questions.
- yeldarb 8y agoWe gave the non-technical interviews first because we wanted to prioritize the people who wanted _this_ job over the ones who seemed to be applying for _every_ job. If we're going to spend a ton of time onboarding and training someone we want them to be happy with what they're working on so they're more likely to stick with us longer term. It was surprising how many naked resumes we received with no cover letter and no indication that the candidate even knew what company they were applying to.