McGraw Hill·Software Engineer

McGraw Hill Software Engineer interview experience

No offer

Easy

Negative

New York, NYPosted Jul 2026 · Candidate report, summarized by Dataford

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.

I talked through Terraform and how I approached CI/CD pipeline strategy, then got into how GitHub Actions works in practice. A big chunk of the conversation also centered on observability and what production support looks like day to day. Toward the middle, I was asked about basic database schema design for a simple education domain—teachers, students, classes, and assignments—and how I’d think about modeling those relationships.

Overall it felt easy and straightforward:

Create a free Dataford account to unlock the full round-by-round breakdown, the questions asked and the outcome.

Read the full report Read the full report

Preparing for this interview?

McGraw Hill Software Engineer interview guideThe full process, round by round, with the question bank Practice Software Engineer interview questionsReal questions from this role across companies All McGraw Hill interview guidesEvery role we cover at this company