Live data from Hacker News

Interview advice that got me offers

zainrizvi.io

11–20 of 372 posts

Re: Interview advice that got me offers

#11
Some smaller items as well, that I think are worth mentioning, given the post starts out that advice is woefully short - seems like an invitation to throw in my 2p/2c/2satoshi, etc.

Remember that it's really a conversation, and it goes both ways. They want to learn about you, but you need to learn about them as well. Are these people you really want to work with, and are you the kind of person they want to work with. This means you have to show your full self - honest and open, and expect the same from them.

Some tricks here include making sure to turn it into a conversation, and engage the interviewers - something like finishing up your answer with "and, have you faced that problem, and how did you solve it?" works well to make them think, and engage them. You can then have a discussion about the problem and really allow yourself to show how you think and engage with someone. It stops being an exam/quiz setting.

In a similar vein, you want to answer in a way that shows you've solved the problem, or something similar before, in a real setting. So, rather than just providing the book answer, you can say something like: "Well, that's a similar problem to one I had when I was at X, and we solved it by doing Y, and my responsibility there was Z.". This shows that you were genuinely part of the solution, and can work in a team, and have real practical experience that's worth hiring you for.

I find it helps as well, in both the above scenarios, to highlight the problems you had, and how you overcame them. Especially in a technical field, the majority of what you'll be doing is problem solving, so demonstrate that ability.

Use open ended questions to demonstrate what you're passionate about and know really well. Call it out and explain what in the exercise you really enjoy, then explain your most recent tips, techniques, and things you've been experimenting with. Passionate people come across really well, and it's much easier to talk about something you love, it removes some nerves and mental blocks. It also them demonstrates (again), your capacity to learn, grow, and improve.

All of the above help you bring your humanity, as well as you tech skills, and show you can be a great help and contributor to the team they're hiring you for, and get you away from having to just rote repeat book answers to standard questions.

Finally, some smaller items:

1. If you need a second to think, have a drink. I always try to make sure I've got at least a bottle of water, so take a sip, and it'll give you a minute to think, to breathe and to relax. 2. You can always just say, let me think about that, and ask for a whiteboard, notes, etc. So many candidates we interview don't, and it hurts them. In the past I've taken to pushing people to take notes and write things down to keep their thinking in order.

Re: Interview advice that got me offers

#12

> Keeping those skills sharp even when you’re not job hunting. I rather hire someone with wisdom across multiple areas than a bleeding edge expert in few, very narrow specialty. In my experience, a group of generalists will often deal better with a problem than a group of specialist.

Perhaps your experience has only been in general problems?

Re: Interview advice that got me offers

#13

“Keeping those skills sharp even when you’re not job hunting.” It’s so tiring to continue to see this. If the “skills” you need to keep sharp are not the same thing as the skills you exercise through your job, that’s a giant red flag that the hiring company should be avoided. If you’re practicing leetcode or Kaggle in your spare time to pass interviews, you need to stop and realize you’ve set up your goals completely…

You're being downvoted because much of the Software Engineering community suffers from a form of Stockholm Syndrome.

Re: Interview advice that got me offers

#14

> Keeping those skills sharp even when you’re not job hunting. I rather hire someone with wisdom across multiple areas than a bleeding edge expert in few, very narrow specialty. In my experience, a group of generalists will often deal better with a problem than a group of specialist.

I prefer to be specialist in some areas and generalist in the periphery. e.g. I am excellent in distributed systems, Networking and FS, and have decent knowledge of web services, aws and kubernetes. I don't have any idea about embedded systems, mobile development and have no intention of acquiring that.

Re: Interview advice that got me offers

#16
One additional tip on recruiters: have a cheat sheet ready (web page or public Google doc) that answers the basic questions they'll have for you and makes clear your expectations.

Here's the info I ask them to provide:

- Job Title and Salary

- Job Description

- Company Overview and Location

- Steps in Hiring Process

Whenever I'm emailed by a recruiter, I politely thank them for reaching out, paste the link to the cheat sheet, and invite them to review it and write back if they still think I'm a good match. It quickly separates the professionals from the wannabes. (You usually don't hear back from the wannabes.) The ones who do write back often thank me for it.

I'm pretty cynical when it comes to recruiters. So I find it interesting that 3 of my last 4 jobs have come through one.

Re: Interview advice that got me offers

#17
post #2

> Your mad technical skills no longer matter to them. If anything, humility and an openness to learning will show you in the best light. I've been interviewing for the last couple of weeks and I agree with this. Being a "good" human being, i.e. candid, humble, kind, friendly, seems to be valued a lot more than what I thought before. At the end of the day is people working with people, and the more humans that interac…

[deleted]

Re: Interview advice that got me offers

#18
post #5

Tip 3 is huge. I ask hard questions during interviews, and I don’t expect a perfect answer. What I do want is the interviewee to handle failure without being defensive, and to ask probing questions.

Same here. Some of my goto questions are questions I don't expect a solution to. I'll tell people that - I know some people use similar questions without telling candidates that, but I don't think the extra pressure is necessary. I also explicitly explain to people that what I want to see is how they think, more so than the final solution.

It tells me a lot about how a candidate will work within a team if they're capable to actually bounce ideas back and forth and explain their thinking, and I've often preferred someone who doesn't get as far but who can show me better communications skills and who seems eager to learn.

Re: Interview advice that got me offers

#19

“Keeping those skills sharp even when you’re not job hunting.” It’s so tiring to continue to see this. If the “skills” you need to keep sharp are not the same thing as the skills you exercise through your job, that’s a giant red flag that the hiring company should be avoided. If you’re practicing leetcode or Kaggle in your spare time to pass interviews, you need to stop and realize you’ve set up your goals completely…

The advice of going on interviews semi-regularly is one that I tell everyone soliciting advice (even my direct reports, though only once and only if conversation veers that way!).

I don’t mean the leetcode hoops (etc, though that is part of the game) but once you’re in the door.

It’s a unique skillset that degrades fast, not unlike dating skills.

Re: Interview advice that got me offers

#20

“Keeping those skills sharp even when you’re not job hunting.” It’s so tiring to continue to see this. If the “skills” you need to keep sharp are not the same thing as the skills you exercise through your job, that’s a giant red flag that the hiring company should be avoided. If you’re practicing leetcode or Kaggle in your spare time to pass interviews, you need to stop and realize you’ve set up your goals completely…

You're being downvoted because much of the Software Engineering community suffers from a form of Stockholm Syndrome.

Most engineers are introverts and relatively humble - so interviewing is difficult. We have to remind ourselves that we are pretty good.

I always went on 2 practice interviews before the real interview and it worked.

Post reply on HN