<?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 Jared Casner on Medium]]></title>
        <description><![CDATA[Stories by Jared Casner on Medium]]></description>
        <link>https://medium.com/@jaredcaz?source=rss-20bc6a624c75------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Vf9rZx-36t5VNwqERP_pMA.jpeg</url>
            <title>Stories by Jared Casner on Medium</title>
            <link>https://medium.com/@jaredcaz?source=rss-20bc6a624c75------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:48:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jaredcaz/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[Why I cofounded Blacksmith InfoSec]]></title>
            <link>https://medium.com/@jaredcaz/why-i-cofounded-blacksmith-infosec-033af27bcf8f?source=rss-20bc6a624c75------2</link>
            <guid isPermaLink="false">https://medium.com/p/033af27bcf8f</guid>
            <category><![CDATA[founder-stories]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Jared Casner]]></dc:creator>
            <pubDate>Fri, 16 Feb 2024 16:23:10 GMT</pubDate>
            <atom:updated>2024-02-17T16:01:38.818Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mFnE1S_9xK838PS7" /></figure><p>First a little backstory for context — feel free to skip to the next paragraph if you want! I have often described the early stages of my career journey as accidental — through a bit of happenstance and a bit of just saying “yes” at the right time, I took a somewhat meandering path through the working world. This journey started at Visa, where I helped build out data centers, pulled network cables, and configured routers and servers in a job that would be described today as a DevOps engineer. Looking to move into a more “pure software” role and also interested in travel, I took a job as a technical consultant at Sapient. I ended up with a TS/SCI clearance and subcontracted for some of the 3 letter agencies in our national intelligence community. Frustrated by the pace of innovation, I took a similar job at a (then) startup named Aprimo, traveling the world (including a 3-year stint in London). Life and luck led me to moving to San Francisco where I joined Numenta, a machine intelligence company, where I led applications engineering. This was followed by technical leadership roles at Opengov (govtech) and Sindeo (fintech). When <a href="https://medium.com/@jaredcaz/winding-down-9d636bfac249">Sindeo collapsed</a>, I took the summer for some soul searching and got much more intentional about my career. I ran engineering at CNote (fintech) before pivoting to healthcare, first with Pear Therapeutics and then Trayt Health.</p><p>Why the preamble? I think this context is important in understanding how I ended up building something new. And not just anything, <strong><em>this</em></strong><em> </em>something. Despite, or perhaps because of, my start in big companies and government services, I found my home at small companies where I had to be scrappy to survive — budgets were tiny, teams were small, and we just had to <strong>figure it out</strong>. At the same time, many of these companies played in heavily regulated spaces and required a deeper scrutiny on security than some other startups might have. After all, when dealing with personal finance or healthcare details, I had a responsibility to protect the data I was collecting.</p><p>As such, at each of my last few companies, I had to put a security program in place. This meant writing security policies and procedures. Providing security awareness training to my staff. Defining a security roadmap. Managing organizational risk. Ensuring compliance with NIST CSF, SOC2, and HIPAA. And yet, my budget was often so small I couldn’t afford the best in class tools that my friends at larger companies recommended. I’ve <a href="https://www.youtube.com/watch?v=gtP5OU-8OEk">talked about this for years</a> — bootstrapping a security program on a shoestring budget is hard work.</p><p>Then, in August 2023, I found myself looking for my next opportunity. As I was talking to my good friend and former colleague <a href="https://www.linkedin.com/in/michaelzbarsky/">Michael Zbarsky</a>, also looking for work after his employer filed chapter 11 bankruptcy, I realized that I was about to see my last few jobs play out again. And so was Mike. We had both built security programs from scratch at our last few employers, and we could already see the writing on the walls during our interviews that crafting a new security program was first up for us in any new role.</p><p>It didn’t take long for us to say “this is crazy; why would we put ourselves through all that again?”. And so, in September, we incorporated, put some cash into a business bank account, and started building <a href="https://blacksmithinfosec.com/">Blacksmith InfoSec</a>. We wanted to make sure that, if nothing else, future Mike and future Jared would have a tool to simplify our lives. We wanted something built — and priced — for small businesses, a tool that was approachable, easy-to-use, and that would fit the budgets of SMBs. We didn’t want to compete with the big players and their expensive tools, but we did want to make sure that SMBs had a good foundation. And we wanted to make it easy for SMBs to outgrow our software over time. That’s right — we didn’t want tight vendor lock-in or an expensive growth trajectory.</p><p>So, if you’re running a small business and are interested in starting your security program but don’t have the budget for specialized, enterprise software, come check out what <a href="https://blacksmithinfosec.com/overview">Blacksmith has to offer</a>. You can generate custom security policies in minutes that are specifically written to pass an audit for whichever security and compliance frameworks you choose. Today, we support NIST CSF, HIPAA, SOC2, NIST 800–171, CMMC, NYCRR Part 500, and the SEC security rule. As you generate your policies, we build out a prioritized security roadmap for you, so you can focus on the things that matter most to your business. We provide security awareness training for your staff that is both concise and comprehensive. We track your user’s progress through acknowledging policies and completing their training. We provide tools for risk management. Each of these modules can be disabled (and the data exported) as you outgrow our services and move into the more robust solutions offered by specialist vendors. And we’re priced so that any SMB can afford us — only $200 / month or $2000 / year, regardless of how many users you have. We offer everyone the same great customer service and features at the same low price. No hidden fees. No up charges. No per-user costs. Just one great tool at one low price.</p><p>The founder journey is never easy and we’re far from finished here. But we’re having fun and we’re helping secure small businesses across America.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=033af27bcf8f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Choosing better passwords for your financial accounts | CNote’s Official Blog]]></title>
            <link>https://medium.com/gocnote/choosing-better-passwords-for-your-financial-accounts-cnotes-official-blog-ecd97c7a1174?source=rss-20bc6a624c75------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecd97c7a1174</guid>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Jared Casner]]></dc:creator>
            <pubDate>Thu, 05 Apr 2018 19:24:00 GMT</pubDate>
            <atom:updated>2018-04-10T04:23:22.987Z</atom:updated>
            <content:encoded><![CDATA[<p>The first line of defense in information security is… you!</p><p>Obviously, anyone who has access to your data has an obligation to store it securely, protect it from unauthorized access, and keep your identity, data, and money safe. But, it doesn’t matter how secure your financial institution is if you don’t take some simple steps to protect yourself.</p><p>This post will focus on choosing a secure password to help protect your data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/1*yWlCf_Of9Q2Usv3OIPmpHA.png" /></figure><h3>Common Myths of Password Security</h3><p>There are a lot of common security practices that, when done right, can lead to better security and stronger passwords. However, it is just as likely that forcing users to conform to specific standards can lead to <em>less</em> secure passwords. That’s why we believe step 1 in choosing a secure password isn’t creating onerous requirements for our users. Rather, it is educating you on some good practices so that you can make informed decisions for yourself.</p><h3>Myth 1. Changing Passwords Every 90 Days Guarantees Security</h3><p>Don’t get us wrong — you definitely want to change your passwords <em>eventually</em>. However, when users are forced to change their passwords frequently, they typically use an incremental password, meaning hunter2 becomes hunter3 and so on. How many of you reading this are “guilty” of something like this? These incremental passwords are no more secure than the previous password and are equally easy (or hard) to guess. Don’t believe us, here’s a good <a href="https://www.ftc.gov/news-events/blogs/techftc/2016/03/time-rethink-mandatory-password-changes">synopsis on a couple peer-reviewed studies</a> that show the potential detrimental effects of frequent password changes. So, when you do change your password, make sure to make it unique, unpredictable, and do it at an uneven interval.</p><h3>Myth 2. Using a Password Manager Is Perfectly Secure</h3><p>There is no question that a password manager is better than writing your password on a sticky note or saving them to a word document (even an encrypted one). However, if someone gains access to your master password, they now have knowledge of and access to every site that you have stored in them. It won’t matter how secure your site passwords are if someone can access them with ease, so knowing how to craft a secure master password is even more important.</p><p>Interested in learning more? Here are some <a href="https://www.tomsguide.com/us/password-manager-pros-cons,news-19018.html">pros and cons to password managers</a> so you can make an informed decision for yourself.</p><h3>Myth 3. Long Passwords Are ALWAYS Better</h3><p>The more characters you use, the harder it will be to guess your password using a pure, uninformed “brute force” attack. However, attackers are smart, so before they try every possible combination in order, they start with some really common passwords. Choosing something like 123456789 or password1 is <a href="https://en.wikipedia.org/wiki/Password_strength#Entropy_as_a_measure_of_password_strength"><em>mathematically</em></a> more difficult to brute force than a password like 6BqP9@.</p><p>In practice, however, using sequences (e.g. 1234), common dictionary words (e.g.: password), and common substitutions (e.g.: a = @, s = $) makes the attackers job much easier.</p><h3>Choosing a Secure Password</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*QQBD5BHwPDe4N-m0zEdU5g.png" /></figure><p>Secure passwords have some common characteristics. <a href="https://www.nas.nasa.gov/hecc/support/kb/what-are-the-requirements-for-creating-a-password_8.html">NASA</a> publishes some pretty clear guidelines on secure passwords for their users that adhere to <a href="https://pages.nist.gov/800-63-3/">NIST</a> identity protection guidelines but are presented in a way that is easy to read and understand. Some things to consider when choosing your password:</p><ul><li><strong>Hard to Guess (</strong>i.e. unpredictable<strong>)</strong></li><li><strong>Easy to Remember</strong> (so you don’t need to write it down)</li><li><strong>Unique</strong> (meaning, you don’t use it on other websites)</li></ul><p>Passwords like g5pe@cK7WY9 definitely qualify as hard to guess, but how easy to remember is that? Passwords like JaredCnote! might be easy to remember and unique for you, but are also pretty easy to guess.</p><p>The best password is a random one, but it turns out humans like patterns and therefore create “random” passwords in very predictable ways. This makes it really easy for cyber-thieves to guess them. It turns out that choosing 4 random words can make a really secure, easy to remember password. Here’s a fun (albeit slightly technical) <a href="https://xkcd.com/936/">webcomic about random four-word passphrases</a>.</p><p>Now… can you remember a different 4 random word combination for every site you use? Probably not. But, if you use a very secure passphrase as your master password for your favorite password manager, you can protect your digital vault reasonably well. Then, you can use that password manager to ensure you have unique, truly random, highly secure passwords that are remembered for you.</p><h3>Other Considerations</h3><p>Choosing your secure password is only half the battle. Keeping it secure is the other half. For this reason, you should never share your password with anyone else. The only place you should use your CNote password, for example, is on the CNote login page — our employees will never ask you for your password and you should never volunteer it to us.</p><h3>Additional Resources</h3><p>The <a href="http://www.surveygizmo.com/s3/2758757/The-Password-Game-Carnegie-Mellon-University-website">Password Game</a> by Nature and Carnegie Mellon University will test your knowledge of what a secure password really is.</p><p><em>Originally published at </em><a href="https://blog.mycnote.com/2018/04/05/choosing-better-passwords-for-your-financial-accounts/"><em>blog.mycnote.com</em></a><em> on April 5, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecd97c7a1174" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gocnote/choosing-better-passwords-for-your-financial-accounts-cnotes-official-blog-ecd97c7a1174">Choosing better passwords for your financial accounts | CNote’s Official Blog</a> was originally published in <a href="https://medium.com/gocnote">goCNote</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meaningful Conversations]]></title>
            <link>https://medium.com/@jaredcaz/meaningful-conversations-8972a00347e6?source=rss-20bc6a624c75------2</link>
            <guid isPermaLink="false">https://medium.com/p/8972a00347e6</guid>
            <category><![CDATA[human-connection]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[one-on-one]]></category>
            <dc:creator><![CDATA[Jared Casner]]></dc:creator>
            <pubDate>Fri, 15 Sep 2017 16:18:17 GMT</pubDate>
            <atom:updated>2017-09-15T16:18:17.581Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>I’ve only had a single 1:1 with my manager in the past 6 weeks. And, when I do manage to have a 1:1, my manager is dismissive / distracted / disinterested.</blockquote><p>I’ve heard that refrain, or something very similar, over and over again from people I coach. Too often, it seems, managers treat scheduled 1:1 time with their team as optional or unimportant. This leads to uncertainty, fear, and frustration at the office, which can paralyze a team if left to fester. Conversely, in the words of Anne Mulcahy, CEO of Xerox,</p><blockquote>Employees who believe that management is concerned about them as a whole person — not just an employee — are more productive, more satisfied, more fulfilled. Satisfied employees mean satisfied customers, which leads to profitability.</blockquote><p>When I mentor leaders, here are some principles I encourage them to think about with respect to the conversations they have with their direct reports:</p><ul><li><strong>Treat the time as sacred</strong>. Sure, rescheduling is OK if there’s something urgent that needs to be dealt with, one of you is on PTO, or similar. However, your staff will come to like and depend on that time. I frequently ask people what day/time is best for them; I don’t want to schedule in the middle of their most productive period, at an hour that makes them anxious about commuting, etc. And then I do everything in my power to make it to those meetings and find a timely follow up window if one of us can’t make it.</li><li><strong>Make it a safe space</strong>. This does not mean that there will be no repercussions that come out of discussions that happen in your 1:1, but it does mean that you will do what you can to protect your staff’s privacy and provide constructive feedback to improve things where necessary. In short, it requires empathy, <a href="http://www.ccl.org/wp-content/uploads/2015/04/EmpathyInTheWorkplace.pdf">which studies show is positively related to job performance</a>. One simple way to do this is to ask, “What did I miss?” That one question both demonstrates that you know you’re not omniscient and shows that you value their input and opinion. You should also recognize that <a href="http://www.mckinsey.com/global-themes/leadership/top-executives-need-feedback-and--heres-how-they-can-get-it">your employees can be great coaches for you</a> if they feel safe providing feedback, so fostering a healthy environment is a serious win-win. I’ve learned some hard truths about myself — including that I’m long winded! — from these discussions, which give me some great areas to focus on personally.</li><li><strong>Be an active listener</strong>. Unless there’s a good case for it, I leave my electronics at my desk during 1:1s. Instead, I’ll take paper and a pen only to jot down any action items that come out. My attention therefore remains focused on my employee. I’m interested in what they’re saying and what they’re not saying. I ask probing questions and don’t just take things at face value. I want to know why things are “great” just as much as I’m interested in why things are “not so great”. Active listening also means not responding “cool” when your employee tells you they just booked a flight to Vegas, it means following up with questions like “Great, when do we leave?” But seriously, showing an interest in your team and asking follow up questions will help develop a <a href="https://www.decision-wise.com/how-connection-drives-employee-engagement/">deeper human connection which leads to higher employee engagement</a>.</li><li><strong>Provide candid feedback.</strong> In general, my approach is to provide so much candid feedback at each 1:1 (and in between for that matter), that my team can effectively write their own reviews. If anyone from my team(s) is surprised by anything on their review, either positive or constructive, I take that as a personal failure. When providing feedback, be specific. “You’re doing a great job” is far less effective at conveying how valued an employee is than “Wow, that new module you wrote really knocked it out of the park! I was personally impressed and have heard great feedback from Alice, Bob, and Chris, too”. Likewise, “You really messed that up” is not helpful, whereas having a real, positive, and constructive dialogue about how to do better can make a tangible change in your workforce.</li><li><strong>Focus on the individual</strong>. Taking a “one size fits all” approach to your 1:1s or making them very formulaic will likely be seen as disingenuous. It is not just a time for you, the manager, to satisfy your needs. Rather, it is a time to satisfy the needs of your employees and make sure they are heard and valued. Ask about what’s going on outside of work. Consider getting out of the office — a walk, a coffee shop, a park bench — whatever it takes for each employee to feel comfortable and heard. Perhaps most importantly, change the tune and topics to be relevant over time. The only constant in life is change; switching things up will keep your 1:1s fresh and enhance their long term value to you and the individuals you manage.</li></ul><p>Yes, these guidelines can make for time consuming 1:1s. They are meant to do so. Your employees are important. In fact, HBR notes that <a href="https://hbr.org/2015/03/positive-teams-are-more-productive">Positive Teams Are More Productive</a>. You can easily promote a culture of positivity by doubling down on those things that make your team happy and course correcting when your team is unhappy. Investing in your 1:1s and your team will pay dividends.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8972a00347e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Hiring Right]]></title>
            <link>https://medium.com/@jaredcaz/getting-hiring-right-a7eeaf220745?source=rss-20bc6a624c75------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7eeaf220745</guid>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Jared Casner]]></dc:creator>
            <pubDate>Sat, 05 Aug 2017 14:43:10 GMT</pubDate>
            <atom:updated>2017-08-05T14:43:10.907Z</atom:updated>
            <content:encoded><![CDATA[<p>While this post primarily focuses on hiring engineers since that’s where I have the most experience, many of the thoughts here are applicable across the organization.</p><p>Since writing about <a href="https://medium.com/@jaredcaz/winding-down-9d636bfac249">Sindeo’s shutdown a few weeks ago</a>, in addition to my own search, I’ve had the unique experience of being an observer and mentor to a team of engineers going through the hiring process at dozens of companies. Most of these have been net-positive experiences for my former colleagues. However, it has really highlighted that even when companies try to be scientific about hiring, they are probably focusing on the wrong areas. My firm belief is that hiring is both an art and a science in nearly equal measures. Some <a href="https://www.google.com/search?q=hiring+science+or+art%3F&amp;oq=hiring+science+or+art%3F&amp;aqs=chrome..69i57.3407j0j1&amp;sourceid=chrome&amp;ie=UTF-8">quick Googling</a> shows that I’m not alone in this belief (yes, confirmation bias at work here!) Where do things go wrong?</p><h4>Define the Role</h4><p>It’s still amazing to me when I talk to hiring managers and they are still unclear on what they’re hiring for. It’s one thing to refine your search a little bit, but the difference between a junior front-end and a senior full-stack engineer is pretty significant. Similarly, a hands on, engineer-first manager will not necessarily have the same long term motivations as a candidate who has been relatively hands off but is great at building teams and managing people and process. To avoid wasting time, be honest about the pieces that are missing within your organization. Then make sure everyone internally is bought into the role. I talked to one company recently where the hiring manager (CEO) was talking about a VP of Engineering role but the incumbent director of engineering thought he was getting a peer to manage another development team — that made for an awkward conversation with the “peer”. Finally, craft your job description(s) to make sure you are clear about what you want so that you get the right sort of candidates.</p><h4>Job Description</h4><blockquote>If I had seen the job description before I interviewed, I never would have applied!</blockquote><p>Yes, that’s a real quote from one of my team members <em>after getting the job</em>! On paper, this engineer wouldn’t have been qualified for the posted position. However, after blowing the company away on the tech challenge and interviews, it became clear how good this engineer is and what a natural fit there was. Getting your job description right is critical to getting a good applicant pool. Too often, I see job descriptions include laundry lists of every single thing the employee <em>might</em> need to know, not just those skills that are critical for success. This has been <a href="https://www.sussex.ac.uk/webteam/gateway/file.php?name=gendered-wording-in-job-adverts.pdf&amp;site=7">shown to introduce bias</a> at the very first external step of the hiring process. Instead, when you’re taking that first, internal step of determining what you need, make an effort to distill that list down to the most critical success factors. After you’ve drafted the description, run it through a bias detector. There are <a href="http://gender-decoder.katmatfield.com/">free options available</a>, but you can also find paid services like <a href="https://textio.com/">Textio</a> that are more robust if your budget will support it.</p><h4>Sourcing</h4><p>Once you have a clear job description, you can start to fill your funnel. This is where you’ll find the difference between good and bad recruiters. What separates them? Research. Despite how simple this sounds, there’s actually enough that goes into this that I’ll write a separate post on recruiters and sourcing. In the meantime, suffice it to say that if you’re sourcing yourself, you should do a little homework before reaching out to a candidate. If you’re using an internal or external recruiter, make sure they’re doing the same. <a href="https://www.forbes.com/sites/work-in-progress/2014/09/05/how-important-is-your-first-impression-really/#2e2c51e053de">First impressions are critical</a> to getting the ball rolling smoothly.</p><h4>Technical Challenges</h4><p>As a hiring manager, I find technical / coding challenges to be an essential part of the hiring process. I want to know how someone thinks, if they can solve problems, and if they can write some code. Some gross generalizations for myself: I’m <em>typically </em>looking for generalists, so I don’t care what language they take the test in, am not concerned with whether they can find the O(1) algorithmic solution, and could care less if they need to Google some syntax along the way. Obviously there will be exceptions to these “rules”. So it has surprised me to see the various tests that my team has gone through. Front-end engineers being asked deep SQL questions or to code an entire back-end in Ruby. Junior engineers being given senior challenges “because we have never hired someone with less than 10 years of experience and don’t know how to modify our challenge accordingly.” Exercises where the candidate is asked to spend “no more than 8 hours” on the test, but then is given <em>no feedback</em> at the end of it. Tests that have implicit bias such as spelling at grammar.</p><p>Just like with your job descriptions, structuring your technical challenges is important and they should reflect the skills needed for the position they are intended for. If you’re looking for a computer vision engineer, then questions about Convolutional Neural Networks makes a lot of sense. In that vein, I can see an English test being really useful when evaluating a marketer, sales person, or lawyer, but its utility for an engineer is less obvious to me. While some have suggested <a href="https://www.linkedin.com/pulse/beware-hackerrank-richard-linnell">moving away from the automated challenge</a>, I think those are fine. Instead, I’d encourage you to focus on the skills that are most critical when designing your challenge. For example, my wife recently created a case study for entry level operations candidates. The critical skills for her team are problem solving and attention to detail; Excel skills are nice to haves. She did a great job of structuring the case study as an Excel spreadsheet in a way that allowed for a “brute force” method that didn’t require Excel knowledge, but would allow for candidates with specific expertise to shine.</p><h4>Interviews</h4><p>Interviewing is a two-way street, an opportunity for the candidate to vet you as much as for you to vet the candidate. So, while you expect the candidates to come in having done a lot of research into your company and well prepared for the interview, they would like to see the same level of effort from you. Spend some time briefing all of your interviewers on the specific areas of focus to make sure questions aren’t being repeated. Make sure your team has read the candidate’s resume, looked at their github, browsed their LinkedIn, etc. (<a href="https://hiring.monster.com/hr/hr-best-practices/recruiting-hiring-advice/acquiring-job-candidates/social-media-recruiting-guidelines.aspx">but be careful about what you look for and use</a>). <a href="https://www.slideshare.net/eremedia/how-to-train-your-hiring-managers-to-be-master-interviewers">Train your interviewers</a> and make sure <a href="https://rework.withgoogle.com/guides/hiring-train-your-interviewers/steps/giving-interviewers-practice/">they practice</a> in advance and are able to <a href="https://hiring.monster.com/hr/hr-best-practices/recruiting-hiring-advice/interviewing-candidates/legal-job-interview-questions.aspx">keep the interview legal</a>. I’ve been surprised by how many stories I’ve heard of inappropriate or illegal questions that my friends have been asked during interviews.</p><p>You generally only get one chance for an onsite interview with the candidate, so you want to make sure to get all of your questions answered. Well prepared and rehearsed interviewers will stick to the schedule, be more effective in the questions they are asking, ensure they get the answers they need, and provide a better candidate experience. Speaking of which…</p><h4>The Candidate Experience</h4><p>The candidate experience during the interview process is really important. Yes, the candidate needs to sell themselves to you, but the same is true in reverse. Given how small the world is in combination with tools like Glassdoor, negative candidate experiences can really impact your ability to hire. A couple of anecdotes:</p><ul><li>Three of the Sindeo engineers interviewed at one company. After the interviews, they compared notes and discovered that answers to their questions about mentoring, internal promotions, and process were not consistent. When only one of the three received an offer and the other two didn’t even receive follow up emails, it made the decision not to accept the offer easy.</li><li>I’ve heard from several female friends and colleagues that they are asked inappropriate questions about their appearance, dating status, and worse during interviews. Needless to say, they were unimpressed and decided to take their talents elsewhere (and in several cases, filed complaints with the HR teams and/or EEOC).</li><li>A former colleague went into an interview where the CEO, rather than giving an upbeat sales pitch about why the candidate should join the new company spent the entire time trashing the candidate’s current employer. Some advice here for candidates and hiring manager’s alike — you want people running <em>to </em>a new job, not <em>from</em> an old one.</li></ul><p>In short, the more excited you are about a candidate, the more likely they are to get excited about you. Ultimately, you want all of your candidates to walk away from the interview as net promoters of your company, even if they don’t get the job. Ultimately, their <a href="http://www.lifehack.org/articles/lifestyle/your-perception-is-your-reality.html">perception of your company becomes their reality</a>.</p><h4>The Cost of Failure</h4><blockquote>Interviewers tend to be most concerned with trying to avoid “false positives” as hiring a candidate who doesn’t work out can be highly problematic. <br>— <a href="https://hbr.org/2016/02/a-scorecard-for-making-better-hiring-decisions">Harvard Business Review</a></blockquote><p>There is absolutely a tangible cost to getting hiring wrong. In fact, the cost of advancing a “bad” candidate increases at each stage of the funnel. It’s really low cost to reject someone based purely on their resume, but by the time they’ve come onsite, you’ve invested a lot of time and energy into the candidate. And, if you make a “bad” hire, it can really be painful and expensive to fix. To that end, I typically give everyone on the interview panel “veto” rights — and vetoes aren’t explicit. If anyone is lukewarm about a candidate, that’s a signal not to hire. However, there is also an opportunity cost to not filling a role. Multiple times in my time as a hiring manager, I’ve had a critical role that we just couldn’t come to consensus on any candidates. To get around it, I’ve brought on engineers in a contract-to-hire capacity. This gives people, especially introverts, an opportunity to overcome a “good, not great” interview experience through on the job experiences. I am very candid with these employees about what the yellow flags were that prevented a full time position so that they know what, exactly, I’m evaluating while they’re under contract. And I give them open and honest feedback along the way so that they know how they’re doing. This helps avoid the “misses” while keeping the cost of a false positive a little lower…</p><h4>It’s All About Culture</h4><p>I’m planning to write more extensively about culture — specifically about building and nurturing it intentionally — but until then it’s important to mention in the context of hiring. Whether you’re a company with well articulated values that people live and breathe or an organization that aspires to have that level of culture, you still want to make culture a focal point of interviewing. Some companies (like <a href="https://www.amazon.jobs/principles">Amazon</a>) describe their core values clearly on their websites. Others send their values to all candidates. Their goal isn’t get find more homogenous cogs for their organization, but to find people who believe in the same values, even if they have different approaches to getting there. At a recent @fintech-devs-pms <a href="https://medium.com/fintech-devs-pms/how-to-build-engineering-and-product-culture-b9a1328e0ae5">meetup</a>, <a href="https://www.linkedin.com/in/klochner/">Kevin Lochner</a>, Engineering Lead at <a href="https://clara.com/">Clara</a>, talked about hiring for <a href="https://www.youtube.com/watch?v=F8UuYPgkMks">competency fit rather than culture fit</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FF8UuYPgkMks%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DF8UuYPgkMks&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FF8UuYPgkMks%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f2af42ae78db9dab358f8e52114dd4ce/href">https://medium.com/media/f2af42ae78db9dab358f8e52114dd4ce/href</a></iframe><p>Personally, I advocate for <a href="https://www.feld.com/archives/2017/06/go-culture-add-not-culture-fit.html">“culture add” over “culture fit”</a>, which is very closely related to these concepts. Knowing what you value will help you find people who share those values even if their approach to adopting those values is different.</p><blockquote>A hiring process built around an undefined notion of “culture fit” is fraught with bias.<br> — <a href="https://www.forbes.com/sites/larsschmidt/2017/03/21/the-end-of-culture-fit/#2e222e638ae1">Forbes</a></blockquote><p>This is by no means an exhaustive post, but will hopefully provide some help to overcoming some of the common “mistakes” I’ve seen in hiring processes. Any questions or comments? I plan on diving into these topics and more in future posts and would love to share stories from others about what works and doesn’t work!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7eeaf220745" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Winding Down…]]></title>
            <link>https://medium.com/@jaredcaz/winding-down-9d636bfac249?source=rss-20bc6a624c75------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d636bfac249</guid>
            <category><![CDATA[people]]></category>
            <category><![CDATA[family]]></category>
            <category><![CDATA[opportunity]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Jared Casner]]></dc:creator>
            <pubDate>Sun, 25 Jun 2017 14:22:30 GMT</pubDate>
            <atom:updated>2017-06-25T14:22:30.269Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kDmI0KEIwZx-6ptsqoajnw.jpeg" /><figcaption>Sindeo Team, February 2017</figcaption></figure><p>It seems somewhat backwards that my first post would be titled “winding down”. Yet after <a href="https://www.housingwire.com/articles/40493-heres-why-sindeo-shuttered-its-business">Sindeo closed its doors unexpectedly</a>, it seems entirely appropriate. Despite <a href="https://www.fastcompany.com/40433057/just-got-laid-off-this-is-the-two-month-plan-you-need-to-follow">advice to write about my experience on day 1</a>, I opted to wait a while, to give myself time to write something that I could actually share publicly. As I went through the <a href="https://grief.com/the-five-stages-of-grief/">five stages of grief</a>, I lingered for a while on depression. We had something special — a great team, a great vision, and we were solving a real problem. We just didn’t have gas in the tank.</p><p>The day Sindeo closed down, I sent a message on <a href="https://www.linkedin.com/feed/update/urn:li:activity:6283087889127608320/">LinkedIn</a>, <a href="https://www.facebook.com/jaredmcasner/posts/10211632120472283?pnref=story">Facebook</a>, and <a href="https://twitter.com/jaredcaz/status/877323020276080641">Twitter</a> looking for anyone who could help my team find new jobs. The response was overwhelming. Literally. In addition to the comments on the posts, I received hundreds of emails, private messages across multiple channels, and dozens of phone calls. And not just from people I know well or even know at all. I half expect the next email I open to be from my cousin’s neighbor’s roommate’s girlfriend or some equally tenuous connection. While it would be really easy to be bitter, depressed, or angry about how things went down, the support and outreach have been incredible, uplifting, and heartwarming.</p><p>As with everything in life, time provides perspective. While I’m still disappointed that we didn’t get to realize our vision, I also recognize that through adversity comes opportunity. I’m seeing that in the options that former Sindeons are looking at. There are a lot of exciting roles with companies who don’t just have the vision, the team, and the problem, they also have the gas. The people at Sindeo have become as close as family to me despite our short time together, and I can’t wait to see where they go and what they do next.</p><p>As for me, I plan to take a deep breath, reflect on what’s important to me and my family, and be patient about my next move. In the meantime, I’m hoping that getting this first post up will spur me to do a little more writing. I’m planning to do a little prototyping of some ideas I’ve been kicking around for a while and never found the time to think about properly. Most importantly, I’ll get to spend some quality time with my wife and daughter. Yet more evidence that through adversity comes opportunity. Can’t wait.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d636bfac249" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>