LinkedIn offer after 8 months of on and off interviewing while employed
Numerous applications, I didn’t count but I know I applied to many, many positions. I debated posting about this because I don’t want to brag but I’m sure there’s many that could use some of the things I know led to success.
Enter the Interview Pipeline 1. Networking: the easiest way to start the interview process is to get referrals for positions that you want. This is easier than the second step and will get you to the interview process faster.
- Resume: of course this comes to know surprise but it’s always good to spruce it up every two months or so. I ended up using ChatGPT to help me write out the things I did at each of my previous + current employers that would also be relevant to the job I’m applying for. Example: write a resume based on the following job description [paste job description] and it will spit something out that you can tailor (as much as you like) to your own resume.
Interviewing 3. DSA: usually the first interview will be data structures and algorithms so you need to get this down. Leetcode is definitely where it’s at from everything else that I have tried (e.g. interviewbit). However, it’s good to have a solid approach to it. Doing random questions will not help and can in fact harm your progress for DSA. Neetcode is a good option but the Tech Interview Handbook helped more since it strategizes the order of questions that you should be following. Even more useful if you have limited time or just want to maintain your DSA skills.
Architecture and System Design: this is for mid-level or higher so don’t worry about this part if you’re not there yet but it can’t hurt either. I followed the link below: https://github.com/weeeBox/mobile-system-design To help me get a good understanding of system design. I also did a hellointerview practice interview to get an idea of what I could do better on. This was about a month before my onsite, but it gave me a good idea of what I needed to improve and be prepared for.
Engineering blogs: this is the difference maker. Obtain a list of engineering blogs and read one or two a week while taking notes. If you can read blogs on the company you’re interviewing for it will drastically benefit you when it comes to conversing with the interviewers.
The interview process itself was as follows: Applied for position Week or two later got message from recruiter interested to interview. Technical interview screen: DSA - I didn’t write down the specific question so I don’t remember. The next week got feedback that they wanted to do onsite, scheduled onsite for almost a month out. Onsite: 1. DSA - I don’t remember the question but I’m certain it was medium and solved it optimally after some discussing with interviewer 2. Mobile System design - typical system design with a focus on the mobile end 3. Behavioral - unlike typical behavioral interviews (using STAR) we discussed a technical problem without any virtual white board or code. 4. Mobile coding 1 - I’m completely blanking on this round but I want to say it was swift coding focused on less app building. 5. Mobile coding 2 - was given a small Xcode application that I had to make instructed contributions to. Just focusing on the task is important. Received offer the next week.
Hopefully this is helpful, I also have several notes I may release that helped me evolve and stay on track. Good luck!
EDIT: forgot to mention it was a mobile position hence the focus on mobile system design and mobile coding.