Honeywell Interview Questions in Sydney | Glassdoor

Honeywell Interview Questions in Sydney

Updated Sep 26, 2016
1 Interview Review

Interview Experience

Interview Experience
0%
0%
100%

Getting an Interview

Getting an Interview
100%

Interview Difficulty

2.0
Average

Interview Difficulty

Hard

Average

Easy

1 Candidate Interview Review Back to all Interviews

Filter

Sort: Popular Date Difficulty

Filter

Sort: Popular Date Difficulty
  1.  

    Graduate Software Engineer Interview

    Anonymous Interview Candidate in Sydney (Australia)
    No Offer
    Negative Experience
    Easy Interview

    Application

    I applied through college or university. The process took 3 weeks. I interviewed at Honeywell (Sydney (Australia)) in September 2016.

    Interview

    Met Honeywell at a careers fair. Filled out their online application form.

    Did a cognitive ability test (RCAT) with Revelian, pretty easy but worth practicing similar ones before you do the real thing.

    Phone screen (What is Honeywell, why do you want to work here). Obviously, make sure you know they work with large scale legacy systems - browse their site for this stuff.

    An ipsative personality quiz followed, took about 30 minutes. Pretty unexciting.

    On site interview included logic and technical reading tests, followed by a 2:1 interview by senior engineers. Both were multi-choice questions, taken under exam conditions with a time limit of 25 minutes each.

    The logic test involved diagrammatic reasoning. If a symbol means a certain action, what action results from this series of symbols?

    The technical reading comprehension test used paragraphs of different technical content (about hardware or software specifications, features). Some of the paragraphs had badly kerned text which was hard to read given a short time.

    The interview consisted of STAR type questions. Find a bunch online and pre-prepare your answers, this helps a lot. Smiling, and generally being calm and collected during the interview gave me very positive feedback.

    Send them an example of code that is "relevant to Honeywell." This was pretty broadly defined, I hadn't built anything that resembled what they wanted (and was open source) so the interview process stopped here.

    They didn't including this step when documenting the hiring process, and probably should have - it felt unfortunate to miss out because of that. Not everyone has the luxury of being able to share what large scale projects they worked on. Even a whiteboard / coding test would have been more effective.

    Anyway, after this stage there is one more interview before reference checks/offers, to do with culture fit.

    Interview Questions

    • What course was your favourite and why?
      Describe how you could test a project.
      Describe a time you dealt with conflict within a team.  
      Answer Question
Don't Miss Out On a Job You Love
Upload a resume to easily apply to jobs from anywhere. It's simple to set up.