I’m on my LC grind per instructions, but in the meantime I am going to be conducting some interviews. Is there anything you wish your interviewers would say or do to make the experience better?
TC: 150
YOE: 5
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
Instead of expecting them to know to write a multi line comment explaining what they’re gonna do, explicitly ask them to. Then ask time and space complexity. For the purposes of these interviews, any answer that shows up on leetcode is probably fine in terms of demonstrating coding skill. A clean brute force o(n^2) approach can be just as good at indicating a good web dev as the o(n) solution.
Paste the problem. Give them time to read it. Keep in mind many tier 1 companies don’t actually expect to run the candidate’s code, they just look at it themselves even if there’s syntax highlighting. After the code is done or a helper method is finished ask the candidate to explain line by line how everything will work in a given test case.
If you don’t pay much then probably just give the candidate test cases to pass as the first step instead of making them come up with their own. With the idea that if the code works for those cases then it passes no matter what. (Eg no need to bother checking for null if you don’t provide a null test case)
I believe the reason is that virtual interviews were inspired by whiteboard interviews, and typos aren’t interesting to worry about.