Getting an Interview
Getting an Interview
Interviews for Top Jobs at Thales
- Software Engineer (6)
- Software Developer (3)
- Project Manager (2)
- Engineering (2)
- Software Analyst (2)
- Procurement Manager (2)
- Ingénieur logiciel (2)
- Ingénieur Systèmes (1)
- Gestionnaire des contrats (1)
- Ingénieur banc (1)
- Business Analyst (1)
- Verification and Validation Specialist (1)
- Validation and Verification Engineer (1)
- Java Software Engineer (1)
- Business Performance Analyst (1)
- Linux Kernel Engineer (1)
- Graduate Software Engineer (1)
- Hardware Engineer (1)
- Senior Account Manager (1)
- Senior Counsel (1)
- Accountant (1)
- Systems Engineer (1)
- Project Planner (1)
- Technical Manager (1)
- Design Engineer (1)
- Graduate Systems Engineer (1)
- Développeur (1)
- Human Resources Generalist (1)
Helpful (1)No OfferNegative ExperienceAverage Interview
I applied through an employee referral. The process took 2+ weeks. I interviewed at Thales (Toronto, ON (Canada)) in April 2015.
Was referred by their current employee. Got a phone call from hr associate calling in for walkin interview. Then same hr send me an email with details of walk in interview. Went for interview in the beginning there was no hr. First technical round then some other hr joined. Some random person not referred in email. Interview seemed to go well. Was told that they will let me know in a week. After a week followed up with hr who sent email in beginning. No reply for another week. I find their process is very unprofessional. They already have candidate in mind whome they want to hire but still call others. There should be phone screening and then only call the candidate for walkin interview. Wastage of time.
- How did you handle difficult situation 1 Answer
Helpful (1)No OfferPositive ExperienceAverage Interview
I applied online. I interviewed at Thales (Toronto, ON (Canada)) in February 2015.
Applied online, and got a call ~ two weeks later. This was to set up the interview. Introduction Interview with HR on the phone. HR person had general question and introduced the company. Then a 2nd interview was set up a week later. It was pulled in by 4 days. I went to the office and was taken to the interview area. The 2nd interview was with the hiring managers. There were two managers and HR in the room. Went over interview questions, and then described the job and what you would be doing. Then there was time for me to ask questions and i did ask 3 questions for which i got answers. Then we said our good byes and HR escorted me out.
- Mostly questions about the resume and what i did. 1 - Describe some skills you didn't have an needed to learn in your last position 2 - How do you handle pressure, and days where things are not moving 3 - How many projects have you worked on simultaneously 4 - What technical challenges did you face in your last position 5 - What are some of your weaknesses Answer Question
Helpful (6)No OfferPositive ExperienceAverage Interview
I applied online. The process took 4 weeks. I interviewed at Thales (Toronto, ON (Canada)) in November 2014.
1. Phone Call 2. HR Interview 3. 2 hour Technical Interviews I advice you to be prepared for lost of questions from STL- Know how to work with linked list and string from STL. More function you know from STL, writing a program, and developing an algorithm would be easier! For example: Inserting a node, removing a node, copy str, length of string, swap string,...! It would be great if you know about Rail Signaling basics, and what's the difference between automatic and the traditional ones! Review the very basic formulas about Feedback in linear control systems (stable systems, and unstable systems). Their system is based on communication protocols, you shouldn't be surprised if they ask you about WiFi and networking protocols.
- Accepted Offer
Casual process. Just asked about past experiences and what you done in the past. two technical questions. One was to list the compile issues with a program printed on a paper and the other was to print a small program that does a calculation
- Was given a printed out program and was instructed to find the 15 compile bugs somewhere in the code. Found about half. Answer Question
Helpful (1)No OfferNeutral ExperienceDifficult Interview
I applied online. The process took 2 weeks. I interviewed at Thales (Toronto, ON (Canada)) in June 2014.
1. HR interview 2. Interview with different project managers to see which project was the best fit for me 3.Technical interview
- Questions about queues, heaps, arrays, algorithms... 1 Answer
- No OfferPositive ExperienceAverage Interview
I applied online. The process took 1 day. I interviewed at Thales (Burnaby, BC (Canada)) in June 2014.
interviewed with many people in the office and as well as people in remote office. asked technical questions for C++ and general programming knowledge. They also asked how fast I can learn. Waited a few weeks and HR emailed me that I am not selected. Was a good interview process though.
- Explain the differences between std::vector and std::list. When each of them can be used more effectively. Answer Question
- No OfferDifficult Interview
I applied online. The process took 1 day. I interviewed at Thales (Montreal, QC (Canada)) in May 2014.
Firstly, i got a phone interview about some general questions : my experiences, my degree. Next week, i had a video interview in their office with managers in Toronto. They are very nice and friendly. Interview was pretty relax, there are no technical question. That continue for about half an hour. There wasn't a technical interview after that as what they told about at phone.
Helpful (3)Accepted OfferPositive Experience
The interview process was very thorough in testing my knowledge. I went did a technical interview with senior developers and they would ask technical questions related to the job. The engineers that tested me were highly competent and inviting. I also got the feeling that they were also sizing how I would integrate with their team. Overall, it was one of the better interviews I've been to.
- Afterwards, they provided me an exam that tested my knowledge of data structures and algorithms. This exam was pretty difficult and is not at all the simple; "for loop using recursion". I will not disclose the exact details but it was detailed a problem and with many possible solutions. Afterwards, the interview would sit down and rate how you did on the exam given the time frame. Answer Question
Helpful (3)No OfferNegative ExperienceDifficult Interview
I applied online. The process took 4+ weeks. I interviewed at Thales (Toronto, ON (Canada)) in February 2013.
First Interview - very nice and decent about your work experience and personality. Little talk about way you code and how to handle projects. Second interview - full on technical interview two expert from Thales will come to interview ONLY PREPARE FOR TECHNICAL. there will no other questions
- ALL QUESTIONS were most difficult and unexpected. They are quite not sure about how to prepare interview questions they will be same if you are experienced junior or intermediate. They want everyone to know all stuff in depth. IF you successfully answer one question another question in depth of that will be ready until you give up. 50% questions will be out of requirements. not sure what they want out of candidate but they want candidate to know everything. 1 Answer
Helpful (3)Accepted OfferNeutral ExperienceAverage Interview
I applied in-person. The process took 3 weeks. I interviewed at Thales (Toronto, ON (Canada)) in March 2010.
I met the manager at Job fair and have been called for interview by HR. I met a HR manager and the Hiring manager together. Few technical questions have been asked. When they called me they asked to send my expected salary for contract and for full time employee.
- They asked me if I want to be under contract or full time employee. I said both work for me. When the called me for contract and just told me the salary. They did not give a chance for negotiation or discussing about it. 1 Answer
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review