Backend Engineer

Before applying, read the Hiring Process so you know what you’re signing up for.

Read this first (self-selection)

Stop reading if:

• You’re optimizing for comfort, stability, or a “stay in your lane” role.
• You want perfectly defined specs, endless alignment meetings, and a low-responsibility environment.
• You equate performance with effort instead of outcomes.
• You dislike direct feedback, written communication, and being held accountable for what ships.

Continue only if:

• You’re a high-agency builder: you see problems, you propose solutions, you execute.
• You care about craft (clean design, maintainability, performance, security) and you’re willing to defend trade-offs.
• You want your work to hit production and matter quickly.
• You like a small, fast team where quality is non-negotiable.

About Revas

We are building RevasOS, the WorkOS for the next generation of business.

We believe the modern software stack is broken—too many tools, too little intelligence, and zero privacy. We are fixing this by centralizing the chaos.

RevasOS is a secure, sovereign Cloud SaaS designed to be the central nervous system of a company. We combine data-first strategies with AI-native workflows to create a platform that is powerful enough to run a business, but private enough to own it. We don't build "productivity tools"; we build the engine room.

We are experts on distributed cloud systems and ML/AI workflows.

• Stage: Bootstrapped.
• Team: 2: Nicolò - manages the technology and the company, Davide - manages design, marketing, sales and customers.
• Location: Remote. We also love to meet and work together.

The role

You’re joining as a Backend Engineer.

Your mission: ship secure, reliable backend capabilities that keep production boring and enable product velocity.

Baseline expectations (everyone, every role)

Regardless of title, you’re expected to:

• Collaborate closely with customers. You will seek clarity from real users, validate assumptions, and treat customer feedback as a first-class input (not an interruption).
• Write and maintain documentation. If you change the system, you change the docs. We keep the knowledge base (KB) clean, structured, and easy to navigate.
• Be an elite human engineer. High standards of professionalism: reliability, ownership, clear written communication, ethical behavior at work, and zero tolerance for creating unnecessary work for others.

What you’ll do

60% standard accountancy management, 30% document writing, 10% customer management.

• Build and evolve web APIs (design, implementation, documentation, versioning).
• Design for failure: retries, timeouts, idempotency, backpressure, graceful degradation.
• Own production outcomes: instrumentation, SLOs, alerting, incident response, postmortems.
• Ship infrastructure changes safely (IaC, canaries, rollbacks) and keep environments reproducible.
• Raise the quality bar: testing strategy, code review standards, secure defaults.
• Work directly with users and support signals to prioritize the right fixes.

What you won’t do

• You won’t be a “ticket taker” implementing pre-written specs.
• You won’t spend your life in meetings coordinating between large teams.
• You won’t be expected to do full-time front-end UI work (but you should be able to collaborate effectively).

What success looks like

In the first 30 days

• Get the system running locally and in a sandbox; understand deploy, rollback, and alerting flows.
• Ship at least one small production change that improves safety (timeouts, input validation, auth hardening, better logging).

By 90 days

• Own a meaningful slice (one service or a core domain area) with measurable SLOs.
• Reduce a real pain: latency tail, error rate, on-call noise, security gap, or support burden.

By 180 days

• Lead a project from problem → design → implementation → rollout → measurement.
• Improve system architecture in a durable way (cleaner boundaries, better auth model, event-driven workflows).

The environment (what it feels like)

This is a high-ownership environment.

• We prefer small teams, clear goals, and shipping.
• We move fast, but we don’t worship chaos.
• We value written clarity and directness.
• We expect you to be resilient: reality is messy, production is real, customers have opinions.

Requirements

You should have most of these:

• Strong Go engineering skills; ability to write readable, testable, production-grade services.
• Experience building HTTP APIs (REST/JSON or gRPC) including versioning, auth, pagination, rate limits.
• Practical cloud experience (Google Cloud); comfortable shipping infrastructure changes.
• Proficiency with Docker and container-native development.
• Solid grounding in distributed systems fundamentals (consistency trade-offs, failure modes, delivery semantics).
• Security mindset: OWASP basics, secrets handling, dependency hygiene, defensive coding.
• Comfort with open identity/security standards like OIDC and JWT.
• Ownership: you debug production with logs/metrics/traces and follow issues through to resolution.

If you don’t have every single requirement but you feel strongly aligned with our culture, mission, and genuine interest in this role, apply anyway.

Nice to have

• Experience with Go kit (or similar service frameworks) and evolving legacy patterns safely.
• Python and/or Rust for tooling, scripts, or performance-sensitive components.
• Serverless patterns (Cloud Run/Functions) and event-driven systems.
• Cryptography experience beyond “use TLS” (key management, threat modeling, protocol intuition).
• Multi-tenant SaaS concerns: authZ, isolation, billing hooks, audit logs.
• Compliance-adjacent systems (GDPR, retention policies, auditability).

Tools & stack

• Languages: Go (primary); Python/Rust (secondary, as needed).
• API: HTTP/JSON; often OpenAPI for contracts; gRPC/protobuf when it makes sense.
• Infra/Cloud: Google Cloud.
• IaC: Terraform and Pulumi.
• Containers: Docker.
• Security: OIDC/JWT, secrets management, least-privilege IAM.
• Observability: structured logs + metrics + traces (OpenTelemetry recommended); dashboards + alerting.

Equal Opportunity & Accessibility

We welcome applicants regardless of gender, gender identity/expression, age, nationality, ethnicity, religion/belief, disability, sexual orientation, or family/caregiver status.

We aim to provide a safe and accessible environment, including for people living with disabilities. If you need reasonable accommodations at any step of the hiring process (e.g., assistive technologies, additional time, alternative formats), tell us and we’ll adapt.

Candidate Privacy (GDPR)

If you apply, your personal data will be processed for recruitment and selection purposes in accordance with the GDPR (Regulation (EU) 2016/679), including the Art. 13 information duties, and applicable local laws.

Candidate privacy notice:

• https://policies.revas.io/it/privacy/informative/candidati-job-posting.html

Compensation & perks

We try to be explicit and realistic.

• Compensation philosophy: We’re bootstrapped. We may not match top-of-market packages at larger/VC-backed companies; our goal is fair compensation and continuous improvement over time.
• Contract & classification: Employment contract aligned with the applicable CCNL (level defined in the offer).
• Salary: Base annual gross salary (RAL) depends on experience and scope; we will share a range early.
• Benefits / welfare: Profit-sharing when applicable; welfare/fringe benefits via compliant tools, tax-efficient when possible and within statutory thresholds (subject to taxation and local rules).
• On-call rotation: This role may participate in a scheduled on-call rotation for production systems. Rotations are planned in advance and designed to protect rest and recovery.
• Equipment: Company laptop + needed peripherals.
• Working mode: Remote-first, flexible hours, outcome-driven.

How to apply (high-signal)

Send one email to nicolo.gardoni@revas.io with subject “Backend Engineer — {Your Name}”.

Include:

1. Evidence of work: GitHub, portfolio, or 1–3 projects (links).
2. Hard problems: describe 2–3 of the hardest problems you solved and exactly how you solved them.
   • Context
   • Constraints
   • Trade-offs you considered
   • What you shipped (and how you measured success)
3. One failure: the worst bug/incident you caused (or owned), what happened, and what you changed so it won’t repeat.
4. Why Revas / why this role: 5–10 lines.

If this feels like “too much work”, this won’t be a fit.