2 ms·
> Don’t suck at something you say you’re an expert at This one. If you say you are expert/advanced at X, we will check for some level of competence. It's amazi
by EdwardDiego 12y ago
> Don’t suck at something you say you’re an expert at
This one. If you say you are expert/advanced at X, we will check for some level of competence. It's amazing how many candidates with CVs claiming 'advanced SQL skills' don't know about the existence of the HAVING clause. An exaggerated CV is a very easy filter.
- andrewstuart 12y agoI agree that people shouldn't exaggerate their skills but you need to be cautious about how you go about proving that they do not. It's easy to prove that someone is clueless by quizzing them about specific technical details or syntax. You will of course find something they do not know, but are you really trying to prove your own cleverness by catching them out? "You say you're an expert eh? We'll let me prove you're wrong and I'm smarter cause I'll ask arcane technical facts till I find something that shows you're not an expert!"
- ap22213 12y agoSeriously - I remember once stating that I was skilled in Java (would never use the word 'expert', though). The technical interviewers must have taken it as a challenge to them, as they spent 30 minutes quizzing me on all of the different executables that made up the JDK and all of the different arguments to them.
- andrewstuart 12y agoI'm a recruiter and do technical interviews for a living. I almost never ask specific questions of syntax. You will incorrectly assess someone as not being knowledgable if your questions are about specific syntax and therefore possibly lose a great developer.
- deleted 12y ago[deleted]
- EdwardDiego 12y ago> I agree that people shouldn't exaggerate their skills but you need to be cautious about how you go about proving that they do not. It's easy to prove that someone is clueless by quizzing them about specific technical details or syntax. I agree, which is why I gave GROUP BY HAVING as an example filter for 'advanced' SQL skills (especially as my team manages data warehousing and analytics). It's not a minor implementation detail, it's the major tool for filtering on aggregated values - something like 'find customers who have purchased two more products in one month' can either be done as a query of an aggregated sub-query, or as one query using HAVING to filter for customers with a COUNT(*) > 2. Again, this is only for people claiming advanced skills, and it's not that an 'advanced' feature. I don't expect every developer to know about SQL:2003's window functions, but HAVING has been around since at least 1992. I agree with not asking silly technicalities, as a Java developer, knowing why new Integer(100) == new Integer(100) but new Integer(1000) != new Integer(1000) is an interesting piece of trivia, but using it in an interview is a waste of everyone's time.
- deleted 12y ago[deleted]
- andrewstuart 12y agoSo you're saying you think that questions on syntax are important. We'll have to agree to disagree on that.
- EdwardDiego 12y agoThat isn't a question on syntax, sorry. We'll have to very much disagree if you think this is just syntax. It's a core part of SQL that anyone with advanced SQL skills should at least be aware of. Syntax would be caring if they put the ORDER BY in front of the GROUP BY.