{"id":19073,"date":"2019-07-29T17:20:26","date_gmt":"2019-07-29T16:20:26","guid":{"rendered":"https:\/\/www.architect-us.com\/blog\/?p=19073"},"modified":"2020-11-06T11:22:44","modified_gmt":"2020-11-06T10:22:44","slug":"red-flags-to-look-for-when-interviewing-possible-candidate","status":"publish","type":"post","link":"https:\/\/www.architect-us.com\/blog\/2019\/07\/red-flags-to-look-for-when-interviewing-possible-candidate\/","title":{"rendered":"Red flags to look for when interviewing a possible candidate"},"content":{"rendered":"

One of the hardest parts of maintaining a strong company culture<\/strong> and growing the company<\/strong> is the on-boarding process.<\/strong> For many the interview process is a crucial stage of the on-boarding process, considering it is the first time that you will get to interact with the possible candidate. Here at Architect-US<\/strong><\/a> we understand the importance of the interview process, and we want to make sure you have the proper tools for how to find the right fit for your team.<\/p>\n

1. A lack of interest<\/b><\/p>\n

Many architecture firms tend to be boutique niche firms, and thus tend to have a smaller team in comparison to the bigger firms within the industry. Smaller teams means that bringing new team members on is a huge balancing act<\/strong> that should not be taken lightly. You should always make sure you are bringing on talents that are interested in the work you are doing!<\/p>\n

If the candidate you are interviewing doesn’t express interest in the projects your firm is taking on or the company mission, then they are most likely not going to care about the impact that they have on their counterparts or the team dynamic overall. It is a massive dynamic shift if one person does not believe.<\/p>\n

2. No personal weakness to highlight<\/b><\/p>\n

We are all human!<\/strong> We all have some flaws! A candidate that is unable to articulate their weaknesses and\/or provide remedies for these weakness is not being honest with themselves. Someone who is not in touch with their own flaws will probably have a harder time receiving constructive criticism, which is a crucial part of growing with a company.<\/strong><\/p>\n

In order to form a strong team it is necessary to understand every person’s strengths and weaknesses, in this way they can be leveraged to maximize quality and output. A lack of self-understanding<\/strong> makes it more difficult for that candidate to fit in with the team, since they will not always be aware of how their actions impacts others.<\/p>\n

3.\u00a0<\/b>Understands how to balance between talking about self and others<\/b><\/p>\n

A candidate must always understand how to balance between stories from their perspective ( I statements), but also\u00a0highlight stories\u00a0from other people or a group dynamic such as an office or community. If the candidate never mentions their colleagues by name and they are heavily using I statements, make sure you dig deeper into their ability to work in a team.<\/p>\n

Candidates need to know that it is good to\u00a0talk about team accomplishment stories.<\/strong>\u00a0Ask about how the\u00a0team accomplished their goals and ask them to\u00a0describe the role they played in making it happen. This balance can go to the other extreme as well! Some candidates do not talk about their accomplishments enough, but instead focus too much on the office dynamic.<\/p>\n

Remember to keep track of how they view accomplishments<\/strong> and they present them to you.<\/p>\n

\"Interview\"
Photo by Christina Wocintechchat<\/figcaption><\/figure>\n

4. Short, concise, and to the point! NO long-winded explanations.<\/b><\/p>\n

An inability to explain themselves\u00a0in a short, concise and through<\/strong> manner is a red flag, especially in architecture where you must always be ready to defend your ideas and techniques. If the candidate provides a long-winded explanation and\/or negativity when talking about leaving a position or not getting along with the office dynamic, this could be a red flag as well.<\/p>\n

Most often than not professionals have simple reasons for moving on from a position. Long-winded answers to a question that they anticipated receiving may implicate a rehearsed response, which is never good!<\/p>\n

The best architects are confident<\/strong> about their decisions and\u00a0honest about their reasoning. Taking ownership of their own actions is a crucial aspect of their personality that should be understood.<\/p>\n

5. Any and all phone use<\/b><\/p>\n

Any candidate that is willing to pull out their smartphone during an interview is clearly not present and not fully committed to the company. Not only that, but it is rude to be using a phone during a conversation with another person. If they are not willing to respect your time, then they probably will not respect their position.<\/p>\n

6. Body Language<\/b><\/p>\n

Make sure they are not slumping<\/strong> in their chair and are able to maintain eye contact<\/strong>. These two initial factors are key to understanding if they take themselves and the work they do seriously. If their eyes stray and are unable to focus on you and the task at hand, then they are clearly thinking about something else. Make sure that they are not crossing their arms<\/strong> or showing a lack of confidence. By reading how they feel within their environment you can better understand what they are thinking.<\/p>\n

7. No (or poor) references<\/b><\/p>\n

If they do not have references or they only have older references, but none from their most recent employers, then this could be a red flag. You want to make sure that they have moved from a good and fruitful experience to now your company. Any break in time for professional work could be another reason for a lack of recommendation letters.<\/p>\n

\"Interview
Photo by Tim Gouw<\/figcaption><\/figure>\n

All of these are red flags<\/strong> to keep in mind when on-boarding new team members! Make sure you protect your company culture and provide clear guidelines as to how coworkers will interact at your firm.<\/p>\n

<\/div>