Senior Platform Engineer: Storage

Contenido del rol extraído en secciones para revisar más rápido.

Design and evolve multiple production Ceph clusters, from hardware design, to driving network requirements to configuring, tuning and operating clusters and their clients
Create efficient, generalizable APIs using systems/kernel features to provide safe, as-fast-as-possible live-migrations of stateful workload between hosts
Design and build API and Orchestration services to tie storage primitives to higher level primitives using Go, gRPC, ScyllaDB and Temporal
Write Engineering Requirement Documents to take something from idea, to defined tasks, to implementation, to monitoring it’s success
Design build a suite of storage primitives that can be used by customer applications, internal services and enable higher level platform features such as streaming image pulls or movable build caches

Experience architecting and implementing distributed systems. You enjoy building fault tolerant, resilient, and scalable services
Production experience with distributed block device systems (e.g Ceph) or a solid understanding of network storage cluster design from first principles
Understanding and experience with current gen filesystems (Ext4, ZFS, BTRFS). Bonus points for next gen (EROFS, bcachefs)
A solid intuition about how long your solutions will last. All systems age. In startups, we can hope for 2-3 orders of magnitude, or 12-18mo.
The tact to implement your solution, creator monitors for it’s error boundaries, and document any requirements for when you’re not around
A great sense of direction and prioritization when it comes to dealing with the ambiguity of an early stage startup
A sense of grit to dive into a problem, implement a solution, scale that solution, and replace it when needed
A great set of communication skills for getting your point across, solution implemented, and beyond

We're distributed ALL across the globe, and that's only going to be more and more distributed. As a result, stuff is ALWAYS happening.
We do NOT expect you to work all the time, but you'll have to be diligent about your boundaries because the end of your day may overlap with the start of someone else's.
We're a small team, with high ownership, who are not only passionate about what we do, but seek to be exceptional as well. At the time of writing we're 21, serving hundreds of thousands of users. There's a lot of stuff going on, and a lot of ambiguity.
We want you to own it. We believe that ownership is a key to growth, and part of that growth is not only being able to make the choices, but owning the success, or failure, that comes with those choices.

Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.
Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.
Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.
Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.

This is completely open ended and we're just trying to see who you are, what you want to do, and where you wanna go.
Asynchronously implement the following:
Pre-interview: Design a Storage Engine to power something like Railway's Volume
You can, and SHOULD! ask us questions ahead of time.

Roles similares