Hadrian
Software Engineer, Builder Tools
About this role
Hadrian seeks a Software Engineer to build and maintain the CI/CD infrastructure, internal tooling, and AI-assisted development workflows that empower engineering teams across the company. You'll design high-leverage systems that directly impact developer productivity and help accelerate manufacturing innovation in aerospace and defense.
What you'll do
- Build and maintain CI/CD pipeline libraries for multi-team use across build, release, and deployment
- Design internal tools, APIs, and CLI utilities that reduce developer friction and automate routine engineering tasks
- Make internal systems AI-ready for coding agents by building harness tooling and feedback loops
- Instrument developer productivity systems and surface bottlenecks through metrics
- Partner with application teams to identify needs and drive adoption of CI/CD best practices
- Participate in on-call rotation and contribute to incident postmortems
What they're looking for
- CI/CD pipeline design and infrastructure (5–8 years experience)
- Programming in Go, Python, TypeScript, or similar languages
- Docker and container orchestration (Kubernetes or equivalent)
- Git and source control concepts
- Complex systems troubleshooting and debugging
- Developer experience and API design
- AI coding tools and agent integration (preferred)
- GitOps principles (preferred)
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Hadrian
Hadrian builds aerospace and defense manufacturing systems, offering enterprise software platforms, advanced tooling design, and highly automated production capabilities for the sector. The company is hiring full stack engineers, manufacturing and tooling specialists, infrastructure and identity management experts, and workforce systems architects to support its rapid scaling.
View all jobs at HadrianLikely interview questions
- Walk us through a complex CI/CD pipeline you've built or maintained. What were the key design decisions, and how did you measure its impact on developer velocity?
- Describe your experience building internal developer tools or APIs. How did you ensure adoption across engineering teams, and how did you handle feedback?