Lead Engineer

The short version

Elexive’s first dedicated engineering hire. You take over lead development from Rolf (Executive Chair, CTO background) and own the technical direction of both Brain and the customer-facing operations tools. You contribute to product vision. You shape what grows from here.

What you are walking into

Rolf has led development alongside executive advisory work. That was the right call at the start. It is not the right setup for where we are going: more customers, more tools in production, Brain evolving faster than one person can drive it part-time.

You are not joining an engineering team. You are becoming the engineering function, with everything that implies: the decisions, the architecture, the standards, and the path to growing it when the time comes.

The two halves of the work

Brain (internal platform, becoming product)

The system that holds a company’s numbers, decisions and plans, kept current, answering anything asked from their own data. Not a dashboard. Not a chatbot. The place a leadership team goes for the current picture.

Your work here:

• Knowledge architecture that compounds. Every engagement makes the next one smarter.
• Retrieval from a customer’s own record, isolated, never the open web.
• AI orchestration: multiple models, multiple data sources, coherent answers.
• Interfaces that a non-technical executive can use without training.

Customer operations tools (revenue-generating)

Tools built for a specific company’s specific problem, then kept running as a managed service. This is paid work. You build what customers pay for, see the impact directly, and hear from the people using it.

Your work here:

• Scoped builds from reusable components. Nothing starts at zero.
• Deployment pipelines that stand up each customer’s own isolated environment.
• The component library and boilerplates that make a printed price honest.
• Direct involvement in client engagements: understanding the problem, building the tool, staying until it runs.

This is not a side obligation. It is the upside. You see your work used by real companies, running real operations, generating real revenue. The breadth is the point.

What the role grows into

You start as the technical lead. You own decisions, architecture, and delivery. As the company grows, you shape what the engineering practice becomes: whether that is a team you lead, a technical co-founder seat, or something else that makes sense for both sides. The path is designed together, not predetermined.

How you would work

Hands-on. Customer-facing. You sit with leadership teams, hear what they need, then build it.

You work directly with both founders. Henri runs the business and client relationships. Rolf has the technical domain expertise and the advisory background. The handover is real: Rolf stays involved in product thinking, but day-to-day technical leadership moves to you.

Remote-first, flexible schedule, based in Finland (Tampere or Helsinki preferred). English is the working language. No meeting culture. No performative presence.

The technical environment

• AI-native development workflow. Claude Code, Cursor, and whatever comes next are primary tools, not experiments.
• Deployment: AWS, isolated per customer, infrastructure as code.
• The stack is practical: what works and ships, not what interviews well.
• You choose the tools. No procurement process, no justification forms.

What we look for beyond skills

• Ownership instinct. You do not wait for someone to define the work. You see what needs doing and do it, then tell people what you did.
• Clear communication. You can make a technical decision land for a non-technical CEO. No jargon when plain language works.
• Judgment under ambiguity. We are small, things change, and not every decision has perfect information. You make the call anyway and adjust when you learn more.
• You want to build something. Not maintain it, not optimize it, not consult about it. Build it, see it used, see it matter.

Not a fit if

• You want a large team around you from day one
• You want someone else to set your roadmap and priorities
• You prefer pure product work with no customer contact
• You need process and structure defined before you can move

Interested?

Tell us what you would want to own and what you would build first. The conversation is with Rolf (technical) and Henri (business), no recruiter layer.