Candidatei-me por meio de recrutador(a). O processo levou 1 dia. Fui entrevistado pela McGraw Hill (Seattle, WA) em set. de 2019
Entrevista
I was contacted by a recruiter. Afterwards I had a phone interview. After the pone interview I was invited onsite. The onsite interview went well until it didn't. I really though I was a perfect fit for this position. I mean who has 10 years experience with php and 3 years angular. The exact tech stack they were committed to. It all came down to the site reliability engineer asking me several questions about micro services. I couldn't answer. Who in their right mind is using php to build micro service architecture. Anyway. That is when it all went south. My php experience was using drupal, magento, code igniter, and symfony. That didn't cut it. Ever since this interview I have been educating myself on micro services. In the process of educating myself though .net core I realized the site reality engineer who was interviewing me didn't even know what he was talking about. Dude was deploying the same php code on the same hosted server which isn't a micro service at all. When I met the site reliability engineer I had an immediate feeling that he did not like me. From the first second we met hands I had an intuition that the interview was not going to go well.
Perguntas de entrevista [1]
Pergunta 1
A bunch of micro service questions. Several questions about how to monitor health, design patterns, and logging. Ironically not many Angular questions. I question whether anyone actually knew angular.
Candidatei-me online. Fui entrevistado pela McGraw Hill em abr. de 2026
Entrevista
I passed the screening round, which was an async video submitted to the recruiter. I was then invited to the next round, but they didn’t provide any details about the hiring process, what to expect, or the interview format.
They said they would send the interview link shortly, but never did. I had to follow up myself, and only received the link a few minutes before the interview started.
I was expecting behavioural questions since there was no mention of a technical round. However, I was asked to do live coding for a React problem and also design a near real-time system for a teacher dashboard.
One of the interviewers came across as unfriendly and didn’t provide any feedback during the session.
After the interview, it took 2 weeks for the company to send the rejection email finally, although even if they wanted to proceed by that time I already got an offer
Perguntas de entrevista [1]
Pergunta 1
Typical screening questions, what was a bug you worked on, why a new role
Candidatei-me por meio de recrutador(a). O processo levou 6 dias. Fui entrevistado pela McGraw Hill em ago. de 2014
Entrevista
Interview process was a complete chaos. Contacted by recruiter, then insisted on scheduling an on-site interview on a specific day. Pushed back several times and explain no availability on that day, but was innundated by emails, calls, voice mails etc. Once on-site interview was scheduled finally on my available time, they asked to schedule a phone interview. Basic Java questions on phone interview. No coding questions during on-site interview, no write some code on board nothing, all behavioral interviewing. Talked on conf call to a senior tech mgmt during on-site interview which complained about problems with higher sr. mgmt?? Got calls from recruiting after interview to move fwd, and thought we are entering offer negotiations. Wrong! I was scheduled to talk to HR after all the process who again asked me behavioral questions and desired salary, and I had to repeat myself again. I was asked to apply to position online after all this, and just got email to fill out background again! Serious disconnect between departments, and major flaws in hiring process points to an disorganized work culture.
