Real Interview Experiences
Learn what to expect directly from candidates and interviewers who've been through it.
Interviewed recently? Share your experience to try it free, or become a member for full access.
“Technical screening wasn't that hard. Have to solve 3 SQL and 3 Python. You are fighting against the time.”
“More difficult than I had expected. The questions were new, and there was a lot more counter questioning than expected. Especially in the product design round.”
“Overall, the interview process was pretty straightforward and well organized. The interviewers were friendly and gave me a good opportunity to talk through my experience and approach to problems. The process was a little lengthy, but overall it was a positive experience.”
“Overall, I felt that the interview went well. I was able to clearly explain my experiences, discuss the projects I have worked on, and connect them to why I was interested in the position. I was also comfortable answering technical and behavioral questions, and I think I communicated my thought process effectively rather than just giving short answers.”
“The Overall Interview ProcessStep 1: Online Assessment (OA): A 60-90 minute screening on platforms like Codility or HackerRank, often featuring 2 LeetCode Medium coding questions and sometimes logic or SQL-based multiple-choice questions.Step 2: Technical Screening (often via Karat): A live technical interview with a third-party partner like Karat. This focuses on core Data Structures and Algorithms (DSA) and fundamental software engineering principles.Step 3: Technical Deep-Dive / Team Panel: A more thorough session with Citi engineers focusing on System Design, Java/Python specifics (like multithreading or database ACID properties), and a deep-dive into your past project architecture.Step 4: Hiring Manager / Behavioral Round: A "culture fit" discussion using the STAR method to evaluate your teamwork and communication, often ending with HR discussions on salary and policy”
“The interview process consisted of several stages: an initial recruiter screening, an online assessment, technical/product interviews, and a final round of behavioral interviews. The recruiter screen focused on my background, product experience, and motivation for applying to Meta. This was followed by an online assessment that tested my product thinking, analytical skills, and ability to structure solutions clearly. In the technical interviews, I was evaluated on product sense, execution, and analytical thinking. I was asked to design product features, define success metrics, and walk through how I would investigate changes in key performance indicators. These interviews emphasized structured thinking, user-centric design, and data-driven decision-making. The final stage included behavioral interviews, where I discussed past experiences, leadership, conflict resolution, and how I align with Meta’s values. There was a strong focus on collaboration, impact, and ownership. Overall, the process was rigorous but well-structured. It largely matched my expectations in terms of the focus on product design, metrics, and behavioral fit. The emphasis on clarity of thought and structured problem-solving was particularly consistent with what I had anticipated. ”
“The process was more rigorous than most interviews I’ve done at other large tech companies. The recruiter was accurate and helpful about what to expect, which made it easier to prepare. The interviews themselves were structured and generally well run. A few questions and follow-ups caught me off guard, and some rounds felt more dependent on navigating ambiguity in the moment than I expected.”
“The process started with a recruiter screening testing some behavioral questions and some technical questions she read from a question bank. Then, I did a coding interview online. Finally, a 4 rounds loop online (as opposed to my previous attempt when I did the loop in one of their London (UK) offices): 2 coding interviews, 1 system design, 1 behavioral with an engineering manager.”
“The process was standard, with a recruiter chat first, then scheduling round 1 with 2 PMs: 1 on product sense and the other on metrics. Product sense - the interviewer likes to know how you frame the problem, set goals, and how it ties with the overall company strategy. Make sure to be concise and walk users through problems to solutions before time is up.”
Preview full access of other recent interview experiences
“The weirdest Anthropic round was the company values interview. It was almost like a therapy session, and honestly if you went to a therapist at some point, you will pass that round much more easily.”
“What was very unusual is they didn’t give me any tooling to draw the system design, so I just sketched it on a piece of paper and talked them through it, then we got into this oddly deep debate about whether hover-over history should count as a recommendation signal.”
