Senior Software Engineer (iOS)

Job description Why join usbuild tech for good (really)true remote environment (all of Engineering is full remote)very experienced team (10y+ average experience)unique tech & product challengescompetitive compensation (90-120 k/year)ðª Your team and contextYou'll be joining our Mobile team as our third iOS engineer. This team is responsible for designing, building, testing, and operating our native apps. Your peers will also include two Android engineers.ð Your missionsOn a day-to-day basis, your work will be a combination of:Deliver projects. Given high-level requirements discussed with your current squad, you're responsible for architecture, technical design and programming, 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 the 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, and production bugs as well as plan work to address these with the rest of the engineering 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.ð BenefitsCompetitive compensation: 90-120k /year depending on experience.Share options.Work anywhere (in Europe).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.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. Job requirements Professionally,You have 3+ years of building native iOS apps.You have solid knowledge and experience in Swift.You can demonstrate a good understanding of SwiftUI and the benefits/tradeoffs when compared to UIKit.You know how to write testable code and have an automated testing mindset (we care about our unit/UI test coverage).You have experience with CI/CD including automating releases (we use Xcode Cloud to ship weekly releases)You have strong computer science fundamentals, from data structures to algorithmic complexityYou can implement and integrate with network modules (we are heavy users of async await)You have worked in an early-stage startup environment.You want to work remotely, with a distributed team.Personally,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 are fluent in written and spoken English.You live in Europe (incl. EU, EEE, or UK).You are willing to travel 3-4 days every 2-3 months to meet the team in person.ð About PeanutNo woman should have to navigate motherhood without a support network.Our mission is to provide a safe social network 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 2 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.Our team of 33 people is multidisciplinary, distributed, diverse, and experienced.Some of us have previously worked with 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.ð§‍ð» How we workOur main product work happens inside cross-functional squads. Those are newly formed every 3-4 months 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 tasks, 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 good tools. We communicate mostly through Slack and manage work and prioritisation with Notion, 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 chats as required during a given project.ð Our work ethicWe 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.ð Hiring processStill reading, but not entirely sure the role is a good fit for you? That's okay! We're happy to consider you and answer your questions. Here's what the process looks like:Submit your application. This includes a resume and answers to a few practical questions. No cover letter is needed, although a few words are appreciated.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.Intro interview and Q&A with one of our engineering managers.Technical interview with an iOS engineer. We'll ask you to complete a small programming task ahead of the interview.Final interview with Julien (our CTO) and an engineering manager.Our commitmentWe’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).