Head of Engineering

Remote position. This role has been filled.

RaftLabs is an AI-native custom software development company building products and platforms for clients across the globe. We operate as a fully remote team across SaaS products, enterprise integrations, and AI-powered workflows.

The role

This is not a hands-off leadership role.

You would own engineering quality, architecture decisions, technical standards, and the growth of every developer at RaftLabs. You would manage our tech leads directly and be the final word on how we build things — and also own at least one active client project end to end.

The co-founder should not have to get involved in technical decisions. That's what this role is for.

What you'd own

Code quality and architecture: own and enforce coding standards across all active projects. Review architectural decisions before they go into production, not after. Catch scalability issues and technical debt early.

Technical standards and stack discipline: define how the team uses our technology stack. Push back on unnecessary tool changes. Evaluate new tools critically — the bar is "this solves a real problem we have better than what we already use," not "this is new."

Tech lead management: manage all tech leads directly. Coach them on architecture, scalability, and decision-making. Build a culture where leads think before they act and can justify their choices.

Developer growth: identify skill gaps and close them. Create an environment where developers improve, not just ship.

AI-native development standards: define how the team uses Claude Code and similar tools in a structured, consistent way. Standardize AI-assisted development practices so they are a genuine productivity lever, not a wildcard.

Project ownership: own at least one active client project end to end as an active technical lead.

Requirements

• 6–9 years of software development experience, with at least 2–3 years in an engineering leadership role.

• Has built and shipped large-scale, production-grade applications that have handled real growth and real load.

• Has directly managed tech leads or senior developers, not just individual contributors.

• Solid understanding of modern full-stack web development. Familiarity with Next.js, Vercel, and related tools is a must.

• Technically strong but not a gatekeeping engineer: you enable the team, not slow it down.

• Strong communicator who can explain complex technical trade-offs to non-technical audiences without losing accuracy.

• Has worked in a fully remote engineering environment. Disciplined about async communication and documentation.