Founding Backend/Systems Engineer

About REM Labs

REM Labs is building an autonomous software delivery platform that executes engineering workflows end to end with enterprise-grade reliability, control, and governance.

As AI systems begin participating directly in engineering workflows, the hard problem is no longer output generation or agent orchestration. It is reliable execution, safety, and explainability.

We are building the execution infrastructure that makes this possible.

Role Overview

We are hiring a Founding Backend/Systems Engineer to help build the core execution systems powering REM.

This is a deeply technical founding engineering role focused on backend systems, execution infrastructure, workflow orchestration, distributed state management, integrations, and runtime reliability.

You will work directly with the founder and early engineering team to design and build the systems that allow autonomous engineering workflows to execute safely across real enterprise environments.

This is not a conventional CRUD backend role.

The problems involve long-running execution workflows, distributed coordination, failure recovery, retries, state management, system integrations, execution guarantees, and observability.

We are looking for engineers who are strong builders, think in systems, and enjoy solving hard infrastructure problems with real operational complexity.

What You Will Work OnExecution Infrastructure

Build backend systems that orchestrate autonomous engineering workflows across tools, services, and enterprise systems.

Workflow Orchestration

Design execution flows involving multi-step task coordination, retries, compensation handling, state transitions, and execution guarantees.

State and Context Management

Build systems for execution state persistence, workflow context handling, execution history, and runtime continuity.

Enterprise Integrations

Build reliable integrations with Git providers, CI/CD systems, issue trackers, cloud infrastructure, identity systems, and developer tooling.

Reliability Engineering

Design mechanisms for failure recovery, idempotency, retries, partial failure isolation, and operational resilience.

Runtime Observability

Build visibility into execution state, audit trails, debugging workflows, telemetry, and operational introspection.

Enterprise Integrations & Execution Adapters

Build the integration layer that connects REM with enterprise systems including engineering tools, CI/CD platforms, identity systems, observability infrastructure, ticketing systems, and internal enterprise APIs through scalable connector and adapter abstractions.

Platform Foundations

Help shape engineering abstractions, platform architecture, implementation standards, and long-term technical direction.

What We Are Looking For

Typically 7-15 years of hands-on software engineering experience building production backend, infrastructure, or distributed systems.

Strong candidates typically have meaningful experience across several of the following:

• backend engineering in Python, Go, Java, or similar systems languages
• distributed systems and concurrent execution models
• workflow orchestration or execution systems
• platform engineering or backend infrastructure
• stateful backend systems
• production APIs and service architecture
• connector frameworks, adapter systems, and enterprise API integrations
• observability, reliability engineering, and failure handling
• cloud-native infrastructure and modern engineering tooling

Experience with developer infrastructure, CI/CD systems, internal platforms, execution engines, or workflow systems is a strong plus. Exposure to AI systems, agent runtimes, or autonomous execution systems is a plus, but not mandatory.

We care far more about systems engineering depth, execution thinking, and engineering quality.

What Success Looks Like

In the first few months, success means:

• building core execution infrastructure that powers REM's autonomous workflows
• improving orchestration reliability, execution correctness, and failure handling
• contributing to critical architectural decisions across the platform
• shipping production-grade backend systems with strong operational quality
• collaborating closely with the founding engineering team
• participating in technical architecture discussions where needed

Over time, this role is expected to evolve into a major technical leadership position as the platform scales.

Team Culture

We value:

• first-principles thinking
• strong engineering judgment
• wicked smart energy
• design thinking and product craftsmanship
• high agency
• low ego collaboration
• intellectual honesty
• building durable systems over short-term hacks

This is a founding-stage environment. Problems are ambiguous, constraints evolve quickly, and many patterns do not yet exist.

Location

Bangalore

Compensation

• competitive cash compensation
• meaningful founding-stage equity
• significant technical ownership and long-term influence