Fortran Traffic Systems Software Engineer Jr interview questions
based on 3 ratings - Updated Sep 18, 2024
Averageinterview difficulty
Mostly negativeinterview experience
How others got an interview
100%
Applied online
Applied online
Interview search
3 interviews
Fortran Traffic Systems interviews FAQs
Software Engineer Jr applicants have rated the interview process at Fortran Traffic Systems with 3 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 85.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer Jr roles take an average of 7 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Fortran Traffic Systems overall takes an average of 8 days.
Common stages of the interview process at Fortran Traffic Systems as a Software Engineer Jr according to 2 Glassdoor interviews include:
Phone interview: 100%
Here are the most commonly searched roles for interview reports -
I interviewed at Fortran Traffic Systems (Toronto, ON)
Interview
Phone screen and then in person interview, not more than half hour each. Standard stuff, including brain teaser like problems (think Feynman estimation). Interview with manager and a senior developer in turn.
I applied online. The process took 1 week. I interviewed at Fortran Traffic Systems (Scarborough, ON) in Mar 2021
Interview
Got an email saying that they will be phone screening and asked for time confirmation. Received a phone call a few days later and was bombarded with several questions. When the interview was done, there were a few questions that I wanted to ask, but the interviewer said that he doesn't answer questions in phone screening.
I applied online. The process took 5 days. I interviewed at Fortran Traffic Systems (Toronto, ON) in Jun 2015
Interview
Had a quick phone called and later called in for an interview. I was interviewed by two individuals and the questions were very technical. Seems like a very small company with a even smaller developers team. Asked questions which seemed beyond the requirements for a junior position.
Interview questions [1]
Question 1
A lot of Javascript questions. Why is Javascript good and bad. Some C++ questions, like what is a shared pointer. General problem solving questions, such as if you're given 7 balls and a scale then how can you tell which of the 7 is the lightest by only using the scale twice.