<?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 John Peurifoy on Medium]]></title>
        <description><![CDATA[Stories by John Peurifoy on Medium]]></description>
        <link>https://medium.com/@john_86166?source=rss-4358d66af4aa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pGXB1511Eve2V4WdMlmh3A.jpeg</url>
            <title>Stories by John Peurifoy on Medium</title>
            <link>https://medium.com/@john_86166?source=rss-4358d66af4aa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:33:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@john_86166/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[We are using too many prepositional phrases in this intro - it makes the language sounds weak and…]]></title>
            <link>https://medium.com/@john_86166/we-are-using-too-many-prepositional-phrases-in-this-intro-it-makes-the-language-sounds-weak-and-3b3c2afed038?source=rss-4358d66af4aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b3c2afed038</guid>
            <dc:creator><![CDATA[John Peurifoy]]></dc:creator>
            <pubDate>Tue, 25 Oct 2022 17:12:32 GMT</pubDate>
            <atom:updated>2022-10-25T17:12:32.289Z</atom:updated>
            <content:encoded><![CDATA[<p>We are using too many prepositional phrases in this intro - it makes the language sounds weak and passive. We need to remove some of them/make it more direct</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b3c2afed038" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Compensation Restructuring (Post Series A)]]></title>
            <link>https://medium.com/floating-point-group/compensation-restructuring-post-series-a-7dbc488735c9?source=rss-4358d66af4aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/7dbc488735c9</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[people]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[compensation]]></category>
            <dc:creator><![CDATA[John Peurifoy]]></dc:creator>
            <pubDate>Mon, 21 Mar 2022 13:03:06 GMT</pubDate>
            <atom:updated>2022-04-29T17:15:20.954Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Hi! I’m John! I’m a co-Founder of a Series-A company which recently restructured compensation for a Series A through Series B transition. This article is useful for any founder who is building out their compensation scheme. If you are interested in HR, or building novel systems in cryptocurrency — please reach out, </em><a href="https://boards.greenhouse.io/fpg"><em>we are actively hiring</em></a><em>!</em></p><p><em>I’m incredibly grateful to: Tity Lyngdoh, Sutton Kauss (if you have HR questions, please reach out to her!), Rafael Lopez, Katherine Markel, Justin Lee, Michelle Luong, Kevin March, and Van Phu for all their advice and assistance with this.</em></p><p><strong>Table of Contents:</strong></p><ul><li>Summary</li><li>Motivation</li><li>Process of Updating Compensation</li><li>New Compensation Scheme &amp; Model</li><li>Conclusion</li></ul><h3>Summary</h3><p><strong>Reasons for doing it</strong></p><p>Our company is about to undergo a sizable scale-up. As of 3/6/22, we have 30 full-fledged floaters. Our plan is to target 200 full-fledged floaters by the end of 2022. This represents about a 600% increase in personnel. It strained us to maintain consistency and fairness in our compensation for the first 30 and we dreaded what it would look like at 300. So we cleared the HR debt and systematized it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vMebdoseZ1J4J1wel_ZBBQ.png" /></figure><p>Compensation is something that is incredibly personal and speaks to what our company values. A startup’s only true assets are the people that are a part of it and a company’s objective should be to both achieve its external mission and to nurture the people inside of it. Learning, Happiness, and Compensation are the three things that an organization can give to its members, and it should give those in abundance.</p><p><strong>What you will get from this</strong></p><blockquote><strong>This post describes a learning process about compensation, the ultimate conclusions that we discovered, and how we are now using those for the next chapter of the company.</strong></blockquote><h3>Motivation — how did we do it before</h3><p><strong>How we compensated sub 30 people</strong></p><p>We used three sources:</p><ul><li><a href="https://tools.aeqium.com/offer_analysis">Aeqium</a>’s compensation tool — used to price equity</li><li><a href="https://www.advanced-hr.com/VCECS">VCECS</a> — good for high level ideas for senior folk</li><li><a href="https://buffer.com/salaries">Buffer’s salary calculator</a>. If you know nothing on compensation, Buffer’s salary calculator is probably the best 80/20 you can achieve.</li></ul><p>Our initial method of benchmarking was coarse. We had roughly two ways of getting industry salaries:</p><ul><li>Take the title of the job, and go to Glassdoor, <a href="https://www.levels.fyi/">Levels.fyi</a>, and other locations to estimate industry pay. Take the average, and add 20% (pay above market rate) to get the Total Compensation Value.</li><li>Split the organization into two tracts: Business and Engineering. For the engineering team, base it off <a href="https://www.levels.fyi/">Levels.fyi</a>. We had 3 levels we then placed engineers in: L1, L2, and L3. These corresponded approximately to L3, L4, and L5 at Google respectively. For the business team, we used our best definition of L1 in the business world and used the same ratios/experiences to create business bands.</li></ul><p><strong>This system had several issues:</strong></p><ul><li>We treated business roles equally because it was easier than creating a ladder for each non-engineering speciality.</li><li>We had little understanding of how the industry was benchmarking people. We couldn’t accurately understand how much the person was previously making/should be making.</li><li>Our internal leveling was ad-hoc and the benchmarks for those levels (outside of engineering) were quite poor.</li><li>Negotiating was becoming a substantial issue. We didn’t have clear guidelines on what we could or couldn’t do for certain roles and it created tension in the interview process.</li><li>A lot of people asked often when we review compensation, how we think about, and how we benchmark it. We had no clear answers.</li></ul><p>Because of these reasons, we realized that we needed to update our compensation.</p><h3>Process</h3><p><strong>What we learned</strong></p><p>During these conversations, we did three things:</p><ul><li>Wrote down the original process that we use to compute compensation. It was a lot easier to modify a process and explain its shortcomings if you write down what the process is.</li><li>Drafted our compensation philosophy. Just tenets that we thought would be good to be guided by.</li><li>Talked to people about how to price equity.</li></ul><p>The draft compensation philosophy was pretty useless itself, but instead discussing <strong>what tradeoffs it promotes</strong> made it highly valuable. For instance, the value of we pay people based on the value they provide is, I think, mostly agreeable. However, reframing that as:</p><ul><li>We pay people in NY the same as those in India</li><li>We do not incentivize people to live near the office (indeed based on net pay/effective rates, we discourage it)</li><li>We do not pay experienced people at the company more than others joining recently</li></ul><p>Gave a lot more stimulating conversation on whether we wanted that to be a core part of our compensation philosophy or not.</p><p>It took us a while to find good data sources. Finally, we discovered enough sources — it was hard to find banking (McLagan) and regulatory data (OptionImpact and Radford), and then getting a more clear picture on SWE (OptionImpact, Levels.fyi) was difficult as well.</p><p>We mapped out departments to different data sources:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iZ2_bPC28sB4ySdTUmcUGg.png" /><figcaption>Source Benchmarking</figcaption></figure><h3>New Compensation Structure</h3><p>There were five deliverables for the end of the project:</p><ol><li>Compensation Philosophy</li><li>Compensation FAQ</li><li>Benchmarking</li><li>Equity Pricing</li><li>Calculation worksheet for compensation</li></ol><h4>Compensation Philosophy</h4><p>We settled on a five part compensation philosophy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jt56qu9Kd0K9jB4KoxXndQ.png" /><figcaption>FPG Compensation Philosophy</figcaption></figure><h4>Compensation FAQ</h4><p>We put together a page summarizing how Compensation works, how we calculate the Total Compensation Value, and answering some common FAQ questions on it. The idea is that this is shared with all employees of FPG — we aren’t quite comfortable yet to share this with all applicants, but it is a near term goal to achieve that level of transparency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aKjwnUCIEUi_6MHpxOilyg.png" /><figcaption>Salary Setting Page &amp; FAQs</figcaption></figure><p>We also created an FAQ document with all the questions we have been asked:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3mLWBHMMS8WJM8rH17z9mw.png" /><figcaption>Sample of some of our FAQs</figcaption></figure><h4>Benchmarking</h4><p><strong>Data Sources</strong></p><p>We use 4 data sources:</p><ul><li><a href="https://www.optionimpact.com/">OptionImpact</a> — free, great data for startups with equity and salary breakout.</li><li><a href="https://www.levels.fyi/">Levels.fyi</a> — free, great data for engineering roles and organizations. Has most big tech in it</li><li><a href="https://radford.aon.com/">Radford</a> — cost. Good general purpose data (has Janitors and CTOs), but more designed for SME businesses</li><li><a href="https://mclagan.aon.com/">McLagan</a> — cost. Has investment banking data, which nearly no one has.</li></ul><p>As auxiliary, we use a few others:</p><ul><li><a href="http://pave.com/">Pave.com</a> — free, good at auto-generating levels and seeing them. They use the same leveling system as Radford, and worked with an outside firm on creating the underlying model. Their data comes from everyone on their system, and the system is free.</li><li><a href="https://carta.com/private-companies/total-compensation-management/">Carta total compensation</a> — cost. Will auto-pull from Carta &amp; your payroll provider to show where you sit with payments and salary. Newer tool, but pretty cool.</li></ul><p><strong>It is important to note, if you are doing this as a startup I would strongly recommend OptionImpact &amp; </strong><a href="https://www.levels.fyi/"><strong>Levels.fyi</strong></a><strong>. Under few conditions would you need to venture out from them</strong>. Carta’s tool is a bit early, but honestly looks pretty promising to reduce some of the searching and have quick integrations.</p><h4>Equity Pricing</h4><p>We created a page on equity pricing.</p><p>Equity pricing is used for two things — to inform candidates how much their offers/options could potentially be wroth, and to inform how many shares should be given for certain levels of compensation.</p><p>We struggled with how to communicate this, but eventually decided that the way it was done in the <a href="https://www.amazon.com/Recruiting-Ryan-Breslow/dp/B09NGVLQ8W">Recruiting book</a> was probably the best method. Showing just the range of possibilities:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jD_LPI2cYCJxeHkFC4krvQ.png" /><figcaption>FPG Options Pricing / Ranges</figcaption></figure><p>Most companies use internally either <em>best value</em> (which is last priced round valuation), or some multiple of their revenue/spot. We used a bit of a conservative average — slightly above our <em>best value</em><strong><em> </em></strong>as we have grown quite a bit since out last round.</p><p><strong>If you are a start-up post Series A, using best value may be a good 80/20 to get consistency to other organizations.</strong></p><h3>Contributions</h3><p>Compensation is a challenging subject. We were very fortunate to have an amazing team and group of colleagues who embarked on this project with us, but for many people that don’t have those resources — please reach out and let us know what edits/items we should do better!</p><p>John Peurifoy</p><p><a href="http://john@floating.group/">john@floating.group</a></p><p>Floating Point Group | Friendly People Group</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7dbc488735c9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/floating-point-group/compensation-restructuring-post-series-a-7dbc488735c9">Compensation Restructuring (Post Series A)</a> was originally published in <a href="https://medium.com/floating-point-group">Floating Point Group</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CFTC, USAO, FBI vs. BitMEX]]></title>
            <link>https://medium.com/floating-point-group/cftc-usao-fbi-vs-bitmex-7132cf638a56?source=rss-4358d66af4aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/7132cf638a56</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[futures-trading]]></category>
            <category><![CDATA[regulation]]></category>
            <category><![CDATA[trading]]></category>
            <category><![CDATA[bitmex]]></category>
            <dc:creator><![CDATA[John Peurifoy]]></dc:creator>
            <pubDate>Fri, 02 Oct 2020 16:29:15 GMT</pubDate>
            <atom:updated>2020-10-02T17:17:13.945Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By: John Peurifoy, Merav Shor, Kevin March. Updated: 12:30 PM ET, Fri October 2, 2020</em></p><p><em>Questions? Content to add? Thoughts? Please send them to </em><em>press@floating.group and if we include them, we will add you as a collaborator.</em></p><h3><strong>Introduction</strong></h3><p><a href="https://www.cftc.gov/PressRoom/PressReleases/8270-20">On October 1st, 2020, the CFTC charged BitMEX owners</a> with illegally operating a cryptocurrency derivatives trading platform. Further, the U.S. attorney for the district of New York and the FBI indicted the owners for violating the Bank Secrecy Act.</p><p><a href="https://floating.group/10-2-industry-news-bitmex-timeline/">This is a timeline of the history of BitMEX</a> outlining the relevant issues in the recent charge brought by the CFTC as well as the generally increased focus on regulation in the space. The entire CFTC report can be found on the CFTC website <a href="https://www.cftc.gov/media/4886/enfhdrglobaltradingcomplaint100120/download">here</a> and the USAO and FBI indictment can be found <a href="https://www.justice.gov/usao-sdny/pr/founders-and-executives-shore-cryptocurrency-derivatives-exchange-charged-violation">here</a>. This visual is only meant to summarize the key developments in chronological fashion. Each item in the timeline is hyperlinked to the page in the report it comes from or the relevant outside news article.</p><h3><strong>Some Key Findings</strong></h3><ul><li>The regulators base all action on the <em>Relevant Period </em>— defined as starting when BitMEX formed to its current operating date.</li><li>The initial probe of BitMEX was announced mid-2019, and in the wake several things happened quickly: customers withdrew funds from BitMEX, BitMEX announced a new holding structure, and BitMEX parted ways with its then COO, Angelina Kwan.</li><li>BitMEX <a href="https://blog.bitmex.com/announcing-the-bitmex-user-verification-programme/">announced</a> in August 2020 that it would require all customers to undergo KYC, nearly a year after the announcement of the probe.</li><li>The most flagrant issues were likely two things: lack of KYC in violation of the BSA (punctuated by open remarks by the founders chastising others for following KYC), and willful neglect (in some cases encouragement) to evade restrictions against U.S. users signing up on the platform — most notably in the form of encouraging the use of VPNs.</li></ul><p>An interactive version of this timeline can be found <a href="https://floating.group/10-2-industry-news-bitmex-timeline/">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EcTlS7vO70VXfXbHHfE5Yw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V9QK9lFahLs7AJcZ54UduQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3C5BSEr6aWzHGCaatij7bA.png" /></figure><h3><strong>Takeways</strong></h3><ol><li>US regulators care about anti money laundering. Not only FinCEN but also the CFTC, the USAO and the FBI will not hesitate to go after those who blatantly violate the rules. Cryptocurrency firms who disregard their anti-money laundering obligations under the US Bank Secrecy Act, including Know Your customer (“KYC”) rules are hurting themselves, their customers, as well as tainting the reputation of the crypto industry as a whole. As the CFTC noted: “Effective anti-money laundering procedures are among the fundamental requirements of intermediaries in the derivatives markets”.</li><li>Executives of cryptocurrency firms who flagrantly violate their BSA obligations may face criminal charges and serve up to 5 years in prison.</li><li>The CFTC will go after those operating an unlicensed cryptocurrency derivatives exchange while allowing US customers on their platform. It is not sufficient for your User Agreement to state that the US is a “restricted jurisdiction”. You must actively prevent US persons from transacting on your platform by establishing proper policies and controls. Deleting US accounts after the fact will not suffice either.</li><li>After numerous enforcement actions over the past years against cryptocurrency firms by the CFTC, SEC, FinCEN, the DOJ, and other regulators the message should be read clear. Compliance must be the crypto industry standard as it will ensure the maturation and sustainability of the space by promoting trust among all users, participants, and regulators.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7132cf638a56" width="1" height="1" alt=""><hr><p><a href="https://medium.com/floating-point-group/cftc-usao-fbi-vs-bitmex-7132cf638a56">CFTC, USAO, FBI vs. BitMEX</a> was originally published in <a href="https://medium.com/floating-point-group">Floating Point Group</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>