You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Early Window: Closes in
Company hidden

Staff Engineer On Prem

  • Remote
  • 6+ years

Salary

Not stated

Similar roles pay $155K - 240K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company is building its first on-premises product: a version of its existing CI platform that customers install, deploy, upgrade and run in their own environments, without the company operating it.

The work means adapting a mature application to new environments by changing its architecture, creating reusable deployment and versioning processes, and adding features and tooling that make it a solid product. The team spans application software, infrastructure and customer experience and works alongside the Product, Billing, Platform and Reliability teams.

This is a hands-on technical leadership role. You will decide which questions need answers, make those calls, and define the work that senior engineers carry out. You will also write software yourself.

Current challenges include packaging the application so it can be installed, configured and run where the company has no access; handling version compatibility, deployment order and migrations so that retries, timeouts and partial runs neither repeat actions nor lose progress; setting access, control, administration and audit boundaries when the customer and the company share operation; giving other teams a safe, considerate and fast way to build for on-prem; and making complex systems understandable for customers and operators, even where a technically correct design would confuse them.

A typical day may involve planning how a set of services gets versioned and deployed in sequence across customer environments, reviewing a senior engineer's decision and its effects on security, upgrades or customer data, splitting an architecture change into pieces the team can own, prototyping and measuring options before committing, agreeing a golden path with another team, writing a technical case for those it affects, and coding on the riskiest parts of the system.

Responsibilities

  • Own major technical direction for the on-prem product.
  • Design core systems with clear interfaces and safeguards covering security, version compatibility, deployment order, migrations, administration and auditing.
  • Identify open decisions, make them, and turn them into well-scoped work for senior engineers.
  • Tell apart decisions engineers can take alone from critical ones; step into the critical ones, explain their implications and make sure the right choice is made.
  • Design golden paths so the Product, Billing, Platform and Reliability teams can build safely, considerately and quickly in a shared environment.
  • Balance reliability and security against a product that is simple to use and run.
  • Collect evidence, build clear technical cases, decide, and see the work through to delivery.
  • Prototype architecture changes, measure trade-offs, and work with other engineering teams to take the chosen approach to production.
  • Write application code, APIs, infrastructure automation and tooling on the highest-risk, most complex parts of the system.
  • Develop other engineers through design reviews, documentation and pairing, and help them work in unfamiliar parts of the stack.

Requirements

  • The team is built from complementary strengths: you need deep experience in several areas, good judgement, and the ability to pick up the rest.
  • Production software engineering: you have built and supported software people depend on, and can explain your decisions, trade-offs and outcomes after release.
  • AWS, Kubernetes and infrastructure as code: you have run production systems on AWS and Kubernetes and managed infrastructure with Terraform or a comparable tool.
  • Technical direction: you have set direction for a product, platform or large system and taken it to production. Experience in a nearby area, or real depth in one the team can build on, is enough.
  • Decision judgement: you know which decisions others can make alone and which need closer review, and you can explain a decision's implications to the people making it.
  • Cross-team delivery: you can get several teams to agree on an approach and deliver work that depends on them.
  • Security boundaries and shared ownership: you can reason about access, control and responsibility when a product is run jointly with another company. This may come from technical controls, enterprise integrations or designing developer or customer workflows; a security job title is not required.
  • Developer and customer experience: you consider how people use and run a system, including where a technically correct design leaves them confused or unable to work.
  • Operational judgement: you account for reliability, observability, safe change and recovery while designing and building, rather than leaving them to others.
  • Communication and collaboration: you explain decisions, ask questions, resolve disagreements and make room for other views across a distributed team.
  • Useful additional experience: CI/CD, developer tooling or distributed systems.
  • Useful additional experience: enterprise software, integrations, or identity and access workflows.
  • Useful additional experience: remote application upgrades, database migrations or observability.

Conditions

The role is remote-first and works asynchronously by default: reasoning is written down, meetings are used deliberately, and focused work time is protected.

Benefits

  • A compensation package made up of salary, equity and locally relevant benefits.
  • Flexible remote work built around clear writing, careful collaboration and deep focus.
  • Significant infrastructure work for a CI platform that has to keep up with changes in how software is built.
  • Real ownership of work that visibly shapes the platform, customers and business.
  • A welcoming team that listens to different views and lets people learn from honest mistakes.

About the company

Company hidden

  • Industry: SaaS

Your chances

Still hiring, not crowded yet, and you'd be among the first.

  • 15 checks run
  • 4 good signs
  • 1 red flag

Still hiring?

10 checks

Actively hiring

In its favour2

  • Still on the company's own careers site, checked 1 h agoModerate evidence
  • Found in the last 48 hours, before the big job boardsModerate evidence

How crowded?

5 checks

Low

In its favour2

  • In its Early Window: not on the big job boards yetStrong evidence
  • Senior level: far fewer people qualifySlight evidence

Against it1

  • Remote from anywhere: the widest pool of applicants there isModerate evidence

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details11 facts · Role, Location, Compensation, Company
Tech stack
  • AWS
  • Kubernetes
  • Terraform
  • CI/CD
Seniority
Staff
Equity
Equity offered
Industry
SaaS
Specialty
Backend
Region
United States
Show 5 more factsShow less

Role

Category
Development
Specialty
Backend
Seniority
Staff
Experience
6+ years
Tech stack
  • AWS
  • Kubernetes
  • Terraform
  • CI/CD

Location

Work model
Remote
Region
United States

Compensation

Salary
Salary by agreement
Pay period
Annual
Equity
Equity offered

Company

Industry
SaaS

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason