<?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 Adam Bossy-Mendoza on Medium]]></title>
        <description><![CDATA[Stories by Adam Bossy-Mendoza on Medium]]></description>
        <link>https://medium.com/@abossy?source=rss-dcc34fafb41f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*fdHl3YiBcKJwBvdO.jpeg</url>
            <title>Stories by Adam Bossy-Mendoza on Medium</title>
            <link>https://medium.com/@abossy?source=rss-dcc34fafb41f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:58:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abossy/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[Five Ways Patreon Supports Engineers Of All Backgrounds]]></title>
            <link>https://medium.com/art-work-behind-the-scenes-at-patreon/five-ways-patreon-supports-engineers-of-all-backgrounds-567eb0812576?source=rss-dcc34fafb41f------2</link>
            <guid isPermaLink="false">https://medium.com/p/567eb0812576</guid>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[patreon]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[patreon-engineering]]></category>
            <dc:creator><![CDATA[Adam Bossy-Mendoza]]></dc:creator>
            <pubDate>Tue, 28 Nov 2017 20:23:17 GMT</pubDate>
            <atom:updated>2017-11-28T21:42:47.509Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jM-EAD76CegagrU_WLbLMA.jpeg" /></figure><p>At Patreon, we strive to create an equitable workplace for people of all backgrounds. This forces us to challenge the norms and systems that have governed our society and industry for a long time. We have set forth the following policies and practices that help us work toward this goal in a meaningful way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/801/1*xDBe8893cFTBh_16HkApBg.png" /></figure><h3><strong>1. We’ve established a clear compensation policy in order to achieve pay equity.</strong></h3><p>I’m listing compensation first, because money and power are inextricably linked in our country. We know that there’s a pay gap that negatively affects people from underrepresented groups. Our compensation policy strives for fairness both internally and externally.</p><p>Our job levels serve as the foundation of our compensation policy. There are six levels in engineering, with one being the lowest and six being the highest. We have a document which describes the expectations and responsibilities of an engineer at each level, and we regularly reference and refine this document because of how much we depend on it. Accurately placing folks at the levels that are commensurate with their skill level is one of our biggest challenges. I touch upon how we calibrate folks across levels in the third point of this post.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sd2uoAUtiDNQJ7YG1U_nZw.png" /><figcaption>Just your classic engineering/product/design cross-team huddle</figcaption></figure><p>The compensation we offer all our teammates is determined by their job level within our organization. We leverage a person’s job level and job type (Engineering, HR, Data Science etc.) to gather their compensation target from a survey-based compensation tool called Option Impact, which aggregates the compensation and equity offerings of other startups in our industry and location.¹</p><p>Teammates of the same level receive approximately the same compensation, with only minor variations due to performance and proximity to reaching the next level. Our engineering leveling is consistent across functions, such as Infrastructure, Backend, Web, and Mobile. We review both cash and equity annually to ensure that folks are being compensated in accordance with their level and to safeguard against bias.</p><p>We hope that in doing this work, no two people get paid differently for doing the same work.</p><h3><strong>2. We strive for fairness when we seek to fill leadership roles and other opportunities.</strong></h3><p>Looking around at many tech companies, it’s clear that leadership roles aren’t proportionately distributed across people from a diverse set of backgrounds. We are careful to scrutinize our own decisions about who gets placed into which leadership roles. In engineering, formal leadership is generally available in two forms: management and product engineering lead positions (called PEL for shorthand).</p><p>Our engineering manager role is exactly what you would expect at any startup. It’s a permanent role that we hire directly into, and folks regard changing into this role as a significant career transition. We’ve made an effort to source a diverse candidate pool to ensure that we give a fair shot to individuals that aren’t commonly represented in engineering management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bCLBdMAD4uscT2o5gpwviw.jpeg" /><figcaption>Lyn, full stack engineer</figcaption></figure><p>The PEL role is similar to a technical product manager role at other startups. They change on a per-project or per-several-project basis. It isn’t an official title change; instead, the role is rotational and it’s a way of growing engineers as leaders at a faster rate than we open jobs. By making it rotational, it gives us the ability to consider a wide range of engineers for the role on an continual basis.</p><p>Leadership can also be demonstrated informally, by engineers that don’t possess a manager or PEL title. These opportunities — such as giving a presentation, providing technical leadership on a new architecture or tooling — arise often, and we are diligent in advocating for and supporting folks of all backgrounds that might benefit from these opportunities. We’re able to do this with the process I discuss in the next point.</p><h3><strong>3. We carefully calibrate our promotion criteria across the engineering org to achieve fairness and clarity of expectations about how to grow and advance.</strong></h3><p>For the past few quarters, engineering management has done a full review of each individual in our organization. We effectively answer these few questions:</p><ul><li><em>What is this person passionate about?</em></li><li><em>How do they want to grow?</em></li><li><em>What challenges should we be looking for for them?</em></li><li><em>How close are they to being promoted?</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YSBlseW8kiXmmU_pz9aDPw.jpeg" /></figure><p>This review has a bunch of benefits for everybody in engineering. It helps us:</p><ul><li><em>Find the right growth opportunities for the individuals in our organization</em></li><li><em>Set very clear expectations about what engineers should be doing to improve</em></li><li><em>Calibrate our promotion criteria across managers</em></li><li><em>Deeply incorporate our engineering levels guide into our conversation</em></li><li><em>Understand our levels guide’s strengths and weaknesses better, allowing us to iterate on it and make it better.</em></li></ul><p>In many organizations, management only talks about the people being put up for promotion. Patreon’s process of talking regularly about everyone allows us to challenge each other not just on who is getting promoted but who is not and why.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D5UIPTfxOcOZelfn5R0hUw.jpeg" /><figcaption>Erica and Val, engineering managers</figcaption></figure><h3><strong>4. We encourage and exemplify behaviors that foster a culture of inclusion.</strong></h3><p>It’s common knowledge that women are often interrupted by men in the workplace. A vast majority of our employees are excellent listeners and wait to take turns to speak. Additionally, it’s important to encourage participation in the first place. Meeting facilitators at Patreon regularly employ techniques to encourage participation from folks that might not get the chance to speak up. For instance, one engineering manager conducts group discussion by having everybody raise their hands to speak, and he explicitly invites others who haven’t spoken yet to speak up. One engineer conducts meeting by soliciting everybody’s input one person at a time, and allowing for discussion after each comment.</p><p>Engineering leadership at Patreon frequently devises new ways in which we can help everybody’s voice be heard. This means questioning and re-evaluating how we conduct important meetings, like brainstorms or retrospectives. We strongly believe that the collective wisdom of every team outweighs the knowledge of any single individual, and we’ve seen time and time again that the time we take to listen to folks has a clear payoff.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JZIfl4X0uCG3Az-QnNP3Aw.jpeg" /><figcaption>Michaela, payments engineer</figcaption></figure><p>Last, we actively question whether meetings include all the relevant stakeholders. We want to ensure everybody has a seat at the table but also that we don’t have too many cooks in the kitchen for any decision. It’s a difficult balance to strike!</p><h3><strong>5. We ensure our hiring funnels fairly include and evaluate candidates of all backgrounds.</strong></h3><p>Until this point, I’ve only discussed ways in which we promote equity for employees already working at Patreon. However, we need to hire women and other folks from underrepresented groups for any of this to really matter, and that means having a fair hiring pipeline that mitigates bias at each step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0v7uYHah86xfjOsSWnKnFQ.jpeg" /><figcaption>Coding &amp; caffeination, featuring Ana (engineering manager) &amp; Ben (frontend engineer)</figcaption></figure><p>Exhaustively detailing what we do to ensure fairness in our hiring process is beyond the scope of this point, but it would include things that are considered industry best practices today, like asking technical interview questions that reflect real work, ensuring our interview panels are diverse (despite the cost to the Second Shift, to which we are sensitive, and it’s important to check in with interviewers to rebalance their interview load, if necessary), and sourcing to increase diversity at the top of the funnel. It’s important to put a process in place which allows us to fairly analyze a candidate’s skill, regardless of background, and to have enough diversity in our hiring funnel that representation of marginalized groups improves over time.</p><p>If this sounds like the type of environment in which you’d like to work, please <a href="https://www.patreon.com/careers#positions">check out our open positions</a>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6TkPfTt9CZGDlnWoAiZb2g.jpeg" /><figcaption>A candid thumbs up and thanks for reading, from me (Adam with the shiny head)!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/801/1*xDBe8893cFTBh_16HkApBg.png" /></figure><p><em>¹ We acknowledge that the integrity of our compensation data depends on this tool, and we’ll continually look for the highest quality we can get.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=567eb0812576" width="1" height="1" alt=""><hr><p><a href="https://medium.com/art-work-behind-the-scenes-at-patreon/five-ways-patreon-supports-engineers-of-all-backgrounds-567eb0812576">Five Ways Patreon Supports Engineers Of All Backgrounds</a> was originally published in <a href="https://medium.com/art-work-behind-the-scenes-at-patreon">art/work -behind the scenes at patreon</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Exercise In Survival]]></title>
            <link>https://medium.com/@abossy/an-exercise-in-survival-173b09c92f09?source=rss-dcc34fafb41f------2</link>
            <guid isPermaLink="false">https://medium.com/p/173b09c92f09</guid>
            <category><![CDATA[jungle]]></category>
            <category><![CDATA[bolivia]]></category>
            <category><![CDATA[travel]]></category>
            <dc:creator><![CDATA[Adam Bossy-Mendoza]]></dc:creator>
            <pubDate>Wed, 30 Dec 2015 16:55:29 GMT</pubDate>
            <atom:updated>2015-12-30T16:55:29.490Z</atom:updated>
            <content:encoded><![CDATA[<p><em>November 4–9, 2014. Written during a five-month backpacking trip through Argentina, Bolivia, Peru and Colombia.</em></p><p>Who knew that my rainforest dreams would ever be realized, and in such a spectacular way?</p><p>As a child, I developed an allergy to pet dander, which led me to have a tumultuous relationship with dogs, cats, rabbits, ferrets, and especially birds; even the occasional hamster would yield anxiety. Well-intentioned sleepovers would become complex affairs, occasionally resulting in middle-of-the-night rescue missions by my parents to pick up an asthmatic, younger Adam from the perils of a dander-infested suburban household.</p><p>Naturally, reptiles drew the focus of my affection. I dreamt of transforming my Colorado bedroom into a rainforest, and got as far as two anoleys, a frog that I caught — in Denver, the most unlikely of places — a recurring series of goldfish that would invariably die, and a few fake plants to give my carpeted room that authentic rainforest feel.</p><p>Needless to say, visiting the jungle during my South American backpacking trip was not a matter of “if,” but “when.”</p><p>I traveled with Katja, my travel partner and belle for a portion of my journey. She was a German med student, equal parts bubbly and sharp-witted. I found German travelers to be physically relentless, and she proved to be an able companion on many enduring adventures. We’d met a few stops earlier in Cordoba, Argentina. I’ve never read <em>Eat, Pray, Love</em>, but I imagine our romance flourished in a way that’d do the book justice.</p><p>We met our guide at the tour company’s eco-lodge, which acts as headquarters for these tours. Immediately I sized him up. He was small, skinny, and dark-skinned, and had the half-lidded eyes and relaxed demeanor of a serious pothead. We made small talk, and the first time he laughed, he freaked me out: he jutted his head forward, brought it within inches of mine, and cackled maniacally, never fully opening his eyes. Like Robin Williams’ character in Jumanji, he’d clearly spent far too much of his life in the jungle.</p><p>I was apprehensive about what we signed up for, especially given that we opted for a five-day tour. This was longer than any other tour group! Sweltering heat, endless bugs, and the real possibilities of dengue fever and malaria were par for the course, not to mention the simple fact that I’d never been camping for five days straight.</p><p>My anxiety was quickly quelled, however. We spent the next five days watching our guide perfectly mimic the call of every animal we heard—jaguars, howler monkeys and tapirs were all fair game—we saw him hack his way through the jungle thicket, inexhaustibly chase after wildlife, carry ungodly loads on his back and generally perform superhuman endeavors. His name? Fittingly, it was Darwin.</p><p>We were joined by a cook, Sergio, a sweet, soft-spoken and effeminate guy, and Sarah, a Swiss girl with a history of anorexia. We were off.</p><p>After no more than 10 minutes of hiking, Darwin gathered us around a tree. With the tip of his machete, he peeled off a piece of bark to reveal that the tree was full of termites. He put his tongue to the tree and had himself a small snack. We all took turns tasting the termites, oblivious to what diseases they could carry. They tasted woody.</p><p>This is the type of trip we would be having.</p><p>We hiked all day. There was no map nor trail. Darwin’s intuition guided us, along with the sun and the river.</p><p>Have you ever seen aerial shots of rivers snaking through the jungle? Well, the River Tuichi in Madidi is exactly like that. There were large walls of thicket that would separate the clearing of the river bank from the dense jungle. Inside the thicket, there were no paths—Darwin would hack his way through with his machete, and we were constantly navigating our way over, under and around all sorts of plant life.</p><p>As dusk approached, we perused Tuichi’s bank in hopes of finding a big enough clearing to build a shelter for the night. Suddenly, Darwin hushed us and motioned for us to put down our packs. We complied. Darkness had nearly encapsulated us — we crept forward silently to see a large, dark blob plodding along, not 10 meters away. A tapir!</p><p>We quickly approached it, but as jungle amateurs, we were too loud and frightened the beast before we could get too close. We roamed the river bank, flashlights in hand, to no avail. Its footprints disappeared into the thicket.</p><p>What excitement! Tomorrow’s possibilities were endless. Darwin hacked together a hut out of bamboo sticks, from which we hung a rain tarp and mosquito nets. It was a hot and physically taxing day. We slept soundly during our first night in the deep jungle.</p><p>The next day, I experienced a moment forever burned into my sensory memory. As we continued along the river in the morning, Darwin and Sergio hushed us once again. Prepared this time, we quickly fell quiet and followed their lead. I could not hear their murmurs from where I stood crouched, but I could tell that excitement was in store.</p><p>Sergio left our group and entered the thicket downriver. We followed Darwin inside, unsure of which exciting animal we were pursuing and unable to afford the noise required to ask.</p><p>As we crept our way through, we kept an eye out for thorns, fire ants and other jungle perils. We heard growling in the distance and approached it. As we drew closer, it grew louder, more fierce. Aggressive even. Was it two animals fighting?</p><p>My mind reached for the logical explanation. Animals must have been fighting. Jaguars? We heard loud growls. My senses tingled.</p><p>Darwin, in his excitement, heard this and charged forward. We kept a close distance behind. They sounded louder than ever. We were almost upon the wild beasts. The intensity of their growls were terrifying. The creatures would appear through the brush at any moment.</p><p>Darwin suddenly sensed something, and rapidly broke to his left. Surely, they were turning their aggression towards us! Adrenaline filled my body. I never felt so alert. I contemplated how to defend myself and the girls. Only Darwin was armed. I prepared for him to lift his machete and do battle. But what were the mysterious creatures?</p><p>WILD PIGS! A stampede of wild pigs — passing blurs! — emerged in the brush. They moved faster than I knew pigs could move. They were endless! They shook the ground before us!</p><p>Darwin later estimated that there were 200 in total, and we found evidence later that day; their footprints gutted a muddy river bank we crossed, and they were countless.</p><p>Suddenly, it was clear: Sergio flanked and scared them toward us, resulting in one of the scariest moments of my life. The subsequent adrenaline release from seeing the first pig appear is forever scarred into my senses.</p><p>The wild pigs, as it turns out, aren’t native to the Madidi jungle. They were brought by farmers generations earlier, and, finding the ecosystem hospitable, they profligated wildly. Their numbers have imbalanced the ecosystem, and while conservation laws ban hunting in the national park, the ban is lifted on special holidays as an ad hoc way of helping restore balance.</p><p>I later read a journal published in National Geographic in the year 2000, in which a photographer tells a story of how a local was evicerated by a band of angry wild pigs in Madidi. Evicerated. I would later wondered how much of Darwin’s guidance shielded us from true danger. Or perhaps he didn’t shield us. Ignorance is bliss, as they say.</p><p>We fished for food later that night. Darwin conjured a slab of rotting, raw meat from one of Sergio’s bag and attached it to two homemade fishing lines. The ladies took the first attempt.</p><p>Katja’s line tightened, and she pulled out a fish that measured a good eighteen inches. It wriggled around desperately, and in a show of mercy, Darwin took the liberty of savagely beating its head with the flat end of his machete. THWAP! THWAP! THWAP! After several blows it stopped convulsing and its life gave way entirely.</p><p>Sarah demanded that he stop. She sat down on the nearest rock, lightheaded and nauseous. I took the line. Within a few minutes, the line felt tight and I pulled out another fish. We let this one die one a slow, drawn-out death.</p><p>Darwin later wrapped one fish in a large leaf and smoked it for dinner. While it cooked, he told us the story of another animal he had killed. An aunt of his was married to a man that was into dogfighting. They lived next door to Darwin and kept a fierce pitbull tied up outside. The pitbull aggressively barked at passersby, and one day, it managed to free itself as a woman walked past with her child. It attacked the woman unprovoked, biting her in the leg. Hearing the woman’s screams, Darwin rushed out of his house, baseball bat in hand, and beat the dog into submission. The dog died and his aunt was furious. Not only was he reprimanded for killing the beast, but his aunt demanded that Darwin pay for the woman’s medical bill.</p><p>To make up for lost time, we had a 5am wake-up call on the third day. We hiked for three hours before breakfast. Our second fish had disappeared overnight. Darwin picked up extra weight each day. He had a head-splitting toothache, and he was quite grateful for the few pills I offered him. He refused to take the whole bottle, even though I insisted that I could easily replace it. Sergio playfully carved our names into the sand in fancy type.</p><p>The volume of bugs reached ungodly volumes. Our aggressive use of 25% DEET and prevented most mosquito problems. Notably, the Madidi mosquitos turned out not to carry malaria, so the mosquito situation was relatively painless compared to what we had imagined.</p><p>Instead, we were blessed with baby bees. Thousands of tiny, fastidious bees. They swarmed in numbers that would test my sanity. They would land on my skin and immediately fly away, with more curiosity than malevolence. At such volume, they were nature’s torture device. It was insanity by a thousand taps. After a few minutes of actively ignoring them, I could barely resist the urge to scream. Blocking them out required a degree of mental fortitude that I do not possess.</p><p>The afternoon grew worse. We headed into the hills for the first time, having walked mostly flat ground until this point. Our ascent was fierce, occasionally reaching up to a 45-degree-plus incline. We would fall to all fours, literally crawling our way up the hillside through a path that Darwin claimed was readied for us by the jungle’s tapirs.</p><p>I climbed uphill with a pack weighing 40–50 pounds. Katja had at least 20 and a much less ergonomic pack. The heat was unbearable. Throughout the course of the next five hours, my legs threatened to collapse from exhaustion. Heat stroke felt like a real possibility. I drank small sips of water consistently, not feeling thirsty per se, but acknowledging the threat of dehydration. My mind wandered.</p><p>I daydreamed of simpler times. I thought of the ice cold watermelon juice I had been enjoying in Bolivia. I imagined bringing the feint red liquid up to my face, my lips tingling from the cold, the sweetness covering my tongue and filling my mouth, the sugar nutrifying my debilitated body. I imagined sitting at Blue Bottle coffee in sunny San Francisco, enjoying their signature New Orleans iced coffee, the simultaneous sensation of sweetness and caffeine stimulation overcoming me with pleasure. I sat there early on a weekday morning, watching techies make their way in and out for their morning fix. Light was flooding the Mission and the sun peeked over the hills. The coffee quenched not only my thirst, but my dreams and desires.</p><p>It occurred to me that I had never experienced such a raw physical challenge. There was numbness in my legs; stifling heat and humidity; lack of sleep. Few intellectual, educational or physical challenges measured up to the sheer intensity of pushing my body to its limits in an unfamiliar environment.</p><p>We paused for a break.</p><blockquote>“How is it going?” Darwin asked in Spanish.</blockquote><blockquote>“My legs can’t endure any longer,” I replied.</blockquote><blockquote>“It’s not the body, but the mind!”</blockquote><p>He went on to explain that he could go on for two to three days with food or water. He could go on longer without food, but was careful to reassure me that this was only possible if he drank water. I didn’t doubt it.</p><p>Focusing on the struggle slowed down time. I heeded Darwin’s advice and shifted my thoughts from desires to practical reflection. Regardless of the physical taxation, we never stopped making progress, one step at a time. I tucked this moment in my back pocket as an analogy for more complex situations, in which progress isn’t clearly measured in the short-term, but evident over the course of time.</p><p>I reflected on my career. I resolved to somehow shift my career focus in a dramatic way, a challenge which previously seemed impractical or insurmountable.</p><p>Such is the value of travel. When one finds oneself traipsing through a hot jungle far from human life, prior obstacles are demagnified. Everything is small enough from far away.</p><p>It was clear to me, in this moment, that travel would play a much bigger role in my life in years to come.</p><p>Our brutal hike through the hills was momentarily interrupted by a howler monkey sighting in the distance. Darwin had been calling all day and they finally replied in the late afternoon. He dashed off without warning, and we struggled to follow along.</p><p>We failed to get within camera-shot of the monkeys given the terrain. My memory of this moment reminds me of a slapstick comedy; Darwin effortlessly sprinting up and down the hills and through the thick plant life ahead of us, while Katja and I struggle to muster the energy to keep up. Sarah was somewhere in between. When our sprint was concluded, Darwin sat down to nurse a bleeding gash on his ankle.</p><p>We reached our campground that night as the last traces of light disappeared from the sky. Our third, and hardest day, was concluded. The next two days would be relatively easy. Instead of following Darwin’s improvised tour, we would follow the general tourist schedule, which involves visiting a local farm and seeing parrots fly around from a lookout point.</p><p>The following morning, we walked a few hours to a second campground and found several fellow tourists. They jarred our reality; they were bored, impeccably clean, and they complained of the heat. It looked like they hadn’t gone anywhere all morning. The heat! What audacity! I had nearly been mauled by wild pigs! I braved the hills and the heat! Our white shirts were stained brown, and would stay that way for months.</p><p>The smiles on our faces were unconquerable.</p><p>It occurred to me that we hadn’t seen another human being — let alone a sign of human life! — for the last three days. Our journey was a thrill ride and our resulting energy was palpable. In photos, exhaustion marked our eyes and made our skin pale, yet Katja and I look back on our expedition with utter delight. We long to return one day, and hope that Darwin will still be offering tours.</p><p>Once we arrived at the eco-lodge, it became clear that our trip was exceptional. The other guides were obese and looked unfit to lead a tour like ours. They stared creepily at Katja when she wasn’t looking, whereas Darwin and Sergio had been perfect gentlemen.</p><p>Most other tourists sign up for a carefully planned two or three days tour, and they use the eco-lodge as a base from which to visit nearby sights. We lucked out by scheduling the five-day tour, because that meant Darwin was assigned to us, who is typically responsible for trips that take between six to fifteen days. On a side note, he once guided a couple for a fifteen-day tour, and a man secretly brought a suit. An actual suit. About ten days in, he wore it and proposed to his girlfriend. Just.. Wow.</p><p>Many of the other guides were supposedly “English-speaking,” though we found Bolivian English to be barely comprehensible. English speakers earned a premium of 150 Bolivianos a day ($22), where as Darwin, as a Spanish-speaking guide, earned 120 Bolivianos a day ($17 and change). Sergio, as a cook, earned 110 Bolivianos ($16) daily. It hardly seemed fair.</p><p>We continued with the tourist schedule for the next two days, which was a welcome change of pace. The eco-lodge had beds, showers, clean bathrooms and it felt like a 5-star resort. I finally got my watermelon juice, although it wasn’t as cold as in my dreams.</p><p>We spent one last night in La Paz before continuing to Lake Titicaca. We stayed in a hotel downtown run by an American expat. The bed was so comfortable that I fell asleep immediately. In the middle of the night, I awoke with a light sweat, just like I had been doing for the last five days. I quickly brushed the bugs off of my legs, their mild stings resonating lightly. I went to the bathroom to pee. I discovered that I wasn’t sweating and that I had no bites. There were no bugs in our room.</p><p>I was grateful for these aftereffects. I cherished this connectedness to nature for a final, fleeting moment before falling back into a deep, restorative sleep.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=173b09c92f09" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Real Reasons Why Hiring Growth Engineers is Hard]]></title>
            <link>https://medium.com/@abossy/the-real-reasons-why-hiring-growth-engineers-is-hard-153ec7ac00f9?source=rss-dcc34fafb41f------2</link>
            <guid isPermaLink="false">https://medium.com/p/153ec7ac00f9</guid>
            <dc:creator><![CDATA[Adam Bossy-Mendoza]]></dc:creator>
            <pubDate>Tue, 29 Jul 2014 05:39:34 GMT</pubDate>
            <atom:updated>2014-07-29T16:46:56.205Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*6-Hrr12t81mIqs9abFn6GA.jpeg" /><figcaption>“Up and to the right!”</figcaption></figure><p>I’ve been working on growth at shopkick for the past two years, and I recently came across “<a href="http://blog.chrisbolman.com/why-impossible-hire-growth-engineers/">Why It’s Impossible to Hire Good Growth Engineers</a>,” an article which describes why hiring growth engineers is a difficult, if not futile, task.</p><p>I believe the author has a few misconceptions about what a strong engineering culture entails. His assumptions are that:</p><ol><li>New entrants to the field have a “competitive” impetus for growing companies but incumbent ones don’t;</li><li>Engineers want a high degree of structured work;</li><li>Engineers like big teams;</li><li>Growth engineers are fiercely independent (probably true, but no different from any other engineer).</li></ol><p>These certainly don’t align with my own experience as an engineer during the last six years, and are certain to lead to hiring challenges as a result. Many factors play into forming an attractive engineering, and from the investigation I’ve done, it could be a problem with the type of talent his company (<a href="https://percolate.com/">Percolate</a>) is attracting, whether it be because they are in the wrong market (New York), have the wrong type of company (a b2b marketing platform), or something else, they are likely not well-positioned to attract top engineering talent.</p><p>Software engineering hires in general are hard and a company requires a very specific type of culture to foster a strong engineering team. The author’s challenges in this scenario are the norm.</p><p>From being in the industry for 6+ years, the few universal traits that candidates seek are:</p><ol><li>Solve challenging problems</li><li>Be valued</li><li>Have high impact</li><li>Don’t be micromanaged</li></ol><p>There are few places that can honestly offer this type of employment environment and engineers tend to gravitate there. Furthermore, growth engineers have a special set of qualities which distinguish them from the rest, and I’ll explain why.</p><p><strong>Growth is a new field so the candidate pool is small.</strong></p><p>A chart in the author’s post shows that Google search result for growth engineer began in 2008. There has been little time for companies to create growth teams and roles, for engineers to work on a growth team, and for engineers to develop the skillset that constitutes a “growth engineer.”</p><p>According to Paul Graham, <a href="http://paulgraham.com/growth.html">Startup = Growth</a>. Growth is a fundamental competency that any successful startup must have (per Graham’s definition of a startup), and growth teams are the manifestation of this need; they’ve learned to build out cross-disciplinary teams which can rapidly design and prototype new features, A/B test hypotheses and gain product insight at an exceedingly fast pace.</p><p><strong>The standards for a growth engineer are not well-defined nor well-understood.</strong></p><p>Growth engineering combines a number of disciplines: marketing, data science, user experience and interaction design, and, of course, software engineering. Furthermore, it’s not clear what mix of these characteristics is “best.” Strong data science skills can help a team understand a product more deeply, while stronger marketing skills can help a team generate more creative and effective ideas.</p><p>It’s nearly impossible for any growth engineer to excel at all of these, and the interview process for measuring these skills in a growth candidate has little maturity. Additionally, successfully growing a company requires a huge confluence of factors, such as product/market fit, which is generally out of a single individual’s control, therefore assessing a candidate on previous experience is quite difficult.</p><p><strong>There is little training for growth engineers.</strong></p><p>University curriculums certainly don’t teach classes on growth engineering (e-mail me if this is not the case! adambossy@gmail.com); only private schools like General Assembly have any form of training.</p><p>However, growth engineering doesn’t happen in a vacuum. It’s a marathon-like process in which hypothesis after hypothesis must be tested, and each team’s approach for efficiently testing hypotheses is going to be different. The best way to learn growth is by doing, so there’s the catch-22 of having to be put on a growth team to learn growth engineering in the first place.</p><p><strong>Growth engineers generally need to be high-level.</strong></p><p>Growth teams generally have a stronger feedback loop than other teams, in which project metrics are meticulously measured and iterated upon. The learnings of a growth team inevitably affects overall product strategy and direction and so it’s important for a growth team to either be run by upper management or have upper management’s ear.</p><p>Additionally, given the confluence of skills necessary for an effective growth engineer (marketing, data science, user experience design, and engineering), it requires a more experienced—and therefore—expensive engineer (or super-talented younger ones).</p><p>Given how critical growth is for a startup’s success, richer companies are apt to throw more money at the problem, making the hiring game more difficult for everybody else.</p><p><strong>Conclusion</strong></p><p>My friend, John Egan, published an response to the previously cited article, entitled <a href="http://jwegan.com/growth-hacking/hiring-growth-engineers-impossible/">Why Hiring Growth Engineers Is Not Impossible</a>. His advise is sensible; cultivate engineers that don’t have a growth background but who can think about the big picture and quickly learn new skills. John led our growth team at shopkick for a while, and some of us grew deeply into the role and others moved on to other interesting challenges.</p><p>It’s not impossible, it’s just that hiring for a mystical role that will solve all your company’s problems is unlikely to ever happen. With the right incentives and the right management structure, you’re more likely to get mileage out of talented and creative individuals regardless of their title.</p><p><em>Edited to soften the sarcastic language. Also, the obligatory, these views are my own and do not represent those of my employer, shopkick. But is that really necessary to state? This is a personal account, and in no way tied back to shopkick, as are most blogs in the universe. Shouldn’t people point it out when their views DO reflect that of their employer?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=153ec7ac00f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>