The other day Kyle complained about system design interviews on twitter and I shared a few words of advice. You might like them too :)
This is the point of system design interviews. To find where your strengths are and aren't. (important for team building)
Ideally you have a rough high level sketchy understanding of all the pieces and enough humility to say "I don't know"
I've done several dozen of these interviews over the past ~year and the easiest way to fail were people who pretended to know about something they didn't.
Anyone who said "I've never done this but here's what I'd look into" got a 👍
Details depend on position.
I'd expect a fullstack engineer to know SQL and be able to explain what a CDN is for. But for a pure frontend, I'd dig more into domain modeling and state management.
As for how to get better ... I think this is one of those things that work like the pottery class metaphor.
You have to design a bunch of systems and get feedback.
The best feedback comes from production.
Here's how it works 👇
And get thoughtful letters 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️