<?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 Jim England on Medium]]></title>
        <description><![CDATA[Stories by Jim England on Medium]]></description>
        <link>https://medium.com/@JimEngland?source=rss-13bd72dfbd00------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*FkW9AeoTOL3Ixg0J3jWUPg.jpeg</url>
            <title>Stories by Jim England on Medium</title>
            <link>https://medium.com/@JimEngland?source=rss-13bd72dfbd00------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 15 Nov 2026 05:37:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@JimEngland/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[What to look for in a product designer]]></title>
            <link>https://medium.com/@JimEngland/what-to-look-for-in-a-product-designer-e14adeac3c17?source=rss-13bd72dfbd00------2</link>
            <guid isPermaLink="false">https://medium.com/p/e14adeac3c17</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Jim England]]></dc:creator>
            <pubDate>Wed, 27 Jan 2016 15:09:37 GMT</pubDate>
            <atom:updated>2016-01-29T15:51:17.514Z</atom:updated>
            <content:encoded><![CDATA[<p>One of my proudest accomplishments at Quirky was our ability to recruit an amazing team of designers and developers. One year into my employment at Quirky, we had quadrupled the team size and significantly raised the bar for success, injecting fresh thinking and industry experience into a startup yearning to transition into a software technology company.</p><p>We were able to accomplish this by becoming organized during the selection process and very specific in what we were looking for.</p><p>For the product designer role in particular, we identified characteristics and traits of the most successful product designers currently on the team and used those to build a framework for future hires. We identified 10 main attributes of a successful product designer; candidates were rated in each category on a four star scale. Each interview session had a focus on a high level category: Product, Design &amp; Interaction, or Implementation.</p><p>This template is for a generic product designer role and can be used in a variety of circumstances. However, I’d recommend adding in a few specific questions relevant to your startup to ensure the candidate did their homework prior to the interview.</p><h3><strong>Product</strong></h3><p>The best product designers are empathetic, obsessive, and pragmatic when working with a team to build products.</p><h4><strong>Empathetic</strong> — Able to strongly comprehend the goals of users. Can understand the motivations, abilities, and triggers that get them to complete tasks.</h4><ul><li>Discuss the personas for a product you’ve worked on. What were their wants and needs? What were their motivations?</li><li>How did you identify the top personas for something you work on? How did the personas change over time?</li><li>Describe the behavioral model (motivation, ability, trigger) for a persona for a product you’ve worked on. What hypotheses did you have to improve the motivation or ability of a user using your products? What were the results?</li><li>How would you establish the personas for our product?</li></ul><h4><strong>Obsessive</strong> — Wants to know every nitty gritty detail about how a product works. Craves intimate knowledge of the entire system and how every relevant party interacts with that system. Is curious and explores other products.</h4><ul><li>Discuss a product you love in detail. What are the strongest pieces of the product and why? What are the weakest areas? What would you improve?</li><li>Discuss a product you’ve worked on in detail. What was the situation of the product when you started? What changed over time? What was something that was counterintuitive on the product that surprised you and would surprise outsiders on how the product was used?</li><li>Describe the data model for a product you’ve worked on in the past.</li></ul><h4><strong>Pragmatic</strong> — Handles problems during development with poise. Can modify features to reduce engineering complexity while still achieving benefits to users.</h4><ul><li>Describe a time where a product had to change due to technical constraints. How did you determine what changed?</li><li>What are the best characteristics for a developer to have in order to work well with you?</li><li>Describe a time in which you had difficulty working with another team member. How did you resolve the issue?</li></ul><h3><strong>Design / Interaction</strong></h3><p>The best design is consistent, elegant, data-driven, and visually-inclined.</p><h4><strong>Consistent</strong> — Applies best practices whenever appropriate and does not try to reinvent the wheel.</h4><ul><li>What design framework have you used in the past (either internal or open source)? What modifications did you make to the framework?</li><li>Go through a product they have worked on in the past. Note common UI elements and talk about them. Note unique UI elements and talk about them.</li></ul><h4><strong>Elegant</strong> — Crafts experiences that make the complex and confusing the simple and understandable.</h4><ul><li>Find a complicated interaction in a less-than-stellar product. Work together on the whiteboard to try and simplify it and improve it.</li><li>Go through a flow on a product the interviewee has built in the past. Ask about their design decisions.</li><li>Go through the first time user experience of your current product. Ask them how they would improve it.</li></ul><h4><strong>Data-Driven</strong> — Uses data to inform design decisions.</h4><ul><li>Describe the top metrics you tracked for for a product you’ve worked on. Why were these the most important metrics?</li><li>How did the design of your last product change based on data?</li><li>Describe an A/B test you ran on a product. Why was it run? What was the result?</li><li>What user behaviors should our product be tracking?</li></ul><h4><strong>Visually-Inclined</strong> — Crafts experiences that align directly with the goals of the Creative team through both aesthetics and voice.</h4><ul><li>What are the best design brands in your opinion? Why are they your favorite?</li><li>Show me your proudest visual work. What makes it your favorite portfolio piece?</li></ul><h3><strong>Implementation</strong></h3><p>The best product designers can get things accomplished. They are proactive, resourceful, and accomplished.</p><h4><strong>Proactive </strong>— Initiate changes rather than reacting to events.</h4><ul><li>At your last job, what impact did you make outside of your core day-to-day responsibilities?</li><li>Walk me through a time you had to fight a fire or resolve an issue quickly. How did you resolve the issue? What did you do to prevent it from happening ever again?</li></ul><h4><strong>Resourceful </strong>— Has the technical abilities to deliver a product successfully or the resourcefulness to get the developer everything they need to ship a killer product.</h4><ul><li>What is your technical background?</li><li>What is something you wish you knew more about from a technical perspective?</li><li>In your last position, how did you track what a developer was working on? How did you help that developer?</li></ul><h4><strong>Accomplished</strong> — Takes products over the finish line. Does not rest until the best possible implementation of the product is delivered.</h4><ul><li>Walk me through the time you led a project from start to finish. How did you measure success? How did the project turn out? Why?</li><li>How have you communicated product releases in the past with both internal and external stakeholders? Is this important to you? Why?</li></ul><p>This template helped us find excellent product designers and I hope it helps you too.</p><p>Shout outs to the design team at Quirky that built this framework: <a href="http://ryanscherf.net/">Ryan Scherf</a>, <a href="http://thecodecampus.com/">Raj Sidhu</a>, <a href="http://hello.anthonytadina.com/">Anthony Tadina</a>, <a href="http://verygreyc.com/">Grace Varga</a>, and <a href="https://twitter.com/stevenwalker">Steven Walker</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e14adeac3c17" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>