Hacker News new | ask | show | jobs
by Mattish 2005 days ago
> ...This is meant for new software engineers...

Do these big companies really need so many developers that only know how to use this long list of 'fundamentals'?

I've interviewed a lot of people of all ranges, ages and skews. No matter what, when it comes down to sitting down with them and asking them to write out a simple program without any technicalities, 9/10 of them fail due to clearly not spending enough time just making things.

Are these big companies _really_ hiring juniors with this as their laundry list?

> ...Write code on a whiteboard or paper, not a computer. Test with some sample inputs. Then test it out on a computer....

A junior to me who has spent a year banging away making real failing programs and can talk about what and where they struggled with is useful to me(and the company).

A junior who hasn't built a single project, but can tell me about the one time they spent 4 months writing data structures on white boards is little more then a warm, but dead silent body in a design meeting.

1 comments

I think the whiteboard advice is for being comfortable in interviews.
Google expects you to write production ready code in a Google Doc for two Leetcode hard problems in 40 minutes.