Hi, I have onsite interview coming up with Vrbo previously Homeaway in Austin TX for SWE 2. The schedule shows I have 4 rounds 45 minutes each. Can some one please let me know what is the LC difficulty level? Anything else that I should know before onsite? Updating the post on popular demand about my experience. I interviewed for SWE 2 and went to onsite in Austin. Had 4 rounds, 3 are pure LC problem solving stuff. Last round is supposed to be culture fit discussion but had a LC problem adked as well. The difficulty is LC Medium. String manipulation, DFS/BFS, basic dynamic programming, some system design knowledge as well. I got the offer two days after the onsite and will be joining them soon.
It will be easy, LC medium/easy. Expect system design. You will probably be interviewed by the team that is hiring for your position.
How did the interview go? What was the focus on?
Hey OP can you pls update your experience? How was the phone screen and the onsite?
Hi, Can you update your onsite interview experience?
Hi,did you end up interviewing at vrbo? Can you share your experience?
Or has anyone got onsite scheduled?
Updated post. Thanks for the interest.
Congrats and thanks
Do you mind sharing whaLC questions were being asked
LC difficulty? Meaning... Leetcode? I'd bet 90% of our engineers don't even bother/know about Leetcode. For SWE 2 aka "Engineer", I'd expect 3 (if not all 4) interviews to involve traditional whiteboard questions around algorithms and OOP. Probably some tech specific questions depending on the team and/or your resume. (Ie, if you're a node person... You might get asked something specific about node if the team also happens to use node)
I got asked an LC hard question in first round - hirevue technical video interview. I solved like only ~40% and still got invited to onsite. I am a .Net guy and applying for Java position. I am good with coding in java but don’t know the frameworks etc.. When you say traditional algorithms can you share an example?
For an Engineer role, I've asked algorithm questions to just get a feel of the candidate's ability to problem solve and work through the problem. We don't ask them any more, because they are so overused and known by most candidates in advance, but things like sum exists or loop in a linked list. (Google "sum exists interview question" -- it's a simple algorithm question with 3 different answers, so it's easy to iterate and discuss big O complexity. For an Engineer role, that's not an unreasonable question since most SWE 2 level folks are still close enough to college that you might remember that stuff!)