Data Structures for Coding Interviews
interviewcake.com
Data Structures for Coding Interviews
1–10 of 238 posts
Re: Data Structures for Coding Interviews
#2And eager to receive any feedback.
Thanks for the post!
Re: Data Structures for Coding Interviews
#3Original Author here. Happy to answer questions about this piece or coding interviews in general! And eager to receive any feedback. Thanks for the post!
My suggestion would be to have a slightly cheaper tier (probably no more than a hundred bucks). This mirrors the cost of two-to-three interview books. You could add a custom grading or personalized tutoring option for the full 500, or heck, even more (this is sort of like the GRE/GMAT prep option). Come to think of it .. I wonder why the GRE/GMAT prep crowd hasn't tackled programming interviews?
Re: Data Structures for Coding Interviews
#4Original Author here. Happy to answer questions about this piece or coding interviews in general! And eager to receive any feedback. Thanks for the post!
I found the newsletter upsell in the sidebar very distracting. I know you're considered a fool if you fail to bash people over the head with newsletter sign-up requests these days, but maybe just keep the ones interspersed in the text and get rid of the one I have to see all the time? Or I guess AB test it or whatever the cool kids are doing for this stuff. I dunno, but it really detracted from what I otherwise thought was great content.
Best of luck to you!
Re: Data Structures for Coding Interviews
#5Original Author here. Happy to answer questions about this piece or coding interviews in general! And eager to receive any feedback. Thanks for the post!
You've got a cool site and I appreciate all the hard work creating high quality content (I've looked at the free questions and considered subscribing a few times in the past). I think your business model/pricing could use work. Unless I'm mistaken and things are going well .. in that case, I'll withdraw to my cave :-p My suggestion would be to have a slightly cheaper tier (probably no more than a hundred bucks). This…
We've been working on some /tech/ to enable tiered pricing in the meantime. The Site's all custom, and so far there's no notion of a "product" yet...just "paid" and "unpaid."
Share your question re: where's Kaplan on this stuff!
Re: Data Structures for Coding Interviews
#6Original Author here. Happy to answer questions about this piece or coding interviews in general! And eager to receive any feedback. Thanks for the post!
Nice graphics! I really like from-the-bits-up explanations of things like this. I found the newsletter upsell in the sidebar very distracting. I know you're considered a fool if you fail to bash people over the head with newsletter sign-up requests these days, but maybe just keep the ones interspersed in the text and get rid of the one I have to see all the time? Or I guess AB test it or whatever the cool kids are do…
We're really focused on trying to "twist the knobs" only up to the point right /before/ it starts getting annoying.
Re: Data Structures for Coding Interviews
#7Aaaaand this is why I hate using this as a method for interviewing. I actually care a great deal about people that care about that stuff. I would rather you know all the principles and can reason your way back up, however slowly, than repeat something you've practiced enough for an interview.
I understand the author really only wants to help people, but let me tell you as someone who works for one of the "cool unicorns" that the quality of software engineers is really bad, most likely because of this efficient "gaming of the system".
Re: Data Structures for Coding Interviews
#8> Don't worry—we'll skip the convoluted academic jargon and proofs. Aaaaand this is why I hate using this as a method for interviewing. I actually care a great deal about people that care about that stuff. I would rather you know all the principles and can reason your way back up, however slowly, than repeat something you've practiced enough for an interview. I understand the author really only wants to help people,…
I agree with you, this method for interviewing sucks.
Re: Data Structures for Coding Interviews
#9> Don't worry—we'll skip the convoluted academic jargon and proofs. Aaaaand this is why I hate using this as a method for interviewing. I actually care a great deal about people that care about that stuff. I would rather you know all the principles and can reason your way back up, however slowly, than repeat something you've practiced enough for an interview. I understand the author really only wants to help people,…
Here's what a Google lead said in a tweet:
> Hello, my name is Tim. I'm a lead at Google with over 30 years coding experience and I need to look up how to get length of a python string.
DHH:
> Hello, my name is David. I would fail to write bubble sort on a whiteboard. I look code up on the internet all the time. I don't do riddles.
Max Howell:
> Google: 90% of our engineers use the software you wrote (Homebrew), but you can’t invert a binary tree on a whiteboard so fuck off.
And yet, everyone is asking these questions about print a string in zigzag fashion or something silly like that.
Engineers are gaming the system because the system is garbage. None of us are looking forward to waking up and solving HackerRank, LeetCode and CtCI problems till the joy of programming leaves our bodies.
Re: Data Structures for Coding Interviews
#10Original Author here. Happy to answer questions about this piece or coding interviews in general! And eager to receive any feedback. Thanks for the post!