<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mark Barrett on Medium]]></title>
        <description><![CDATA[Stories by Mark Barrett on Medium]]></description>
        <link>https://medium.com/@barrettology?source=rss-975f9c8d57de------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*lzihaYdep-omDh5Y.jpg</url>
            <title>Stories by Mark Barrett on Medium</title>
            <link>https://medium.com/@barrettology?source=rss-975f9c8d57de------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 18:19:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@barrettology/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[2019 — My year in review]]></title>
            <link>https://medium.com/@barrettology/2019-my-year-in-review-432e36bae2cf?source=rss-975f9c8d57de------2</link>
            <guid isPermaLink="false">https://medium.com/p/432e36bae2cf</guid>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[year-in-review]]></category>
            <category><![CDATA[2019]]></category>
            <dc:creator><![CDATA[Mark Barrett]]></dc:creator>
            <pubDate>Tue, 31 Dec 2019 20:17:30 GMT</pubDate>
            <atom:updated>2019-12-31T22:22:45.547Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ifLJ3SYGdJKP0D_BOxb4Yw@2x.jpeg" /></figure><h3>2019 — My year in review</h3><p>Towards the end of the year it’s become a tradition of mine to scroll through the pictures on my phone to pause, reflect and call out some of the yearly highlights.</p><p><em>Before we start I should mention </em><a href="https://medium.com/u/a9fa40aa3cbf"><em>Phil Hale</em></a><em> here because he was the first to show me this end of year reflection technique and it’s something I’ve tried to do ever since. Thank you Phil. Would love to see others share their highlights if they feel the need.</em></p><p>Last February we had some family members visit us in New York and we took them to a Brooklyn Nets game at the Barclays Center. I love the NBA, it’s something I’ve picked up since moving to the US. The Nets are not doing too badly right now, it’s certainly better than supporting the Knicks!</p><p>Every time I go to watch the NBA it’s awesome, so quick and high scoring plus the entertainment that goes on during breaks and time outs — pure sports entertainment — there is nothing like it back in the UK.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ogKlRzcK5kQaephREeEe0g@2x.jpeg" /><figcaption>Barclays Center, Brooklyn — February 2019</figcaption></figure><p>Mid-March 2019 we had a huge dump of snow in NYC. It was really deep, crunchy powder. The last time I saw something similar I was snowboarding on the Alps! The kids loved making snowmen and having snowball fights. Ok maybe I got involved too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1AuNJClyOmo6rvW0JQXmDA@2x.jpeg" /><figcaption>McCarren Park, Brooklyn — March 2019</figcaption></figure><p>May 2019 was a big highlight for me because the Advertising Studio team met up in Indianapolis and we had a blast. It’s always tough to plan and schedule a team meet but it worked like a charm. We had so many great sessions and it sparked a ton of conversation and ideas. It really set us up for the rest of the year. Plus it’s so beneficial, especially for a remote based team, to see your colleagues in person. Good times indeed.</p><p>Here is a candid shot taken at the start of our retrospective, by the end we had filled that window with post-its and action items!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J0nqWN-QXWGGf4CCDGrsvw@2x.jpeg" /><figcaption>Salesforce Tower, Indianapolis — May 2019</figcaption></figure><p>What can I say about July — I had the best day of my life bar none. I was lucky enough to marry my wife Amy and we had the best day. The venue was great, we got the weather we hoped for and to see everyone there having fun and celebrating it with us was just amazing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8dK033RiKZoHoQmCocch3g@2x.jpeg" /><figcaption>Powderham Castle, Devon — July 2019</figcaption></figure><p>The picture obviously doesn’t show all the stress and cost a wedding takes to plan but it was a superb day. I would do it all again tomorrow.</p><p>Fast forward to September and we had the happy surprise that we were going to have a baby! Very, very blessed. It was like it was meant to be — 2019 was certainly filled with some big life events for me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SFp61VA_e9R9EJoOyT6Ciw@2x.jpeg" /><figcaption>New baby announcement, Brooklyn — September 2019</figcaption></figure><p>Soon our thoughts turned towards Christmas and we started to decorate our apartment just after Thanksgiving. We have a tradition of building gingerbread houses — or in this case a gingerbread train.</p><p>This is Cruz’s creation, the hardest part is making sure the kids don’t eat the candy before it gets added but it’s a lot of fun!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T3uPKGmDqYdKlngpJ05IIw@2x.jpeg" /><figcaption>Gingerbread train, Brooklyn — December 2019</figcaption></figure><p>And that’s it from me — what a year it has been. So much fun and laughter but also a lot of hard work at the same time.</p><p>Thanks to everyone that made the year such a pleasure and here’s to more good times in 2020!!!</p><p>~Mark</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=432e36bae2cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Committing to continuous feedback]]></title>
            <link>https://medium.com/salesforce-engineering/committing-to-continuous-feedback-79d4a3ed72a0?source=rss-975f9c8d57de------2</link>
            <guid isPermaLink="false">https://medium.com/p/79d4a3ed72a0</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[performance-reviews]]></category>
            <category><![CDATA[employee-feedback]]></category>
            <dc:creator><![CDATA[Mark Barrett]]></dc:creator>
            <pubDate>Mon, 27 Feb 2017 18:34:27 GMT</pubDate>
            <atom:updated>2017-02-27T18:34:27.244Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b5nLxITXVXegAk7d7YSrrg.jpeg" /></figure><p>I recently posted a tweet that gained some attention.</p><h3>Mark Barrett on Twitter</h3><p>Remember when code was deployed once a year? Madness. Now imagine a world where performance reviews happen once a year. Yeah. That.</p><p>I don’t have a huge Twitter following, but it got enough retweets for me to take notice.</p><p>The original sentiment in my tweet was very much:</p><blockquote>It’s January. That means Performance Review time. Here we go again.</blockquote><p>Generally speaking, annual performance reviews are usually met with trepidation by line-managers and treated with disdain by team members.</p><p>So why is this? I would like to call out 3 key reasons:</p><ol><li>Line managers find it difficult to summarise an entire year of an individual’s contribution in a neat, succinct, and honest manner.</li><li>We prepare ourselves to fall into 3 categories — we are excelling (awesome), we are on track (that’s ok) or we are under performing (you’re kidding me, right?).</li><li>Due to points 1 &amp; 2 above the end result becomes a categorisation exercise that means accurate, behaviour-changing feedback becomes too diluted and is therefore unlikely to have any positive effect on the performance of the individual.</li></ol><p>Let me highlight that last section:</p><blockquote>I do not think that annual performance reviews are effective at changing an individual’s performance.</blockquote><p>There, I said it.</p><p>For the most part, annual performance reviews have become a yearly tick box exercise. Managers are expected to provide examples which will justify an employee’s categorisation while the individual takes the feedback as politely as possible with very little collaboration or discussion. I might be outlining a worst case scenario, but you get the point.</p><h3>Is there a better way?</h3><p>Quite frankly, yes.</p><p>We are trialling a new concept this year within Salesforce and my engineering group is one of the early adopters. We have thrown away annual performance reviews and have moved toward continuous feedback.</p><p>Continuous feedback is a simple concept; we give our peers feedback early and often.</p><p>The intention is to create a culture of open, honest, and transparent feedback. We intend to positively change performance of an individual with the right feedback at the right time. If you think someone did a good job, let them know. If you spot something that they can develop or improve, let them know.</p><p>While this sounds very utopian in nature, there are some key elements to continuous feedback that are important for adoption. Without a few guardrails, feedback can be misinterpreted or taken in the wrong way, ultimately having a negative effect on your team and individuals.</p><h3>Make a promise to your team</h3><p>Engineers can be a dubious group, so it is important to outline the new process, manage any apprehension, and get buy-in.</p><p>Set expectations with each individual on your team that you will provide feedback on their performance at least once a month. At <em>least</em> once a month. It may be more but it will not be any less.</p><p>Not only that, but assure your team that any feedback will then form part of the discussion in your next 1:1. This sets the tone that you are serious about continuous feedback and it is front and centre in your mind.</p><p>Following up on your comments in a 1:1 is crucial if you want to see behavioural change. Do you have a common understanding? Do they have questions or points they want to raise about it? Are there any next steps?</p><p>Feedback is not something to avoid. Have those important conversations early and regularly.</p><h3>Ask your team to commit to continuous feedback</h3><p>Embrace the fact that continuous feedback is a two-way mechanism between line manager and direct report.</p><p>Make it clear that you want to hear their comments about your performance at least once a month. Again, raise any feedback you have received during your next 1:1.</p><p>Don’t be afraid to dig deep into what might be an awkward conversation. It is much better to have the tough discussions early when there is still an opportunity to work through the feedback and think about actions rather than lettings things fester in the background.</p><h3>Take ownership of your feedback</h3><p>We built a new feedback app at Salesforce. It is an impressive internal tool with dashboards and charts but its main function is to provide us with the ability to send timely feedback to our manager and peers.</p><p>The app contains an option of sending feedback anonymously. I can appreciate why that may be needed, but I am personally adamant that we should own our feedback and put our name to every comment.</p><p>If I cannot own a piece of feedback then I ask myself:</p><blockquote>Is this the right forum to be posting this? Why can I not put my name to it?</blockquote><p>Continuous feedback is more than just being open and honest. It is about feeling safe. Sometimes a chat is best, sometimes a comment in the app is best. What is great is <strong>we</strong> get to decide when and how to relay feedback to our peers.</p><h3>Always provide examples</h3><p>When you write a piece of feedback think about including a recent example or, even better, use the <strong>Situation — Behaviour — Impact</strong> model (<a href="https://www.linkedin.com/pulse/situation-behavior-impact-feedback-tool-marlon-cotera">SBI</a>).</p><p>It becomes a lot easier to give and receive feedback when you have a specific situation in mind that you can talk through.</p><p>From experience, engineers are happiest when presented with quantitative data (numerical data you can measure) but struggle with qualitative data (subjective data collected via observations). Unfortunately, peer feedback tends to be much more qualitative, so having an example or situation to analyse is key to gaining a common understanding from which you can establish a way forward.</p><p>If there is one thing you take away from this post, I hope it is to lean on SBI whenever you need to effectively communicate feedback. An absolute must.</p><h3>Keep an open mind</h3><p>It is vital that we keep an open mind when reading feedback about ourselves. Consider that the person has taken time to write feedback for us and it was coming from a place of good intentions rather than being critical or personal.</p><p>As humans, we often ignore or disbelieve any praise that comes our way and over-emphasize the negative comments. Be aware when you are focusing too much on critical feedback.</p><p>If necessary, take a step back, try to remove yourself emotionally, and ask for a private session to talk through the situation face-to-face.</p><h3>Reflect - iterate - improve</h3><p>Turning away from the familiar routine of the annual performance review is not the most obvious path forward. In fact, the process may be imperfect at first. But just as we process feedback for ourselves, we can reflect on our move to continuous feedback the same way: keep doing the things that are working, and make small, iterative changes to the items that need improving. The change will be worthwhile.</p><p>By adopting continuous feedback, I believe teams and individuals become more secure, more productive, and more transparent because performance is discussed in the right way and at the right time.</p><p><em>Do you run performance reviews with your team? Have you found a way to make them work for you? Perhaps you have taken a different path entirely?</em></p><p><em>Would love to hear your thoughts; please share and comment!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79d4a3ed72a0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforce-engineering/committing-to-continuous-feedback-79d4a3ed72a0">Committing to continuous feedback</a> was originally published in <a href="https://medium.com/salesforce-engineering">Salesforce Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 habits that keep retrospectives relevant]]></title>
            <link>https://medium.com/salesforce-engineering/3-habits-that-keep-retrospectives-relevant-74b5ced63eae?source=rss-975f9c8d57de------2</link>
            <guid isPermaLink="false">https://medium.com/p/74b5ced63eae</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Mark Barrett]]></dc:creator>
            <pubDate>Tue, 12 Apr 2016 14:33:56 GMT</pubDate>
            <atom:updated>2016-04-12T14:33:56.754Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*T1fuyaNkhy_k8oW8aqWMtA.png" /></figure><p>Our engineering group is a big believer in continuous improvement and we think retrospectives are a valuable tool as long as the sessions remain relevant and productive.</p><p>An example of how retrospectives can be beneficial is found within <a href="https://medium.com/u/8cf4513b0912">Kevina Finn-Braun</a>’s post <a href="https://medium.com/salesforce-engineering/from-blame-to-blameless-1cd5341d84cf#.rys5wws2s">From Blame to Blameless</a>. Rather than running a postmortem to analyse incidents, our site reliability team now holds a retrospective because it creates a much more productive and non-confrontational environment.</p><p>The premise of a retrospective is an honest one; ask the team to look back and fix problems from their last sprint as well as highlight the good methods that have been successful. Then why is it so common to see team members roll their eyes when the retrospective invite is sent out or even worse, have retrospectives drop off the calendar altogether?</p><p><strong>Here are 3 approaches that re-established our faith in retrospectives by keeping the sessions fresh and rewarding:</strong></p><h4>1. Never facilitate your own retrospective</h4><p>The facilitator is a key ingredient for a successful retrospective. If the individual running the session is part of the team it becomes very difficult to facilitate and contribute at the same time. The end result is both roles are performed badly. By handing over the facilitation, it frees everyone on the team from the distraction of running the session. It also has the added benefit of including an unbiased outsider who can ask questions that the rest of the team may not think of.</p><p>To be a good facilitator is tough. It takes patience and practice but in time you can gain the required skills to keep the conversation relevant and engaging.</p><p>A decent facilitator should be an advocate of active listening, be adept at taking relevant notes, provide questions when appropriate and keep an eye on the clock to make sure the session remains on track and within time.</p><h4>2. Build a toolkit of exercises</h4><p>An obvious technique to avoid boring retrospectives is to have a number of different activities that you can choose from as opposed to facilitating the same session over and over again.</p><p>One of our favourites is ‘<a href="https://www.retrium.com/resources/techniques/start-stop-continue">STOP, START, CONTINUE</a>’. What should the team STOP doing, what should we START doing and what is working well that we should CONTINUE. A similar approach to the ‘<a href="http://retrospectivewiki.org/index.php?title=Glad,_Sad,_Mad">MAD, SAD, GLAD</a>’ exercise.</p><p>Both of these activities lead to open discussion so we prefer to use this technique across large groups of people. The activity provides an opportunity for discussion to flow around the room whilst at the same time giving the session some structure.</p><p>For small teams (6 people or less), the ‘Like to Like’ game can be really effective. Prior to the activity, it is necessary for the facilitator to prepare 6 cards that capture a specific quality with vaguely positive or negative connotations. For example, ‘productive’ or ‘fun’ for positive, and ‘flawed’ or ‘nervous’ for negative.</p><p>We begin the session by asking each team member to write 6 post-its: 2 things that went well, 2 things that went badly and 2 things they want to do more of. A quality card is picked and each team member has to choose one of their post-its and explain how it relates to the quality card. Each member’s post-its will keep the conversation varied, while the quality cards provide a common focus for discussion. For example, if the quality card is ‘productive’ the team can talk about anything that they found productive whether on the post-its they wrote, or something they may have just thought of. The idea is to keep the conversation structured but still open and inclusive of all team members.</p><p>At the end of the round, the person who first picked the quality card will choose a winner based on who had the most creative answer linking the quality card to their post-it. The game can become quite competitive as each team member tries to win a round for themselves.</p><p>This activity is great for smaller groups as it promotes team member contribution. There is no hiding place and everyone is given a platform and an opportunity to voice their opinion. With a little guidance some very insightful thoughts come out of the session. This activity is also a useful method of encouraging friendly competition. Individuals generally respond in a fun way when a little competition is introduced.</p><p>These are only a few examples of activities you can facilitate in your retrospective. Be prepared to get creative. Some sessions will work, some will not. Concentrate on variety and when things feel a little stale be ready to change the activity. There are plenty of good resources online and in reference books which you can get inspiration from.</p><h4>3. Promote team authority</h4><p>During a retrospective you will often hear, “Why did we do it like that?” or “We should really fix that.” Spin these suggestions into actions by writing them on the board and assigning someone responsibility.</p><p>This is where facilitation is important. Make sure the action is relevant and achievable within the next sprint. Break it down and take baby steps if necessary. A good question to ask is, “What is the first thing you would do to fix this after you leave the room?”</p><p>Once the actions are written down make sure to follow up at the start of the next retrospective by reviewing any actions that are incomplete. Tread carefully though, we do not want to introduce a level of blame which leads to an unhealthy team dynamic.</p><p>A common mistake that can damage team authority is to continually assign actions to the team lead or manager. This could mean that actions become stuck in one person’s to-do list, the same problems may occur, and the lack of improvement may make the team begin to question the value of retrospectives. They may see it as more of a ceremony vs. a means to healthy improvement over time.</p><p>Instead of assigning to one person, assign the action to the person most passionate about solving the problem.</p><p>Also, focus on continuous improvement. If there is something you can do, no matter how small, write it down and make someone accountable. Show them that the team has the authority to act and improve the environment around them.</p><p>By implementing the practices outlined above our engineering team has transformed retrospectives for the better. Rather than falling into ceremony, our retrospectives foster a culture of continuous improvement and support a healthy, productive team dynamic.</p><h4>Further reading</h4><p><a href="http://www.benlinders.com/2013/whats-an-agile-retrospective-and-why-would-you-do-it/">What’s an Agile retrospective and why should you do it?</a> (Ben Linders)<br><a href="http://blog.crisp.se/2012/01/27/yassalsundman/great-retrospectives">Great retrospectives</a> (Yassal Sundman)<br><a href="http://skycoach.be/2010/06/17/12-retrospective-exercises/">12 retrospective exercises</a> (Nick Oostvogels)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74b5ced63eae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforce-engineering/3-habits-that-keep-retrospectives-relevant-74b5ced63eae">3 habits that keep retrospectives relevant</a> was originally published in <a href="https://medium.com/salesforce-engineering">Salesforce Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hiring for a cultural fit]]></title>
            <link>https://medium.com/salesforce-engineering/hiring-for-a-cultural-fit-415491d3e6b7?source=rss-975f9c8d57de------2</link>
            <guid isPermaLink="false">https://medium.com/p/415491d3e6b7</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Mark Barrett]]></dc:creator>
            <pubDate>Tue, 26 Jan 2016 17:43:28 GMT</pubDate>
            <atom:updated>2016-04-07T21:43:47.402Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dlN-vF1YJ7ZpOrx8rOGBEQ.jpeg" /></figure><p>There can be few scarier words than “I would like you to run our cultural interview”. Even the most technically-adept developer will shudder at such talk. Perhaps it is the vagueness of the term “cultural interview” that sends us OCD-ridden engineers a little crazy.</p><p>So how can we assess a candidate’s culture? Get an idea of their core principles? Judge if they are aligned to our company values? Oh yes — and we only get an hour.</p><p>Interviewing is an important skill to learn but it should not be something to fear. In simple terms, an interviewer’s role is to provide a platform and encourage the candidate to participate. Given the right guidance, an hour is plenty of time to assess cultural suitability.</p><h4>Conversation not interrogation</h4><p>From experience cultural interviews work best when it becomes a genuine conversation. It definitely helps to use questions that spark debate. Consider asking questions that do not have a clear right or wrong answer. Divide opinion and ask the candidate to take a stance.</p><p>Examples might include how they would implement a breaking change within a REST API, or how they like to structure their unit tests. Be warned that open-ended questions can confuse a candidate so make it clear there is no right answer. What you can look for are opinions and the ability to effectively communicate their opinion succinctly.</p><h4>Set the tone</h4><p>A worthwhile opening question is the ‘ideal world’ scenario; how would the candidate set up a team to work on an application in an ideal world?<br>What team size do they prefer and what roles does it consist of? Are they interested in traditional Scrum or would they jump straight into a Lean approach? What environments do they talk about (local &gt; dev &gt; QA &gt; staging &gt; prod)? When do they consider the deployment pipeline (earlier the better)? What about product input to discuss KPIs? Also, post deploy how about monitoring, logging and alerts?</p><p>That one opening question can often spawn conversation with further queries. Do not be concerned if the conversation spans 15 to 20 minutes. It gives the candidate a chance to warm up and sets expectations. We are not monsters throwing questions at them until they cry. We want a conversation.</p><h4>Build your interview with structure</h4><p>By focusing on specific areas, we can give structure to a cultural interview. This will provide us with a much more colourful judgment of the candidate.</p><p><strong>Passion:</strong> The definitive part of an individual’s make up. Do not expect passion to flow from the first minute, but the candidate should light up when discussing concepts they are passionate about. It could be a language (C#/NodeJS), an approach (Agile/DevOps), or specific technology (MongoDB/Docker).</p><p>If the candidate shows no obvious passion throughout the hour, then you should be a little concerned. Look for individuals that will flourish in your team. A direct question can be the spark a nervous candidate needs, so don’t be afraid to ask directly, “What are you passionate about?”</p><p><strong>Ownership:</strong> Does this candidate give the impression that they will pick up and own a story from concept through to production? Are they more interested in being told what to do? You might have different expectations from different engineering levels but across the board you are looking for candidates who are pro-active and engaged. Can the individual be trusted to take ownership and deliver?</p><p><strong>Craftsmanship:</strong> We need assurances from the candidate that they operate at the very top level. Answers should be sound and not overly complicated. Do they consider testing to be an integral part of development? Recognition of SOLID principles is not always a requirement, but to take an example they should be able to discuss the benefits of the single responsibility principle. Do you leave with the impression the candidate takes pride in their work and will produce that extra level of detail?</p><p><strong>Teamwork:</strong> A team is stronger than any individual contribution. Does the candidate feel the same way? Are they collaborative, open to pairing and keen to explore problems as part of a group? How would they deal with conflicts inside a team? Engineering is a strongly opinionated environment. Are they open to compromise whilst being able to stand up to their core principles? Ideally the interview should end with you thinking, “Yes, I want them on my team.”</p><h4>Go with the flow</h4><p>These suggestions are designed to aid conversation. It is an art to direct the interview but also let it flow organically. It can be easy to dry up during an interview so set questions are useful — but do not worry if you run out of time before asking them.</p><p>The term “cultural interview” does not mean that technical questions are banned. Far from it. Instead try to include questions of a technical nature that prompt conversation — when was the last time they had to compromise on a technical decision? What were the circumstances? What was the final outcome? Don’t forget to co-ordinate with the other interviewers to ensure both technical and cultural questions are covered and you are not asking the same questions.</p><p>Finally, allow time for questions at the end. This is easily overlooked. All too often interviews are considered to support or deny a candidate when in reality we should be humble enough to understand top talent is being pursued and has options.</p><p>The interview should be bi-directional, providing them with a chance to gauge the company you are inviting them to join. Although questions should not be expected, end 5–10 minutes early to give them time should they need it. This will give you both the opportunity to see if it’s a sound cultural fit.</p><h4>Further reading</h4><p>• <a href="http://2015.theleaddeveloper.com/videos?s=12-challenging-steps-to-being-a-better-interviewer">12 challenging steps to being a better interviewer</a> (Cate Huston)<br> • <a href="https://medium.com/buffer-posts/why-we-dont-ask-technical-questions-for-technical-interviews-at-buffer-73f8132a8abd#.isg42a7l6">Why we don’t ask technical questions for technical interviews at Buffer</a> (Sunil Sadasivan)<br> • <a href="https://modelviewculture.com/pieces/cultural-ramifications-of-technical-interviews">Cultural ramifications of technical interviews</a> (Heidy Khlaaf)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=415491d3e6b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforce-engineering/hiring-for-a-cultural-fit-415491d3e6b7">Hiring for a cultural fit</a> was originally published in <a href="https://medium.com/salesforce-engineering">Salesforce Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>