SUPABASETeam FrontendApplication / Alex Kostyniuk

I ship 0→1 and then keep earning the next version from the people using it. I treat types, tests, and CI as the thing that lets me and my agents move fast without breaking production.

Frontend · Full-stack range · Remote from Stockholm

feat(studio): ship it, then earn the next version

alex-kostyniuk wants to merge into main

Open
Alex Kostyniuk

Run 01 / Candidate

types

lint + format

unit + component

contract

migrations

a11y

visual regression

bundle size

7 passed

Why we're a strong match

My Open Source projects

Shipped and public

Why Supabase should hire me

0→1, then earned versions
Everything above went from a blank editor to something strangers use, decided and shipped on my own time. Each one changed after real usage rather than a spec, and the commits are public if you want to read them.
CI as the thing that lets you sprint
Types at the boundaries, lint, unit and component tests, contract tests, a11y, visual regression, bundle budgets. I would rather spend a day on the check than a week on the incident.
Agents with guardrails
I introduced agentic workflows at my company. I review what they write, tighten the architecture where they overreach, and leave them feedback loops so they verify their own work.
The modern React landscape
SSR, streaming, server components, and edge rendering are decisions I make deliberately. This portfolio runs on Next.js 16 with cache components, and I write articles about the trade-offs.
Postgres is the fun part
I read about Postgres internals for pleasure and write articles about what I find. Query plans, indexes, and locking are things I reach for on purpose, not things I look up when something breaks.
Past the UI
TypeScript, Node.js, and AWS alongside it. I own the API contract a screen depends on, and I have planned and run large Postgres migrations in production, designed backwards from the rollback with data reshaped underneath a live product.

Why I want to join Supabase

Building in the open
My side work is already public and open source. Doing that as the day job, in a repo thousands of developers read and contribute to, is the version of this career I actually want.
Studio is a real product
Tooling used by millions of developers, where a small interaction fix is felt immediately, is the highest-leverage frontend I can think of.
A company built on Postgres
I already spend my evenings inside Postgres and writing about it. Supabase is the one place where that is not a hobby I keep to myself, it is the product I would be working on.

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.

SUPABASETeam Frontend

Let's ship it in public, then let the users pick the next version.

Supabase × Alex

Continue to my portfolio

Open Portfolio
Download CV