I was recently interviewed as a Principle Solutions Architect for a new client. It was an unusually confrontational interview. I am sure that most of us who have been consultants for a few years recognize that there are various dynamics in play when being assessed for a new project. It is always a challenge to know exactly how to approach any given interview scenario.
I have found that there are four primary types of interviewer scenarios:
-
Interviewers that are looking to have an understanding of what you know and how you would fit into a given culture
-
Interviewers that are looking to have an understanding of what you don’t know
-
Interviewers that are looking to how you would fit into a given culture regardless of the value you bring to the Client
-
Interviewers that are looking for ways NOT to hire you or sometimes anyone
As a Developer I have found that most environments that you are exposed to are 90% Technology and 10% Politics. As a Development Manage or higher Technology, I have found, is generally the 10% and the Politics is the 90%. This is sometimes true as a development Lead as well. This dynamic play an important part in the interview process and is covert to the interviewees.
A common scenario that plays out is summed up with this quote:
The Operation was a Success …
… But the Patient Died
You do EVERYTHING correctly. You are told that the interview went well. You were eminently qualified and the interviewer(s) seemed to like you. You are informed that they are “Passing” on you. You ask why and are told that it did not seem like a good fit.
As a human being how do you reconcile that? How do you learn from that experience so you can not repeat your mistake? What did you do wrong?
Having conducted 100’s of interviews and been on the other side for dozens more, I can say with a good level of confidence that you more than likely did nothing “Wrong”. You were a victim of one of the above scenarios. Political issues, hidden agendas and changing environments that you had no control over regardless of you actions during the interview.
When I queried about the overt hostility I experienced in the above mentioned interview I was informed that the interviewer was having major issues with the home office and was resisting the mandated changes that were being implemented. No actions on my part could have prevented the inevitable outcome I received.
Here are some tips I have picked up over the years that have helped in situations that are not driven by covert politics:
-
Inform yourself of the details of the business of the Client you being interviewed with a thorough Google research.
-
Have a good understanding of the core services and products provided to their Customers and/or Clients.
-
Get as much information about the business from the Agency’s Senior Account Executive who owns the Client as possible.
-
Get as much information about the history of candidates that have interview before you: Successes and Failures.
-
Query you Account Executive for insights on the personalities of the people interviewing you. Ask during the interview if unknown.
-
Are the Pragmatic (“Just the Facts Maam”) or Extroverted (“A People Person”)
-
Do they like short answers or detailed one.
-
Do they talk fast of slow. Match their speed as much as possible
-
Do they seem to be a Visual, Auditory or Kinesthetic person
-
“I see what you mean”
-
“I hear what you are saying”
-
“I feel that we have an understanding”
-
Try to match their personality type with your words, if possible
-
-
Structure ALL of your answers to get a Yes or Positive response from the Interviewer
-
Insert a Not when a response would invoke a No
-
Yes responses produce different chemical results in the brain that a No response
-
You want the Interviewer to have positive experiences with your interview responses
-
-
Here is the MOST important one of all:
Address all your responses to questions as what is important to Them, NOT You
Avoid say “I need” and address it from the benefit your actions will bring to them and their organization. You are being interviewed to solve a “Business Need” they have. They are not concerned at all that you are unemployed, or soon will be. You need to fill a “Pain Slot” that they have. They need to see you as their solution to an immediate problem.
Some of these ideas may be new to you. Some of them may seem controversial. All of them have worked for countless professionals in the past, including me.
The knowledge of these concepts alone …
… will help you in the stressful process of getting a new Technology engagement
Good luck. Please leave your thoughts as Comments: Pro and Con. Share your successes and failures for the betterment of the Modern Developer Community.
The following two tabs change content below.
I am a Principal Architect at Liquid Hub in the Philadelphia area specializing in Agile Practices as a Certified Scrum Master (CSM). I use Test Driven Development (TDD) and Acceptance Test Driven Development (ATDD) with Behavior Driven Development (BDD) as my bridge to Agile User Stories Acceptance Criteria in a Domain Driven Design (DDD) implementing true RESTful services
Latest posts by Brad Huett (see all)
- DevOps: A Bridge to Your DevOps Culture - March 25, 2016
- Embracing Test Driven Development (TDD) - March 25, 2016
- DevOps: Delivering Agile Projects - March 25, 2016