So far I thankfully haven't had major issues with Leetcode problems...who know how long this reign will last, but even if I do come across a problem that stumps me, I love learning it anyway.
Most of my failures come from other stupid things like being tested on advanced language, design patterns, or framework specific concepts that I'm a bit rusty though have had experience with. How do I improve on these things? I failed Netflix, Dropbox, and Asana because of this...
I'm feeling really discouraged...
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
It really depends on the company and the level and position.
In my last search it was about 50/50
G for example didn’t give a shit about language specific while fb it was over 50% of the tech part.
Asked about what my fortes were - but since I did some node and some ror I was asked some light topics there and when coming to system design that helped a lot
I work at Dropbox and had an Asana offer. Neither of these companies will ask you about advanced language or framework specific concepts. Asana has a design portion but they tell you beforehand that it will be a design interview.
You can Leetcode your way into F/G, but the reason I think these other companies have a “high hiring bar” is because they’re aiming to quiz your computer science knowledge (which solving algorithms problems is a subset of), not just your Leetcode knowledge.
That being said, questions about systems, memory, basic probability, etc. is not at all the focus of the interview, but it’s fair game.
When I interview candidates, the goal is to see their critical thinking ability, not if they can just churn out code for a problem they memorized.
You are much more likely to need knowledge of some Rails quirks to be productive at a Rails shop than knowing how to trap rainwater in 3d and add binary strings.