• Location
    • Remote
  • Date Posted
  • May. 24, 2021
  • Function
  • Design & UI
  • Sector
  • Media

Are you a web frontend engineer with strong React experience?

  • Are you looking to help build a product that aims to make the world a slightly better place?
  • Do you want to work with a very experienced team who love what they’re doing?
  • Read on, this might be for you.

Intro

  • We created Peanut with the idea that no woman should have to navigate motherhood without a support network.
  • Our mission is to provide a safe space for all women to form new friendships, find their communities, and provide support to each other.
  • Unlike other social networks, we put safety and wellbeing first.
  • Since 2017, over 1 million women have joined. We’ve grown quickly across the US and other countries, and received numerous accolades from Apple, the New York Times, Good Morning America, and the BBC to name a few.
  • We’re a multidisciplinary, distributed, diverse, and experienced team of 28 people. Some of us have previously worked with Skyscanner, Citymapper, Deliveroo, Twitter, Pinterest, or Bumble.
  • We’re passionate about creating a great product that actually does social good.
  • We thrive on collaboration.
  • We experiment and discover solutions to problems we don’t believe anyone has solved well.

Our work ethic

We believe that great teams build great products — and we live to high standards we’ve learned through past experiences.

Collaboration. No one person can come up with a perfect solution, be it about technology or user experience. We strive to listen to everyone and co-design the product across engineering, design, and beyond.

Trust. We trust each other to do their best and to know how to execute within their role and beyond. So we never micromanage — instead, we agree on scope and let each team member be responsible for execution … and expect everyone to ask for (and get) support when they need it.

Mastery. We care about quality and detail, because we care about our audience. We push ourselves and question our assumptions. We always experiment and keep learning, individually and as a team.

Ambition. We have a bold mission, and we aim to make a dent into what we see as a problem in society. We’re committed to the health of our users, our team, and our company.

Feel free to ask us more about how we work!

Your team

You’ll be the first person in our Web Frontend team — which comes with much responsibility and autonomy! But far from alone, you’ll be supported by several very capable full-stack engineers in our Backend team.

The Backend team is currently responsible for our public website and content moderation UI — on top of building the APIs that serve our user’s mobile apps.

The new Frontend team (supported by Backend as needed) will take over existing front-end responsibilities over time, and work on one key project: bringing the Peanut experience over from native apps to the web.

Our main product work happens inside cross-disciplinary teams, that we call squads. Those are formed ad-hoc (on a per-project basis) so that we don’t silo anyone into a specific part of the product or software areas.

On top of this, each team member spends every 4th or 5th week tackling smaller projects, ranging from support issues to bug fixing, maintenance, or performance work. We keep our technical debt low on an ongoing basis.

We make pragmatic choices when picking tools. We communicate mostly through Slack and manage work and prioritisation with Monday, review code through Github pull requests, and meet with Whereby or Google Meet.

We have few meetings: a short, daily standup, a weekly town hall meeting to discuss product and/or analytics, plus ad hoc squad meetings as required during a given squad project.

Your role

On a day-to-day basis, your work will be a combination of:

  • Implement features.
  • Given high-level requirements discussed with your current squad, you’re responsible for modelling and implementation, through to testing, delivery and maintenance of individual features.
  • Support others.
  • Within Engineering, this means contributing to code reviews, as well as co-designing APIs or data models with others — whether or not they are in your current squad. Within the Product organisation, you may be called to assess technical feasibility and difficulty of upcoming projects.
  • Continuously improve code and operations.
  • You’ll keep your eyes peeled for areas of technical debt to fix, performance or scalability issues, production bugs, and plan work to address these with the Backend team.
  • Share your ideas.

You’ll participate in ideation workshops, as well as be expected to submit ideas for new features, be they technical or user-facing. Everyone contributes to the product because we’d never want to miss out on good ideas.

Job requirements

About you

This role might be for you if:

  • You want to build technology for good.
  • You feel that our work ethic resonates with yours, and you see how they can act as guidance for your day-to-day work.
  • You have 5+ years of frontend engineering experience, including 3+ years with the React ecosystem.
  • You have built elaborate front-ends that leverage local storage, lazy loading, code splitting.
  • Web standards have few secrets for you (HTTP, HTML, CSS, JS, the DOM).
  • You have strong computer science fundamentals, from data structures to algorithmic complexity.
  • You have worked in a startup environment.
  • You have worked remotely, and/or with a distributed team.
  • You are fluent in written and spoken English.
  • While not a requirement, it’ll help if you’ve done some backend work in the past, particularly in Ruby.

Benefits

  • Competitive compensation. Your package will vary based on your skill and location.
  • If you live in the UK, your gross salary will be between 75,000 GBP and 95,000 GBP per year.
  • If you live in continental Europe, your compensation will be between 90,000 EUR and 120,000 EUR (or local currency).
  • Work anywhere. We care about the work done, not where you do it from. Most of us work remotely full time, and we’re equally happy if you’d prefer to work from our London HQ or anywhere in Europe. You just need a suitable workspace and a good internet connection.
  • (Note that we do not currently consider candidates living outside the UK or the EU)
  • Flexible schedule. Many of us are parents and/or have various personal life commitments. While we typically work around 40 hours a week, how you schedule your work hours is up to you.
  • Travel to meet the team (post-pandemic!)

We know from experience that face time matters in distributed teams. Every 2 months, we gather the team for 3 to 4 days somewhere in Europe, and use that time to run workshops and socialise.

Hiring process

Still reading, but not entirely sure the role is a good fit for you? That’s okay! We’re happy to consider you. Here’s what the process looks like:

  • Submit your application using the link below. This includes a resume and answers to a few practical questions. No cover letter is needed, although a few words are appreciated.
  • Application screening. We read every application to understand your motivation, skills, and experience. Once your application has been screened, you’ll receive a response whether the outcome is in your favour or not.
  • Initial interview and Q&A with one of our engineers.
  • Technical interview with a full-stack engineer. We’ll ask you to complete a small programming task ahead of the interview.
  • Interview with Michelle (Founder and CEO) and Julien (CTO).

Our commitment

We’re building a product for people who have been traditionally underserved, and we’re committed to hiring people with different backgrounds and experiences. It helps us build a better product, make better decisions, and better help our users.

We’re committed to building a workforce that’s as diverse as the community of users who love Peanut! So, we welcome everyone to our team. If you need reasonable accommodation at any point in the application or interview process, please let us know. In your application, please feel free to note which pronouns you use (for example - she/her/hers, he/him/his, they/them/theirs, etc).