Senior Software Engineer – Backend
Senior Software Engineer – Backend

Senior Software Engineer – Backend

Here's the tl;dr:

This is Rise

We set out to build a company that helps teams make the most of their time. Why? Because time is the most valuable asset we can spend only once. Becoming more aware of the fact that we have limited time is one of our key beliefs. And, not coincidentally, the central point in Rick’s bestselling book, launching internationally in February 2022.

Read more

There are thousands of books and apps that promise more focus and productivity. A lot of them require a healthy dose of discipline. You might be someone who can do that, but most in your team might not. We made it our goal to build a tool that solves a problem instead of yet another complicated workflow to adopt.

From the outset we knew we wanted to build something to help find time for what matters most. Our research confirmed this: most teams know what’s important, they just don’t have the time. Schedules are packed and distractions everywhere. And because everyone has different working schedules – something that’s enlarged since the pandemic – it’s impossible to be mindful of everyones preferences. So we opt for the very next empty spot we can find.

It does not matter how empathetic you are as a leader or co-worker, you simply don't have the time to make it work for everyone.

So when we started building the first version of Rise in May 2021, we set out to fix this. Rise is a webbased calendar that sits on top of the Google Calendar API, so there's no signup or data migration required. We believe building a new client is crucial to drastically improve the UX for scheduling. It's also a differentiator that we believe will boost adoption. Finally: by building our own client it's easier to expand to include other services than if we would build a plugin specifically for Google Calendar.

With the first version of this scheduler ready for us to try, we figured we wanted a way to let teams experience the value of Rise without actually using Rise. To do that we built a feature we called Rise Report. With a single Google login, we analyze all calendars of a team and (virtually) reschedule as many internal events we can find using our scheduler. Before and after we measure time to focus (at least 120 mins of uninterrupted time) and fragmented time (the pockets of time shorter than 120 mins).

image

The results absolutely blew us away. Without changing how many meetings teams have, we estimate that Rise can get back hundreds of hours to focus every week. There's even more potential, since the scheduler is quite conservative: we skip events that are long, with external people or are overlapping other events, for example. So far we ran the reports for about 30 different companies, and here are some results:

Companysize
Focustime won per week
35
26 hours
67
100 hours
46
48 hours
9
15 hours
20
45 hours
83
304 hours

image

Overview

The Rise backend powers our front-end and apps on one side, and integrates with downstream calendar providers like Google Calendar on the other. Additionally we've built a scheduling engine that can instantly rank and score timeslots for our Find a Time feature. The initial backend is built with a Heroku/Ruby/PostgreSQL/Redis/Sidekiq stack. We are looking for a senior backend engineer to help launch and scale the Rise product.

What you'll be working on 💻

As an early engineer you'll work on many different aspects of the product. A few examples:

  • Collaborate with our client and mobile teams to define a scalable and extensible API
  • Dive deep into our event scheduling engine to improve performance or extend the capabilities
  • Optimize our development workflow (for example making the first-time local setup for new hires easier, to setting up a staging environment, improve our build pipeline)
  • Evaluate and utilize new libraries, frameworks and and tooling
  • Involvement in hiring and onboarding of new engineers

What our ideal candidate looks like 💅

  • Significant experience in building distributed, scalable, performant and asynchronous backend applications in the cloud (AWS, GCP, etc)
  • Significant experience with at least one scripting language, preferably Ruby 💎
  • Cares a lot about high quality, readable, structured object oriented code. Advocates best practices and architecture patterns. Is able to make trade-offs between extensibility, optimization and execution speed. Empowers others by reviewing code.
  • Proficient with different types of testing (integration, unit, stress, etc)
  • Experience with system observability: automates eyes and ears throughout the stack with tooling (Grafana, New Relic, Sentry, etc). Familiarity with incident handling is a plus.
  • Has a habit of being paranoid about security and privacy (input validation, network encryption, authentication, authorization)
  • Is autonomous, able to independently pick up tasks and full projects and work through them end-to-end
  • Is product and user minded: is always focused on how their work will impact or optimize the experience of Rise users

We realize that as a founding team we're from similar backgrounds, that we have unconscious biasses and that we have work to do here. This is why we explicitly want to invite and encourage people from underrepresented groups to apply.

👉
Interested and ready to Rise? We'd love to jump on a call with you. Email willem@risecalendar.com or @wspruijt at Twitter (DM's are open).

image

Refer a friend and get €5k when they join. Read more

Your Future Colleagues

image

Emiel Janson (left)

Designed digital products that are used by millions of people. Worked for companies like Tidal, Palantir, Blendle and designed the Dutch COVID notification app.

Shipped 8 of his own Mac/iOS apps before. Many of which became a top paid app.

Rick and Emiel worked closely together at Blendle for almost three years.

Rick Pastoor (middle)

Authored a bestselling book on productivity (GRIP, sold over 75.000 copies in the Netherlands). Rights sold to the US, UK, Spain and Finland, Israel, Germany, more to come.

Led product and engineering as CPO at Blendle (millions of users, consumer product, micropayments and subscription). Blendle was sold to Cafeyn in 2020.

Has engineering background with CS degree.

Willem Spruijt (right)

Engineer with a keen eye for detail and skilled in balancing quality and speed of development.

Responsible for large parts of the payments infrastructure at Uber and building out the Amsterdam engineering site from 7 to 220 engineers in 5 years.

Found and sold 2 companies before that: Yunoo (personal budgeting, sold to AFAS) and Fosbury (digital ticketing platform).