Checked at the source 1 h ago
With your free Joonow account, you continue to the company site and the job stays in your applications.
No real employer charges a fee, a course, an exam or a uniform. Suspicious?
Job description
About Revel
At Revel, we are revolutionizing the way the world's most critical hardware is controlled—across aerospace, automotive, energy, and manufacturing sectors. Our next-generation software stack combines an intuitive command/control interface, a specialized programming language tailored for hardware control, and a high-performance runtime environment. We empower engineers to build, test, and deploy critical systems rapidly, reliably, and safely.
The role
We’re building a new data platform to add to Revel’s current products. The data platform receives, stores, and serves telemetry from our customers’ hardware. It helps customers develop and operate their hardware faster and more effectively.
As a Site Reliability Engineer, you will join very early in the project and help to decide how we deploy, run, and maintain the platform in every environment our customers need.
Problems you’ll work on
One platform, every environment. The platform must run in commercial cloud, in government cloud, and on-prem. You will design one system that deploys to all three, not three separate systems. This starts with technology choices. You will pick tools that are truly portable, not tools that lock us into one environment.
Environments that stay healthy. Launch is only the start. Every environment needs upgrades, patches, and sometimes hands-on hardware maintenance. You will make this work repeatable, so the effort does not grow with each new environment.
Security for regulated customers. Government and defense customers have strict security requirements. You will design the networks, access control, and system hardening that meet those requirements and pass audits.
Reliability from day one. Customers record data during hardware tests that can be expensive or impossible to repeat. You will decide what “up” means for them. You will set SLOs and error budgets, and build on-call and incident practices before the first big outage, not after it.
Growth in data volume. As customers connect more hardware, the platform receives more data. You will plan capacity, keep performance high, and help to control cost as the data grows.
What you’ll do
Own the infrastructure for the data platform in every environment: networks, firewalls, access control, capacity, and cost
Choose portable technology, and write infrastructure as code so each new environment follows a tested, documented process
Keep every environment healthy over time with upgrades, patches, tested backups, and hardware maintenance when needed
Agree on SLOs and error budgets with the team, and use them to decide when to ship and when to fix
Build the observability stack, and set the standard for alerts: few, clear, and actionable
Start on-call, incident response, and blameless postmortems, and make sure each incident leads to a lasting fix
Give engineers the pipelines, tools, and runbooks to ship and run their services safely on their own
Review designs with our distributed systems engineers to find failure modes and operating costs before launch
Lead security and compliance for government customers, and work with customer IT and security teams on deployments, audits, and accreditation
Help hire and mentor our second SRE
What we are looking for
You’ve designed and run a production environment yourself, including networks, security, and identity.
You choose technology for the long term. You can explain when a tool is portable enough to run anywhere, and when a managed service from one cloud provider is worth the lock-in.
You write infrastructure as code and automation that other engineers trust and use (e.g., Terraform, Kubernetes, and CI/CD tools).
You’ve defined SLOs and built the alerting and incident practices around them, not only followed ones someone else set.
You’ve run data-heavy distributed systems, including high-availability databases. You can read and change the application code that runs on them.
You want to make other engineers better at running their services, not do all the operations work yourself.
You’re comfortable with hands-on work, from cloud accounts to physical servers.
You want to be the first person in a role and define how it works.
Experience with government cloud (e.g., AWS GovCloud), FIPS or FedRAMP, air-gapped deployments, or aerospace, defense, or industrial environments is a plus.
Join us to redefine what’s possible in software for hardware.
ITAR Requirements
To conform to U.S. Government export regulations, applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C. 1157, or (iv) Asylee under 8 U.S.C. 1158, or be eligible to obtain the required authorizations from the U.S. Department of State. Learn more about the ITAR here.