HNHacker News
TopNewBestAskShowJobs

beccaodelay

7 karma · joined June 30, 2022

lover of words. believer in poetry. currently common room. formerly aws and airbnb.
submissionscomments
beccaodelay··on [dead]
As a Head of Community responsible for stewarding and sharing knowledge, I thought this Q from a community member a prescient one:

"How do people decide whether working at seed/A stage is right for you?"

One of the replies to this Q in our Uncommon community Slack pointed back to a HN thread based on the same question: https://news.ycombinator.com/item?id=18534132

That HN thread is too old to reply to, so I thought it'd be useful to re-open the convo.

The below is the answer I offered (abridged for characters):

Great question!

I have a feeling the HN post is full of gold, but before it biases me in my thinking, I'll share a bit about my own experiences at early stage startups!

My 'n' is small (3), so please receive this with my 'n' of 3 experience, rather than an entirety of experience (which the HN article probably represents well!)

When folks ask me about whether I'd recommend working at a startup, I ask them to reflect on:

1. What's most important to their lifestyle at this period in their life/What's best for them in terms of work-style that allows them to show up best and produce work they're proud of? - If it's stability and routine, I personally haven't found the magic way of infusing my life with that when at a startup - If it's eagerness to experiment quickly, evolve and iterate through uncertainty, and band together with colleagues and customers to solve something, then the seed/A/B stage can be super rewarding!

2. There's a conversation to be had around 'ego' - For me, there's a large amount of ego-lessness that has to happen at a startup. You have to constantly "kill your darlings" (is there a better phrase for that?), because what worked two weeks ago or what you thought would work next week just didn't, or doesn't, or won't - Some people love exercising that muscle of ego-lessness. For others, it's super disruptive to their work style and well-being. I suppose this goes back to the stability/certainty/routine preferences I mentioned above

3. There's a conversation around compensation and "job security" you should have (with yourself/your family/dependents as well as with the hiring team) - Usually there's less cash and more equity on the table. Does this suit your current needs in life? - Startups often (almost always, I've seen) have to respond way more quickly to fluctuations in the market. This results in having to lay folks off not because of any performance/merit issue, but because of sheer cashflow, balance sheet adjustments, and/or stage/size/right-now needs vs having a "padding" that can offer buffer. It's not personal, but it can still hurt! (Both from a job security POV and a "is it me/my work/my value" POV). This again goes back to the stability/certainty/routine I mentioned above—you should make sure you're ok/good/ready for a relatively larger uncertainty around job security.

4. Work-life balance considerations - I've heard of startups that afford this to their employees/teams—I have not experienced this myself. This is not the fault of my employers or teams, but rather a function of the first bullet point I mentioned—when I've worked at the startups I've chosen, it's because I'm super jazzed about the work and team and product and vision and customer set and community (like here at Common Room!), and I am really dedicated and excited to be a part of it and wanting to evolve with it and helping to co-build it. That also means that I work/am reachable pretty much all of the time! - If that's not the place you wish to be in your life at this moment, I'd think really hard about how you'll set boundaries and adhere to them, and I'd also establish expectations around those boundaries with your potential new company/team. And even when and if you're able to do that, I'd still be prepared for those boundaries to...erode ;)

...

I hope that helps!

Now I'm off to read the HN article and see where my experience overlaps (or doesn't) :)

beccaodelay··on The 2023 Developer Relations compensation & culture report
Happy to help how I can!
beccaodelay··on The 2023 Developer Relations compensation & culture report
Great question!

70.2% of respondents this year (out of 136 respondents) have previously worked as software engineers, so you're in good company.

A few of our community members in our Uncommon community Slack have asked the same question because they too were seeking to move from traditional SDE work into DevRel roles. Tactically, they focused their resumes on the skills they learned from being an SDE that applied to the DevRel roles they were looking at: most of these skills revolved around their community contributions, whether through their activity on GitHub or via their answers on Stack Overflow, Reddit, Discord, Discourse, and other user forums meant to help developers succeed with a product or codebase.

Based on the results of this year's report, the two most common primary responsibilities for a DevRel professional are creating educational content and resources (61.5%) and delivering in-person talks and workshops (51.1%). If you've done either of those things through your SDE work (maybe you help create user tutorials or maintain internal wikis, maybe you run internal hackathons or lead demo days, or maybe you speak about your SDE work at events or conferences or internal brownbag sessions...all of that experience can be applied to what you would do as a Developer Relations professional, and I would recommend highlighting that!)

Additionally, the two primary business objectives for Developer Relations professionals are product awareness (58.6%) and product adoption (54.1%). If, as an SDE, you've worked with a certain product before (or products similar to it) - you might want to look for DevRel roles at those companies first. You could apply your own experiences while using the product to how you would evangelize it and to whom (awareness), as well as how you would get people hands-on with it (adoption).

Ultimately, exactly how you position yourself for a DevRel role depends on what the organization is looking for (their job description should be clear and, if it isn't, you should ask!). But in general, I hope and believe that: 1. You already have very applicable skills from your SDE work and 2. The information in our 2023 report can help you understand what's most expected from a DevRel role, and can help you position yourself and your skills contextually within the role as you step into this new space.

If you want to connect with other DevRel and community leaders about topics like this, consider joining our Uncommon community in Slack :) https://www.commonroom.io/join-slack/

I hope this helps!

beccaodelay··on The 2023 Developer Relations compensation & culture report
This year's report highlights the lived experiences of 136 Developer Relations professionals. It offers data focused on compensation, roles and responsibilities, expectations, and personal wellbeing in the industry in an effort to present a more holistic view of a career in DevRel. With it, we hope to empower more informed conversations for everyone in the community. The report is free to download for everyone.

Highlights:

1. Across all industries and geographies, the median total gross compensation, pre-tax, for Developer Relations professionals is equivalent to $175,000 USD.

2. 61.5% of respondents list creating educational content and resources as their primary responsibility.

3. 58.6% of DevRel professionals are tasked with delivering on a primary business objective: product awareness.

4. When asked what would improve their physical, mental, or emotional wellbeing the most, 53.8% of respondents seek access to data that allows them to show the impact of their role on business objectives.

...

The 2023 Developer Relations compensation & culture report is produced with special thanks to every DevRel professional who shared their experience with us, and to Mary Thengvall, Tessa Kriesel, Shawn Wang, Ahmad Awais, Wesley Faulkner, PJ Hagerty, Ed Finkler, Matty Stratton, Daniel Reis, the DevRelX team at SlashData, and the DeveloperRelations.com team at Hoopy for their feedback on survey design, their help in distributing the survey to DevRel leaders around the world, and their input on the final report.

beccaodelay··on 9-Min Survey: Developer Relations Compensation and Culture
We’re back with the 9-minute 2023 Developer Relations Compensation & Culture survey: https://commonroomresearch.typeform.com/devrelsurvey-23

Last year, our 2022 survey had 147 respondents who shared their experiences to empower DevRel builders to have more informed compensation conversations—download the free 2022 report here: https://www.commonroom.io/resources/developer-relations-comp...

This year, we added questions about DevRel well-being and mental health to help each other understand more about the profession and to create a healthier space for all.

We'll freely share back the 2023 findings with everyone in the community in August.

In the meantime, this survey (and its analysis) are made possible with special thanks to DevRel leaders like Tessa Kriesel, Mary Thengvall, PJ Hagerty, Matty Stratton, Ed Finkler, Ahmad Awais, Wesley Faulkner, Shawn Wang, the SlashData and DevRel communities, and builders like you. So thank you.

Got questions? Here for them.

beccaodelay··on Developer Relations Compensation Report
Today, we published the first ever Developer Relations Compensation Report.

It was a labor of love and trust with everyone in the DevRel and Dev Advocacy community—so many builders lent us their experiences (147 of them!) so we could create this report.

It's our hope that, with it as a community resource, every DevRel builder will feel more informed, confident, and empowered when they enter their next compensation conversation.

Five key stats we highlight in the findings:

1. Median gross total compensation: $180,000 USD equivalent, pre-tax, across all DevRel professionals globally.

2. Industry that pays the highest DevRel salaries: Cloud Infrastructure.

3. Top four roles and responsibilities in DevRel: Creating educational content and resources, delivering in-person talks and workshops, building brand awareness and affinity, and building and managing community programs.

4. Gender and racial identification: The majority of DevRel professionals identify as male and white.

5. Previous experience dependencies: Developer Relations professionals with previous experience in software engineering earn 26.3% higher median salaries than those without.

For deeper details, read the full report. It's available to everyone for free. To connect with 1000+ DevRel and community leaders, join Common Room's Uncommon community Slack: https://commonroom.io/join-slack

beccaodelay··on More informed comp talks: Take a 5-minute DevRel Compensation Survey
I'm Rebecca, and I'm at Common Room leading a 5-minute Developer Relations Compensation Survey with partnership from DevRel leaders like Mary Thengvall, Tessa Kriesel, Shawn Wang, and the DevRelx team at SlashData.

Our goal is to empower Developer Relations and Developer Advocacy professionals with better context and more informed expectations when having compensation conversations. We'll publish and freely share the results in late July. With your help, we're hopeful we'll be able to co-create a more equitable DevRel community for all. The survey: https://forms.gle/rxVXsrRvj8gbazJq6

Thanks for reading :)