Rather Labs Engineering Manifesto

At Rather Labs, we build serious technology for serious problems. We work with advanced blockchain and AI systems, and we partner with startups and companies that need high-performance engineering teams. Some highlights we achieved during this year:

• We built an institutional platform that managed more than U$S 10B in loans
• We deployed a lending protocol that successfully managed more than U$S 300M TVL, with near 100% uptime, zero security breaches, and flawless operational continuity.
• We launched a stablecoin that achieved adoption and met all its performance and stability goals.
• We tackled highly complex blockchain ecosystems like Nervos and MultiversX, in addition to more traditional platforms like Bitcoin and EVMs blockchains.
• We built the first Move compiler for Arbitrum
• Most importantly, we built a highly talented, professional, high-performing, and remarkably human team.

Rather Labs was founded by engineers. We move fast, we ship, we go deep into technical complexity. We always aim for clarity and impact. We take our work seriously. And we are proud of that.

This is a short summary of how we build.

‍

Think critically. Don’t just execute.

We don’t follow processes blindly. If something doesn’t make sense, we stop and fix it. We value people who challenge assumptions, ask why, and offer better alternatives. One simple question guides our work:

Does this add value? Is it the best solution?

We want builders who think.

‍

Take ownership. Be accountable.

When you approve or contribute to something, you own it. That doesn’t mean working alone, but it does mean being responsible for the quality of what you touch. If you don’t understand the context of a task, ask. If something’s off, say it. If you’re going to skip a review, communicate it.

Clarity and accountability are non-negotiable. Professionalism is not optional. It’s the baseline.

‍

Keep it simple.

Smart solutions are not complex by default. Simplicity is a sign of experience. We avoid over-engineering by designing for the size of the problem, not our ego. Every extra layer of complexity has a cost. We focus on building clean systems that solve real problems and evolve well over time. We feel inspired by The Zen of Python.

‍

Prioritize with purpose.

Not all tasks matter equally. We train ourselves to distinguish what moves the needle from what just fills time. That means understanding the business impact, the difficulty, and the risk of each task, and acting accordingly. If everything is urgent, nothing really is.

We work smart. We keep focus. We say no when it matters.

‍

Protect your focus.

We don’t believe in multitasking. We protect time for deep work, especially for engineers. Distraction kills quality. We block distractions, structure our days, and avoid unnecessary context switching. Being busy is not the goal. Building great things is.

‍

Communicate like a team.

Good engineering requires good communication. We’re precise in meetings, direct in messages, and clear about ownership. We write things down, define action items, and make sure everyone knows what’s expected. We prefer overcommunication to ambiguity.

Clarity at the outset significantly reduces the need for revisions later.

‍

Use AI. Learn fast. Stay sharp.

We work with cutting-edge tech, and we act accordingly. AI is a shared toolset, and we expect everyone to use it to increase both output and quality.

But tools alone aren’t enough: we keep learning. No matter your role or seniority, if you’re not learning, you’re falling behind.

We value speed not just in delivery, but in growth: make mistakes, and learn from them as fast as possible. Not making mistakes often means you’re not growing. So don’t be afraid to break things. Just be fast to fix and learn.

Staying sharp is part of the job.

‍

Be Proactive.

We don’t micromanage. We hire smart people and trust them to push forward. Initiative is expected. That means flagging risks early, proposing solutions, and leading from where you are. Autonomy is part of the deal.

Have opinions. Challenge your peers. A strong opinion is a sign of mastery, not arrogance. If you see a better path, speak up. Raise your hand and share your thoughts. Being proactive also means being vocal.

‍

Aim for Mastery

We’re not just here to build features. We’re here to master a craft. Many of us come from scientific or engineering backgrounds, and we carry that mindset into everything we do: questioning assumptions, learning constantly, and aiming for precision.

We train for technical excellence. We read, test, refactor, and explore new tools constantly. We know that staying sharp is part of staying relevant. Professionalism means bringing rigor, curiosity, and pride to the work itself.

‍

Engineering is also Leadership

Technical leadership is more than being a good engineer. It means creating clarity for others, giving feedback, and mentoring when it matters. We train people for key roles before they’re “needed,” because we believe in continuity and growth.

We lead by enabling others.