Always Be Coding – How to Land an Engineering Job
1–10 of 250 posts
Re: Always Be Coding – How to Land an Engineering Job
#2Great read. I think you're missing a link in there.
"Spend at least 40 hours coding solutions to different types of problems. One of the best resources is TopCoder. Read this. Then try solving problems."
Did you mean to link to the top coder algorithm tutorials?
Re: Always Be Coding – How to Land an Engineering Job
#3These are good tips, and the advice is well-worded, too. I will bookmark this for myself and my friends.
Re: Always Be Coding – How to Land an Engineering Job
#4Good tips, although I'm not sure if the ratio means anything. When I was young I'd happily apply to jobs even if I didn't match on everything in the ad, even though the end chance of getting the position was lower no matter how well I interviewed.
Now that I'm older and have a job I like I usually pop out a really high salary number as early in the process as possible to scare away any companies that would take a lot of work to interview with and then not be able to afford me.
So you could have a very low ratio of offers for reasons other than your interview performance. :)
Re: Always Be Coding – How to Land an Engineering Job
#5The page won't scroll on chrome for android :(
Re: Always Be Coding – How to Land an Engineering Job
#6Great read. I think you're missing a link in there. "Spend at least 40 hours coding solutions to different types of problems. One of the best resources is TopCoder. Read this. Then try solving problems." Did you mean to link to the top coder algorithm tutorials?
Thanks! Fixed.
Re: Always Be Coding – How to Land an Engineering Job
#7You can build a startup in the time it takes to thoroughly prepare for these interviews/positions.
Willingly subjecting yourself to this rat race is essentially the same thing as stamping yourself as an "ibm man," in the words of Jobs.
Who cares if you don't know the intricacies of all the hot algorithms of the day. Spend your time creating actual value for the world, instead of practicing just for the sake of impressing someone.
Re: Always Be Coding – How to Land an Engineering Job
#8Good tips, although I'm not sure if the ratio means anything. When I was young I'd happily apply to jobs even if I didn't match on everything in the ad, even though the end chance of getting the position was lower no matter how well I interviewed. Now that I'm older and have a job I like I usually pop out a really high salary number as early in the process as possible to scare away any companies that would take a lot…
I made it clear that this doesn't mean "applied to" but actually onsite interviews.
But your'e right, the ratio doesn't mean anything. ;)
Re: Always Be Coding – How to Land an Engineering Job
#9Really good post, thanks David.
I'm really curious as to how you landed an interview at Google (let alone a job) without a college degree. My understanding is they are very strict about that and it's hard to even get a foot in the door without a degree.
[disclosure: I'm on a 10 year "hiatus" from my senior year in college]
Re: Always Be Coding – How to Land an Engineering Job
#10Really good post, thanks David. I'm really curious as to how you landed an interview at Google (let alone a job) without a college degree. My understanding is they are very strict about that and it's hard to even get a foot in the door without a degree. [disclosure: I'm on a 10 year "hiatus" from my senior year in college]
I had six years of experience in video games and was a hardcore C++ programmer. To be honest, I was surprised they called me.
Nowadays, showing a body of work speaks volumes. Show, don't tell!