Johns Hopkins Applied Physics Laboratory·Software Engineer

Johns Hopkins Applied Physics Laboratory Software Engineer interview experience

No offer

Easy

Neutral

Laurel, MDPosted Aug 2015 · Candidate report, summarized by Dataford

The process took a while from first contact through the interview, and by the time I actually sat down with people it felt oddly unclear.

I met with a series of individuals one-on-one across a department, and it didn’t feel like anyone fully aligned on why they were interviewing me. Different people pitched different priorities and ideas, and I walked away not really sure what the department did day to day—or what specific skill set they were trying to add.

I also went in with assumptions that turned out to be wrong: I believed I was making more than they intended to pay. When the conversation touched compensation, I told HR I wasn’t looking to leave just for salary and that everything was negotiable, but HR still wasn’t very

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?

Johns Hopkins Applied Physics Laboratory 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 Johns Hopkins Applied Physics Laboratory interview guidesEvery role we cover at this company