Live data from Hacker News

LeetCode for System Design

leetsys.dev

1–10 of 56 posts

Re: LeetCode for System Design

#3
This kind of thing frustrates me so much. Hiring and interviewing for software engineers is just so broken and detached from reality.

In theory, this should be the easiest discussion to pass while interviewing if you've done some kind of related work or qualified. Instead it's just turning into another insane cargo culted game where you need to do things according to some weird rules and hit certain buzzwords.

Re: LeetCode for System Design

#4
post #3

This kind of thing frustrates me so much. Hiring and interviewing for software engineers is just so broken and detached from reality. In theory, this should be the easiest discussion to pass while interviewing if you've done some kind of related work or qualified. Instead it's just turning into another insane cargo culted game where you need to do things according to some weird rules and hit certain buzzwords.

> In theory, this should be the easiest discussion to pass while interviewing if you've done some kind of related work or qualified. Instead it's just turning into another insane cargo culted game where you need to do things according to some weird rules and hit certain buzzwords.

Your comment reads as if you think system design interviews are good if you can pass them but they are bad if you fail them.

Re: LeetCode for System Design

#5
post #4
post #3

This kind of thing frustrates me so much. Hiring and interviewing for software engineers is just so broken and detached from reality. In theory, this should be the easiest discussion to pass while interviewing if you've done some kind of related work or qualified. Instead it's just turning into another insane cargo culted game where you need to do things according to some weird rules and hit certain buzzwords.

> In theory, this should be the easiest discussion to pass while interviewing if you've done some kind of related work or qualified. Instead it's just turning into another insane cargo culted game where you need to do things according to some weird rules and hit certain buzzwords. Your comment reads as if you think system design interviews are good if you can pass them but they are bad if you fail them.

What the poster is insinuating is that system design interviews may devolve into a scripted / memorized hoop-jumping experience rather than being a creative technical problem solving discussion.

Re: LeetCode for System Design

#6
post #4
post #3

This kind of thing frustrates me so much. Hiring and interviewing for software engineers is just so broken and detached from reality. In theory, this should be the easiest discussion to pass while interviewing if you've done some kind of related work or qualified. Instead it's just turning into another insane cargo culted game where you need to do things according to some weird rules and hit certain buzzwords.

> In theory, this should be the easiest discussion to pass while interviewing if you've done some kind of related work or qualified. Instead it's just turning into another insane cargo culted game where you need to do things according to some weird rules and hit certain buzzwords. Your comment reads as if you think system design interviews are good if you can pass them but they are bad if you fail them.

I've failed system design interview where they repeatedly asked me to design "for scale" but all the volume and latency requirements I could get from them could be handled by a single HA pair running a monolithic server+ external managed data store.

They also seemed annoyed that I am asking them questions that are not part of the problem statement instead of getting down to drawing a fancy diagram.

I'm sure they hired someone who drew a lot of boxes with cute logos because webscale.

Re: LeetCode for System Design

#7
post #4
post #3

This kind of thing frustrates me so much. Hiring and interviewing for software engineers is just so broken and detached from reality. In theory, this should be the easiest discussion to pass while interviewing if you've done some kind of related work or qualified. Instead it's just turning into another insane cargo culted game where you need to do things according to some weird rules and hit certain buzzwords.

> In theory, this should be the easiest discussion to pass while interviewing if you've done some kind of related work or qualified. Instead it's just turning into another insane cargo culted game where you need to do things according to some weird rules and hit certain buzzwords. Your comment reads as if you think system design interviews are good if you can pass them but they are bad if you fail them.

Thinking of it as pass or fail is really the problem. That leads to having some kind of criteria that ends up being gamed. Which is what happened to this style of interviewing.

"system design" as it's done now by everyone is a bad interview whether I can pass it or not. You just need to hit the right buzzwords or draw the right boxes. How is that effective?

Re: LeetCode for System Design

#8
Thanks for posting. I like the concept but ran into several showstopping bugs. I clicked on the "Start Interview" button and received a "No response from Gemini" error. When I exited the interview, it said that I had used all free interviews and suggested that I upgrade to Premium for $5 a month.

With all due respect, why would I pay $5 a month for something that self-implodes as soon as I hit one button?

Re: LeetCode for System Design

#10

Thanks for posting. I like the concept but ran into several showstopping bugs. I clicked on the "Start Interview" button and received a "No response from Gemini" error. When I exited the interview, it said that I had used all free interviews and suggested that I upgrade to Premium for $5 a month. With all due respect, why would I pay $5 a month for something that self-implodes as soon as I hit one button?

Hi - please email me with your username at leetsys02@gmail.com

Did not expect this to be gaining traction! Working to get the bugs fixed.

Post reply on HN