Application Process & Interviews at Datacom New Zealand

The interviews were great! The managers and team members were great, But with the recruiter there needs to be better communication. I was told a certain role was available that I was going to but the role title is completely different so when I started I was very confused. For some reason I was told I would be going for x role but when I started I was told something else and there was a document with the specifics which I was suppose to be shown during the recruitment process.

Seamless process Went through the lines and got plenty of onboarding instruction loved the graduate cohort induction week

Initial group interview (1 hour), followed by technical test (untimed, took me about 1.5 hours) followed by standard panel interview (45 min)

Super easy and stress free

I was an internal transfer to this role and the process was very straight forward and clear.

Liz was wonderful to deal with

Unclear comms on where to go/who to report to on first day. No assessments, pretty relaxed interview.

I was an intern and reached out to multiple people to express my interest in a position. I never had a formal interview, everything was labelled as a "catch-up". I met with a Practice Manager twice, a Director once, and a Principal Consultant once. The first three interviews involved questions about my background, experience, and what role interests me. The fourth interview involved a role play of a Story Mapping exercise.

The stages: - A small coding test online - A few days later, a technical interview for about an hour. - Another few days later, a behavioural interview for about an hour.

Interests, tell me about yourself - any experience? How do you prioritize?

Technical skills & experience, personal development & team experience

The first interview was more like an observed group exercise. The questions in the final interview were mainly technical about the test I had completed, some questions about what I was looking for and some about my studies.

Not many, mostly Nigel just described the role. The conversation more or less flowed for the allotted time frame.

More empathy/relationship-focused than other employers who asked more technical/previous experience questions.

I don't recall exactly what was asked.

Technical interview: - To explain what I know about react, and other simple programming principles. Behavioural: - Tell me a time when you had to deal with conflict, difficult teammates, etc etc. Hypothetical questions e.g. "how would you have dealt with a teammate if they had done or said x/y/z". - What are your salary expectations - Other very stock-standard behaviour questions In both speaking interviews I was given the opportunity to ask my own questions about the company, role, and culture.

Be yourself, have a way that you would "brand yourself" have something that will make you memorable. Show that you are actually passionate.

continue in growth mindset contain knowledge areas of interest..

Don't be intimated by the tech world. You don't need to know every piece of tech to work there, as long as you are willing to learn you'll be great.

Be prepared to do nothing for the first few months but it becomes busier as you learn

Get any verbal promises made to you in writing, included in your contract.

I don't have any tips.

Reflect on past experiences that you have learned from and can refer to in an interview to show you are a good team player with a good level of self awareness and emotional intelligence. If appropriate to the role, prepare for technical questions that you would typically expect. Think about what you want/value in a role, and make sure to ask questions that can indicate to you whether or not the role/company is a good fit.