NEKO HEALTHProduct EngineeringApplication / Alex Kostyniuk

I look for the architectural change that makes something ten times better rather than ten percent, and I have the receipts for it. Member-facing software is where that discipline actually shows.

Lead Software Engineer · Full-stack · Stockholm

Alex Kostyniuk

Member 001 / Candidate

Body scan

00:47:12

  • Heart and circulation

    In range

  • Bloodwork

    In range

  • Skin

    Reviewed

  • Eyes and metabolism

    In range

Thousands of data points, one visit, before symptoms.

Done

Why we're a strong match

Your first 6 to 12 months, my read

Member first

  1. First 3 months

    Fully ramped and owning a slice of Member Experience, with work in front of real members rather than in a branch.

  2. By 6 months

    An end-to-end feature architected and delivered, plus the reliability work that keeps it safe when a clinic is busy.

  3. By 12 months

    AI-first workflows normal for the team, and one automation that removes a class of work instead of trimming it.

Why Neko Health should hire me

10x, not 10%
I turned a ten-minute core workflow into a twenty-second one by changing the architecture rather than tuning it. That is the instinct your posting describes, already exercised.
AI-native, every day
Claude Code and agentic workflows are how I work, and I introduced them at my company. I can tell you exactly where they carry the eighty percent and where they must not be trusted.
Full-stack ownership
TypeScript and React in front, Node, PostgreSQL, and AWS behind. I own outcomes across the whole path rather than handing the problem to the next team.
Fail-safe on purpose
Types at the boundaries, tests, CI, and observability are how I make systems that hold. For member-facing health software that is the baseline, not a finishing touch.
Operational interfaces
I have built Kanban, Gantt, and scheduling interfaces: multi-step flows, permissions, and dense state. Clinical workflows are the same problem with higher stakes.
Lead by example
I lead a team today through reviews, design feedback, and direct honest answers, and I still ship the hard parts myself.

Why I want to join Neko Health

Prevention is the right bet
Catching things before symptoms is the rare kind of software where the outcome is measured in someone's years, not in engagement.
Vertically integrated is rare
Hardware, data science, and product under one roof means a frontend decision can change what a clinic can actually do. That feedback loop barely exists elsewhere.
Stockholm, in the building
I am in Stockholm and I want to be near the clinic and the people running it. Proximity is what makes the hard trade-offs quick.

How I work.

I start with either a problem to solve or a business idea. I shape it around customer needs and technical realities, and look for a solution that can serve many customers instead of just one. Once the core is clear, I work with Design team on the experience, break it down into a focused story, and leave it ready for a developer or me to build.

How I develop features

  1. 01

    Start with an agent

    I always work with an agent. For bigger features or bugs that aren't obvious at first, I use specific skills to help it focus. For smaller tasks, I explain what needs doing and jump in.

  2. 02

    Scope the solution

    When the work needs a plan, I turn it into a detailed spec, including edge cases and what done looks like.

  3. 03

    Implement with agents

    Once the task is clear, I let one or more agents build the feature.

  4. 04

    Create feedback loops

    Browser Use, types, and tests help the agents see what they built and catch their own mistakes.

  5. 05

    Check manually

    I still open the feature and use it myself, from start to finish.

  6. 06

    Run an agent review

    I ask fresh agents to review the work and catch anything the first ones missed.

  7. 07

    Review the code

    Then I read the diff myself and fix whatever is left.

  8. 08

    Babysit the PR

    Finally, an agent watches CI and review comments until the PR is ready to merge.

Outcome

The result is a feature that has been planned, built, checked, and reviewed from a few different angles, usually in much less time.

NEKO HEALTHProduct Engineering

Let's make prevention the normal way to stay well.

Neko Health × Alex

Continue to my portfolio

Open Portfolio
Download CV