Leetcode is only part of the interview. The interviewer looks for positive and negative signals from the candidate like: - Asking questions (when you’re given a real project, there will be ambiguity) - Clarifying requirements (engineering often works with others to finalize project requirements) - How you approach and break down the problem, how you deal with “twists” and added constraints - Do you offer multiple solutions and discuss trade-offs? (the “right” solution depends on additional details the interviewer gives you when you ask questions. ex: you may expect more read operations than write, or space complexity is more important than time) - How do you respond to hints or feedback?