5 ms·

Also not OP, and also similar experience. Most of my interviews are an hour or two of conversation, sometimes with a "I've been told I have to ask.. " techy que

by Jenk 4y ago

Also not OP, and also similar experience. Most of my interviews are an hour or two of conversation, sometimes with a "I've been told I have to ask.. " techy question but never involves any actual code/whiteboard. Several times the interviewer has said something to the effect of "I won't insult you by asking you to do a tech test, it's clear to me that you understand the work" or similar. One occassion (some years ago now) I've replied to a request to complete a tech test with a "Would you rather look at my open source code/contributions?" which they did and I didn't need to perform the test.

ARandomerDude 4y ago
Not quite as experienced as you (I’m in the 10-15 year bracket). I never ask LeetCode questions because it’s far easier on both sides to ask experience-based questions like “what do you like/dislike about <technology on your resume>?” If I get superficial answers that tells me something. If i get well thought-out answers from people who have clearly spent time in the trenches that tells me something too.
- Jenk 4y ago
  Yes, I'm exactly the same.
- CWuestefeld 4y ago
  I've been doing this for 30+ years, and I've found the same. It's not just whether the candidate can answer correctly, but how they answer. Back when I was doing C/C++ interviews, I'd ask questions like: What's the difference between single and double quotes? A meh candidate answers something about you need single quotes for just a single character. A good candidate answers about how the data type for a double-quoted constant is a char. If I want to pass a variable into a function, and have its value changed by the function, what do I do?* A lousy candidate says "put an ampersand in front of it". A meh candidate says to pass a pointer to the variable. The best candidate will talk about the difference between call-by-value versus call-by-reference. People really do reveal a lot about themselves not just in what they say, but the way they say it.
  - jenscow 4y ago
    Both great questions, where the answer will give you a level of knowledge, rather than a yes/no. (personally, I would be a meh candidate until you probed further - but I've not touched C for.. hmm, I'm old) I often get questions where I need to determine if they're looking the textbook answer, or a real-life answer. Usually I will go with "well generally, the answer is $Textbook. However, ..."
  - CWuestefeld 4y ago
    I just realized that my above model answer gets broken by the formatter. the first question should get answered with char-star, that is, pointer to char.
    - ARandomerDude 4y ago
      This is why I don't use C. ;)
    - Izkata 4y ago
      If you put a backslash in front of the asterisk it should be kept as-is instead of triggering the formatting.
  - MaxBarraclough 4y ago
    > If I want to pass a variable into a function, and have its value changed by the function, what do I do? A lousy candidate says "put an ampersand in front of it". A meh candidate says to pass a pointer to the variable. The best candidate will talk about the difference between call-by-value versus call-by-reference. I agree it's good for a candidate to demonstrate a solid understanding of evaluation strategies, but the way you phrased the question, the 'meh' answer seems about right. You asked what do I do? which invites a narrow answer specific to the language.
    - Sohcahtoa82 4y ago
      Agreed. In fact, I had an instructor in college that would have marked you down if a quiz/test asked this question and you wrote an entire paragraph describing call-by-value versus call-by-reference. On the final, he said "Each of these questions is answerable in 1-3 sentences. If you're writing 1-3 paragraphs, you're wasting my time and I will subtract points even if your answer is correct."
- kubami 4y ago
  Exactly this! I haven't been interviewed for a long time now, but since the beginning of my career, when I have interviewed people I ask deeper questions. Even with tech tests, I use them as a jumping board for diving deeper into language design, tradeoffs and experiences. Even a trivial, reverse-a-string kind of questions can take you deep into candidate's knowledge.

by Jenk 4y ago

ARandomerDude 4y ago

Not quite as experienced as you (I’m in the 10-15 year bracket). I never ask LeetCode questions because it’s far easier on both sides to ask experience-based questions like “what do you like/dislike about <technology on your resume>?” If I get superficial answers that tells me something. If i get well thought-out answers from people who have clearly spent time in the trenches that tells me something too.

Jenk 4y ago
Yes, I'm exactly the same.
CWuestefeld 4y ago
I've been doing this for 30+ years, and I've found the same. It's not just whether the candidate can answer correctly, but how they answer. Back when I was doing C/C++ interviews, I'd ask questions like: What's the difference between single and double quotes? A meh candidate answers something about you need single quotes for just a single character. A good candidate answers about how the data type for a double-quoted constant is a char. If I want to pass a variable into a function, and have its value changed by the function, what do I do?* A lousy candidate says "put an ampersand in front of it". A meh candidate says to pass a pointer to the variable. The best candidate will talk about the difference between call-by-value versus call-by-reference. People really do reveal a lot about themselves not just in what they say, but the way they say it.
- jenscow 4y ago
  Both great questions, where the answer will give you a level of knowledge, rather than a yes/no. (personally, I would be a meh candidate until you probed further - but I've not touched C for.. hmm, I'm old) I often get questions where I need to determine if they're looking the textbook answer, or a real-life answer. Usually I will go with "well generally, the answer is $Textbook. However, ..."
- CWuestefeld 4y ago
  I just realized that my above model answer gets broken by the formatter. the first question should get answered with char-star, that is, pointer to char.
  - ARandomerDude 4y ago
    This is why I don't use C. ;)
  - Izkata 4y ago
    If you put a backslash in front of the asterisk it should be kept as-is instead of triggering the formatting.
- MaxBarraclough 4y ago
  > If I want to pass a variable into a function, and have its value changed by the function, what do I do? A lousy candidate says "put an ampersand in front of it". A meh candidate says to pass a pointer to the variable. The best candidate will talk about the difference between call-by-value versus call-by-reference. I agree it's good for a candidate to demonstrate a solid understanding of evaluation strategies, but the way you phrased the question, the 'meh' answer seems about right. You asked what do I do? which invites a narrow answer specific to the language.
  - Sohcahtoa82 4y ago
    Agreed. In fact, I had an instructor in college that would have marked you down if a quiz/test asked this question and you wrote an entire paragraph describing call-by-value versus call-by-reference. On the final, he said "Each of these questions is answerable in 1-3 sentences. If you're writing 1-3 paragraphs, you're wasting my time and I will subtract points even if your answer is correct."
kubami 4y ago
Exactly this! I haven't been interviewed for a long time now, but since the beginning of my career, when I have interviewed people I ask deeper questions. Even with tech tests, I use them as a jumping board for diving deeper into language design, tradeoffs and experiences. Even a trivial, reverse-a-string kind of questions can take you deep into candidate's knowledge.