Related Posts
Recently I gave my interview with Amazon, 2 screening rounds and 6 virtual Onsite interview rounds. The process took 2 months.
Now HR is saying ‘the position got filled internally, we are trying to map you to a new requirement’.
Is it worth waiting or should I keep looking out for other opportunities?
Please suggest. Thanks in advance
More Posts
Additional Posts in Software Engineering
I’m a mechanical engineer working for an aerospace company but I want to make the transition into tech. During my last 2 semesters of college, I took some coding classes and realized this is what I really wanted to do. I graduated in December, 2021 and have been teaching myself programming ever since. I still have a log to learn but I want to eventually land a job at HubSpot or Spotify. In the meantime I’m looking for mentors. Is anybody willing to chat and offer some advice and connections?
At least data algorithms, data structures, OOP related questions
D1's answer is usually the correct one, especially at larger companies. Generally though, the question is broad and difficult to answer without knowing what industries/companies he's applying to and what his area of focus is. Small to mid-sized companies sometimes have take-home exercises or more experience/skills based (vs theory-based) questions.
Glassdoor is great to get a sense of the type of interview questions to expect (esp. at bigger companies).
Getting that first position is the most difficult and can be an emotional roller coaster of hopefulness and disappointment. Gotta just keep keep practicing & applying, and studying up on the questions you missed. Also, pro-tip: apply to dream / stretch companies after getting some interview experience rather than first.
“How to Crack the Coding Interview”
Great book.
It’s the secret to all of them
Even mid or senior level can fail technical interviews if they are not familiar with the leetcode/codility platform.
The technical and technical interview skills are two different things.
This right here, great point.
Technical interviews involving DSA vs your knowledge based on work experiences/projects can be 2 completely different things.
He should expect questions he won't be able to answer clearly and immediately, and expect to have to explain a pattern of approach to how he'd figure out how to solve them. Keeping a level head and remembering nobody wins them all will be worth a lot. Persistence and willingness to be communicative are important.
A general understanding of HTTP response status codes
Not the answer you're looking for, but I wouldn't work for vanguard at an entry level software eng job.
Their software is bad. They don't update or innovate. He won't learn much