Software Engineer applicants have rated the interview process at BRAIN CORP with 2.6 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 36% positive. To compare, the company-average is 37.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 23 days to get hired, when considering 11 user submitted interviews for this role. To compare, the hiring process at BRAIN CORP overall takes an average of 27 days.
Common stages of the interview process at BRAIN CORP as a Software Engineer according to 11 Glassdoor interviews include:
Phone interview: 30%
Presentation: 25%
One on one interview: 20%
Group panel interview: 15%
IQ intelligence test: 5%
Skills test: 5%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 4 weeks. I interviewed at BRAIN CORP in Apr 2019
Interview
applied, then got a response about a month later asking to do a take home coding project. i've never really been a fan of these and those timed exams, but do a few timed exams for companies where I know I can get some feedback. I swiftly let the recruiter that I'd like to respectfully remove myself from consideration from the role because of my experience with take home projects. If you look at other interviews on glassdoor, you can see my suspicions are confirmed since some people haven't gotten feedback. The recruiter let me know that they give feedback to some candidates, but to others, "we just receive poor code and the engineers don't have the time to coach/mentor candidates." The phrasing "don't have the time" indicates a bit of an ego on their end. Regardless of the outcome, Brain Corp is asking candidates for a time investment, it's only fair to ask for an equal investment on feedback. That phrasing re-assured me that this was not a company I'd like to interview for.
Whether you're early on in your career or have years of experience, always remember that interviewing is a 2 way street. Please realize your time is as valuable as theirs.
Interview questions [1]
Question 1
Do a coding challenge, you have up to 2 weeks to do it.
Interviewed onsite for the Software Engineer, Proof of Concept role. The team members I met were friendly, and some conversations were interesting, especially around applied AI, robotics, and proof-of-concept development.
The process could have been more clear and consistent. The onsite instructions mentioned that AI coding tools were allowed/expected, but in one technical round I was told not to use them. Clearer expectations for each round would make the experience better for candidates.
Interview questions [1]
Question 1
The interview included a hands-on coding/project-style exercise, an OOP-based coding question where code was given directly with limited explanation, behavioral questions, and some applied ML questions. Some rounds were useful and interesting, but overall the interview process felt a bit unstructured, and in a few parts it seemed like the team was not fully prepared or aligned on what was expected from the candidate.
Called at a random time so couldn't be prepared. After that had a coding test. I have not gone further process due to my coding was not clean. Good luck to all who see this.
Interview questions [1]
Question 1
CAD experience python coding about calculating the distance that how much the car moved,
There were 4-5 sessions.
In each session I interviewed with each teams' leaders. As for problem, I answered and discussion continued.
Overall interview atmosphere were good.
There was lunch time between morning and afternoon session.
Interview questions [1]
Question 1
They asked about basic robotics concepts like localization, calibration, etc.
and about several python questions, and C++.