<div> <div><section><details><summary><h2 id="about-posthog"><strong>About PostHog</strong></h2></summary><p>PostHog helps engineers build better products. We are a single platform to analyze, test, observe, and deploy new features. We give engineers product &amp; web analytics, session replay, feature flags, experiments, a CDP, SQL access, and a data warehouse… and there’s plenty more to come.</p> <p>PostHog was created as an open-source project during Y Combinator's W20 cohort and had the most successful B2B software launch on HackerNews since 2012 - with a product that was just 4 weeks old. Since then, more than 70,000 companies have installed the platform. We've had huge success with our paid upgrades, raised $27m from some of the world's top <a target="_blank" rel="noopener noreferrer nofollow" href="https://posthog.com/handbook/strategy/investors"><u>investors</u></a>, and have shown strong product-led growth - 97% driven by word of mouth. </p> <p>We're growing quickly but sustainably - we're <a target="_blank" rel="noopener noreferrer nofollow" href="http://www.paulgraham.com/aord.html"><u>default alive</u></a>, averaging 10% monthly revenue growth, with &gt;$10m ARR. We're staying focused on building an awesome product for end users, hiring a handful of exceptional team members, and seeing fantastic growth as a result.</p> <p></p> <h3><strong>What we value</strong></h3> <ul> <li><p>We are<a target="_blank" rel="noopener noreferrer nofollow" href="https://posthog.com/handbook/company/values#we-are-open-source"> <u>open source</u></a> - building a huge community around a free-for-life product is key to PostHog's strategy.</p></li> <li><p>We aim to become <em>the</em> most transparent company, ever. In order to enable teams to make great decisions, we share as much information as we can. In our<a target="_blank" rel="noopener noreferrer nofollow" href="https://posthog.com/handbook"> <u>public handbook</u></a> <em>everyone</em> can read about our roadmap, how we pay (or even let go of) people, what our strategy is, and who we have raised money from.</p></li> <li><p>Working autonomously and maximizing impact - we don’t tell anyone what to do. Everyone chooses what to work on next based on what is going to have the biggest impact on our customers.</p></li> <li><p>Solve big problems -<a target="_blank" rel="noopener noreferrer nofollow" href="https://posthog.com/handbook/company/values#we-havent-built-our-defining-feature-yet"><u> we haven't built our defining feature yet</u></a>. We are all about shipping fast, talking to users, and iterating.</p></li> </ul> <p></p></details><details><summary><h2 id="who-we're-looking-for"><strong>Who we’re looking for</strong></h2></summary><p>To put it simply, we’re looking for a Support Engineer who loves talking to customers and helping them solve their problems. Answering tickets is important, but we want someone who can also build out our support tooling at the same time. </p> <p>You’ll be the face of PostHog for many of our customers, so you’ll need to be extremely helpful and engaging. This isn’t a support <em>agent </em>role - you’ll be resolving most issues directly yourself, and only escalating the more complex ones directly to the relevant engineering team. </p> <p><em>Please note: we are only considering people in GMT +2:00 to -5:00 timezones for this particular role!</em></p> <p></p></details><details><summary><h2 id="what-you'll-be-doing"><strong>What you’ll be doing</strong></h2></summary><ul> <li><p>Improving the way we do support - we’re growing rapidly so need to make sure we are set up for future success. This means better tooling, automation, reporting, and more. </p></li> <li><p>With your knowledge of PostHog, you’ll be answering the majority of tickets yourself across our products, ensuring that customers are able to use the platform without blockers.</p></li> <li><p>You’ll also be working closely with the product teams to ensure that they are aware of any issues requiring product development work, helping them prioritize requests based on customer profile.</p></li> <li><p>You’ll be working closely with the rest of the Customer Success team to ensure that we are meeting our internal targets for support ticket response.</p></li> </ul> <h3><strong>What you won’t be doing</strong></h3> <p>❌ Acting solely as a first line support agent - we expect you to be able to diagnose and fix issues themselves, escalating to the appropriate team when development work is needed.</p> <p></p></details><details><summary><h2 id="requirements"><strong>Requirements</strong></h2></summary><ul> <li><p>Strong customer focus - you need to help our users and remove any blockers to them using PostHog effectively.</p></li> <li><p>Good at prioritizing and context switching - we have a high volume of tickets across various product areas.</p></li> <li><p>Engineering background - the majority of our users are engineers and as such need help from someone equally as technical.</p></li> <li><p>Able to build solutions yourself - we are also responsible for Support and Customer Success tooling so need to take ownership of improvements.</p></li> </ul> <p><em>Nice to have</em></p> <ul> <li><p>Experience providing support for similar products, ie. analytics, session replay, feature flags, A/B testing, data warehouses, CDP etc. </p></li> <li><p>Previous support engineer experience</p></li> </ul> <p><em><br>We believe people from diverse backgrounds, with different identities and experiences, make our product and our company better. That’s why we dedicated a page in our handbook to</em><a target="_blank" rel="noopener noreferrer nofollow" href="https://posthog.com/handbook/company/diversity"><em><u> diversity and inclusion</u></em></a><em>. No matter your background, we'd love to hear from you! Alignment with our values is just as important as experience! 🙏</em></p> <p><em><br>Also, if you have a disability, please let us know if there's any way we can make the interview process better for you - we're happy to accommodate! </em></p> <p><em>#LI-DNI</em></p> <p></p></details></section></div> <details><summary><h2 id="salary">Salary</h2></summary><p>We have a set system for compensation as part of being transparent. Salary varies based on location and level of experience.</p> <p><a href="#">Learn more about compensation</a></p> <div><div> <div> <h3>Location (based on market rates)</h3> <p>The benchmark for each role we are hiring for is based on the market rate in San Francisco.</p> <div> <div> <label id="headlessui-combobox-label-undefined">Country</label><div id="headlessui-combobox-button-undefined" tabindex="-1" aria-haspopup="listbox" aria-expanded="false"> <span></span> </div> </div> <div> <label id="headlessui-combobox-label-undefined">Region</label><div id="headlessui-combobox-button-undefined" tabindex="-1" aria-haspopup="listbox" aria-expanded="false"> <span></span> </div> </div> </div> </div> <div> <h3>Level</h3> <p>We pay more experienced team members a greater amount since it is reasonable to expect this correlates with an increase in skill</p> <div><div id="headlessui-combobox-button-undefined" tabindex="-1" aria-haspopup="listbox" aria-expanded="false"> <span></span> </div></div> </div> <div> <h3>Step</h3> <p>We hire into the Established step by default and believe there's a place to have incremental steps to allow for more flexibility.</p> <div><div id="headlessui-combobox-button-undefined" tabindex="-1" aria-haspopup="listbox" aria-expanded="false"> <span></span> </div></div> </div> <div> <h3>Salary calculator</h3> <div> <ol> <li> <span>Benchmark (United States - San Francisco, California)</span> <span>$171,000</span> </li> <li> <span> Level modifier</span> <span>1</span> </li> <li> <span> Step modifier</span> <span>0.95 - 1.04</span> </li> </ol> <div id="compensation"> <span>Salary</span><span><span>$162,450 - $177,840</span><span>plus equity</span></span> </div> </div> </div> </div></div></details><details><summary><h2 id="benefits">Benefits</h2></summary><ul> <li> <span>Generous, transparent compensation &amp; equity</span> </li> <li> <span>Unlimited vacation (with a minimum!)</span> </li> <li> <span>Two meeting-free days per week</span> </li> <li> <span>Home office</span> </li> <li> <span>Coworking credit</span> </li> <li> <span>Private health, dental, and vision insurance.</span> </li> <li> <span>Training budget</span> </li> <li> <span>Access to our Hedge House</span> </li> <li> <span>Carbon offsetting</span> </li> <li> <span>Pension &amp; 401k contributions</span> </li> <li> <span>We hire and pay locally</span> </li> <li> <span>Company offsites</span> </li> </ul> <p>Get more details about all our benefits on the <a href="#">Careers page</a>.</p></details><details><summary><h2 id="mission-objectives">Your team's mission and objectives</h2></summary><div> <p>Make sure customers have what they need to be successful with PostHog and deliver information in a way which sparks joy.</p> <p>Make sure customers have the information they need to be successful with PostHog and deliver it in a way which sparks joy.</p> <h3 id="hit-our-expanded-slas-while-keeping-csat-stable-marcus--steven">Hit our expanded SLAs while keeping CSAT stable (Marcus + Steven)</h3> <ul> <li> <strong>Rationale:</strong> Reliable support = Good support.</li> <li> <strong>What we'll ship:</strong> Grow the team, train other teams. </li> <li> <strong>We'll know we're successful when:</strong> 80% SLA achievement or above for <em>all</em> Normal and High priority tickets. CSAT average does not fall below 4.1 (4.6 at start of Q3).</li> </ul> <h3 id="level-up-our-processes-and-automations-steven">Level up our processes and automations (Steven)</h3> <ul> <li> <strong>Rationale:</strong> Good processes = Fewer tickets, happier users.</li> <li> <strong>What we'll ship:</strong> Zendesk improvements (<a href="https://github.com/PostHog/meta/issues/201">domain problem</a>, <a href="https://github.com/PostHog/company-internal/issues/1324">bounced emails</a> etc.), MaxAI v2, handbook definitions (incl. definitions of what we don't support), team tracking.</li> <li> <strong>We'll know we're successful when:</strong> MaxAI v2 feels worth keeping and incoming tickets aren't getting out of control.</li> </ul> <h3 id="make-sure-we-have-successful-launches-for-new-products-joe">Make sure we have successful launches for new products (Joe)</h3> <ul> <li> <strong>Rationale:</strong> More products = More revenue. </li> <li> <strong>What we'll ship:</strong> <a href="https://github.com/PostHog/meta/issues/215">See issue</a>.</li> <li> <strong>We'll know we're successful when:</strong> We're successfully completing all launch plans.</li> </ul> <h3 id="continue-supporting-cs--sales-joe">Continue supporting CS &amp; Sales (Joe)</h3> <ul> <li> <strong>Rationale:</strong> There's a lot of things still left to do.</li> <li> <strong>What we'll ship:</strong> <a href="https://github.com/PostHog/meta/issues/215">See issue</a>.</li> <li> <strong>We'll know we're successful when:</strong> We're effectively processing deals of all sizes and up/cross-selling users into new features.</li> </ul> <h3 id="onboard-community-manager-joe">Onboard community manager (Joe)</h3> <ul> <li> <strong>Rationale:</strong> More WOM = More growth</li> <li> <strong>What we'll ship:</strong> <a href="https://github.com/PostHog/meta/issues/215">See issue</a>.</li> <li> <strong>We'll know we're successful when:</strong> They've found two influencers we can work with successfully.</li> </ul> <h2 id="side-quests">Side quests</h2> <ul><li>Run another YC S24 campaign, but with less direct work (Joe)</li></ul> </div></details><details><summary><h2 id="interview-process">Interview process</h2></summary><div> <p>We do 2-3 short interviews, then pay you to do some real-life (or close to real-life) work.</p> <ul> <li> <div><span>1</span></div> <div> <h5> <span>Application</span><span>(You are here)</span> </h5> <p>Our talent team will review your application to see how your skills and experience align with our needs.</p> </div> </li> <li> <div><span>2</span></div> <div> <h5> <span>Culture interview</span><span>30-min video call</span> </h5> <p>Our goal is to explore your motivations to join our team, learn why you’d be a great fit, and answer questions about us.</p> </div> </li> <li> <div><span>3</span></div> <div> <h5> <span>Technical interview</span><span>45 minutes, varies by role</span> </h5> <p>You'll meet the hiring team who will evaluate skills needed to be successful in your role. No live coding.</p> </div> </li> <li> <div><span>4</span></div> <div> <h5> <span>PostHog SuperDay</span><span>Paid day of work</span> </h5> <p>You’ll join a standup, meet the team, and work on a task related to your role, offering a realistic view of what it’s like working at PostHog.</p> </div> </li> <li> <div><span>5</span></div> <div> <h5> <span>Offer</span><span>Pop the champagne (after you sign)</span> </h5> <p>If everyone’s happy, we’ll make you an offer to join us - YAY!</p> </div> </li> </ul> </div></details><details><summary><h2 id="apply">Apply</h2></summary><div><div> <h4>(Now for the fun part...)</h4> <p>Just fill out this painless form and we'll get back to you within a few days. Thanks in advance!</p> <p><span>Bolded fields</span> are required</p> </div></div></details> </div>