Software Engineer applicants have rated the interview process at Ocient with 3.9 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 33% positive. To compare, the company-average is 40% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 20 days to get hired, when considering 18 user submitted interviews for this role. To compare, the hiring process at Ocient overall takes an average of 20 days.
Common stages of the interview process at Ocient as a Software Engineer according to 18 Glassdoor interviews include:
One on one interview: 24%
Skills test: 21%
Presentation: 18%
Phone interview: 18%
Personality test: 6%
IQ intelligence test: 6%
Background check: 3%
Group panel interview: 3%
Other: 3%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Ocient (Chicago, IL) in Oct 2022
Interview
Extremely hard OA with one question for maybe 1.5-2 hours. If you do well, then schedule 3 interviews - 2 coding and 1 behavioral. Rejected with no feedback or other communication after 1st coding, although OA with 100% test cases passes.
Quick screening call with the recruiter. The recruiter was responsive and easy to communicate with. Then there was a 2+ hour Hackerrank assessment equivalent to a Leetcode hard or more. I completed about 1/3 of the test cases and received the rejection email a few days after submitting.
Interview questions [1]
Question 1
Build a string parser for mathematical and string operations (a recursive descent parser)
I applied online. The process took 3 weeks. I interviewed at Ocient in Jul 2025
Interview
Decent enough interview cycle for a senior engineering role. Recruiter was friendly and accommodating of my schedule since I was on holiday when they first reached out to me. We started interviewing a few days after I returned home and I made it through three rounds and got to the final round, as the hiring manager put it.
Since the conversation naturally evolved to showing off some side projects of mine via screen share, where I walked the hiring manager and senior on the team through the code, showed them how things got deployed and how I built a security model the application and infrastructure, they decided to not give me a coding assessment but I was asked a set of deeply technical questions and scenarios-which seemed fair-and I got excellent feedback during that my responses were good and right in line with what they were looking for.
The recruiter said I should hear from them rapidly as he prefers to keep candidates in the loop and keep things smooth for everyone…
…except I didn’t hear back from them for a few weeks so I decided to check the careers page again, the role was no longer present, I email the recruiter for a follow up, and it was only then that I got what looked automated response that the role had been filled.
The overall experience was fine I guess, but a little professional courtesy of saying “thank you for interviewing with us but we moved on” would have at least softened the blow from not being chosen for what looked like a pretty interesting job role instead of leaving me to find out on my own after two weeks of radio silence.