Live data from Hacker News

LeetCode for System Design

leetsys.dev

11–20 of 56 posts

Re: LeetCode for System Design

#13
post #5
post #4

Earlier quoted context omitted.

> 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.

> 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.

I think you're trying to rarionalize away the fact that system design involves knowing patterns and how to apply them.

In each and every single technical field, it's good to be able to improvise but it's even better to know what you are doing.

What you dismiss as "scripted / memorized hoop-jumping experience" actually translates to theoretical and practical knowledge to solve specific problems. Improvisation is a last-resort to fix problems you never faced before.

So yeah, this blend of criticism boils down to complaining that the only good tests are the ones you can pass, and everyone who is more experienced, prepared, and outright competent should not given preferential treatment.

Re: LeetCode for System Design

#15
I have a lot of feedback.

No links to the Terms of Service and Privacy Policy.

No way to preview without signing in.

Only way to sign in is with Google.

"Trusted by engineers landing jobs at" ...given how new this is, is this line marketing fluff or is there evidence that engineers actually trust LeetSys?

Finally, I'm worried that this will make system design interviews as miserable as coding interviews.

Re: LeetCode for System Design

#16
post #7
post #4

Earlier quoted context omitted.

> 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?

> 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.

What do you think a technical interview is? Everyone steps into a job interview hoping to outperform all other candidates in whatever criterias they will be evaluated on. Vibes play a role, but don't you think that being able to demonstrate technical skills matters?

Re: LeetCode for System Design

#17
post #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.

This goes for anyone experiencing the API timeout!

Using the beta/preview gemini live audio models - so there have been some hiccups

Re: LeetCode for System Design

#19
post #4

Earlier quoted context omitted.

> 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 hire…

> 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.

It's nice that you estimated throughputs and provided your assessment. Odds are that's not the problem you were tasked to solve?

I mean, arguing your way out of proposing a design for scale reads as if you're at a test and you're claiming you shouldn't be asked some questions.

> 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.

Clarifying questions are an expected part of the process, but by it's own nature the design process is iterative and has a initial design on where to iterate over. If you do not show forward progress or present any tangible design, your own system design skills are immediately called into question as, in the very least, it shows you're succumbing to analysis paralysis.

Think about it: you're presented with a problem, and your contribution is to complain about the problem instead of actually offering a solution? What do you think is the output valued by interviewers?

Re: LeetCode for System Design

#20

I have a lot of feedback. No links to the Terms of Service and Privacy Policy. No way to preview without signing in. Only way to sign in is with Google. "Trusted by engineers landing jobs at" ...given how new this is, is this line marketing fluff or is there evidence that engineers actually trust LeetSys? Finally, I'm worried that this will make system design interviews as miserable as coding interviews.

> "Trusted by engineers landing jobs at"

Semi off topic, but is it really legal to put Google/Netflix/etc's logos on their website like that?

Post reply on HN