Tips on Coding and System Design interviews format and time management?

Amazon / Eng
happypupy1

Go to company page Amazon Eng

PRE
Amazon
BIO
SDE2
happypupy1
Oct 4, 2021 14 Comments

I am preparing hard for coding (grinding leetcode) and system design (grinding YouTube videos, DDIA book, etc.).

I thought i gained good enough knowledge. So, I tried some mock interviews with few folks in real companies and I failed.

The reason is that I fail to do time management and format following.

Coding:
Spent too much time on discussion, jumped directly to optimized solution, etc.

System Design:
Spent too much time showing off scaling number calculation (its waste of time in most of interviews i guess)
Didn't spent much time on API design..
directly draw complex diagram without a simple start... (YouTube videos trained like that)

It sucks if you are prepared but can't follow format and get failure. (which means you are not prepared).

I want this post to act like a guide from experienced interviewers and candidates (who failed and then succeeded by learning abt format and time mgmt) in this area.

Please help giving pointers which helps me improve on these aspects .

TC: 220k

comments

Want to comment? LOG IN or SIGN UP
TOP 14 Comments
  • Uber / Eng
    au23803

    Go to company page Uber Eng

    PRE
    EPAM Systems, Groupe Renault
    au23803
    This one helped me a lot during system design round: https://leetcode.com/discuss/career/229177/My-System-Design-Template

    For coding I use the following approach:
    1. Requirements and constraint - 5 minutes
    2. Write few test cases (happy path, corner cases, etc) - 5 minutes
    3. Brute force
    4. Optimization

    The most important thing is not what you write, but how you behave, speak and ask.
    Oct 4, 2021 4
    • Also, you know how they say “System design has no right answer”. Again, not so true all the time, specially so with Uber interviewer, who for some reason was more interested in hearing to his version and wasn’t open to hearing new ideas.
      Oct 4, 2021
    • Uber / Eng
      au23803

      Go to company page Uber Eng

      PRE
      EPAM Systems, Groupe Renault
      au23803
      Microsoft, I agree with you.

      Coding round often depends on the expectation... for EMs it is often fine to not to solve the problem, but for IC it is likely nohire.

      For the system design round you will be pushed into deep dive in the area which is a core competency of the interviewer.
      @OP I would also recommend to check their LinkedIn profiles :))
      Oct 4, 2021
  • Apple
    ViHG60

    Go to company page Apple

    ViHG60
    In my 5 onsite rounds I never did estimations and interviewer didn't ask. Still got 3 offers. I think jts safe to skip but keep in mind those numbers if asked
    Oct 4, 2021 1
  • Yes nobody cares about scaling numbers except nerds. I normally just say "I assume it should support a lot of users" and they agree and we just continue with multiple of each layer rather than specific numbers

    Weird they complain about coding optimal right away unless you didn't even talk about other slower solutions before implementing. Mentioning slower then implementing optimal is fine
    Oct 4, 2021 1
  • @OP, Which service / site you used for mock interviews? How was the experience?
    Oct 4, 2021 2
  • New
    Chic

    New

    Chic
    I think you have all the pointers you need? Understanding the tech is one part, but you also have to consider the whole 'performance'. The things you point out are all important too.
    Oct 4, 2021 1