DevOps Engineer

Orynt is an Abu Dhabi-based subsidiary of CrossAngle, a Series B startup backed by major Korean financial institutions. Our team works across Abu Dhabi and Seoul.

The opportunity

Help design how an AI-driven engineering company runs its systems.

Work directly with Orynt’s founder to build an operating model where LLMs perform much of the investigation and implementation, and engineers provide context, verify outcomes, and remain accountable for production.

For example, an agent might prepare an infrastructure change; you would examine its assumptions, review the proposed changes, and validate the result before deployment. You will help turn these approaches into repeatable automation.

You can learn this approach with us. Strong fundamentals, diligence, and learning ability matter more than prior expertise with AI tools.

What you will help build

Orynt builds orchestration software for regulated financial institutions launching digital-asset services. Our engine coordinates workflows across custody, identity, on/off-ramp services, and ledgers, applies the institution’s policies, and maintains verifiable audit records. As we prepare for production launch, you will help make these systems dependable to deploy, operate, and recover.

The engineering environment includes Go, Temporal, PostgreSQL, AWS, and containerized services. You will work across infrastructure and application boundaries, building both operational depth and a broader understanding of distributed systems.

Your work

Together with the founder, you will progressively co-own cloud infrastructure, CI/CD, observability, incident response, security, database operations, and developer tooling. You are not expected to independently own every area from day one.

Your initial focus will be production readiness: dependable deployments, monitoring, backups, and recovery procedures, alongside technical preparation for SOC attestation.

You will:

• Strengthen operational security: implement least-privilege access, secure secrets management, and infrastructure hardening, with changes reviewed and verified before rollout.
• Turn operational work into automation: use LLMs to investigate and implement changes, then build repeatable workflows with checks, recovery steps, and clear human escalation.
• Solve problems across the stack: follow an issue from infrastructure into application code, including reading and modifying Go when needed.
• Make operations transferable: capture decisions, runbooks, and verification steps so colleagues and automated systems can carry out essential work.
• Support operational assurance: implement technical controls and evidence collection for our planned SOC attestation, guided by an external advisor.

Your main focus will be Orynt infrastructure, with occasional support for customer environments in coordination with their teams.

How we will work together

You will review architecture and operational decisions directly with the founder, with backup from our DevOps team in Seoul. You will help choose which processes to redesign, what agents should handle, and how to verify their work. As your understanding grows, you will increasingly lead these improvements.

Normal working hours follow Abu Dhabi time, with occasional scheduled overlap with colleagues in Seoul. Serious incidents may require response and recovery outside normal working hours, in coordination with the founder and Seoul team.

What you bring

• Around 2–6 years of relevant engineering experience, with evidence that you learn quickly and follow through. The exact number of years is flexible.
• Solid Linux, networking, and programming fundamentals, plus practical experience deploying or operating software in a cloud environment.
• The ability to investigate unfamiliar code, explain your reasoning, and verify a change with tests and system evidence.
• Care and persistence: you notice loose ends, investigate unexpected results, and see work through to completion.
• Initiative and judgment: you propose next steps, communicate clearly, and know when to ask for help.
• A willingness to rethink established practices and test whether a better approach actually works.

Experience with our stack, infrastructure as code, or SOC preparation is useful. You can learn unfamiliar tools and the LLM-driven approach alongside us.