Lead Infrastructure Engineer

About Nomain

Nomain is a deep-tech startup accelerating legacy code modernization. Our AI-powered platform extracts decades of hidden insights from legacy mainframe codebases and presents them through an intuitive interface for developers, business analysts, and architects alike.

We believe AI will accelerate experts—not replace them. Great software systems are built by people who have the right context and the right tools. Our product delivers that specific context while leaving the ultimate decisions in the hands of the experts.

Our Culture

At Nomain, we are customer-obsessed. We work closely with our users to understand their challenges and build solutions that truly make a difference. Our culture is built on ownership, transparency and continuous learning. We’re a tight-knit, ambitious team that values curiosity, autonomy, and building things that matter. Everyone has a voice, and we’re united by a shared mission to solve complex problems with practical and impactful solutions.

The Opportunity

We're at an inflection point. Our platform is gaining traction with two distinct customer models: pure cloud SaaS customers running in our multi-tenant environment, and customers running in their own cloud (BYOC) with a split data/control plane architecture. We need to build and scale the infrastructure that supports both.

We're looking for our first infrastructure engineer to own these systems.

You'll join as a founding infrastructure engineer, working directly with the CTO and founding team. The infrastructure decisions you make now will shape how we operate as we scale from where we are today to serving hundreds of customers with diverse deployment requirements.

We've established good engineering practices—infrastructure-as-code, GitOps workflows, ring-based deployments, and architecture decision records. Now we need someone who can take these foundations and scale them to meet the complexity of multi-cloud, multi-environment deployments.

You'll have the autonomy to choose the right approaches and tools, with the responsibility to make them work reliably. As we grow, there's a natural path to building and leading the infrastructure team.

What You'll Build

You'll design and implement infrastructure for two distinct but interconnected deployment models. For our cloud SaaS customers, you'll own and scale our multi-tenant environment. For BYOC customers, you'll build the provisioning automation and control plane that manages their data planes running in Azure, AWS, GCP, and future environments.

This means evolving our GitOps workflows to handle both centralized and distributed deployments, establishing Kubernetes patterns that work across both models, and creating observability systems that provide unified visibility regardless of where workloads run. Security is foundational to everything we build—you'll work within our zero-trust architecture and help strengthen our infrastructure and application security as we progress towards ISO 27001 certification.

We're building for cloud-agnostic deployment—leveraging technologies like Azure Arc to enable consistent management across any public cloud provider and preparing for on-premises deployments. The technical challenges are real: reliable automation across diverse environments, multi-tenant isolation and security, multi-cloud orchestration, scalable observability, and continuous deployment practices that teams can trust.

You'll be solving these problems with direct impact on our product and customers.

If you have experience with MLOps or infrastructure for AI workloads, that's a bonus—we're exploring capabilities in this space, and your expertise would help shape our approach.

What We're Looking For

We need someone who has operated production infrastructure at scale and understands what it takes to build reliable systems. You should be fluent in Kubernetes, comfortable with cloud provisioning, and treat infrastructure-as-code as the baseline. Experience with multi-tenant architectures and understanding the security and isolation requirements is valuable.

Experience in early-stage environments is valuable—you know how to balance building quickly with building sustainably. You're comfortable making decisions without perfect information and documenting those decisions for the team.

What matters most: you can look at complex infrastructure challenges and see practical solutions. You ship working systems that scale, not perfect architectures that never launch.

Beyond technical skills, you bring the mindset that aligns with our culture:

  • Customer-obsessed: You understand that infrastructure exists to serve customers. You think about the impact of your decisions on user experience and work backwards from customer needs.
  • Solution focused: You don't see a problem, you see an opportunity for improvement. You don't focus on the obstacles, but on the possible paths between them or how to remove them.
  • Transparent communication: You share context openly, document decisions clearly, and aren't afraid to admit when you don't know something. You make your reasoning visible to others.
  • Continuous learner: Technology evolves, and so do you. You stay current with infrastructure trends, experiment with new approaches, and share what you learn with the team.
  • Curious and autonomous: You ask why things work the way they do and take the initiative to improve them. You don't wait for perfect requirements—you gather context and move forward.
  • Practical problem solver: You focus on impact over elegance. You build solutions that work and matter, not showcases for technical sophistication.
  • Collaborative contributor: You value everyone's input and contribute your voice constructively. You make the people around you better through mentorship and knowledge sharing.

Why This Role

Technical ownership: You'll make the foundational infrastructure decisions. The systems you build will be yours to own and evolve.

Direct impact: Your work directly enables customer growth and new capabilities. There's no separation between infrastructure work and business outcomes.

Growth path: This is a founding role with clear trajectory to infrastructure leadership as we scale the team.

Founding team access: You'll work directly with the founding team, understanding business context and technical requirements without layers of abstraction.

Greenfield opportunity: Most infrastructure decisions are still ahead. You'll define the patterns and practices we use going forward.

Technical Environment

  • Platform languages: C#, TypeScript, Python
  • Cloud strategy: Azure, AWS, GCP, with Azure Arc for hybrid management
  • Future direction: Any public cloud provider and on-premises support
  • Current practices: GitOps, ring-based deployments, LADR, IaC, zero-trust architecture
  • Security posture: Infrastructure and application security embedded in practices, working towards ISO 27001
  • What you'll work on: Scaling these practices for multi-environment complexity

Details

  • Location: Remote
  • Compensation: 5000-7000€/month + options program possibility

How to Apply

If this resonates, tell us about infrastructure systems you've built and the impact they had. We're interested in how you think about technical problems and the decisions you make when building foundational systems.

Send your application to hector.tortosa@nomain.com.