Software Engineer, Infrastructure
Job description
About the role
The platform scales securely as customer workloads grow, and critical infrastructure components remain reliable under load. Roadmap and architecture decisions direct identity security for enterprises and startups.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Ownership of critical infrastructure components keeps the platform stable, secure, scalable, and performant. Product engineers use tools and systems created and refined to unblock daily workflows. Security and engineering teams interact directly to turn product feedback and issues into solutions. Infrastructure decisions for roadmap and architecture serve Databricks, Figma, and diverse customers. Engineering best practices and processes are documented and improved to support long term maintainability.
Requirements
The posting states a bachelor's degree requirement. The platform operates on Kubernetes, so Kubernetes services are managed. Backend services are built with Golang, while identity data at scale is handled by Postgres and Redis. Terraform and GraphQL enable infrastructure as code and programmable, observable systems. TypeScript and React fluency support frontend tooling and internal dashboards. Experience with cloud providers such as AWS or GCP demonstrates distributed infrastructure scaling at scale. Four or more years of full-time software engineering or equivalent building large distributed systems is required.
Practical notes
The team works closely with leadership, product, and other engineers, and operates under a degree requirement as stated. Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
Modern identity governance focuses on access control for AI driven workflows. Security teams rely on clear controls without slowing innovation. Infrastructure tools include cloud platforms, containers, databases, and declarative configuration. Engineering practices emphasize reliability, observability, and maintainability. This role operates in fast growing technology companies with high impact decisions.
Questions to ask
Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.
About the company
Security: At Opal, we're building modern identity governance for the AI era - intelligent access management that empowers enterprises to move fast while staying secure. Our mission is to bring clarity, control, and confidence to complex enterprise environments, helping teams govern access without slowing down innovation.