2 ms·

Sure you can: 1. HackerRank (or similar) challenges are pretty close to what you'd find in a lot of technical interviews. 2. Searching online for "<technology

Sure you can: 1. HackerRank (or similar) challenges are pretty close to what you'd find in a lot of technical interviews. 2. Searching online for "<technology> interview questions" for a few of the technologies that you're likely going to be asked about. Make sure you have good answers for the questions that pop up a lot. This helps a lot with remembering Stuff You Should Know that kind of slipped your mind (ie., angular digest cycle) because you maybe haven't seen it in a bit. 3. Write up a summary of your previous accomplishments and be sure you can call them out on the spot. A lot of what the interviewer is looking for is confidence. And preparation begets confidence.

moufestaphio 5y ago
Yeah I agree with this. If you drill enough of the Coding questions, they all start to run into similar buckets, and the way you approach them improves too. Buy a whiteboard off amazon, solve them legit out loud explaining what you're doing to yourself. You will get better. The other stuff is great advice too, always try to have a summary (in your mind or on paper) of recent projects etc. And of course.. Doing interviews helps to :D
WalterSear 5y ago
This is the conventional wisdom, and IME, it's minimally effective. I've followed this practice for years. I've completed almost 10% of leetcode's problem set. Interviewers should be looking for competence, not confidence.
- mywittyname 5y ago
  Something to keep in mind is interviewers basically never receive any kind of training, and even experienced technical interviewers do it maybe once a week or so. These people are doing their best to gauge technical aptitude and culture fit from a one hour conversation. It's not easy either. If I mess up once while giving advice on a place where the candidate is stuck, I can really confuse the candidate. Plus the time cost of reviewing a person's resume to determine what questions are appropriate for them. Lastly, I can't be expected to know all the tech on someone's resume at a level that I can gauge their capabilities, I use other means to determine if what a COBOL person is telling me is accurate. So you have to kind of plan that interviewers take shortcuts (like judging confidence) and take advantage of that fact. If someone asks what are some benefits or drawbacks to a tech stack you use, have at the ready a good story about a shitty/hilarious/intersting experience you had while developing it. The experience doesn't need to be a 1-to-1 mapping either, it's a-okay to kind of nudge a question towards an answer you prepared. This is better advice than you're really appreciating. If you feel like you are doing this, but still am having trouble, it's likely that you need work in some other non-obvious aspect of interviewing. I highly suggest finding a coach or someone who can take you through mock interviews and help you find out exactly what you can do to improve your chances!
raydev 5y ago
Okay, so how do I reproduce the feeling of being watched by someone who's determining my future and livelihood?
- oneepic 5y ago
  In my prep I didn't reproduce that, but I had success with focusing more on solving the problem and less on the person. Every once in a while I made the note of saying something like, "Does that make sense/seem reasonable?" to check in with the interviewer.

moufestaphio 5y ago

Yeah I agree with this. If you drill enough of the Coding questions, they all start to run into similar buckets, and the way you approach them improves too. Buy a whiteboard off amazon, solve them legit out loud explaining what you're doing to yourself. You will get better. The other stuff is great advice too, always try to have a summary (in your mind or on paper) of recent projects etc. And of course.. Doing interviews helps to :D

WalterSear 5y ago

This is the conventional wisdom, and IME, it's minimally effective. I've followed this practice for years. I've completed almost 10% of leetcode's problem set. Interviewers should be looking for competence, not confidence.

mywittyname 5y ago
Something to keep in mind is interviewers basically never receive any kind of training, and even experienced technical interviewers do it maybe once a week or so. These people are doing their best to gauge technical aptitude and culture fit from a one hour conversation. It's not easy either. If I mess up once while giving advice on a place where the candidate is stuck, I can really confuse the candidate. Plus the time cost of reviewing a person's resume to determine what questions are appropriate for them. Lastly, I can't be expected to know all the tech on someone's resume at a level that I can gauge their capabilities, I use other means to determine if what a COBOL person is telling me is accurate. So you have to kind of plan that interviewers take shortcuts (like judging confidence) and take advantage of that fact. If someone asks what are some benefits or drawbacks to a tech stack you use, have at the ready a good story about a shitty/hilarious/intersting experience you had while developing it. The experience doesn't need to be a 1-to-1 mapping either, it's a-okay to kind of nudge a question towards an answer you prepared. This is better advice than you're really appreciating. If you feel like you are doing this, but still am having trouble, it's likely that you need work in some other non-obvious aspect of interviewing. I highly suggest finding a coach or someone who can take you through mock interviews and help you find out exactly what you can do to improve your chances!

raydev 5y ago

Okay, so how do I reproduce the feeling of being watched by someone who's determining my future and livelihood?

oneepic 5y ago
In my prep I didn't reproduce that, but I had success with focusing more on solving the problem and less on the person. Every once in a while I made the note of saying something like, "Does that make sense/seem reasonable?" to check in with the interviewer.