<?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 pebble {code} on Medium]]></title>
        <description><![CDATA[Stories by pebble {code} on Medium]]></description>
        <link>https://medium.com/@pebblecode?source=rss-65e413ccf8b1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*6nvO9uKD2-cX2CZ8.png</url>
            <title>Stories by pebble {code} on Medium</title>
            <link>https://medium.com/@pebblecode?source=rss-65e413ccf8b1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:28:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pebblecode/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[Cloning our founders]]></title>
            <link>https://medium.com/@pebblecode/cloning-our-founders-bd49b95e74ef?source=rss-65e413ccf8b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd49b95e74ef</guid>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[growth-strategy]]></category>
            <dc:creator><![CDATA[pebble {code}]]></dc:creator>
            <pubDate>Thu, 16 Jul 2015 12:41:54 GMT</pubDate>
            <atom:updated>2015-08-26T15:17:34.060Z</atom:updated>
            <content:encoded><![CDATA[<p>pebble {code} recently had a big win; we appointed <a href="https://twitter.com/smecrownrep">Stephen Allott</a> as our Chairman, who is guiding us through the next phase of growth. The first steps to get us there, we need to free up our founders time to focus more on growth and strategy and less on client lead work.</p><blockquote>Our first quest: Find a clone of our founders.</blockquote><p>We created a new role for a Senior Technical Solutions Architect and started advertising this position on job boards, but compared to the other roles we were recruiting for, it has been a bit tricky finding the right person with the right experience we were looking for.</p><p>It became apparent that if we were to fill this role, we would have to actively find that person rather than wait for someone to find us.</p><h3>Finding people with a digital footprint</h3><p>We briefly flirted with the idea of finding people based on their digital presence. The assumption was that if we want to look for a clone of anyone, then we need to find someone who has a similar digital footprint. This would mean examining Github, Twitter, Blogs and references that to the individual online. There has been a lot of interest in this idea recently; with many startups hoping to disrupt the recruitment space, betting that this is “<a href="http://techcrunch.com/2015/06/16/ex-googlers-raise-6m-for-connectifier-an-ai-approach-to-recruitment-search/">The Future of Recruitment</a>”.</p><p>The assumptions were that Github would show us what a developer’s coding ability was like. Twitter would show us what kind of developer he/she is connected with and the type of discussions they are passionate about. Blogs would allow us a more qualitative look at the developer’s expertise, interest and network.</p><h3>Tearing our assumptions apart</h3><p>While there were a few developers who shared similar digital footprints with our founders, the people we assumed would have a similar footprint (a small selection of people on Linkedin who’s current titles were CTOs) often didn’t have the same level of activity or followers as our founders did. Examining people within our company revealed a similar pattern. Developers we knew to be excellent programmers within the company didn’t show a lot of activity on their accounts. A lot of the Github activity we were looking for were either not publicly available because they were private projects or because CTOs are no longer focusing on writing code anymore.</p><p>Twitter shared similar challenges. While it could be a great way to determine a person’s network and professional interest, this data would only be useful if the developer were actively using the platform.</p><p>Blogs are useful for getting a sense for persons thought process, but at this stage in time we are still working on identifying potential candidates so we will come back to this at a later time.</p><h3>Focusing on attributes</h3><p>Our Chairman had a slightly different take on this. He introduced a brainstorming technique he uses when he is looking to hire for a key role in a company. His method focuses on specific attributes of the person we are looking to hire.</p><p>This was broken down into the following categories:</p><p><strong>Capability</strong>: The kind of skills we were looking for</p><p><strong>Quality</strong>: How they have shown their capability</p><p><strong>Potential</strong>: What they would be able to do</p><p><strong>Experience</strong>: Time in a particular field or industry</p><p><strong>Strategy</strong>: How we identify and reach the people wanted to hire</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fX4PvkLQjuJvLWXV7DDmtw.jpeg" /><figcaption>We listed as many points as we could in each section and highlighted 3 of our most important criteria.</figcaption></figure><p>It was interesting to see where we overlapped and where we differed. It showed us how we had roughly the same idea of the person we were looking for, but highlighted that we all carried slightly different assumptions about what the perfect candidate would look like.</p><h3>Solving the right problem</h3><p>The brainstorming session gave us a different view of the type of person we wanted to hire and where we might find them. It placed emphasis on the attributes of the person we were looking to hire but still felt like we were jumping a little ahead of ourselves.</p><p>We needed to look at our hiring like any other business challenge and identify which problem actually needed solving.</p><p>We started with this:</p><blockquote>We need to free up our founders time so that he could focus on the growth and strategy.</blockquote><p>This was <strong>not a problem</strong>. This was <strong>a statement</strong>; a statement that doesn’t tell us why or how freeing the founders time would allow the business grow.</p><p>This lead us on a path to focus on a direct <strong>clone of our founders</strong>.</p><p>We then looked at:</p><blockquote>What part of our founders day to day activity was eating up most of their time?</blockquote><p>Our founders spent a lot of their time on client consulting and acting as a technology leads for client projects. This suggested that we needed to look at someone who has a developer background and also works directly with clients as a consultant.</p><p>We eventually arrived at the problem:</p><blockquote>What is the bottleneck for pebble {code} to grow and scale?</blockquote><p>To understand what’s going on, we needed to look at how pebble {code} as a business is structured, from sales and consulting to design and delivery. Drawing this out allowed us to see where our founders were currently positioned, what they were doing and identify where the bottleneck was.</p><blockquote>It seems we were not looking for a clone of our founders.</blockquote><p>We were actually looking for someone to take over the consulting role with our clients. We have a strong tech delivery team with capable Tech Leads leading the teams, which meant that it wasn’t necessary for this person to focus on both areas.</p><p>Going back to the takeaways from the brainstorming session, the capabilities and the quality of who were were looking for started to make a lot more sense. We were looking for a consultant who could help our clients solve the right problems. Someone who is not afraid to say “No” to clients when they are requesting something that does not help them solve the problem they have. We want someone who can work with our clients to get to what they need rather than what they want.</p><h3>Don’t be a dick</h3><p>Our Creative Director and resident brain scientist <a href="https://twitter.com/johnmildinhall">John Mildinhall</a> took the drawings further: He viewed the role of the consultant as a hub between the client and our team. For this hub to work well with our team, it’s important that:</p><blockquote>These people (our team members) don’t think that you are a dick</blockquote><p>A huge deal for us, and for the kind of business we want to build. In order to work effectively with our team, they have to know what they are talking about, what is feasible and speak in the same language as our team; they will have to have a development background.</p><p>pebble {code} was <em>“built by developers for developer”</em>. It’s one of the many reasons why pebble {code} is a great place to work; why we love what we do; and why we are good at it.</p><p>Hiring someone without this background<strong>*</strong> will take us to the <em>“people think you are a dick”</em> territory.</p><p><strong>*</strong> Jonny’s note: When we say “background”, we really <strong>don’t</strong> mean anything like your nationality / gender / race / religion / age. We want diversity with those! We simply want good people who understand tech, and are not dicks. No offence meant if you are a dick ;-)</p><h3>Where we are now</h3><p>With a clearer definition of what we were looking for, we are now working on a rewrite for the role we are hiring for. We are getting rid of the Senior Technical Solutions Architect role.</p><p>We are creating a new role at pebble {code}; a Lead Creative Technologist perhaps; we haven’t decided on the title just yet.</p><p>We are looking for someone:</p><p>less: Rockstar, Ninja and Unicorn.</p><p>More: Good person who is open minded.</p><p>Someone who was once a developer but now focuses more on the business side of things; someone who can help our clients identify the real problems they need to solve, work with them to create a solution, and can talk the same language as our developers.</p><p>We’re looking for a <a href="http://careers.stackoverflow.com/jobs/93026/lead-creative-technologist-pebble-code">Lead Creative Technologist</a></p><p>Does that sound like someone you know?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd49b95e74ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>