Design 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 Design Engineer.

Your mission: ship fast, accessible, high-performing interfaces users love, with engineering rigor that scales.

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

• Design and implement product UI end-to-end: interaction design → components → production.
• Build and maintain a component system: consistent patterns, accessibility, and strong defaults.
• Own performance: measure, profile, and improve (bundle size, SSR/CSR trade-offs, LCP/CLS/INP).
• Translate ambiguous problems into shippable UX with clear trade-offs.
• Collaborate tightly with backend/ops on API contracts, error states, loading states, and resilience.
• Improve quality: visual regression discipline, e2e tests for critical flows, and well-structured state.
• Contribute to (or own) native surfaces when needed (Flutter).

What you won’t do

• You won’t be limited to “making things pretty”; this is an engineering role with ownership.
• You won’t spend months polishing a design system in isolation from product outcomes.
• You won’t be doing pure marketing design as your primary job (though you may occasionally support it).

What success looks like

In the first 30 days

• Learn the UI architecture, routing, SSR setup, and deployment constraints.
• Ship 1–2 production UI improvements that reduce friction (forms, error handling, empty states, navigation).

By 90 days

• Own a core workflow end-to-end (from discovery → UI → integration → rollout).
• Deliver meaningful performance improvements backed by measurements.

By 180 days

• Lead a major UI initiative (new information architecture, new app shell, or a flagship workflow).
• Raise the product craft bar: accessibility, interaction quality, and perceived performance.

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 HTML/CSS fundamentals (layout, responsive design, modern CSS, accessibility).
• Production React experience.
• Experience with React Router v7 and server-side rendered applications.
• Excellent UX judgment: you can simplify flows, spot sharp edges, and design with constraints.
• Performance competence: profiling, understanding rendering bottlenecks, network waterfalls, caching.
• Solid state management skills (choosing patterns deliberately, avoiding accidental complexity).
• Ability to communicate clearly in writing and defend design/engineering trade-offs.

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 Flutter (shipping real apps, not just prototypes).
• Experience building component libraries and accessibility primitives.
• Experience with front-end observability (RUM, client-side error tracking, performance budgets).
• Familiarity with security basics for web apps (XSS, CSRF, auth flows, safe rendering).
• Experience with internationalization and localization.

Tools & stack

• Web: HTML, CSS, React.
• Routing/SSR: React Router v7 with server-side rendering.
• Performance: Lighthouse/WebPageTest, browser profiling tools, RUM-style metrics.
• State management: pragmatic patterns (context/selectors, lightweight stores) with clear boundaries.
• Native: Flutter (when applicable).
• Quality: component-level testing + end-to-end coverage for critical user journeys.

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).
• 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 “Design 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.