DevOps Engineer

Engineering

The DevOps Engineer at Hyper Solutions plays a critical role in the cloud infrastructure, release, and reliability practices that support Hyper’s products. This position is responsible for designing and operating the AWS infrastructure the platform runs on, the release pipeline, the incident response process, and the on-call rotation. The role reports to the VP of Software Engineering.

This role operates at the intersection of infrastructure engineering, operational process design, and engineering governance.

The DevOps Engineer partners closely with Engineering, Security, and Quality leadership to define how the organization detects, routes, and responds to operational problems and owns the written policies that govern that work. Those policies are version-controlled documents that change by pull request and are reviewed like code.

This position is well-suited for a systems-oriented engineer who is comfortable owning both the infrastructure and the operational practices that govern it, and who treats written process as leverage rather than overhead.

Core Responsibilities

• Design and operate the on-call rotation, including its structure, rostering, escalation model, and supporting tooling.
• Own the incident response process, including triage, severity assignment, escalation paths, and post-incident review requirements.
• Own the release pipeline that moves code from merge to production, including rollback procedures.
• Architect, operate, and evolve Hyper’s AWS cloud infrastructure and the Terraform that describes it.
• Shape how AWS environments are structured, isolated, and governed as the product portfolio expands, including account strategy, preventive controls, and identity.
• Author and maintain operational policy covering on-call, incident response, and release management as version-controlled documents subject to review.

Additional Responsibilities

• Extend infrastructure-as-code and continuous delivery practices so that infrastructure changes are reviewed, repeatable, and auditable by default.
• Strengthen how operational problems are detected, routed, and responded to, and evaluate what tooling investment is warranted as the team grows.
• Partner with product engineering teams so that new workloads, including a new IoT analytics platform, land natively within the cloud architecture rather than being retrofitted into it later.
• Partner with Security and Quality leadership on architecture and operational standards.
• Review infrastructure and pipeline changes contributed by other engineers.
• Maintain operational documentation including runbooks, escalation paths, and architecture decisions.