Day-to-day: Craft Meets Hustle
We don’t have teams. We hire adults who take extreme ownership of their work.
If you thrive in a high-frequency feedback loop where velocity is a virtue, you’ll love it here. If you need a rigid roadmap and a project manager to dictate your tasks, you will be lost.
We operate as One Team. We leave individual egos and outside distractions at the door to focus solely on the craft of building the future.
Production Excellence as a Duty
Excellence is not a slogan. It’s a daily duty.
Our customers come first: understanding their real problems (and the constraints around them) is the top priority. We don’t optimize for clever solutions—we optimize for solutions people can trust, enjoy using, and find valuable.
What “excellence” means in practice:
- Testable by default: We write code that is easy to test, easy to reason about, and easy to change. If it can’t be tested, it’s usually not ready.
- Automation everywhere: We automate boring, repetitive work in every aspect of the business—from tooling, CI, deploys, checks, migrations, and rollbacks to quoting, billing, reporting, and internal operations. We also automate parts of customer service (triage, routing, context collection, suggested fixes), while staying close to customers: automation should increase our responsiveness, not create distance. If we do something twice, we try to automate it.
- Study and plan before building: We read, investigate, and design before we commit to an approach. We aim to do it right the first time—because “almost right” usually means doing it again.
- Resilient, secure architecture: Strong architecture is not optional. We build systems that degrade gracefully, survive failures, and protect customer data.
- Observability and fast response: Observability is every engineer’s job. We instrument what we ship, keep logs/metrics/traces actionable, and optimize for fast time-to-diagnosis and time-to-recovery.
- Pragmatic shipping: We move fast, but we don’t ship chaos. The goal is continuous progress without sacrificing quality.
On-call Rotations (Production Reliability)
We operate production systems. That means incidents can happen — and we take reliability seriously.
This is not an “always on-call” culture. We use scheduled on-call rotations (planned in advance) so we can monitor the system responsibly while still protecting rest.
If you’re on-call and something breaks, we show up and resolve it. After an incident, we make space for recovery time (slower pace, rest, handover), because long-term reliability requires humans who can sleep.
If you need accommodations or constraints around on-call (including for health or disability reasons), say it early — we’ll organize coverage and structure the rotation accordingly.
We keep major incidents to a minimum not by moving slowly, but by building excellent systems: testable code, automation, resilient architecture, and strong observability. We write systems that survive failure, not systems that pretend failure is impossible.
The Operational Rhythm (What you actually do)
Since we don’t have project managers, our day requires high executive function. Here is what that looks like in practice:
- We build RevasOS and deliver consultancy: We work on RevasOS product development and on customer projects—like a normal consultancy firm.
- We maximize RevasOS development: We prioritize RevasOS and try to maximize the time we spend improving it. We take consultancy projects that strengthen the team and, when possible, compound back into the product.
- We choose consultancy intentionally: When possible, we take projects that improve the team’s skills, expand our knowledge, and raise our standards.
- Direct collaboration with customers: We talk to customers a lot. We understand the problem together, align on outcomes, and iterate fast.
- We own design and implementation: We propose and validate the technical design, then implement it end-to-end with quality and accountability.
- Self-management: We split work into clear tasks, self-assign, and keep each other unblocked. Ownership is explicit; coordination is lightweight.
- Syncs, not meetings: We minimize scheduled meetings. We prefer async deep work and short ad-hoc huddles to solve specific problems.
- Handbook-first documentation: We document decisions, runbooks, and learnings. If we fixed it once, we write it down.
We try our best to keep our work ethic high. Sometimes we slip—but we notice quickly, correct course, and stay focused.
What we’re going to improve next
In the near future, we want to improve our responsiveness: faster feedback loops, faster incident response, and clearer ownership.
- Morning context: You don’t start with emails—you start with dashboards. You check the health of what you own before writing a line of new code.
- More documentation: We want a deeper knowledge base (technical decisions, operations, customer learnings).
- AI-forward handbook: We will develop more documentation designed for an AI-heavy future: structured internal knowledge, better runbooks, and clearer “why” behind decisions.
Craft-first Builders: Outcomes Over Optics
We are craft-first builders. We value skill and knowledge above credentials and corporate playbooks.
- No "Business Costumes": We work remotely in pajamas, not in offices in suits. We like to keep things practical. Obviously we look sharp when visiting customers—just no corporate costumes.
- Radical Transparency: We are casual, approachable, and radically transparent. We assume ignorance before we assume malice, but we are thick-skinned and well-intentioned.
- Intellectual Honesty: We expect you to be vocally self-critical. Admitting you are wrong is a sign of high agency, not weakness.
Work Ethics
Ethics at work is showing up, being on time, being reliable, doing what you say you are going to do, being trustworthy, dedicating a fair workday, respecting work, respecting the client, respecting the organization, respecting colleagues, not wasting time, not making work difficult for others, not creating unnecessary work for others, not being a bottleneck, not faking work.
This is a high-intensity, high-stakes environment. We are building an elite team to achieve the impossible. If you’re ready to ship code that matters, this is your day-to-day.