Check out your Company Bowl for anonymous work chats.
Bowls
Get actionable career advice tailored to you by joining more bowls.
Followed companies
Stay ahead in opportunities and insider tips by following your dream companies.
Job searches
Get personalized job recommendations and updates by starting your searches.
Cengage interviews FAQs
Senior Software Developer applicants have rated the interview process at Cengage with 2.5 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 60% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Developer roles take an average of 21 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Cengage overall takes an average of 32 days.
Common stages of the interview process at Cengage as a Senior Software Developer according to 2 Glassdoor interviews include:
Group panel interview: 22%
Phone interview: 22%
One on one interview: 22%
Presentation: 11%
Drug test: 11%
Skills test: 11%
Here are the most commonly searched roles for interview reports -
The process took 5 weeks. I interviewed at Cengage (New York, NY)
Interview
Company made me wait 1 month after giving me verbal offer then revoked the offer. Really bad experience , pretty sure they juggle candidates to allow their best pick gets the offer and 1st days.
I applied through a recruiter. The process took 1 week. I interviewed at Cengage (Boston, MA) in Mar 2017
Interview
It was a very pleasant process that began with a phone screen directly with the hiring manager (I was connected via an outside recruiter). It was more of a conversation around my experiences with different stacks, my thoughts and opinions, and what I was looking for. I was invited for an on-site interview with a few of the team members where they asked me to solve a couple simple problems in an IDE on someone's laptop. They then followed up with their own questions and I had the opportunity to ask my own.
Interview questions [1]
Question 1
What is your approach around managing state in a React application?