Deleted Comment
The best technical interviews I've been on as a interviewee have been those where the expectations are clear. In your example:
"We're not expecting you to create Twitter in 15 minutes, but we want to understand how you think about the challenges and key considerations of building a large system like Twitter"
Many interviewers fail to provide enough context and that leaves the interpretation of the prompt too wide open. At that point, the interview has failed since whether a candidate can provide an answer that is aligned with the expectations of the interviewer has an element of chance to it.yes but this not a defect as youre viewing it.
in real world at amazon, your job to deal with ambiguity. the hand holding phase where youre given or told exactly what to do is maybe 1-2 year for college level hire. you work with ambiguity or you move out.
if you do not want ambiguity challenge then amazon not best fit for you. its not for everyone and amazon certainly has big problems in its culture. not defending any of it but saying to you what it is.
system design interview is more about interviewee asking questions..taking time to understand the problem..ask about product feature or SLA..understand functional and non functional requirement.
then its about candidate showing some knowledge set showing they can think and reason behind some immediate coding task. Demonstrate ability to make judgment..simplify where possible..discuss costs and trade offs.
this interview not about candidate building some system at scale themself. building and supporting has trials and lessons you only learn by doing and failing, not through interview prep or YouTube videos
It seems like lately a lot of our CEO's decisions lack backbone or conviction. It seems like he go the role of CEO by yes-maning Bezos (See brain double quote here: https://www.nytimes.com/2021/02/03/technology/andy-jassy-ama...)
A lot of the decisions made by our CEO lately have been justified with "not invented here" logic. Announcements for both RTO and layoffs have been justified with "other leaders are doing it" statements. Unpopular decisions (like RTO) are made days after a public forum where our CEO could have announced it.
rto not even top 3 company problem though. main issue is fast pace culture that had its own problem with retention now turned into lazy, cancerous zombie.
-performance bar lowered at all levels.
-management layers overrun by hires from failing companies.
i left after 10 years. tech stopped hiring innovators. it simply h1b wagon..people who do exactly as told because they afraid of PIP and having to move back to india. the other class of worker is a politician from some company like ibm. from ibm, they bring EXTREME culture of politics and empire building.
my theory that amazon leadership know this biggest business risk. any rto policy to get these people to quit without severance. amazon leadership know problem so bad they will risk strong talent.
much goodreads leadership same as when amazon bought them. i know because i work close to them before i leave amazon.
tech was outdated ruby on rails. the engineering org has very low technical bar and love inventing things that amazon already solve at scale. more energy put into resisting amazon than thinking about innovation. lots and lots of waste.
i do wonder how amazon layoffs affected goodreads. i would clean house.
Good news: most software engineer not taking derivative or vector calculation like full calculus or linear algebra taught in CS program.
but you need ability to reason about basic maths if your program has any computation at all.
khan academy is good for the math. dont really need much more.
me not arguing either way. but wonder about “quality” of this journalism. it subtly condition reader to believe one side is correct and other side like some German nazi.