💲

What's your salary approach?

The little story behind our salary grid

Every time there's a new job ad ready to be posted, we ask ourselves the same question: should we share the salary range? (Seems familiar right? 😄)

At folk, we decided we'd rather share our salary grid than a raw number so you can fully grasp our approach and easily project yourself.

💁
While building our salary approach, we chose to make it simple and fully aligned with the team experience we're building. We've built our transparent salary grid to show what we value: the impact every team member is bringing to the team.

Salary made simple.

Salary = "Role category" x "Impact"

Our salary approach focuses on two variables:

  • Impact: What matters is the level of accountability and impact you'll have within the team. We believe management paths are as valuable as individual contributors’ path to folk.
  • Description of each Level of impact (Contributor, Owner, Expert, Lead or Principal #1 - #2 - #3)
    Level
    Focus
    Scope of Impact
    GTM Fictional example
    Tech Fictional example
    Contributor
    Learning
    Project: you independently work on well-scoped and well-defined tasks Team: you ask for feedback and you know when to request help.
    Based on the content prepared by the team, Alex scheduled a series of social media posts announcing folk's brand new Open API (Project). They've asked Ari - the Marketing Manager - for validation (Team).
    Alisha works on the subscription flow: introduction of a set of new modals. It is specified and designed. Modals and copy are clearly defined, including the display of the limits progress bar. Limits are already computed. (Project). They express their progress clearly, post their PR, and ask for help when needed. (Team).
    Owner
    Shipping
    Project: you have end-to-end ownership of a project with a controlled level of uncertainty, time, collaboration Team: you proactively communicate clear and concise updates on progress.
    Alex prepared the content for a series of social media posts announcing folk's brand new Open API (Project). To make sure the tone of voice and messaging was appropriate they've asked Ari for feedback before scheduling them (Team).
    Alisha works on the blocking of the workspace when above some limits. Limits are already computed. Blocking involves returning the limits in the API, and displaying a blocked screen when a user is connected. (Project) Alisha clearly indicates the existing mechanism they will reuse and structure the communication on a step-by-step basis. (Team)
    Expert
    Results
    Project: you have end-to-end ownership over a project involving a level of uncertainty, time, collaboration, or operational complexity. Team: you suggest solutions and help course-correct. You clarify stakeholders’ expectations when necessary.
    Alex took ownership of the overall content calendar for the launch of the Open API. They're working closely with Ari who's leading the content strategy around the launch. Alex has defined measurable objectives, timelines, and stakeholders (Project). They made sure to communicate these three items to the entire team during the pre-launch meeting and discussed with each stakeholder to make sure their role and impact were clear (Team).
    Alisha is working on introducing new limits: we want to count the number of attachments and limit the usage to a certain value. Alisha needs to identify strategies to compute the limit in near real time and attachments can be added from different code locations. (Project) Alisha has identified an issue in the pattern to compute all limits, suggests an improvement, and implements it. They clarify the changes it will introduce to the limit computation. (Team)
    Principal #1
    Evangelizing
    Project: you lead a project involving a level of uncertainty, time, collaboration, or operational complexity. Team: you introduce best practices for your team. You have a strong focus on optimizing processes and workflows.
    Alex is leading the overall content strategy around the Open API launch. They’ve sorted out priorities and laid down the overall action plan (Project). Doing so, Alex realized there wasn't any framework for content strategy around feature launches and decided to document one for future launches (Team)
    Alisha works on building a subscription machine: it involves computing the complete state of the workspace (members and limits) and sending a notification to the user when close to the limits or when it will trigger changes to the bill. (Project) Alisha suggests a new centralized component to deal with workspace states, its communication strategy (sync/async) and defines the architecture of the service, compounding on existing strategies. (Team)
    Principal #2
    Advising
    Project: you have end-to-end ownership over a project involving a significant level of uncertainty, time, collaboration, and operational complexity. Team: you're the go-to person for any queries on your field of expertise. You have a track record of driving improvements across multiple teams.
    Alex has identified an opportunity to launch a partnership strategy around Open API. They’re taking ownership of this partnership implementation: identifying adequate partners, negotiating partnerships, planning the launch, etc. (Project) They have also identified the adequate stakeholders to be involved and their roles. They’re aligning with Finance and Admin teams, as well as Customer Experience to prepare the documentation and with Sales for the materials (Team).
    Alisha works on scaling all async update processes, defines a new strategy, and updates the architecture accordingly. They implement it and lead the release and associated migrations. (Project) Alisha presents this new strategy to the team, checks that the team gets it, and makes sure that the remaining refactoring is identified and listed somewhere. (Team)
    Principal #3
    Coaching
    Project: you lead a project involving a significant level of uncertainty, time, collaboration, and operational complexity. Team: you're perceived as a model, helping others grow their expertise.
    Following the success of the partnership strategy, Alex identified an opportunity to launch a partner marketplace. They’re setting up collaboration and action plans with the Product and GTM teams to launch the marketplace both on the landing page and in-app (Project). They ran the kick-off meeting, making sure everyone's responsibilities and role scope were crystal clear. They also sat down with the Content Manager to prepare the messaging, tone of voice, and calendar (Team).
    Alisha has detected that the async update process cannot scale because of how the way db changes are performed. This needs a global switch of technology on the platform over a long period. They lead the project and do the needed analysis to check the feasibility before. (Project) Alisha convinced the whole team including the CPO and the CTO that this change is a requirement to meet future needs. (Team)
    Lead #1
    Mentoring
    Project: you lead the delivery of all your team's projects Team: you facilitate discussions to help your team find the best solution.
    Ari - the Marketing Manager - is coordinating the impact of the overall Marketing team on the API strategy, including content, design, marketing, customer success, and sales. They’re making sure everyone has a clear vision of their objective and impact. (Project) It's the 1st time for Alex to take ownership of the content calendar. They've sat down together to align on priorities, to identify adequate stakeholders, and to review the messaging as well as tone of voice (Team).
    Alisha teams up with a team member and checks that they are moving forward at a good pace, that they face no blocking issues and answers any questions (Project) Alisha helps the team member structure their work in smaller well identified tasks (Team)
    Lead #2
    Empowering
    Project: you translate company-wide strategy into actionable projects for your team. Team: you define a compelling vision for your team.
    Knowing that the nb of sign-ups per week needs to double. Ari identified key Acquisition initiatives to focus on: Social media + Influence strategy + SEO + Affiliate pg + Ads (Project). They presented the Acquisition strategy to the GTM team, aligning on related goals and attributing ownership based on team members’ expertise and will to grow (Team).
    Alisha can coordinate and challenge several major projects, identify overlapping areas, and find solutions for the team (Project) Alisha coordinates with the product and sets a new way to identify overlaps early to smooth the process (Team)
    Lead #3
    Strategizing
    Project: you set a high-level vision and build a company-wide strategy Team: you define a company-wide vision to achieve on strategy that reaches and inspires every team member
    Discussing the Cycle goals, it has been decided that the next revenue milestone is to reach $1.5M ARR in 2024. With this in mind, Ari identified that the two existing channels will need to be scaled and we will need to add two channels on top. They plan the recruitment plans accordingly. The volume of leads underlying will have an impact on sales, customer success, and support and they plan the strategies and recruiting plans accordingly.
    Alisha explains to the team why they are working on their current projects, explaining what’s the meaning behind the priority and why it matters (Project) Alisha presents to the board how teams should be restructured to achieve more velocity and in the end more growth.

    Description of each Sub-Level (New, Established, Moving up, Thriving)

    For each Level of Impact there are 4 sub-levels

    New
    you're jumping onto this new level of impact. 🎯 You’re able to meet 25% of the expectations.
    Established
    you're settling into this level of impact. 🎯 You're able to meet 50% of the expectations.
    Moving up
    you’re growing at ease in this level of impact. 🎯 You’re able to meet 75% of the expectations.
    Thriving
    you're at ease in this level of impact. 🎯 You’re able to meet 100% of the expectations.
  • Role Category: GTM, People, Product, Design, Tech

Salary grid per role category 👇

GTM & PEOPLE

Level of Impact/Sub-level
€42,000
€44,100
€46,200
€48,300
€50,400
€52,500
€54,600
€56,700
€59,430
€62,160
€64,890
€67,620
€70,980
€74,340
€77,700
€81,060
€84,630
€88,200
€91,770
€95,340
€99,120
€102,900
€106,680
€110,460

SALES

Level of Impact/Sub-level
€50,400 (€32,760 base + €17,640 variable)
€52,500 (€34,125 base + €18,375 variable)
€54,600 (€35,490 base + €19,110 variable)
€56,700 (€36,885 base + €19,845 variable)
€59,430 (€38,630 base + €20,800 variable)
€62,160 (€40,404 base + €21,756 variable)
€64,890 (€42,719 base + €22,712 variable)
€67,620 (€43,953 base + €23,667 variable)
€70,980 (€46,137 base + €24,843 variable)
€74,340 (€48,321 base + €26,019 variable)
€77,700 (€50,505 base + €27,195 variable)
€81,060 (€52,689 base + €28,371 variable)
€84,630 (€55,010 base + €29,621 variable)
€88,200 (€57,330 base + €30,870 variable)
€91,770 (€59,651 base + €32,120 variable)
€95,340 (€61,971 base + €33,369 variable)
€99,120 (€64,428 base + €34,692 variable)
€102,900 (€66,885 base + €36,015 variable)
€106,680 (€69,342 base + €37,338 variable)
€110,460 (€71,799 base + €38,661 variable)
€114,467 (€74,404 base + €40,063 variable)
€118,474 (€77,008 base + €41,466 variable)
€122,481 (€79,613 base + €42,868 variable)
€126,488 (€82,217 base + €44,271 variable)

👀 Related documentation:

😃
Commissions

PRODUCT & DESIGN

Level of Impact/Sub-level
€44,000
€46,100
€48,200
€50,300
€52,400
€54,500
€56,600
€58,700
€61,430
€64,160
€66,890
€69,620
€72,980
€76,340
€79,700
€83,060
€86,630
€90,200
€93,770
€97,340
€101,120
€104,900
€108,680
€112,460

TECH

Level of Impact/Sub-level
€50,000
€52,100
€54,200
€56,300
€58,400
€60,500
€62,600
€64,700
€67,430
€70,160
€72,890
€75,620
€78,980
€82,340
€85,700
€89,060
€92,630
€96,200
€99,770
€103,340
€107,120
€110,900
€114,680
€118,460

What are the core principles of our salary grid?

We've chosen a public and transparent salary approach to be:

  • Systemic & Fair
    • Having a transparent salary grid helps us value the impact a person brings to our team rather than their negotiation skills.
    • If we adjust a salary for a person based on market evolution, for instance, we'll adjust it for every other person in the same role.
    • While expanding our team, our salary grid remains the same. We've chosen to provide the same pay for the same role across all time zones. What matters is your impact within the team, not the city you’re located in.
  • Competitive & Market-priced
    • Being transparent on our salary grid helps us challenge the salaries we offer to folkers and compare them to other companies at the same stage of development as us
    • Our goal is to make sure we're putting everything we can in place to attract the utmost and the brightest at competitive rates
  • Evolutive
    • Your position on the salary grid isn't frozen. We follow up with performance reviews to discuss your evolution and projection at folk.
    • Several roles in this salary grid don't exist yet - they are all up for grab
  • Empowering
    • We want to make sure we all own this company. Through our equity plan (stock options), everyone is interested in folk success
    • 1-year cliff, 4-year vesting starting from your very first day with folk

What are the variables taken into account in folk salary approach?

Our salary approach focuses on two variables:

  • Role Category: GTM, People, Product, Design, Tech
  • Impact: What matters is the level of accountability and impact you'll have within the team. We believe management paths are as valuable as individual contributors’ paths to folk.

How do we approach salary positioning in our recruitment process?

How do you project yourself in terms of salary expectations? What are your salary expectations for such a role?

👆This is the question we're going to ask you during the very first call. At folk, salary expectation is a topic we address right at the beginning of each and every interview process.

This first call is all about taking a first step in defining our overall level of alignment and refining it as we move forward with the recruitment process. We believe there’s no point in moving forward if high-level expectations aren't aligned. And no matter how much you're passionate about your role, compensation is a part of it.

In full transparency, our interview process being a funnel, we won't be able to precisely position you within our salary grid until a later stage as we want to have a better vision of your impact and expertise level within our team.

This is one of the many reasons that led us to publicly share our salary approach. As you probably know yourself better than we do, sharing our salary approach upfront might help you position yourself and define if we're aligned right from the beginning of our discussions. Then we'll be able to confidently move forward in the interview process and circle back with you at a later stage to refine your positioning.

👀 If you want to learn more about Equity at folk, check out