Member of Technical Staff, Software Factory
New
P
Perimeter ComputeCompute infrastructure
Fully remote in the US.Full-Time
Salary$150K - $250K; $150K – $250K • Offers Equity
Apply NowOpens the employer's application page
Job Details
- Required Skills
- KubernetesPrometheus
Requirements
- Have built and run production software that people depend on.
- Have owned production software when it broke.
- Have built a platform, build system, or deploy pipeline that other engineers chose to use.
- Have helped a team ship faster without increasing breakage and be able to show the results.
- Have carried a pager and converted lessons into checks that caught subsequent problems.
- Have run a restore drill that found a problem before a real outage.
- Get results from coding agents and know which checks keep their work reliable.
- Be able to make and document a difficult stack decision.
- Nice to have: experience with Bazel or other reproducible build systems.
- Nice to have: Kubernetes, GitOps with Flux or Argo, and infrastructure as code with Pulumi or Terraform.
- Nice to have: Prometheus, OpenTelemetry, or similar observability stacks.
- Nice to have: supply-chain tooling such as image signing, provenance, and vulnerability scanning.
- Nice to have: progressive delivery, including canaries, feature flags, and automatic rollback.
Responsibilities
- Choose the stack and document the frameworks used to make stack decisions.
- Own the paved road for building, shipping, running, and retiring services.
- Own the registry for apps, environments, secrets, and stacks, including checks that reject undeclared items.
- Ensure every durable store has a backup, restore path, and recovery drills in development and production.
- Build service identity and short-lived, least-privilege secrets to the security team's requirements.
- Build agent-first tooling for reproducible builds, reliable CI verdicts, and actionable errors.
- Own production deployments, including health checks, verification, fast rollback, and sign-off for hard-to-reverse changes.
- Standardize service levels, observability, and runbooks, and remove alerts that receive no action.
- Turn incidents and repeat findings into checks that prevent the same mistakes from shipping again.
View Full Description & ApplyYou'll be redirected to the employer's site