About
I'm Raffi, a 3x AWS certified technical consultant who builds backend systems, cloud infrastructure, and automation for companies that value precision over speed. I work directly with founders and engineering leads who need senior-level execution without the agency overhead.
Background
I run Arachnet, a technical consultancy in its third year focused on full-stack development, AWS infrastructure, and automation. I hold three AWS certifications (Solutions Architect, Developer, AI Practitioner) and specialize in building systems that stay maintainable as they scale.
My work spans backend architecture, cloud migrations, and automation pipelines using tools like n8n and Make to eliminate manual processes. I've built everything from real-time event systems to custom inventory management platforms, always with an eye toward long-term maintainability over short-term speed.
I started consulting because I wanted to work on a wider variety of problems, with a higher degree of ownership, and with clients who genuinely value craftsmanship. The best work happens when there's trust, clear communication, and mutual respect for each other's time.
How I Think
I believe most backend problems are fundamentally about managing complexity, not adding features. The best systems are the ones that stay simple as requirements grow—where adding a new capability doesn't require rewiring everything else.
I optimize for maintainability first, performance second. A system that's fast but incomprehensible is technical debt waiting to compound. A system that's clear and well-structured can be optimized later, when you actually know where the bottlenecks are.
I'm skeptical of trends and allergic to resume-driven development. I use boring, proven technologies wherever possible—because the exciting part should be what your system enables, not the stack itself.
I document everything. Not because anyone asks, but because documentation is how you scale yourself. The best code is code that explains itself. The best infrastructure is infrastructure that can be understood by someone who wasn't there when it was built.
Who I Work With
I work best with technical founders, engineering leads, and CTOs at companies with 10-200 employees. Companies that have real users, real revenue (or funded runway), and a genuine need to build systems that will last. You've probably outgrown your initial architecture but don't have the bandwidth to rebuild it while also shipping new features.
Who I Don't Work With
Companies looking for the cheapest option. My rates reflect the value of senior expertise and the cost of doing things right.
Projects with unclear ownership. I need a single point of contact with authority to approve decisions.
Engagements requiring daily standups. I work asynchronously with weekly check-ins.
Crypto, gambling, or anything I wouldn't want to explain to a friend.