<?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 Michal on Medium]]></title>
        <description><![CDATA[Stories by Michal on Medium]]></description>
        <link>https://medium.com/@furchin?source=rss-37ac2f09110------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*1tpzIalqONB61LRq.png</url>
            <title>Stories by Michal on Medium</title>
            <link>https://medium.com/@furchin?source=rss-37ac2f09110------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:16:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@furchin/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[Tips to WFH]]></title>
            <link>https://medium.com/@furchin/tips-to-wfh-b0c01834cafb?source=rss-37ac2f09110------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0c01834cafb</guid>
            <dc:creator><![CDATA[Michal]]></dc:creator>
            <pubDate>Thu, 05 Mar 2020 22:27:52 GMT</pubDate>
            <atom:updated>2020-03-05T22:27:52.291Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a short list of tips and experiences I found useful during my 2+ years as a remote worker.</p><ol><li>Fully establishing a routine is going to take 3 months. This period of time will, sadly, reset with any major changes (e.g., moving, changing jobs, or your childcare situation). The first week or two will be the hardest and it gets easier over time.</li><li>Use an iPad as a second monitor. iOS 13 lets you just AirPlay as a second display, but you can also use Duet Display.</li><li>Pack a work bag with a spare laptop charger with a long cord. Having a spare charger lets you have a dedicated one at your desk that you don’t have to keep reaching under to unplug.</li><li>Keep your camera on during video calls, even if your background is busy, cluttered, or has other people in it. This lets people see you and remember your presence in the meeting. It’s okay to mute your mic if you’re not speaking much.</li><li>Be responsive on Slack — people can’t drop by your desk to ask a question, so try to be available. However you don’t have to respond 24/7 — it’s okay to have a personal life. Use status, away, and do-not-disturb modes as necessary.</li><li>Jamboard has an iOS app. Use it if you need to collaborate in realtime on a whiteboard.</li></ol><p>In light of Covid-19, you may want to avoid working from public places, but here is my advice if you choose to ignore those concerns:</p><ol><li>Location matters. You need solid WiFi. Some coffee shops can be really hit-or-miss; Starbucks is consistently excellent in this regard. Try out a bunch of coffee shops to find your favorites. Don’t forget about public libraries, which often have free WiFi.</li><li>If you’re working at a coffee shop, buy a drink every two hours. They are businesses and need to pay for the space somehow. Some places may have specific rules posted — you should obey these, but in their absence a good rule of thumb is every two hours. Adjust frequency based on capacity: if it’s empty, then you can probably stretch that out a little; conversely if it’s jam-packed then you really should buy more frequently (or find a less crowded shop).</li><li>Don’t forget to socialize. One good way is to find 4–6 friends whom you’d like to see and schedule a standing monthly lunch, which should give you a lunch to socialize at least once a week.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0c01834cafb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pager Team’s Technical Stack]]></title>
            <link>https://medium.com/pagerteam/pager-teams-technical-stack-133d361b7b8f?source=rss-37ac2f09110------2</link>
            <guid isPermaLink="false">https://medium.com/p/133d361b7b8f</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Michal]]></dc:creator>
            <pubDate>Fri, 05 Apr 2019 22:01:06 GMT</pubDate>
            <atom:updated>2019-04-05T22:01:06.177Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MzQaAbWwSJQ0Nf0zWyDjVw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/09FcOqmi8R0?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Luke Pennystan</a> on <a href="https://unsplash.com/search/photos/pancake?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I’ve had a couple of folks reach out, curious about the technology that <a href="https://pagerteam.com">Pager Team</a> is built on top of. While I’ve posted <a href="https://stackshare.io/pager-team/pager-team">Pager Team’s stack on Stack Share</a>, it might not be obvious how everything fits together.</p><p>Everything runs on a Google Kubernetes Engine-managed Kubernetes cluster. GKE is nice, although running the free-tier eligible f1-micro instances is problematic. GKE will let you create a cluster with f1-micro instances, but it will fail in assorted non-obvious ways which I’ve chalked up to insufficient compute power.</p><p>On top of Kubernetes, Pager Team uses <a href="https://traefik.io/">Traefik</a> as the ingress controller. Traefik runs multiple pods using an etcd cluster to share configuration and, importantly, Let’sEncrypt certificates. Traefik also seamlessly handles the ACME protocol to get those certificates from Let’sEncrypt in the first place, and automatically renew when appropriate. When a request hits the Kubernetes cluster, Traefik routes it to the appropriate pod. DNS is handled by AWS Route53.</p><p>Pager Team’s front end is based on a modified <a href="https://github.com/sahat/hackathon-starter">hackathon-starter</a>. It uses uses ExpressJS and renders using pug and SASS. The base CSS framework is <a href="http://getbootstrap.com">Bootstrap</a>. There are a few javascript libraries (<a href="https://heelhook.github.io/chardin.js/">ChardinJS</a>, <a href="https://morphext.fyianlai.com/">Morphext</a>, <a href="https://fullcalendar.io">FullCalendar</a>, <a href="https://prismjs.com/">Prism</a>), but the front-end is relatively simple and it’s mostly just jQuery. For development ease, <a href="https://www.npmjs.com/package/rev-file">rev-file</a> is used as a cache buster for the the browser cache.</p><p>The back end is NodeJS using <a href="http://docs.sequelizejs.com/">sequelize</a> as an ORM against an AWS RDS Aurora MySQL-compatible database. Notifications are done by AWS SES for email (once the SendGrid free trial ran out), and Twilio for SMS and voice. The email provider is abstracted away with <a href="https://nodemailer.com/about/">node-mailer</a> which makes changing email services quite easy.</p><p>Everything undergoes trunk-based development and there’s a <a href="http://drone.io">Drone</a>-powered CI/CD pipeline which runs a bivvy of tests (unit and functional). Functional tests are done by running headless <a href="https://cypress.io">Cypress</a> against the staging environment and test users and rotations to make sure no bugs are introduced. Deployments are conducted using <a href="http://helm.sh">Helm</a>, with the pipeline automatically incrementing the package version on each build and uploading it to GCR.</p><p>Individual Kubernetes cron jobs handle notifications (every minute), on-call rotation (every minute), and scheduling (every few hours). Each cron job is monitored separately. Monitoring is an evolving story using a combination of healthchecks.io, UptimeRobot, and Uptime.com. (The website, API, and cron jobs are all monitored.)</p><p>Cloud infrastructure is versioned with a commit history and is treated using the <a href="https://en.wikipedia.org/wiki/Infrastructure_as_code">Infrastructure as Code</a> principle by utilizing Terraform.</p><p>Analytics are also a bit of a work in progress but a combination of Google Analytics, Crisp, and CrazyEgg are currently enabled to help optimize the site and conversion.</p><p>Billing is done through Stripe, with Paywell for analysis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=133d361b7b8f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pagerteam/pager-teams-technical-stack-133d361b7b8f">Pager Team’s Technical Stack</a> was originally published in <a href="https://medium.com/pagerteam">PagerTeam</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s next?]]></title>
            <link>https://medium.com/pagerteam/whats-next-fe398db18c18?source=rss-37ac2f09110------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe398db18c18</guid>
            <category><![CDATA[growth-hacking]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-hunt]]></category>
            <category><![CDATA[sass]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Michal]]></dc:creator>
            <pubDate>Tue, 26 Mar 2019 20:58:40 GMT</pubDate>
            <atom:updated>2019-03-26T22:42:35.592Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week we covered the <a href="https://medium.com/pagerteam/launching-on-product-hunt-3d4c9aaacd1d">recent Product Hunt launch</a>. What’s next for Pager Team?</p><p>User acquisition. That’s the next step. While we have a handful of signups and free trials, we are well short of where we need to be. We are trying to avoid building new features, however. There are still a lot of features that <em>could </em>be built (single sign on, anyone?), but it’s much smarter to build features in response to actual customer requests rather than hoping we’re building the right things. Instead we’re trying the following approaches to get customers.</p><h4>Internet presence</h4><p>On Tuesday after the PH launch, I kept busy by submitting to each and every single site <a href="https://github.com/mmccaff/PlacesToPostYourStartup">in this list</a>. Most of these appear to have a business model centered around maintaining a long queue of pending products to be posted in a month or two, and charging for “expedited processing”. Looking to minimize expenses, I paid for none of them. A few really stood out as exceptional experiences, including <a href="https://alternativeto.net/software/pager-team/">Alternativeto.net</a>, <a href="https://stackshare.io/pager-team/pager-team">StackShare</a> and <a href="https://changelog.com/">changelog</a>. However, by and large, these are not driving a lot of traffic (yet). My theory is establishing a presence on the internet should help drive organic search traffic — Google Search Console indicates absolutely abysmal search result placement and impressions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_XyXcL_AdHl2UrHS08btmA.png" /><figcaption>2 impressions, on the 3rd results page on average.</figcaption></figure><h4>Direct outreach</h4><p>We’re reaching out to small startups and their founders and asking:</p><ol><li>What are you using today to get notified when your site goes down in the middle of the night?</li><li>How many incidents have you had in the past month?</li></ol><p>These answers help guide us on feature prioritization and help us better understand the market. Most everyone we’ve reached out to has been extremely willing to be helpful, and some even offered their own advice.</p><h4>Social outreach</h4><p>I’ve been active on a number of maker communities as well, incl uding <a href="https://wip.chat/@1424">wip.chat</a>, <a href="https://www.indiehackers.com/product/pager-team">indiehackers.com</a>, and <a href="https://getmakerlog.com/products/pager-team">getmakerlog.com</a>. I’m attending a DevOps meetup this week as well.</p><h4>Follow up with existing customers</h4><p>For those users who’ve signed up but haven’t created a rotation, follow up and see what happened. For users with rotations, see if they have any feedback or concerns, and help guide them out of the free trial into a paid plan (which involves adding a credit card, the holy grail of SaaS).</p><h3>Pager Team traffic sources</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zia1HCNUPb6IUukCwtrfdw.png" /></figure><p>Tracfone appears to be simply Bing ads (more on advertising strategy in another post), and along with alternativeto.net has some of the highest pages/session stats. This makes sense, since people keenly interested in learning more about Pager Team will look at the most amount of content. The overall stat should be low because Pager Team doesn’t have a lot of pages that are accessible without an account, 10 total including things like the privacy policy (which is super important and yet not exactly prime marketing material). With the <a href="https://pagerteam.com/help/compare">recent pricing compare page</a> addition I hope those pages/session stats tick up a little but the main landing page continues to contain most content.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe398db18c18" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pagerteam/whats-next-fe398db18c18">What’s next?</a> was originally published in <a href="https://medium.com/pagerteam">PagerTeam</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Launching on Product Hunt]]></title>
            <link>https://medium.com/pagerteam/launching-on-product-hunt-3d4c9aaacd1d?source=rss-37ac2f09110------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d4c9aaacd1d</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-hunt]]></category>
            <category><![CDATA[on-call]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Michal]]></dc:creator>
            <pubDate>Thu, 21 Mar 2019 22:11:06 GMT</pubDate>
            <atom:updated>2019-03-21T22:11:06.835Z</atom:updated>
            <content:encoded><![CDATA[<p>I launched <a href="https://pagerteam.com">Pager Team</a> on <a href="https://www.producthunt.com/posts/pager-team">Product Hunt</a> this past Monday. A lot of people have asked how it went. In this post I’ll answer that question, and share the steps I took before and after the launch. Why Product Hunt in the first place? Not only is it something I’m familiar with, but its audience is largely skewed towards technical people interested in small companies — precisely the type of customer Pager Team is a good fit for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*KhhnsU6d4wvi5IJXhZW_xA.png" /></figure><h3>A brief history</h3><p>Pager Team went live on February 28, 2019. On March 4th I started to tell my network (specifically meaning friends, family, and colleagues) about Pager Team. On March 6th I <a href="https://chrismessina.typeform.com/to/t5FMAz">booked Chris Messina</a> to post Pager Team on Product Hunt. He has a lovely calendar showing availability, and I picked March 18th because it was the first available Monday. My rationale was to get posted as early in the week as possible, to maximize exposure. Weekend launches come with less competition, but also less traffic. As a tool for businesses, I felt the weekday launch was a better strategy and I wanted to be as early in the week as I could.</p><h3>Preparation and waiting</h3><p>I used <a href="https://previewhunt.com/">Preview Hunt</a> to generate a preview of what the Product Hunt post would look like. More importantly, it’s a great way to make sure your copy complies with length limits.</p><p>I also put together a list of people who I thought would help me. I didn’t want to end up dead last so I wanted to make sure I’d get at least a few upvotes.</p><p>Then I went about continuing to iterate on Pager Team. I got lots and lots of feedback that the value proposition wasn’t being made clear by the original tagline, “On-call rotations without limits”. By the time launch day rolled around that had evolved into “Get system outage notifications the instant they occur”, largely thanks to <a href="https://twitter.com/karj">Erik Karjaluoto</a> who so kindly offers his insights from running a creative agency on <a href="https://officehours.io/people/karj">officehours.io</a>. The website tagline itself evolved into a rotating list starting with “Get system outage notifications” — the list is my way of targeting different audiences with the same tagline.</p><p>An aside on audiences: I view Pager Team as having multiple target customers:</p><ul><li>solo founders who need robust outage notifications but have no need for a rotation</li><li>small teams who fit into Pager Duty/Opsgenie/VictorOps’ free or reduced-cost tiers (the <a href="https://pagerteam.com/help/compare">new Pager Team cost comparison calculator</a> takes all these into account; we still come out ahead in most — but not all — scenarios)</li><li>medium teams (7+ engineers on a single rotation)</li><li>larger organizations who need multiple rotations.</li></ul><p>Right now I’m focusing my customer acquisition efforts on solo founders and small teams.</p><p>I also continued to make improvements to Pager Team itself. The biggest change was introducing consolidated billing: rather than getting one bill per rotation per month, customers get one bill every month for all rotations they own. (The person who creates a rotation is considered the owner and pays for it; other people on the rotation don’t.)</p><h3>Launch Day</h3><p>I stayed up until midnight pacific time to watch Pager Team’s post go live. I ended up staying up for almost an hour before getting a restless night of rest. In my mind one of the worst things that could happen was for the site to buckle under load, so I scaled up the Kubernetes cluster and increased the number of pods running Pager Team.</p><h3>Results</h3><p>All said and done, Pager Team ended up with 74 upvotes ending up in 22nd place out of 33 products.</p><p>246 users visited the site on Monday. This is a significant increase over the previous daily record of 13, but falls well short of a flood of traffic.</p><p>Pager Team has seen 2 user signups since Product Hunt.</p><h3>Takeaways</h3><h4>Things that went well</h4><p>My email went out at 12:01am on Monday morning to a list of 36 people. Rather than spam everyone in my address book (trust me I know when I receive one of <em>those</em> emails), I only picked people who I felt were in some way uniquely positioned to help.</p><blockquote>Hi friends, family, former colleagues, people I barely know, and “how did this guy get my email address”,</blockquote><blockquote>As you may or may not know, I’ve been working on a startup for the past few months called Pager Team. It’s basically a product like Pager Duty, only better (for my objective definition of better).</blockquote><blockquote>To make a long story short, I need customers, and what better way to get customers than by putting it up on ProductHunt! If you don’t know, ProductHunt is a vote-based launch platform for products like Pager Team. If people like it and think the product has value, they vote it up. I’ve never done this before but I’ve read a lot about it :)</blockquote><blockquote>The thing is, every ProductHunt day starts at 12:01am PDT and early leaders get more upvotes simply by being on the front-page all day long. So if I can get Pager Team a boost now in the wee hours of the morning, I hopefully stand a good chance of being pretty high on today’s (Monday’s) list as people wake up / check the internet during lunch / surf the web after dinner / whatever.</blockquote><blockquote>So, if you could do me a favor? I’m not supposed to ask for votes outright, but go ahead and check out <a href="https://www.producthunt.com/posts/pager-team">https://www.producthunt.com/posts/pager-team</a> and if you feel so inclined please take the time to upvote. (You’ll need to create an account if you don’t already have one.)</blockquote><p>I finished with a request that folks reply and let me know if they voted. Out of 36 people, 13 replied. (Since these 36 people will be reading this post, thank you for your support! I know some of you were on vacation, and I’m confident some of you helped and simply didn’t reply. Thank you all.) I’m immensely pleased with the 74 votes Pager Team received especially given the small distribution of my email.</p><p>I’m also super pleased with the early traction, from midnight through 1am. Pager Team placed as high as 4th (ignoring the sponsored listing).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/1*nXtBrzu_3ket91uzOwdukQ.png" /><figcaption>4th place at 12:08am PDT</figcaption></figure><p>This led to early traffic:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6StOScvSdOtVbkxWsfyTUg.png" /><figcaption>Traffic as of 12:11am PDT</figcaption></figure><p>However as the day went on, Pager Team’s initial momentum faded as it dropped positions, and traffic dropped during course of the day. Overall, I’m satisfied with the amount of traffic Product Hunt brought to Pager Team. In the last 7 days, Pager Team has seen 413 users. Not having launched anything on Product Hunt before I wasn’t sure what to expect, though of course more traffic would have been even better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/652/1*yvo9LNHzLTJHhVhFqFPpiQ.png" /></figure><p>Another datapoint I have as a result of all this traffic is the breakdown of desktop/mobile/tablet. Pager Team is a responsive website, and I’ve definitely paid attention to make sure things look okay on a mobile screen, but there hasn’t been a “mobile-first” approach and certainly no native apps. My rationalization for this approach has been that small business owners and developers are the target customers for Pager Team, and they would most often be on desktop. Well as it turns out, they are, 79% of the time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/304/1*wTHEOfhydyt_IEEyNeHiqw.png" /><figcaption>Breakdown of traffic by device type. Tablets are now dedicated Netflix screens.</figcaption></figure><h4>Things I’d do differently</h4><p>Most importantly I’d want to have spent more time investing in the landing page. I’d been getting about ten hits per day so I knew the site wasn’t converting at anywhere near 10%, but I’d like to have had a more solid figure on conversion rate (by “conversion” I mean someone who creates an account), and spent more time making the conversion rate as high as possible, to convert as much of the Product Hunt traffic as possible.</p><p>I’d also have launched around 8am PDT, instead of at midnight. Preview Hunt advises launch timing:</p><blockquote>It’s recommended to launch around 00:01 San Francisco time to get maximum exposure</blockquote><p>In aggregate, yes, it does maximize the amount of time your product is listed on Product Hunt. If you’re going to be that day’s top product, yes by all means get in early, win early, and keep winning. Take all the wins! However, it appears the ranking algorithm isn’t an absolute rank; instead there’s some “hotness” component. For instance, Pager Team with 74 votes is listed behind a number of products with vote counts in the 60s:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*LhgN9RRW70a2FIDbuZw6ew.png" /><figcaption>You win some, you lose some</figcaption></figure><p>If I had to guess, it appears the frequency of votes counts significantly — if a product starts getting a lot of votes, it’ll start climbing. Since my distribution list was largely centered in the US, I can’t help but wonder if I shouldn’t have listed at some point in the morning instead.</p><p>Staying up to watch the launch, and the restless night of sleep that followed, meant I was poorly rested during the day. I’m not sure I would have done a whole lot differently, but at a minimum I totally forgot to share the Product Hunt link on a number of maker communities I’m part of until late in the afternoon.</p><p>Not having an established user-base to serve as a catalyst for initial Product Hunt upvotes. Many companies get some initial traction, then go to Product Hunt, using their existing users to get a boost. The risk with this approach is a more drawn-out initial traction phase which kills your morale, and if you do get traction, someone could hunt you when you’re not prepared (there’s no rule on Product Hunt that you can only submit your own product).</p><p>I would also have liked to have had a mechanism to capture some of the non-converting Product Hunt traffic. Maybe folks who didn’t want to sign up for an account would instead subscribe to a mailing list, or <a href="https://twitter.com/pagerteam">follow Pager Team on Twitter</a>?</p><h3>Why did I do all this?</h3><p>The goal for Pager Team is to become a sustainable business. At a bare minimum, that means covering its expenses but the ideal outcome is covering living expenses for me, so I can continue to make it my full-time job. Right now the primary goal is to get enough traffic to the site to get better data about what resonates with prospective customers and what doesn’t, and of course to convert users into paying customers. I’ll talk about what Pager Team’s funnel looks like, but it doesn’t matter unless there’s something at the top to go through the funnel in the first place.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d4c9aaacd1d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pagerteam/launching-on-product-hunt-3d4c9aaacd1d">Launching on Product Hunt</a> was originally published in <a href="https://medium.com/pagerteam">PagerTeam</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s 3am. I must be lonely.]]></title>
            <link>https://medium.com/pagerteam/its-3am-i-must-be-lonely-e6ca8411e020?source=rss-37ac2f09110------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6ca8411e020</guid>
            <category><![CDATA[outage]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Michal]]></dc:creator>
            <pubDate>Tue, 05 Mar 2019 22:13:27 GMT</pubDate>
            <atom:updated>2019-03-05T22:13:27.074Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttps%2Fwww.youtube.com%2Fembed%2FC-Naa1HXeDQ%3Ffeature%3Doembed&amp;url=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttp%2Fwww.youtube.com%2Fwatch%3Fv%3DC-Naa1HXeDQ&amp;image=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttps%2Fi.ytimg.com%2Fvi%2FC-Naa1HXeDQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/12437f2046eeec9c2de761044bf5e150/href">https://medium.com/media/12437f2046eeec9c2de761044bf5e150/href</a></iframe><p>You are about to dock your boat at your private island in the Bahamas when the wheel makes a strange buzzing noise you hadn’t heard before. You make a mental note to have your mechanic check it out before your next sailing. It buzzes again. Stops. Buzzes. Stops. Buzzes, and shakes this time. There is no boat. You slowly come to the realization it’s your phone. It’s been ringing for a few minutes now. You wake up from your pleasant dream and it’s still ringing. There’s an emergency at work and you’re getting paged. It’s 3am. You stumble out of bed and work to get online. It’s just you. What do you do?</p><h4>The happy path</h4><ol><li>Acknowledge the incident to stop it from escalating</li><li>Follow your team’s runbook that has been meticulously crafted with detailed step-by-step instructions on how to resolve the very issue you’re currently seeing</li><li>Make a mental note to question why the runbook hasn’t been automated yet in the next standup and go back to bed.</li></ol><h4>The unhappy path</h4><ol><li>Acknowledge the incident to stop it from escalating</li><li>Remain calm</li><li>Formulate a hypothesis around a likely cause. Apply Occam’s razor: simpler explanations are more likely to be correct.</li><li>Validate your hypothesis with metrics</li><li>Attempt to bring back functionality — although perhaps degraded; your goal here should be the restoration of critical functionality at the expense of nice-to-haves — by doing one or more of:</li></ol><ul><li>rebooting a machine or fleet</li><li>scaling (deploy additional machines or adjust provisioned capacity on services such as DynamoDB)</li><li>changing configuration settings (eg, turn off feature flags, change connection pools, etc)</li><li>rollbacking recent deployments</li></ul><p>You should be applying band-aid fixes and not addressing the root cause. Before you take action, you should avoid making things worse (“do no harm”). As a rule of thumb you should not:</p><ul><li>write new code</li><li>change existing code</li><li>address the root cause</li></ul><p>You will be paged for areas outside of your expertise. Your fundamental role should be to triage the incident, keep things running as best you can, and engage others as appropriate.</p><h4>When to escalate further</h4><ul><li>If your team’s SLA will be exceeded before you can resolve the incident (many teams will have two different SLAs: a shorter one for really serious problems, and a longer one for less serious issues). If you’re not sure or your team doesn’t have one, use 30 minutes as a rule of thumb</li><li>If customers or other teams are actively asking for updates, and you are too busy fixing the issue to respond. (Plural: if just one customer or one other team is inquiring, this rule does not apply)</li><li>If you are unable to formulate a hypothesis as to what might be wrong, or if you are unable to resolve the issue without writing new code</li><li>If you think you need help or a second set of eyes</li></ul><h4>Additional tips</h4><p>Keep notes. What you see, what you try, and what the result is. You might be asked to explain why you took the steps you did, and you should be able to justify your thought process. Notes will also help someone ramp up to speed so they can help if you need to escalate.</p><p>Avoid blaming others. You’re all in this together, and next time it could be your code that breaks. Focus on a solution instead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6ca8411e020" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pagerteam/its-3am-i-must-be-lonely-e6ca8411e020">It’s 3am. I must be lonely.</a> was originally published in <a href="https://medium.com/pagerteam">PagerTeam</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Turn Signal to Noise Ratio]]></title>
            <link>https://medium.com/@furchin/turn-signal-to-noise-ratio-a83f24372aa?source=rss-37ac2f09110------2</link>
            <guid isPermaLink="false">https://medium.com/p/a83f24372aa</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[pull-request]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-architecture]]></category>
            <dc:creator><![CDATA[Michal]]></dc:creator>
            <pubDate>Wed, 12 Dec 2018 22:44:51 GMT</pubDate>
            <atom:updated>2018-12-12T22:44:51.659Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Parable of Pull Requests</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t-U52zx2mNLlGlKwNqjn1w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/BaPtxjQeRhA?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Lorenzo Rezende</a> on <a href="https://unsplash.com/search/photos/taillight?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I tend to view PRs like I do turn signals.</p><p>I don’t turn on my turn signal to get permission to change lanes.</p><p>I don’t turn on my turn signal to absolve me of responsibility if I hit you.</p><p>I turn on my turn signal to give others around me the opportunity (but not the obligation) to let me know if I’m about to screw something up.</p><p>It lets people know I’m changing lanes, and you can speak up if you see an immediate or future problem, but I’m the one who’s gonna get the ticket.</p><p>And if I get enough tickets I lose my license.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a83f24372aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing CodeBnb]]></title>
            <link>https://medium.com/built-for-me/introducing-codebnb-b454c655eca5?source=rss-37ac2f09110------2</link>
            <guid isPermaLink="false">https://medium.com/p/b454c655eca5</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[recruiting-technology]]></category>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Michal]]></dc:creator>
            <pubDate>Mon, 05 Mar 2018 18:35:42 GMT</pubDate>
            <atom:updated>2018-06-05T17:23:05.498Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z5UAld9ZZPksz_EIwJOZFA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/10y18wlEuf0?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Nathan Lindahl</a> on <a href="https://unsplash.com/search/photos/airbnb?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>We’d like to introduce you to <a href="https://github.com/builtforme/CodeBnb">CodeBnb</a>. CodeBnb is the mechanism we use to manage the project step of our <a href="https://blog.builtforme.tech/designing-a-hiring-process-adf311d16b2c">hiring process</a>. (Asking applicants to undertake a project isn’t at all a <a href="https://automattic.com/work-with-us/">unique</a> or <a href="https://hbr.org/2012/05/projects-are-the-new-job-inter">novel</a> <a href="https://www.safaribooksonline.com/blog/2014/04/01/best-interview-questions/">piece</a> of the <a href="https://www.atlassian.com/blog/statuspage/coding-challenges">hiring</a> process.) The CodeBnb name derives from an amalgamation of “Code” and “AirBnb” since candidates get to use a GitHub repository for a short period of time to complete their project.</p><p>Why a GitHub repository? The goal of a project is demonstrate how a candidate can work with a real problem in a real environment. Rather than evaluating a zip file containing the result, we can now evaluate the result along with the process of how the candidate arrived at the result. GitHub also has a lot of other features which lend themselves towards a project: README.md becomes featured quite prominently (which is why the assignment we give our candidates has only a link in the README to another markdown file containing the instructions; we want candidates to feel free to modify the README without worrying about overwriting the instructions). Pull requests, issues, wiki — all of these are features a candidate can now use. Branching, rebasing, merging. All really important as part of the job of a software engineer that you miss out on when you use a zip file for the project evaluation.</p><blockquote>In the end the final code is really what matters most. But good code along with a nice README, a good sensible commit history, issues filed for pieces that need to be done in the future — that’ll get you to the next step in our hiring process.</blockquote><p>CodeBnb also manages the assignment duration. We want our candidates to spend only a couple of hours on our assignment — it’s honestly unfair to them if we asked for a larger investment so early in our hiring process. We give them 72 hours in which to spend those 2 hours, because sometimes life gets in the way.</p><blockquote>Before we wrote CodeBnb we had a lot of difficulty getting a candidate’s GitHub username and getting specific timing right when someone wanted to start on, say, Saturday evening. With CodeBnb, candidates are able to self-service and start at their leisure, with less coordination necessary.</blockquote><p>CodeBnb runs on AWS Lambda fronted by AWS API Gateway. CodeBnb has an internal endpoint which is used to whitelist a candidate for a project. This endpoint queries the GitHub org for a list of template repos (marked with the <em>project</em> tag) which can be given as an assignment. (We have a few different projects we assign, depending on role.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/714/1*OaaUWkrbsA8Gv4tiqxMDfg.png" /></figure><p>This results in a URL containing an authentication code we provide to the candidate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*TNnAeW39T8tPrNSGAsAyBA.png" /></figure><p>When the candidate goes to that URL, they are presented with a form asking them for their GitHub username and letting them know their 72 hours begins immediately once they submit. This URL is valid for 30 days, so the candidate can start immediately, the next weekend, or anytime in the coming weeks — whatever works for their schedule.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QBK8LtiQxEIzrndK9p3cJQ.png" /></figure><p>Once they submit, CodeBnb automatically clones the template repository into one specific for the candidate. (Both the template and the candidate’s repo are private, because we don’t want candidates to be able to start thinking about the assignment before their window begins.) CodeBnb uses the GitHub API to grant the candidate external collaborator write access to the repo. Doing so causes GitHub to send the candidate an email notification (and a <a href="https://github.com/notifications">GitHub notification</a>) but we had a few candidates who didn’t see either of those so it also provides a link directly to the repo in the confirmation page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3BU3js9gTy_bwf7YGwMQ0g.png" /></figure><p>After the 72 hour window elapses, CodeBnb automatically removes access, and emails us to let us know the candidate’s repo is ready for review.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*7ga-twqnGbqyMYHkfVuZ8w.png" /></figure><p>We review the assignment and inform the candidate of our decision one way or another. CodeBnb isn’t quite done yet, though. After 30 days, it goes in and archives the candidate’s repo into a centralized archive repo. It does this by copying the contents of a candidate’s repo into a candidate-specific folder. All folders are grouped by the assignment, to make it easy to see all candidates who did a given project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/1*Yo8KvhoreBujGOQRre3qqA.png" /></figure><p>For candidates who do not start the project, there’s a CodeBnb notification for that as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*puWXkANSq-sde86fUCIASw.png" /></figure><h3>Future Features</h3><p>CodeBnb is an open source project and we welcome contributions.</p><p>We’d love to have dynamic GitHub seat management. If the GitHub account needs another seat when CodeBnb needs to grant collaborator access, it should provision another seat automatically (and remember to de-provision it after the window).</p><p>CodeBnb currently uses a Google Drive Spreadsheet to track candidates and repositories; this works well for small numbers of candidates and has a huge benefit in that it is easy to read for humans. As we use CodeBnb more extensively, we’ll need to think about changing the data store to something more robust.</p><p>We also have <a href="https://github.com/builtforme/CodeBnb/issues">filed a few issues in CodeBnb</a> around adding unit tests and providing an AWS CloudFormation template to help others set up and configure CodeBnb.</p><blockquote>We hope you found this interesting. If you’d like to give CodeBnb a try for your hiring needs, please do and feel free to reach out if you need any help! If you’d like to experience CodeBnb from the candidate perspective, <a href="https://angel.co/builtforme/jobs">we’re hiring</a>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b454c655eca5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/built-for-me/introducing-codebnb-b454c655eca5">Introducing CodeBnb</a> was originally published in <a href="https://medium.com/built-for-me">Built For Me</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2018 Winter Olympic Events]]></title>
            <link>https://medium.com/@furchin/2018-winter-olympic-events-cd30e672608e?source=rss-37ac2f09110------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd30e672608e</guid>
            <category><![CDATA[pyeongchang2018]]></category>
            <category><![CDATA[olympics]]></category>
            <category><![CDATA[skiing]]></category>
            <category><![CDATA[winter-olympics]]></category>
            <dc:creator><![CDATA[Michal]]></dc:creator>
            <pubDate>Tue, 13 Feb 2018 18:52:58 GMT</pubDate>
            <atom:updated>2018-02-13T18:56:05.649Z</atom:updated>
            <content:encoded><![CDATA[<p>I wanted a list of sports <em>and</em> individual events, and couldn’t find a concise one. Here you go.</p><p><strong>Alpine Skiing</strong></p><ol><li>Men’s downhill</li><li>Men’s slalom</li><li>Men’s giant slalom</li><li>Men’s combined</li><li>Men’s super-G</li><li>Women’s downhill</li><li>Women’s slalom</li><li>Women’s giant slalom</li><li>Women’s combined</li><li>Women’s super-G</li><li>Team event</li></ol><p><strong>Biathlon</strong></p><ol><li>Women’s 7.5km sprint</li><li>Men’s 10km sprint</li><li>Women’s 10km pursuit</li><li>Men’s 12.5km pursuit</li><li>Women’s 15km individual</li><li>Men’s 20km individual</li><li>Women’s 12.5km mass start</li><li>Men’s 15km mass start</li><li>Mixed 2km x 6km / 2km x 7.5km relay</li><li>Women’s 4km x 6km relay</li><li>Men’s 4km x 7.5km relay</li></ol><p><strong>Bobsled</strong></p><ol><li>Two-man</li><li>Four-man</li><li>Two-woman</li></ol><p><strong>Cross-country skiing</strong></p><ol><li>Women’s skiathlon</li><li>Men’s skiathlon</li><li>Men’s &amp; women’s individual sprint qualification classical</li><li>Men’s &amp; women’s individual sprint finals classical</li><li>Women’s 10km freestyle</li><li>Men’s 15km freestyle</li><li>Women’s 4km x 5km relay</li><li>Men’s 4km x 10km relay</li><li>Women’s team sprint freestyle</li><li>Men’s team sprint freestyle</li><li>Men’s 50km mass start classical</li><li>Women’s 30km mass start classical</li></ol><p><strong>Curling</strong></p><ol><li>Men’s</li><li>Women’s</li><li>Mixed doubles</li></ol><p><strong>Figure Skating</strong></p><ol><li>Men’s singles</li><li>Ladies’ singles</li><li>Pair skating</li><li>Ice dancing</li><li>Team</li></ol><p><strong>Freestyle Skiing</strong></p><ol><li>Men’s aerials</li><li>Men’s halfpipe</li><li>Men’s moguls</li><li>Men’s slopestyle</li><li>Men’s ski cross</li><li>Women’s aerials</li><li>Women’s halfpipe</li><li>Women’s moguls</li><li>Women’s slopestyle</li><li>Women’s ski cross</li></ol><p><strong>Hockey</strong></p><ol><li>Men’s</li><li>Women’s</li></ol><p><strong>Luge</strong></p><ol><li>Men’s singles</li><li>Women’s singles</li><li>Doubles</li><li>Team relay</li></ol><p><strong>Nordic Combined</strong></p><ol><li>Individual large hill/10km</li><li>Individual normal hill/10km</li><li>Team large hill/4km x 5km</li></ol><p><strong>Short Track Speed Skating</strong></p><ol><li>Men’s 500 metres</li><li>Men’s 1,000 metres</li><li>Men’s 1,500 metres</li><li>Men’s 5,000 metres</li><li>Women’s 500 metres</li><li>Women’s 1,000 metres</li><li>Women’s 1,500 metres</li><li>Women’s 3,000 metres</li></ol><p><strong>Skeleton</strong></p><ol><li>Men’s</li><li>Women’s</li></ol><p><strong>Ski Jumping</strong></p><ol><li>Normal hill individual</li><li>Large hill individual</li><li>Large hill team</li><li>Women’s</li></ol><p><strong>Snowboarding</strong></p><ol><li>Men’s parallel giant slalom</li><li>Men’s halfpipe</li><li>Men’s big air</li><li>Men’s slopestyle</li><li>Men’s snowboard cross</li><li>Women’s parallel giant slalom</li><li>Women’s halfpipe</li><li>Women’s big air</li><li>Women’s slopestyle</li><li>Women’s snowboard cross</li></ol><p><strong>Speed Skating</strong></p><ol><li>Men’s 500 metres</li><li>Men’s 1,000 metres</li><li>Men’s 1,500 metres</li><li>Men’s 5,000 metres</li><li>Men’s 10,000 metres</li><li>Men’s mass start</li><li>Men’s team pursuit</li><li>Women’s 500 metres</li><li>Women’s 1,000 metres</li><li>Women’s 1,500 metres</li><li>Women’s 3,000 metres</li><li>Women’s 5,000 metres</li><li>Women’s mass start</li><li>Women’s team pursuit</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd30e672608e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Analyzing a Hiring Process]]></title>
            <link>https://medium.com/built-for-me/analyzing-a-hiring-process-217f0c71faf4?source=rss-37ac2f09110------2</link>
            <guid isPermaLink="false">https://medium.com/p/217f0c71faf4</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Michal]]></dc:creator>
            <pubDate>Mon, 27 Nov 2017 18:59:48 GMT</pubDate>
            <atom:updated>2017-11-27T18:59:48.401Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VXA73wVSv3fOZprqPj-uAA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/fw7lR3ibfpU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dawid Małecki</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>A few months ago <a href="https://blog.builtforme.tech/designing-a-hiring-process-adf311d16b2c?">we wrote about designing our hiring process</a>. We can look back and see how that process is working for us — and for our candidates.</p><p>We’re using AngelList as our Applicant Tracking System. It could be better but it does the job much better than a Trello board and it’s free for us and for our applicants. We have several stages — actually we have a <em>lot</em> of stages, more than is visible in the 4-stage hiring process.</p><p>The first stage is <strong>Applied</strong> which everyone gets into as soon as they apply. We do a very superficial scan of the candidate, mostly checking to see that a candidate i) is authorized to work in the US, ii) has 5 years of experience and iii) has a college degree. (These are the two objectively quantifiable <a href="https://blog.builtforme.tech/anatomy-of-a-job-description-7b41e4132669">required qualifications</a>, plus a legal requirement.) We decline 47% of applicants at this point, and the rest move to the Review stage.</p><blockquote>When we decline a candidate — at any stage — we always send them an email letting them know we won’t proceed further in the interview process. We want everyone to know where they stand, and we believe bad news is better than no news.</blockquote><p>On a weekly cadence we’ll do a résumé review of all candidates in the <strong>Review</strong> stage. During this process we’ll dive a little bit deeper into the candidate: we’ll read their résumé, often look at GitHub and LinkedIn and any other links in their profile on AngelList. We’ll determine whether the candidate is likely to be a match for us based on their experience and background. We decline 36% of candidates who made it this far.</p><p>From here we move the candidate to a <strong>Matched</strong> step and send them a brief email pointing them to our hiring process, pointing out a project comes next, and asking if they’d like to proceed. 47% of candidates choose not to.</p><p>Once a candidate confirms they are interested in the software engineering project, we use <a href="https://github.com/builtforme/CodeBnb">CodeBnb</a> to handle the project. (We’ll be blogging about CodeBnb soon.) We give the candidate a CodeBnb link and they have a month to complete the project. Once they have the link and until they’ve completed the project, we move them into a <strong>Project Scheduled</strong> stage for tracking. 31% of candidates to whom we offer the project choose not to start.</p><blockquote>In almost all cases in <strong>Matched</strong> and <strong>Project Scheduled </strong>it is the candidate who is choosing to opt out, sometimes letting us know, and sometimes simply ghosting.</blockquote><p>Once the project is completed, we move the candidate into the <strong>Project Completed</strong> stage and we evaluate the quality of their submission. Of the candidates who started the project, we decline to proceed with 55%. About a third of the candidates we decline fail to submit any code at all, a third provide an incomplete submission, and a third submit all the code they wrote but our evaluation of the project does not place it highly enough to continue with the hiring process.</p><p>All told, it is probably more interesting to provide pass/fail rates for each of the <a href="https://blog.builtforme.tech/designing-a-hiring-process-adf311d16b2c">four steps that are externally visible in our hiring process</a>.</p><h4>Step 1: Résumé Review</h4><p>100% of candidates make it to this step, and 66% do not make it to the next step.</p><h4>Step 2: Software Assignment</h4><p>34% of all candidates make it to this step, and 83% do not make it to the next step.</p><h4>Step 3: Culture Call</h4><p>6% of all candidates make it to this step, and 100% do not make it to the next step. You read that correctly: we haven’t found who we’re looking for. Could it be you? <a href="http://angel.co/builtforme/jobs">We’re hiring.</a></p><blockquote>If you’re someone who has a hiring process that’s similar to ours, we’d love to hear from you in the comments.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=217f0c71faf4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/built-for-me/analyzing-a-hiring-process-217f0c71faf4">Analyzing a Hiring Process</a> was originally published in <a href="https://medium.com/built-for-me">Built For Me</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Effective Is A Résumé Review?]]></title>
            <link>https://medium.com/built-for-me/how-effective-is-a-r%C3%A9sum%C3%A9-review-3b2771c85267?source=rss-37ac2f09110------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b2771c85267</guid>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[a-b-testing]]></category>
            <category><![CDATA[resume]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Michal]]></dc:creator>
            <pubDate>Mon, 13 Nov 2017 22:37:51 GMT</pubDate>
            <atom:updated>2017-12-07T18:46:30.245Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c2K4azlI_PbDOxkucBkAUA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/SQM0sS0htzw?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Raquel Martínez</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I’ll be honest: I wasn’t sure how to tell if a résumé was good or not. Actually I do know how to tell if a résumé is <em>not</em> good, but I didn’t know how important the résumé is as a predictor of interview success. If I reject someone because of a typo on the résumé will I be passing up the most qualified candidate? Don’t people make mistakes all the time? What if it just happened to the most qualified applicant? Or any number of other things: there are grammatical mistakes, spelling errors, general formatting. And then there’s experience. Oh boy is there experience. Not only which companies, or how long, or when, but what projects, achievements, and even <em>how</em> the information is presented — does the candidate work with a team? — are they claiming others’ work as their own? — is there measurable evidence provided? There’s also the “intro note” candidates need to type in AngelList to apply (which ranges from “i lik money” to a well written cover letter). Do these things matter? A résumé is a (virtual) piece of paper (and in many cases, a single piece at that). Is it possible to predict job performance based on a piece of paper with 1,000 words? If not, is it possible to at least predict <em>interview performance?</em></p><p>We set out to answer this question. During the résumé review we have a few minutes to make a decision one way or another. We don’t want to pass up a great candidate by rejecting someone without even talking to them, getting to know them, hearing what they have to say or think, and yet the odds are <a href="https://blog.builtforme.tech/analyzing-a-hiring-process-217f0c71faf4">exceedingly small</a> that the résumé I happen to have in front of me is our next hire. We have to prioritize our time appropriately.</p><h4>Applying a Data-Driven Approach</h4><p>During our résumé reviews, we look at résumés together as a team. Irrespective of the attributes each of us was indexing on, we weren’t sure if we were correctly determining résumé quality. So we decided to run an A/B test. We randomly selected applicants to be part of an experiment: the résumé review proceeded as normal, and when we deemed a résumé to be rejected, we instead advanced the candidate to the <a href="https://blog.builtforme.tech/designing-a-hiring-process-adf311d16b2c">next step of our hiring process</a>.</p><blockquote>60% of the candidates in the test would have been rejected without the test, but instead were advanced to the software engineering project.</blockquote><blockquote>40% of the candidates in the test would have been advanced to the software engineering project without the test, and were.</blockquote><h4>Methodology</h4><p>We tracked our initial impression (based solely on the résumé) and tracked the candidates’ performance through the hiring process. We deemed the résumé review <strong>a success if the initial impression predicted the outcome of the software engineering project</strong>. In other words, if the review was positive and the candidate was invited to the culture call or if the review was negative and the candidate was not invited to the culture call.</p><h4>Results</h4><p>Our résumé review <strong>predicted 78% of outcomes correctly</strong>. In the remaining 22% of cases, it was completely false positive: in other words if the résumé review predicted a negative outcome, that prediction was correct 100% of the time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b2771c85267" width="1" height="1" alt=""><hr><p><a href="https://medium.com/built-for-me/how-effective-is-a-r%C3%A9sum%C3%A9-review-3b2771c85267">How Effective Is A Résumé Review?</a> was originally published in <a href="https://medium.com/built-for-me">Built For Me</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>