<?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 Ilana Sufrin on Medium]]></title>
        <description><![CDATA[Stories by Ilana Sufrin on Medium]]></description>
        <link>https://medium.com/@ilanasufrin?source=rss-5b38c64681d5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ot1CYNk5sITSLzkMpU8HeQ.jpeg</url>
            <title>Stories by Ilana Sufrin on Medium</title>
            <link>https://medium.com/@ilanasufrin?source=rss-5b38c64681d5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:44:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ilanasufrin/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[Hiring Manager Strategies for Closing Software Engineering Candidates]]></title>
            <link>https://medium.com/@ilanasufrin/hiring-manager-strategies-for-closing-software-engineering-candidates-192c18e4a1b8?source=rss-5b38c64681d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/192c18e4a1b8</guid>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[pitching]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Ilana Sufrin]]></dc:creator>
            <pubDate>Tue, 22 Feb 2022 18:02:54 GMT</pubDate>
            <atom:updated>2022-02-22T18:02:54.121Z</atom:updated>
            <content:encoded><![CDATA[<p>We’ve all seen the recent articles about how the market for hiring software engineers has gotten more competitive. Once a candidate passes your interview process, how do you convince them to accept your offer when you’re not the highest bidder?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L821P5VReAzYuPaQ5daN8w.png" /></figure><p>Hiring managers often have a chance to pitch the role and the company during one last phone call. You can use the information that the candidate gave you during the interview process (specifically about why they’re looking to leave their current company, and what they’re looking for in their next role) to figure out what’s most important to them. Your pitch is more likely to resonate if you tailor your message to the individual.</p><p>Here are 3 strategies for highlighting why the candidate should choose you.</p><p>1. For candidates who say they want to work on impactful projects: <strong>Draw a direct line between the work they’ll be doing and the company’s mission</strong></p><p>Candidates who are looking for a chance to demonstrate impact will appreciate you emphasizing how the role is highly visible or important to the company’s goals. They won’t have to struggle to find visible projects once they join your company. It also may be helpful to draw attention to your department’s strong leadership, because if the company strategy changes, the candidate can rest assured that they can trust their leadership team to figure out a new approach.</p><p><em>Caveat: Don’t inflate or exaggerate the work they’ll be doing, or else they’ll be quick to leave your team once they join your company if there’s an expectation mismatch.</em></p><p>2. For ambitious candidates, or candidates who say they’re leaving due to a lack of growth- <strong>Show that you have a plan for their growth</strong></p><p>The candidate may be accepting a role on your team in the short term, but they’re also putting themselves at the mercy of your company’s promotion process, if they plan on staying for the medium and long term. Promotions can be multi-year endeavors, especially at bigger companies, but talking to the candidate about their career aspirations (and how you’ll help them get there) shows that you have a plan for their growth.</p><p><em>Caveat: once they join your team, you’ll have to execute on this plan, or else you’ll have an attrition problem 😉.</em></p><p>3. For candidates who are leaving because of their managers, or who say they want to have a personal connection with their managers:<strong> Reference something they did especially well in the interview</strong></p><p>Telling the candidate why you specifically want to hire them shows that you’re paying attention to their strengths early in your working relationship. If you can connect with them on a personal level by referencing what you think they’ll specifically bring to the role, it will demonstrate that you’re as excited to work with them as they are to work with you. You can also tell them what they <em>didn’t</em> do well in the interview and explain how taking the role will help them fill those gaps, and why you want them anyway.</p><p><em>Caveat: This strategy takes slightly more work than the others because it requires gathering information from your interview team. In my opinion a personal connection is always worth the effort!</em></p><p>Sometimes the best pitch is actually a combination of multiple strategies. And sometimes the candidate can’t be convinced, and is only looking to go to the company that will pay them the most. But if you don’t have the most competitive offer monetarily, highlighting that you can offer something <em>else</em> can be equally compelling!</p><p>Who knew that engineering manager jobs were secretly sales jobs?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=192c18e4a1b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When should a software engineer switch into management?]]></title>
            <link>https://medium.com/@ilanasufrin/when-should-a-software-engineer-switch-into-management-a5c9e044ef87?source=rss-5b38c64681d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5c9e044ef87</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Ilana Sufrin]]></dc:creator>
            <pubDate>Mon, 31 Jan 2022 17:20:01 GMT</pubDate>
            <atom:updated>2022-01-31T17:20:01.383Z</atom:updated>
            <content:encoded><![CDATA[<p>A lot of talented management bloggers before me have focused on <em>who</em> should make the transition to engineering management, and <em>what</em> that job entails, and <em>how</em> to be successful once you’ve made the switch. But recently a team member came to me with a different spin on the question: if you already know that management is for you, <strong><em>when</em></strong> should you make the switch from software engineer to manager?</p><p>To help answer this question, your level of interest in programming is actually a more useful indicator than your level of interest in management.</p><h3>The case for waiting</h3><p>A good rule of thumb is to at least make it to the level of Senior Engineer before switching. Even if you already know that management is your intended career path, there are still many reasons why I recommend waiting as long as you possibly can before making the transition.</p><p>Once you give up your primarily technical job, and stop coding on a daily or even weekly basis, it’s exceedingly difficult to keep your technical knowledge up-to-date. If you stopped writing JavaScript during the jQuery days, it’s certainly <em>possible</em> to keep up with different ways to manage state with React, but you won’t have the benefit of personally trying out different technologies in your day job.</p><p>Some people may find the distance from hands-on technical work to be appealing! Countless articles have focused on how managers make meaningful impact without writing code. But unless all of your future management roles are purely people-focused (every company and team has different expectations for this), you’ll still be expected to keep your technical knowledge relatively current. At the minimum, you must be able to speak with engineers intelligently about technical decisions, and communicate those decisions to other managers.</p><p>Furthermore, many companies still give engineering managers technical interviews. So once it comes time to find your next role, it’s very likely that you’ll at least have a systems design round, and often companies will ask data structures and algorithm questions. Prepping for these interviews becomes infinitely more challenging when you haven’t written a line of code in years. The more years you have under your belt as a programmer before you make the switch to management, the more solid your technical foundation will be for the rest of your career, to help minimize the amount of “brushing up” you’ll need to do.</p><p>Coding to management can be a one-way street (although my current employer, Etsy, allows people to switch back and forth). If your programming skills atrophy, it’s very difficult to switch back into a technical role to deepen your knowledge if you find yourself coming up short. That’s why it’s in your best interest to make sure you’re ready before making the switch.</p><h3>But don’t wait too long</h3><p>On the other hand, management is a different skillset than programming. I’ve heard from many folks that they have no interest in being a senior engineer, because they’re more passionate about people than code. Some programmers who would be <em>excellent</em> managers take a very long time to get promoted to Senior Engineer, because they either don’t have the interest or the aptitude to develop their technical skills beyond a certain point.</p><p>After a few years spent learning the basics, every year spent on the “wrong” side of the IC/management divide is a year that you’re not practicing the craft of management. Additionally, opportunities to transition to management can be few and far between, so if you decline an opportunity because it’s too early, you may not get another chance for a long time. If you’re <strong>sure</strong> that you’re no longer interested in hands-on programming, you should seize the first chance to transition that presents itself to you. After all, at some companies, engineering managers don’t even come from technical backgrounds. If you’ve spent <em>any</em> time as a software engineer, you have more context than engineering managers who were previously Product Managers or Technical Program Managers.</p><h3>So, what should I do?</h3><p>Obviously the choice is very personal, and is highly dependent on the opportunities in front of you. But if I have to make a recommendation: even if you’re very interested in management, wait until your technical skills are as developed as you <em>ever</em> foresee yourself wanting them to be. Once you’re sure that you’ve lost interest in programming, at that point, take the first reasonable opportunity to switch into management that presents itself.</p><p>If you have questions, or disagree with me entirely, feel free to leave a comment or get in touch! I’m curious how long all of you waited before making the switch, and if you’d do anything differently today?</p><p>P.S. If I’m really being pressured to give an absolute number, I made the switch to management after 5 or 6 years of working as an engineer. Retrospectively, I would say that’s on the early end, but not unreasonably so.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5c9e044ef87" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 meeting ideas to keep WFH human]]></title>
            <link>https://medium.com/@ilanasufrin/5-meeting-ideas-to-keep-wfh-human-76c254494ac4?source=rss-5b38c64681d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/76c254494ac4</guid>
            <category><![CDATA[team]]></category>
            <category><![CDATA[distributed-teams]]></category>
            <category><![CDATA[happy-hour]]></category>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[wfh]]></category>
            <dc:creator><![CDATA[Ilana Sufrin]]></dc:creator>
            <pubDate>Fri, 07 Jan 2022 22:10:57 GMT</pubDate>
            <atom:updated>2022-01-07T22:10:57.170Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re on one of the many teams that became virtual (or was newly formed) during the pandemic, you may be searching for new ways to connect with your teammates. My team, the <a href="https://www.etsy.com/impact">Impact Shopping squad</a>, practices these 5 creative ideas for keeping a distributed team engaged and in-sync. After all, you can only play Among Us so many times.</p><h3>Get To Know Your Team</h3><p>Cadence: Every 2 weeks</p><p>My team’s designer borrowed this idea from his previous team at Pinterest, and it’s become my team’s favorite ritual. Each sprint, one person on the team prepares and delivers a short presentation about their lives. We’ve seen this prompt interpreted many different ways- one team member told their life story via a series of emojis, another person showed us some of the recent text messages on their phone, and most people default to showing their embarrassing childhood photos. This is a low-pressure way for the team to bond and practice public speaking.</p><h3>Speedback</h3><p>Cadence: Once per quarter</p><p>Borrowed from <a href="https://medium.com/@joshproduct/speedback-de-stigmatise-feedback-with-speed-dating-principles-4708d493fb63">Josh Richardson at HeadBox</a>, this meeting is essentially speed-dating for feedback. Every member of the team takes turns chatting with every other member in private virtual meeting rooms. The pairs give each other brief feedback, both positive and constructive. In the worst case, if the pair can’t fill the time with feedback, they just chat and get to know each other.</p><h3>Team Norming</h3><p>Cadence: Once per year</p><p>The team manager prepares a series of slides in Google Drawings, which have a line drawn horizontally through them. The line is a spectrum, and on each side of the line, words that represent opposite working styles are written. Some examples are “I work best early in the day vs I work best late in the day”, “I prefer speed vs I prefer thoroughness”, and “I prefer to juggle many tasks vs I prefer to focus on one task”.<br>Team members graph themselves on the spectrums, and discuss possible compromises and behaviors that work for everyone.</p><h3>Unhappy Hour</h3><p>Cadence: Whenever the team needs it</p><p>This is a twist on the classic Happy Hours that many distributed teams practice. In this version, everyone gets on a video call and complains until they feel better.</p><p>There are two rules: 1) everyone must share at least one complaint, so that others feel comfortable opening up, and 2) whatever is said in Unhappy Hour stays in Unhappy Hour.</p><h3>Happy Hour</h3><p>Cadence: Once per month</p><p>Our team does happy hours too! Our favorite activity recently is filling in this <a href="https://www.sporcle.com/games/mhershfield/ive-got-a-blank-map-baby">blank map of the United States</a>. One team member (the “driver”) opens up the map and shares their screen, while the others direct the driver to click on portions of the map. It’s more fun than it sounds, we promise!<br>Other honorable mention games are <a href="https://swellgarfo.com/scattergories/">Scattergories</a>, <a href="https://www.powerlanguage.co.uk/wordle/">Worldle</a>, and <a href="https://play.howstuffworks.com/quiz/how-many-crafting-tools-can-you-name">more</a> <a href="https://www.sporcle.com/">quizzes</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76c254494ac4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips and Tricks for Working with React Native]]></title>
            <link>https://medium.com/@ilanasufrin/tips-and-tricks-for-working-with-react-native-8ed6b6a82243?source=rss-5b38c64681d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ed6b6a82243</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Ilana Sufrin]]></dc:creator>
            <pubDate>Thu, 04 Feb 2016 16:58:42 GMT</pubDate>
            <atom:updated>2016-02-04T16:58:42.207Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post serves as an expanded edition of a </em><a href="https://youtu.be/XFQnRlkWl80?t=1122"><em>talk</em></a><em> my team gave at a meetup with the </em><a href="http://www.meetup.com/NYC-Javascript-React-Group/"><em>NYC JavaScript React Group</em></a><em>.</em></p><p>React Native is an exciting new framework for building native applications, but of course with anything new there is a learning curve. We wanted to share the lessons we learned while developing our company’s first native app, <a href="http://r.thisam.co/Medium">ThisAM</a>, utilizing React Native.</p><p>When our company, Refinery29, a lifestyle digital media company, decided to make its first native app back in mid 2015, we thought it was a cool opportunity to explore something that was brewing in the developer community.</p><p>In January 2015, Facebook released React Native, a JavaScript framework for creating native applications for both iOS and Android. The possibility of being able to build a native app utilizing the same skills and language we’ve already honed to create our web experiences was intriguing.</p><p>Furthermore, the app itself, ThisAM, is a great candidate for this new approach as it is designed to be very minimalist. ThisAM is a simple daily rundown of everything you need to start off your day with a fresh editorial eye. It’s simple, beautiful, and parses down the essential news of the day in a delightful way. <a href="https://itunes.apple.com/us/app/refinery29-8-things-to-know/id988472315?mt=8">Download the app here to see if you agree.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*609ch-P3KIzamIOMiwjT_A.png" /><figcaption>ThisAM’s landing page</figcaption></figure><p>But not everything went smoothly. It would have been awesome to work with an established framework, with polished versions, using tricks and tips from the community that were well-documented. Instead, we were facing a situation where a new stable version was released every two week or so, for a framework that was only recently established (React.js — 2013, React Native -2015), and with a community that has different priorities than we do.</p><p>We still believe that React Native is the future of native app development. If you are a developer and are interested in learning how to work in React Native while it is still getting its sea legs, here is a rundown of our most important learnings.</p><ul><li>We’ve had to scale down our Google Analytics expectations over the course of building ThisAM. We started by forking <a href="https://github.com/lwansbrough/react-native-google-analytics">React Native Google Analytics</a> in order to add support for custom dimensions. This worked really well for us until we realized that the returning users weren’t being recognized because the library’s getClientId() implementation was returning a new user ID every time. We’ve since solved this problem with the help of a library called <a href="https://github.com/rebeccahughes/react-native-device-info">React Native Device Info</a>. DeviceInfo.getUniqueID() generates a consistent, unique ID for each user and is currently the community-recommended solution for this problem.</li><li>When we first started development way back in July of 2015, we used <a href="https://github.com/mjohnston/react-native-webpack-server">React Native Webpack Server</a> instead of the default <a href="https://github.com/facebook/react-native/tree/master/packager">React Packager</a>. To make matters worse, we forked React Native Webpack Server. This turned out to be a mistake because RNWS was abandoned in favor of the default packager and we had to switch back when upgrading our React Native version. Bottom line: stick with the default React Packager.</li><li>In terms of testing, here’s where we landed. For the full rundown on tests, check out <a href="https://medium.com/@jcfrancisco/cea561df242b#.jltx03kwp">this post</a> from my colleague.<br><strong> — </strong><a href="https://facebook.github.io/jest/docs/tutorial-react.html"><strong>Jest</strong></a> for unit tests<br><a href="https://developer.xamarin.com/guides/testcloud/calabash/introduction-to-calabash/"><strong> — Calabash</strong></a> for feature tests<br> — Running both unit tests and feature tests in full on <a href="https://travis-ci.com/"><strong>Travis CI</strong></a></li><li>Don’t be shy about using third-party libraries, especially if you are more comfortable with JavaScript than Objective-C. Forking and building functionality yourself is out of the question if you want to continue to upgrade and take advantage of new features — not to mention community support.</li><li>Keep on eye on the <a href="http://www.reactnative.com/">community</a> and their <a href="https://github.com/facebook/react-native/releases">release notes</a>, and make sure to upvote or submit your requests on <a href="https://productpains.com/product/react-native/">Product Pains</a>. The more feedback we give contributors, the more they can “React” (hehe) to the needs of the community.</li></ul><p>In all, we are proud and excited to have built our app in React Native. We hope these tips can help you smooth out some of the rougher patches of utilizing an exciting new technology. You can also read more about my team’s <a href="https://medium.com/@benmidi/22e2f835f44b#.o781kmyt3">product</a> and <a href="https://medium.com/@jcfrancisco/cea561df242b#.fefix6f2s">testing</a> strategies if you’re interested.</p><p>Thanks for reading, and please contact me at ilana.sufrin@refinery29.com with any questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1012/1*cddjqmSQpa_lfQHEYyJEdg.png" /><figcaption>Sample screens from ThisAM</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ed6b6a82243" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>