
Ocient Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 34 interview experiences · FREE TO READ
Which role are you interviewing for?
5 roles · 34 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Ocient.
Software Engineer
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.
- Inquiries about general networking?
- Inquiries about software in general?
Senior Software Engineer
Had an initial online assessment that lasted about 1.5 hours. It involved a substantial problem that was tough to finish all test cases within the time limit. The tasks weren't technically complex but required a significant amount of work. Following that, there were two coding interviews, which weren't overly challenging. The process involved collaborating with the interviewer to solve problems incrementally. Then, there was a discussion with the hiring manager, which was mainly conversational. The next stage is a system design review, which I haven't completed yet.
- Mostly focused on implementation details.
- Can you walk me through your thought process for solving this coding problem?
Systems Administrator
I applied to Ocient a while ago and made it pretty far, but then got ghosted. I recently reapplied for a similar role since I was still interested in the company. I was happy with the HR communication this time and felt like I showed a lot of interest. I got to the third round, but they ended up going with other candidates they felt were a better fit. I'm not sure if I'd try again; they seemed to be looking for very specific high-level skills that didn't quite match the job description. They mentioned I was the only one interviewed up to that point, but then said there were stronger candidates, which felt a little contradictory. Hopefully, others have better luck if you decide to apply.
- Can you discuss your background with Mac hardware and its administration?
- What kind of leadership experience do you have?
- Have you worked with Okta before?
Director
The interviews were cordial. I first spoke with a recruiter for a screening call. My second interview was with a Director who offered me a role at a lower level, instead of the role to which I applied. After making it clear that I was not interested in continuing with the interview process for a lower level role, I was told that I would be contacted for an interview for a role at the level to which I applied. A couple weeks later, I was given another interview. Toward the end of the interview, I asked the interviewer to verbally confirm the role. I was told that it was the same lower level role as before. I thanked the team for their time and declined to continue any further interviews.
- Tell me about your experience with Agile methodology.
Ocient Interview Questions
Quoted word for word from Ocient interview reports.
“Build memory, parse machine instructions, and build a virtual machine.”
Read reports →“Implement BFS using a breadth-first search approach.”
Read reports →“Can you build a virtual machine using C++?”
Read reports →“How would you implement a fixed-size queue for a Twitter feed that can also handle duplicate removal?”
Read reports →“Could you write code to simulate Conway's Game of Life for N generations?”
Read report →“Using your cursor program, how would you determine the number of moves needed to type a word?”
Read report →“Build a VM as specified by Hackerrank instructions”
Read report →“Could you write a PRNG class that generates reproducible random number sequences?”
Read report →“Could you create a program to simulate cursor movement on a keyboard?”
Read report →Formats, difficulty and experience
Across all 34 Ocient interview reports.