Senior DevOps Engineer

We are looking for an excellent Senior DevOps Engineer to join one of Sweden's fastest growing start-ups which is backed by Nvidia, Microsoft and AWS. The company also operates under the Inspection for Strategic Products.

Location: Fully remote within India. From 2027 you join our Bangalore office as part of the founding local team 

Employment: Full time, permanent 

Start: As soon as you are available

About the job

Antrino Labs is building the platform that makes every square meter intelligent. The physical world runs on processes nobody can actually see. Goods move, people queue, machines idle, space goes unused, and the decisions made about all of it are based on samples, guesses, and reports written after the fact. Software solved this for the digital world twenty years ago. Everything online is measured, understood, and acted on in real time. The physical world is still dark.

We are building the execution layer that closes that gap. Antrino lets any organization deploy vision intelligence into a physical space and get back what is actually happening there, as structured, queryable, real time information rather than footage. Not a research project, not a custom integration, not a team of ML engineers. A platform, where you describe what matters to you and deploy it.

What people build on it is broader than what we designed for. Operators use it to understand processes, find where time and space are being wasted, measure flow and utilization, catch problems while they are still happening, and turn all of it into data good enough to act on.

Everything is built on Privacy by Design. Data protection and GDPR compliance are part of the architecture, not a layer added afterwards.

We recently closed our Seed round, announced together with Dagens Industri, and we are scaling to meet demand. Antrino Labs is also registered with Inspektionen för strategiska produkter (ISP), the Swedish authority for strategic and dual use products.

The role

We are hiring an experienced DevOps Engineer to own the infrastructure this platform runs on.

We will be honest about where we are, because it defines the job. We got here fast by shipping. Our services run on virtual machines managed with a process manager, deploys go out through GitHub Actions, and it has worked well enough to sign customers and prove the product. It will not carry us to where we are going. Turning that into infrastructure that holds thousands of continuous workloads across many customer environments, with real isolation, real observability, and deploys nobody is afraid of, is the work. You would be the first person whose whole job is that.

The workloads are not typical web traffic. Continuous inference pipelines run for weeks at a time, each consuming compute every second it is deployed. Media moves constantly through ingestion, conversion, and storage. Some of our compute sits inside customer facilities on hardware we reach over a private network, which means fleet management, remote updates, and diagnosing failures on machines you cannot walk up to. Alongside that, our customers are enterprises with security questionnaires, audit expectations, and requirements about where data lives, so evidence and controls are part of the job rather than an interruption to it.

You will have real authority over how this is built. We would rather hire one person with strong opinions formed by having operated production systems than three people waiting to be told what to do.

This is a remote first role today, working closely with the engineering team in Stockholm. From 2027 you will be part of the founding group in our Bangalore office. If you want to be an early face of a team as it forms rather than an employee number in one that already exists, that is the opportunity.

Your main areas of responsibility will include:

• Owning our cloud infrastructure on Azure end to end, including compute, networking, storage, and identity, defined as code rather than configured by hand
• Moving us from virtual machines and process managers to a container and orchestration setup that fits our workloads, and being accountable for that migration landing without breaking customers
• Building deployment pipelines for both the TypeScript product and the Python services, with staged rollout, fast rollback, and environments that genuinely mirror each other
• Owning observability across the stack: metrics, logs, traces, and alerting that tells someone what is actually broken instead of paging them at random
• Running the reliability practice, including on call rotation, incident response, runbooks, and postmortems that produce changes rather than documents
• Managing our media and streaming infrastructure: ingestion, conversion, delivery, storage lifecycle, retention policy, and the bandwidth and storage costs that come with all of it
• Building and operating the fleet of compute that runs inside customer facilities, including provisioning, secure connectivity, remote update, and health monitoring
• Owning cloud spend, including capacity planning, right sizing, storage tiering, and giving the team visibility into what each workload actually costs
• Owning platform security: secrets management, network boundaries, access control, patching, backups, and tested restores
• Supporting our work toward formal security certification and answering the infrastructure sections of enterprise security assessments with evidence
• Building the internal tooling and documentation that let engineers deploy, debug, and operate their own services without routing everything through you

Our stack

You do not need experience with all of this, but you should recognize most of it and be able to argue about it.

• Cloud: Azure, with object storage and GPU backed compute
• Runtime today: virtual machines with a process manager, deployed through GitHub Actions
• Runtime we are heading toward: containers with orchestration, defined through infrastructure as code
• Services: Next.js and TypeScript on the product side, Python and FastAPI for inference and media processing
• Data: PostgreSQL through Supabase, with row level security
• Media: RTSP ingestion, RTSP to HLS conversion, live and archive pipelines
• Edge: compute inside customer facilities, reached over Tailscale

Who we are looking for

• Substantial experience operating production infrastructure that people depended on, including the parts that woke you up at night
• Strong Azure, AWS, or GCP experience, with real depth in at least one and the ability to reason about the others
• Fluent with containers and orchestration, and with infrastructure as code such as Terraform, Bicep, or Pulumi
• You have built CI/CD that engineers trusted, and you understand why they stop trusting it
• Solid Linux and networking fundamentals, including the ability to debug across process, container, host, and network boundaries
• Practical observability experience, and clear opinions about what deserves an alert
• Comfortable writing code, not only configuration. Python, Go, or TypeScript is fine
• Security minded in a practical way: secrets, least privilege, patching, backups you have actually restored from
• Experience with media, streaming, or high throughput data infrastructure is a strong advantage, as is managing distributed or remote hardware
• You prioritize well under real constraints. Early stage platform work is choosing the three things that matter and refusing the other twenty
• You work well asynchronously across time zones, write clearly, and raise problems early
• Excellent written and spoken English

What we offer

• Competitive salary, benchmarked to the top of the Indian market for this level and discussed openly early in the process
• Fully remote within India, with genuine ownership rather than delegated tickets, and a seat in the founding group of our Bangalore office from 2027
• Hardware of your choice and a budget for whatever else you need to work well
• Direct access to founders, to the Stockholm engineering team, and to customers
• Travel to Stockholm to work with the team in person

Process

We review applications continuously and contact candidates we think are a good match.

1. An introductory conversation about your background and the role
2. A technical conversation where we discuss systems you have operated, what broke, and what you did about it. No whiteboard algorithm puzzles
3. A working session with the engineering team on a real problem from our stack
4. A conversation with the founders to discuss terms and your long-term future at the company

References may be requested in the final stage. We aim to keep the process short and to respect your time.

Apply with your CV and, if you have one, a link to something you have built or written. A repository, a post about a system you operated, or a short note on an incident you learned from tells us more than a cover letter.