Real, anonymous reports from people who interviewed for Software Engineer at McGraw Hill, newest first and distilled into what to expect across the loop.
After a short recruiter chat, I had a single technical round that was scheduled as a discussion with an engineering manager—but it ended up being led by a senior developer instead. It was mostly verbal, no coding on my screen, and the questions felt very focused on how teams ship and operate software.
The process started with an async video screening submitted to the recruiter. They didn’t give much detail about what came next, and I actually had to follow up to get the interview link shortly before the session started. I was expecting more behavioral questions because there wasn’t any obvious mention of a technical round.
The interview process typically starts with a recruiter call followed by a technical interview, often with multiple interviewers. Candidates noted that the structure was generally clear, with straightforward transitions from one stage to the next, although some experienced delays in communication.
Technical interviews often emphasized practical discussions over live coding, covering topics such as CI/CD strategies, database design, and full-stack development, rather than traditional algorithm challenges. Candidates should prepare for a range of technical concepts relevant to the role, including SQL and system design.
Initial conversations often include behavioral questions, but candidates reported that later interviews shifted focus to technical skills, with varying levels of emphasis on interpersonal dynamics. Candidates should be ready to discuss their experiences and how they align with team operations.
The interview atmosphere varied significantly, with some candidates experiencing friendly and supportive interactions, while others faced unfriendly or unprofessional behavior from interviewers. Candidates should be prepared for a range of interviewer styles and maintain composure in challenging situations.
Candidates noted discrepancies between job descriptions and the actual focus of interviews, particularly regarding the technologies discussed. It's advisable for candidates to clarify expectations about the role and prepare for a broader range of topics than initially indicated.
While many candidates did not receive offers, they reported that the process was generally efficient and less intimidating than other experiences. Candidates should expect timely communication regarding outcomes, though some experienced delays in feedback.