I had a full interview loop at #google yesterday for a Staff software engineer position. Pretty sure I bombed one of the system design interviews but did very well on all the others (another system design, 2 coding, and 1 googlyness). What are the odds that I get through hiring committee? Will I get down levelled? Additional stuff: I have a strong referral and very good resume (large scope at MS and 5 years at FB before MS).
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
Also any good resources that can help with prep?
A good strategy for me in hindsight would be to always start with the REST API design. This is something I have lots of experience with so it’s easy for me to talk about. And, it is a good way to clarify the problem and make sure you and the interviewer are fully aligned.
The other thing I would suggest is to revisit decisions you made earlier and revalidate them. Question yourself even if you are right.
In my example I would have rocked it if I had:
1. started with API design and roughly proposed the request / response payloads
2. Go to Database design and talks about the schema and query model
3. Revisit the API and make sure I actually have the stuff I need to support the query model. Update if necessary
4. Once solidified, move on to the systems design, start adding caches / shards / load balancers to actually scale things out
5. Revisit DB design again etc