Live data from Hacker News

Interview success can depend on how you schedule interviews

tanayagrawal.substack.com

91–100 of 125 posts

Re: Interview success can depend on how you schedule interviews

#91
post #67

Earlier quoted context omitted.

I’ve interviewed many candidates and I’ve interviewed many times myself. Having good conversation skills is the single biggest influence on whether a candidate proceeds or not. Talking is a skill and that really stands out against other candidates. When I’m interviewing, I’ll usually choose a stronger communicator over a stronger engineer.

Isn't that kind of odd? I've worked with software engineers who are good talkers but their code and problem solving skills leave something to be desired. Meanwhile, I've worked with guys who took a while to get comfortable with in terms of having conversations and yet they were some of the most productive members of the team both in code output and skill. Ultimately, most of the time I 'talk' with my team members, we…

You don't intentionally choose weak engineers, but a strong engineer working on the wrong thing because they can't communicate effectively is less useful than a slightly less strong engineer who's always doing the thing that's actually needed.

This hold true as pretty much every level. A junior engineer who will never say "No, I don't understand, can you explain that to me again please?" and spends days/weeks writing code that doesn't meet a requirement is less productive than someone who'll talk to you to understand properly before starting to code. A senior engineer or technical cofounder who can't communicate well with customers will be much less effective in solving real customer problems or finding product/market fit.

Being a great engineer isn't just about writing good code, its about writing the right code - and to know what that is you need good communication skills.

Re: Interview success can depend on how you schedule interviews

#92
post #19

I have a few as well: - You will face rejection (likely a lot). Don't take this personally and don't let it affect your confidence. - Unless you are an outstanding interviewee, this is like a skill/muscle which you need to develop and practice. Hence ensure that you don't schedule your "dream job/company" early in the process. Keep practicing. - Always have a beginner / practice mindset. Otherwise, you will accept th…

I’ve interviewed many candidates and I’ve interviewed many times myself. Having good conversation skills is the single biggest influence on whether a candidate proceeds or not. Talking is a skill and that really stands out against other candidates. When I’m interviewing, I’ll usually choose a stronger communicator over a stronger engineer.

The correct metrics are 1. Strong skillset, and 2. Able to follow instruction (obedient). Every other hot metrics now are pretty much misalign with company goal of earning profit. Purely on your criteria alone "strong communicator" are way down the list while "strong engineer" will be easily top 3 criteria. In a company you only need 1 or 2 strong communicator, usually they will be the head of departments or more likely C leaders. Too many chief and less foot soldiers will be like what happen to Enron where everybody just hop from departments to departments unable to deliver useful productivity. Talk is cheap. Actions speaks louder. Those strong communicators are also the most likely to jump ship and change job for the better within a short time. It will be very detrimental to company having this group of employees. Speaking from over 3 decades of experience in HR.

Re: Interview success can depend on how you schedule interviews

#93

It's pretty tough to follow these rules. Mornings only gives you half the time. All rounds at once and as soon as possible would also mean you got in touch with all the recruiters at once and they got back to you promptly. In practice you more likely to see a steady drip as you ramp up your search. Some recruiters get back fast, some slowly. There's no real way you can control this other than giving some feedback as…

Yes these ideas are all certainly valid concepts about interviewing. But it would be nearly impossible to optimize for all of them. Furthermore, some really are impossible. For example #2 is to schedule interviews in cohorts. I tried to follow this in my most recent job hunt and it is truly impossible. The problem is that some jobs I would go through a phone screen and hear back later that day or the next morning in…

It really depends. I've seen things go pretty quick in other industries, like my wife, who works in marketing. At most she usually has a call, a psychological test of some sort, and a long onsite. She's also had some that were about as long as mine, but on average it's relatively short.

And she never has to grind or prepare beyond making sure her portfolio is ready. They don't ask her to prove her InDesign or Powerpoint or HTML or even tech skills (one job she had to lead a tech initiative to lead the department into evaluating and then switching to new proposal management software that was HTML template driven, and then basically be tech support for a bunch of salespeople that didn't want to invest the time to learn how to use it).

I'd rather go through her process than mine, quite frankly. Although she has found it more difficult than I have to find a company willing to pay her what she's making now, as her salary has gotten pretty high for her field, and she often has to sell them more on what she can bring to the table since she's had experience with so many large accounts in the past.

Meanwhile I could move to SV and double my salary easily, so I'm nowhere near the top, just the top of the ranges for all the recruiters in my region that contact me (I could probably find something in the area that's about $50k higher, I'm guessing, but no one is advertising it, most are advertising about $30k less than I'm making right now). And yet my process always seems to be long and painful.

Re: Interview success can depend on how you schedule interviews

#94
This might depend on the field.

But for the most part, you want to interview as soon as they can and if they have multiple rounds (phone, meet a manager, meet the team) you want to do them as quickly as reasonably possible. They have a position open, they want to fill it, if they hire you quickly, there will be no more competition. They don't want to interview any more people than they have to, so if you're right for the job, they'll hire you fairly quickly. If they aren't willing to schedule your interview fairly quickly, they aren't particularly motivated to fill the position (or have other candidates that they consider higher priority) and might not be worth your time.

When interviewing, remember that the interview is a two way street. Try to figure out what the job really is (the hr who posted position and phone screen people likely know much less about the actual job than the interviewers). If after finding out the details, you are genuinely interested in what they do and what you would do in the position, it'll keep the tone positive, even if you struggle. An underqualified, but motivated, candidate is much more interesting than a highly qualified but apathetic candidate.

Also, by keeping the interview as a conversation (trying to figure out if/how their questions relate to what they job is), you might get glimpses of feedback on how you're doing that you will almost certainly never get directly. This should help get you an idea of if it is going to be a good place to work or not.

If possible, show usages rather than tell qualifications. Rather than saying you can do X, tell a 10 second elevator pitch style story about how you've done it before. Try to have something to say about anything on your resume. They should come out confident that anything you claimed on it was actually you, not just "your team".

If they ask about something you are weak in, admit it, and try to see how they use it and try to offer related experience that shows you understand and are willing and able to learn it. They don't really expect to find a candidate that knows everything, but if you can demonstrate that you are familiar with the space enough to learn it, they'll be more willing to give you a pass.

If you totally fail at the interview but are genuinely interested and show the ability to learn it, you still have a chance. If you show disinterest or get defensive (rather than motivated) when challenged, they won't want to hire you.

If it isn't a good fit in your mind and you'd be looking for something better the day you start, be honest with yourself and them, thank them for their time and let them know that it isn't what you thought it was. A gracious interviewee who doesn't waste their time, may get called back if they have a position that better matches your interests (perhaps even if that interviewer moves to another company). If you accept a job and leave it fairly quickly, that's a big red flag and future employers will likely check that company for references.

Re: Interview success can depend on how you schedule interviews

#95
post #19

I have a few as well: - You will face rejection (likely a lot). Don't take this personally and don't let it affect your confidence. - Unless you are an outstanding interviewee, this is like a skill/muscle which you need to develop and practice. Hence ensure that you don't schedule your "dream job/company" early in the process. Keep practicing. - Always have a beginner / practice mindset. Otherwise, you will accept th…

Some additional points since i'm currently interviewing a lot -Practice leetcode since it will make up 50-60% of the interview process -Study your resume inside and out, know the whys of what you did not just the whats -Don't talk too much, sometimes nervousness and anxiety can make itself with a candidate talking too much or too little, both are bad, be concise with your answers but don't ramble on, the more you ram…

"-Practice leetcode since it will make up 50-60% of the interview process"

I know we're on HackerNews, but this is still a very bold assumption lol

Re: Interview success can depend on how you schedule interviews

#96
post #19

I have a few as well: - You will face rejection (likely a lot). Don't take this personally and don't let it affect your confidence. - Unless you are an outstanding interviewee, this is like a skill/muscle which you need to develop and practice. Hence ensure that you don't schedule your "dream job/company" early in the process. Keep practicing. - Always have a beginner / practice mindset. Otherwise, you will accept th…

Some additional points since i'm currently interviewing a lot -Practice leetcode since it will make up 50-60% of the interview process -Study your resume inside and out, know the whys of what you did not just the whats -Don't talk too much, sometimes nervousness and anxiety can make itself with a candidate talking too much or too little, both are bad, be concise with your answers but don't ramble on, the more you ram…

Any suggestions for practicing leetcode effectively?

Re: Interview success can depend on how you schedule interviews

#97
post #19

I have a few as well: - You will face rejection (likely a lot). Don't take this personally and don't let it affect your confidence. - Unless you are an outstanding interviewee, this is like a skill/muscle which you need to develop and practice. Hence ensure that you don't schedule your "dream job/company" early in the process. Keep practicing. - Always have a beginner / practice mindset. Otherwise, you will accept th…

I’ve interviewed many candidates and I’ve interviewed many times myself. Having good conversation skills is the single biggest influence on whether a candidate proceeds or not. Talking is a skill and that really stands out against other candidates. When I’m interviewing, I’ll usually choose a stronger communicator over a stronger engineer.

Conversely, the interviews that have gone most well for me were those that were largely just technical conversations. That’s not to say that they were nothing but fluff — the bits of conversation were usually accompanied with plenty of skill testing.

The worst were the ones where the interviewer clearly didn’t want to be there and mostly acted as a cold stone statue firing questions of from a sheet of paper. Incidentally those interviews were usually also the ones with the highest number of hackerrank sorts of questions.

Re: Interview success can depend on how you schedule interviews

#98
post #19

I have a few as well: - You will face rejection (likely a lot). Don't take this personally and don't let it affect your confidence. - Unless you are an outstanding interviewee, this is like a skill/muscle which you need to develop and practice. Hence ensure that you don't schedule your "dream job/company" early in the process. Keep practicing. - Always have a beginner / practice mindset. Otherwise, you will accept th…

Some additional points since i'm currently interviewing a lot -Practice leetcode since it will make up 50-60% of the interview process -Study your resume inside and out, know the whys of what you did not just the whats -Don't talk too much, sometimes nervousness and anxiety can make itself with a candidate talking too much or too little, both are bad, be concise with your answers but don't ramble on, the more you ram…

> Practice leetcode since it will make up 50-60% of the interview process

I think this depends on the role. I was interviewing for staff level front end roles a few months ago and didn’t have a single leetcode-style interview. All the coding questions were realistic problems.

Re: Interview success can depend on how you schedule interviews

#99
post #42

An interview is decided in the first several seconds. First impressions are a real thing. Most interviewers will decide based on how you look, act, and talk whether you are going to pass the interview, and they will confirmation bias you into their predetermined decision. Of course with an amazing interview performance you can switch a predetermined no into a yes, and with a very poor interview you can turn a predete…

> An interview is decided in the first several seconds

What if they get the technical questions wrong afterwards?

Re: Interview success can depend on how you schedule interviews

#100

Earlier quoted context omitted.

Some additional points since i'm currently interviewing a lot -Practice leetcode since it will make up 50-60% of the interview process -Study your resume inside and out, know the whys of what you did not just the whats -Don't talk too much, sometimes nervousness and anxiety can make itself with a candidate talking too much or too little, both are bad, be concise with your answers but don't ramble on, the more you ram…

Any suggestions for practicing leetcode effectively?

deeply understanding 1 problem per day is better than reading the solutions of a dozen. Solving leetcode via induction could prove valuable, solve a simple case of n = 1, then try to solve n = 2 do you see a pattern? try to solve n = 3 etc... Don't assume anything, don't categorize problems before thinking of patterns, sometimes dp problems are simple greedy problems, don't go into problem solving with bias. Look to build raw problem solving ability more than remembering problems of a certain flavor. understand advantages of linked list vs arrays, understand dictionaries, understand dfs vs bfs (both traverse graphs but what property does bfs have over dfs?), understand heaps, understand general recursion flow for binary trees,
Post reply on HN