Recently attempted the onsite interview for SWE position(US location). First of all, they have some general questions that they ask repeatedly which is already present over the net(they don’t change the questions). And they expect you to memorize those answers line by line. If you come up with a different approach, then they find it surprising. For instance, one interviewer I met even if the code worked & test cases were passing she always used the phrase ‘surprising how it’s working’. I mean it’s so demotivating for someone taking the interview. Another guy, expected me to solve using a particular data structure, when I was able to solve with better time complexity & all TCs passing - he mentioned that he needs to look up google later if that’s a possible approach 😝. Good luck to them! Thanks for wasting my 5 hrs by a rejection!! Looking forward to my next interviews🤞.
#engineering #software #swe
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
This is why you were rejected. It’s not about LC problem, it’s about explaining your approach and solving the problem together with the interviewer as a team. Sorry to hear you didn’t make it, but your understanding of what we are looking for is completely off. They’re surprised it’s working because they aren’t convinced your approach is solving the problem, and if you can’t explain it in a way they can understand, it can be flagged as a communication/collaboration issue. Not saying that is right or wrong, just stating what might have contributed to the rejection.
Even if your other solution was good, I suspect there were factors beyond coding that led to this rejection. It’s not the end of the world.
Good luck on your current search though, OP. Hang in there & there will be a place for you.
Looks like OP got rejected 🙅♂️