Any tips/suggestions on prepping for Google code review interview? What are the common things to look for? Does leetcoding help?
TC: $350, YOE: 12
#google
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 first just have to go line and line and comment what is wrong like codestyle is not good, algo is not efficient, edge cases not handled, incorrect syntax, no unit tests.
Afterwards I added unit tests to it, and then used it to explain the edge cases not handled.
Then finally suggested ways to fix it, and why the algo was better but not fully implement the fix.
It’s pretty much LC easy except you don’t have to implement the full thing but in the end you kind of do, but more focus on explaining and finding the existing issues from someone else’s “bad solution” to that LC easy solution instead of coding it all up yourself from scratch.