Fixing impostor syndrome in coding interviews • Hacker News Board

Re: Fixing impostor syndrome in coding interviews

#81

Post by tytytytytytytyt » Wed, Mar 14, 2018, 4:49 AM UTC

taurath wrote: post #69

tytytytytytytyt wrote: post #59

Earlier quoted context omitted.

A b-tree or a binary tree? A b-tree doesn't even sound believable, unless there's other info you're not telling us.

I have been asked to write a matrix search robot (Ideal solution using A* algorithm) for a company that was doing CRUD education software apps, in which I was applying for a full stack position with plenty of experience building prod apps in their stack. I just looked them up and they shuttered about 12 months after the interview.

So what happened with the b-tree??

Re: Fixing impostor syndrome in coding interviews

#82

Post by tkxxx7 » Wed, Mar 14, 2018, 4:24 PM UTC

stcredzero wrote: post #67

skybrian wrote: post #62

Earlier quoted context omitted.

I don't think graph theory is in any danger of being lost. That seems overly dramatic. Since people can learn from each other, it's hard to say what people really need to know the day they join the team.

I don't think graph theory is in any danger of being lost. That seems overly dramatic. The Brits and Japanese had no idea of the underlying mechanisms, and our society has the underlying comp sci knowledge in our case, archived in libraries. If an entire generation of computer science grads just fluffs graph theory, it's not like the knowledge will be lost, but it's definitely not a good thing. It's definitely a step…

> EDIT: Isn't anyone curious about what these tools are?

Um, Not when you are making readers feel incompetent for not having them.

Re: Fixing impostor syndrome in coding interviews

#83

Post by alacombe » Wed, Mar 14, 2018, 4:32 PM UTC

emodendroket wrote: post #80

alacombe wrote: post #78

Earlier quoted context omitted.

Most of the candidate of my past job who passed the initial non-technical interview with my former manager, over 2 years, that was probably a dozen people, leading to 3 hires.

Personally I think being willing to do such a thing is a sign of desperation.

On the other side, it saved us from bad hires that would have been difficult to fire otherwise.

Re: Fixing impostor syndrome in coding interviews

#84

Post by rrauenza » Fri, Mar 16, 2018, 3:09 AM UTC

BadCookie wrote: post #41

rrauenza wrote: post #28

Earlier quoted context omitted.

That kind of pressure isn't the same as interview pressure. I've been in whiteboard coding interviews and in situations where "production is down" and they are very different kinds of pressure and expectations.

I agree. I handle work pressure well enough, but social anxiety is a completely different animal.

I'd call it performance anxiety / pressure vs work pressure.