Results?\n\nCoding 1A: Caculator II -> Solved Optimally and follow ups\nCoding 1B: LCA -> Solved slightly suboptimally O(n) space complexity, recursion is better according to interviewer\n\nCoding 2A: Binary Search Question, not tagged. Similar to Koko Banana on LC. Got optimal  solution but messed up follow up\nCoding 2B: Largest Number Optimally Solved.\n\nSystem Design: (WebCrawler) Went okay, pointed out issues/questions with my design and I resolved all of them. Ran out of time for the last question however I had already put the design down for the answer, it was moreso about the interviewer understanding. He said he understood my result.\n\nBehavoiral: Didn\'t have the best examples honestly. my previous role was more so testing then feature development at a big tech company. (Legacy Code with multiple releases a year) 1 Question stumped me.\n\nAny thoughts on pass/fail?\n\nCoding 1: Lean Hire/Hire (Idk if interviewer was satisifed with last answer, 1 Optimal + Slightly SubOptimal?)\nCoding 2: Lean Hire/Hire (got the follow up wrong) (Double Optimal, but answered follow up wrong)\nSystem Design: LeanHire/LeanNoHire -> Could go either way, very diffcult to tell what he wanted\nBehavoiral: Learn Hire/Learn No Hire -> Got stumped on one question, interviewer also had to ask follow ups to other questions. Not the best. But he was an extremely nice person, so Idk hard read.

Results?\n\nCoding 1A: Caculator II -> Solved Optimally and follow ups\nCoding 1B: LCA -> Solved slightly suboptimally O(n) space complexity, recursion is bette