My LinkedIn onsite is in a couple of weeks. Seems to be a standard lineup of 2 coding, 1 system design, 1 tech communication & 1 HM round. But I have a few questions, hopefully someone from LinkedIn can answer. 1) It seems the tech communication round will be a deep dive into my projects. But frankly speaking, my projects till now have been terribly dull & mundane. Nothing particularly challenging or interesting to deep dive into. I expect feedback from this round to be unimpressive, neutral at best. So how much weight is given by the HC to the feedback from this round as compared to the coding or design rounds ? Is it possible to get a hire call despite this if I do well in the other rounds ? 2) For LC Hard problems how bad is it to come up with a correct but not optimal time complexity solution ? Say, a solution which would time out on the last few cases on LeetCode. 2 yoe, SWE PS: I know this isn't a HR issue, but my company is small. Don't want to get doxxed
For 2, it can be bad if solution is too naive. For example a brute force will not indicate your problem solving skills. If solution is near perfect and there are a few issues with complexity and can be fixed easily then it will not be a problem as long as you’re quick thinking and showing confidence around everything.
Makes sense
How do u post as undisclosed?
Anyone from LinkedIn care to weigh in ? Particularly on point 1.
Might look dull to you but could be impressive to someone else. Generally, find the positive aspect of the project and focus on that.
Ok, but can good performance in coding & design make up for an unimpressive tech communication round ?
Are you on H1B? If yes, did they ask you to join on receipt, if you get an offer?
For #1: it’s mostly about how you can describe your project, challenges, approach to solve them and a result. Even dull projects can be interesting if you define the strategy to talk about them. Follow the STAR pattern, practice and make sure that you have your answers ready.
Good answer. I think dull was a poor choice of words on my part. More accurately, the scale & complexity wasn't particularly high tier, ,& as the junior most dev in the team I got stuck with a lot of grunt work.
tyxus they probably care not only about scale but also about your approach. - do you analyze the problem before jumping into coding? - do you communicate with the team? - how do you handle unexpected situations? - do you think outside of the box? - is anyone helping you? How do you handle their feedback? With that being said - junior dev who relies on teamwork and visibility and ready to learn something new - isn’t a bad thing.