Cronofy's mission is to Schedule Everything For Everyone. Over the past 8 years we’ve grown a self-sustaining, profitable business on our enterprise-ready Scheduling API. We’re now building a direct-to-user offering in the form of our Scheduler so we can improve the scheduling workflows of even more people. About the role
We’ve done the hard work of synchronising with all the major calendar services and pushing that data into our Availability Engine. We’re now doing the really hard work of making that power accessible to everyone, not just developers, in a way that respects their privacy.
Building such a product requires a different set of skills to building an API, and so we’re looking to expand our team. Our engineers tend to be full-stack with an area of specialisation, but we’re keen to speak to any engineers familiar with the process of building and maintaining a product over time.
We are looking for people who can, or aspire to, shepherd features from idea through to real-world usage, the experience to make the hundred small decisions along the way that requires, and the humility to ask for feedback at the right times.
We strive to enable people to look to for guidance when needed, not permission, and to provide the resources necessary for you to be self-sufficient and fulfil your potential. As a team we aim to work together to produce ideas and products greater than those we could alone.
You can find out more about our department and some members of our team on the Cronofy engineering department’s about page.
How we work
Remote-first as an engineering team before the pandemic, we’re moving between fully remote and remote-first as is sensible. We value the higher quality of communication you get in the real-world interaction and so like to take advantage of that where possible.
The engineering team currently covers the UK and Spain. We meet in a mixture of London (office) and Nottingham (HQ).
As a team we have a daily sit-down, and weekly planning/review meetings. As a company we have a regular all-hands call to share our experiments and challenges. We use our principles to guide our behaviour as people, and our engineering principles to guide our choices as we developer our platform.
Departmental meetups are likely to be at least quarterly monthly once they can happen again, all travel and accommodation necessary are covered by the company through your own prepaid card.
We aim to meet at least annually as a whole company which will hopefully be less challenging going forward.
How you'll work
Practices such as pairing are neither mandated nor discouraged. We trust you to know how you work best, we only ask that you keep the team informed of your progress and ask for help when needed.
We're strong on compliance but this doesn't mean you have to deal with an arduous development process. Github PRs require the automated test suite to pass (which you will likely have added to), and approval by a peer, before they can be merged. From there, the build and deployment process is automated.
This all generates the audit trail necessary to show we follow our change management process.
On DORA metrics we rank as elite performers with the ability to make changes to production on-demand in under an hour (time from commit to production rollout is 10-15 minutes).
Like all of our processes, they are lightweight, fit-for-purpose, and open to change when we find them lacking.
We pride ourselves on happy customers, so part of your responsibilities are fixing bugs, sharing the technical support, and improving our documentation to reduce the amount of direct support we need to provide.
Our stack
Terraform, AWS, Postgres, Redis, Kubernetes, Ruby on Rails, React, SASS form the core of our stack.
We also have Go in our toolset for situations where performance is paramount.
Familiarity with any of these is a benefit, none of them are essential as you’ll be smart enough to learn what’s necessary with our help.