Real, anonymous reports from people who interviewed for Software Engineer at Fannie Mae, newest first and distilled into what to expect across the loop.
I started with a recruiter touchpoint after applying, then moved into a fairly light interview process. My first conversations mainly centered on my resume and my projects, with the interviewer asking me to talk through what I had done and how I worked with others. A lot of it felt like behavioral screening with only small technical probes, and nobody pushed me into LeetCode-style problem solving.
My process started with a more casual behavioral conversation, and I could tell quickly that they weren’t trying to catch me off guard. The interview style stayed conversational and relaxed, but I still had to cover familiar ground—tell me about yourself, talk through strengths and weaknesses, and walk through projects I’d already put on my resume.
The interview process typically begins with a recruiter touchpoint followed by a series of behavioral and technical rounds, often blending discussions about the candidate's resume and projects. The overall flow is described as straightforward and low-pressure, with a mix of casual and more intense sessions as candidates progress.
Candidates report a strong emphasis on behavioral questions throughout the process, including inquiries about strengths, weaknesses, and past projects. The interviewers maintain a conversational tone, aiming to understand the candidate's experiences rather than catch them off guard.
Technical discussions primarily revolve around foundational programming concepts, particularly in Java and AWS, rather than live coding challenges. Candidates are expected to explain their understanding of OOP, cloud technologies, and related tools, with a focus on conceptual clarity.
While many candidates find the interviews manageable and respectful, some report inconsistencies in difficulty, with later rounds feeling more intense and challenging. Overall, the experience is characterized as professional, but some candidates express disappointment regarding follow-up communication after the interviews.
Candidates suggest that preparation should focus on articulating their experiences and understanding technical concepts rather than memorizing coding solutions. Many felt that being ready to discuss their background in detail was crucial for success in the interviews.
Some candidates experienced logistical issues, such as restrictive scheduling for interviews and delays in communication, which impacted their overall impression of the process. These factors contributed to a sense of frustration, especially when they felt unprepared due to timing constraints.