I see a lot people recommended DDIA for system Design.
Can someone tell me how the book helped you crack the interview?
Also it is quite big, so what chapters/parts would you recommend to read first?
TC : 120K
Yoe: 2
Want to see the real deal?
More inside scoop? View in App
More inside scoop? View in App
blind
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
FOLLOWING
Industries
Job Groups
- Software Engineering
- Product Management
- Information Technology
- Data Science & Analytics
- Management Consulting
- Hardware Engineering
- Design
- Sales
- Security
- Investment Banking & Sell Side
- Marketing
- Private Equity & Buy Side
- Corporate Finance
- Supply Chain
- Business Development
- Human Resources
- Operations
- Legal
- Admin
- Customer Service
- Communications
Return to Office
Work From Home
COVID-19
Layoffs
Investments & Money
Work Visa
Housing
Referrals
Job Openings
Startups
Office Life
Mental Health
HR Issues
Blockchain & Crypto
Fitness & Nutrition
Travel
Health Care & Insurance
Tax
Hobbies & Entertainment
Working Parents
Food & Dining
IPO
Side Jobs
Show more
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
comments
You should be able to show case how you handle an abstract problem.
It is not the answers You give but quality of questions you ask, tradeoffs you make, tools you have at your disposal.
Can you spot potential challenges such as single point of failure, do you create good abstractions, highly cohesive yet loosely coupled system
Do you know what might be the bottleneck (reads or writes) and how do you intend to solve for that.
Do you take cost into consideration? What's your api like? Do you have well defined data model with nice bounded context? When you make a recommendation, are you able to mouth off the cost benefits of your choices?
Do you take reliability, consistency (very different from C in ACID), availability considerations.
If you were to suggest that i will abstract out the complexity of coordination by using a zookeeper cluster.. that's fine.. almost everyone does it.. but when challenged do you know why and how it does what it does).
When you say dynamodb.. do you know why? Why is it key value always available db better but may fail on consistency etc.
So DDIA gives you ammunition to sound more intelligent than you may be.
Can you perhaps sound knowledgeable about causality, vector clock, version vector, which are common things that various distributed databases use. Again it is not that you should know but enough to sound dangerous I think because you never know what you are up against.
This is all assuming you are targeting Staff or Sr Staff engineering role.
Given your YoE being 2 and you may be fairly green, you may not. Educative/grokking is more than enough. I'd focus more on LC and getting those juicy offers
All the best and wish you all green lights OP
Internal candidates like myself get the short end of the stick. Good job here is your promo without $ so that's that
Giving back - how I cleared L6 System Design - Part 1 (Tech Industry)
https://us.teamblind.com/s/4yufM3RY
Flagged by the community.