Lead Full Stack Developer

About the role

LEAD FULL-STACK ENGINEER

Hi, I'm Akbay, Head of Engineering at Reflow.

Most engineering roles at this stage ask you to execute. Pick up tickets, ship features, move to the next one. That's not what we're looking for.

Reflow is building something that requires you to care about the outcome, not just the output. We track how work actually happens inside organizations and turn that into intelligence. The data is messy, the product surface is wide, and the problems are greenfield. You need to want to dig into that, not just be okay with it.

I'm looking for someone who gets energy from complexity, moves fast without cutting corners on the things that matter, and wants to see their fingerprints on a product that real teams depend on. Someone who can build and lead, in that order.

If that sounds like the kind of work you want to be doing, read on.

Akbay

WHY REFLOW EXISTS

Most organizations have no reliable way to understand how work actually gets done. They track outputs, not workflows. They measure activity, not intelligence. The result is a massive blind spot at the operational layer of every team.

Reflow closes that gap. We're a workforce and workflow intelligence platform that integrates with the tools teams already use, detects how work flows through an organization, and surfaces the insights and automation that help teams improve. We're early, growing fast, and moving into the next wave of intelligence-driven capabilities.

WHAT YOU'LL ACTUALLY DO IN THE FIRST 3 MONTHS

Month 1: Get into the product. Learn the codebase, understand the data model, and ship something real. You don't need to know everything on day one, but you should be delivering working, clean code fast enough that the team feels the lift. Expect to spend the majority of your time building.

Month 2: Own a surface. Take end-to-end ownership of a meaningful feature or system, from API design through to the frontend. Start developing strong opinions about how things should be built and why. Begin getting to know the team closely, how they work, what they're good at, and where they need support.

Month 3: Start leading. Move from knowing the team to actively making them better. Run regular 1:1s, give direct feedback, and start removing the things that slow people down. You are still building, but now you are also making it easier for everyone else to build well.

HOW THE ROLE LOOKS BEYOND 3 MONTHS

You stay hands-on; that's non-negotiable. But the balance shifts. Over time, roughly 70% of your time goes to building and technical decision-making, and 30% to the team, hiring, 1:1s, performance conversations, and raising the bar on how we work.

You are not a manager who used to code. You are an engineer who also leads.

Example projects on the horizon:

- Build and scale analytics dashboards that make complex workflow data fast, visual, and actionable.