231–240 of 693 posts
I feel like it's a little weird that one of the author's big examples of a difficult algorithmic question is breadth-first search. While I agree it's not something that's very likely to come up much in real work (especially for a front-end dev!), it's also... not actually hard? You check the current node for your truth condition, you add its children to a queue, you pop the queue and do the same thing for that node.…
If you ask and your interviewer gets glassy-eyed or gives you the laughably generic "it shows how well you think algorithmically" you know that you are being interviewed by someone who has little clue what they are doing. It is a great way, from your side of the table, to understand if your time is being wasted right out of the gate.
1: http://blog.benroux.me/4-steps-to-making-your-interview-suck...
Just went through this process from the POV of employer. The risk of choosing the wrong person is so great, that it's often better to not choose anyone. If there is any doubt what-so-ever, it's better to not make a a hire, it can be too damaging to a team, manager, company. I've tried so many different "coding interview" scenarios. But I found the best one was a real task that a real staff member would be expected to…
> The risk of choosing the wrong person is so great, that it's often better to not choose anyone. If there is any doubt what-so-ever, it's better to not make a a hire, it can be too damaging to a team, manager, company. That's bullshit. Sorry, but it is. If it was such a big risk, companies would: 1) Do much better jobs at retaining employees (that are known to be good). 2) Be in a lot of trouble currently, because c…
Coding contest skills are very unfair to senior developers because they are out of school long time and do not have the time or motivation to engage in coding competition. And this also creates different incentive models. I have seen people who flunked very elementary CS courses (OS, networking etc.) to spend more time coding competition to get hired in big companies. This is really weird because they have to learn these things to become a real developer and they are gonna learn these things in company's time which they should know already. That being said, I personally think, problems like maze solving and inverting binary tree are fair questions. These are not exotic DP problems, these are just simple problems.
OTOH, the whole years of experience thing is unfair for new developers who do not have the experience but smart enough to learn and outperform many developers with experience who just memorized APIs over years of experience. There must be a healthy compromise between these two types of hiring.
Once I found a company that actually _needed_ me, the experience became a positive one - they went out of my way to make me feel comfortable.
I wish there were a way for candidates to pre-screen companies, rather than the other way around. It's a waste of time on both parties if the company isn't actually in need of a new hire, but just dabbling in the option pool.
When I hired a plumber for my heating firm, I put her through a hazing interview, tested her knowledge of Maxwell relations and thermodynamic equations. Oh wait, no I didn't. As she has been a plumber for years, so we recognised her skill and experience and cut to the chase. When I hired a programmer for our doomed to die VC life support funded fart of a project, we put her through numerous rounds of comp sci bingo a…
I have yet to meet a professional plumber who is female, and I've met a lot of plumbers (I'm in construction). Just saying, it's jarring.
When I hired a plumber for my heating firm, I put her through a hazing interview, tested her knowledge of Maxwell relations and thermodynamic equations. Oh wait, no I didn't. As she has been a plumber for years, so we recognised her skill and experience and cut to the chase. When I hired a programmer for our doomed to die VC life support funded fart of a project, we put her through numerous rounds of comp sci bingo a…
I have yet to meet a professional plumber who is female, and I've met a lot of plumbers (I'm in construction). Just saying, it's jarring.
In Portugal I was very amazed by the large amount of women driving buses, taxis and garbage trucks (for instance). Back in Brazil I must have seen at most five or six but in Portugal it is a very common sight.
Now for this kind of specialized trade jobs like plumbers, electricians and auto mechanics I personally never seen a woman doing it in both sides of the pond.
One possible reason is that the brony thing on his github might be a legit turnoff for employers. It's silly, but it's possible. The two people I talk to more than anyone else in this world are bronies (to the extent of going to conventions and whatnot) and have similar issues. Hell, I still don't understand it and find myself irrationally judging them for it, and that's even after daily exposure to it.
I hired Sahat as an intern three years ago while he was an undergrad. It was one of the best hiring decisions I have ever made. He was productive immediately and our (small) team felt the loss when he went back to school. This guy is good and gets stuff done, ask people who have worked with him. I wish Sahat had reached out to more of his network before responding to random recruiters. Tech interviews as Sahat experi…
I'm seeing a lot of "reaching out" in this thread. Is this a new thing, like "passion"?
My impression of what reaching out means today is a chat over coffee, lunch, or less preferably a phone call.