AIRAPlanningApplication / Alex Kostyniuk

I build the dense, visual interfaces that operations teams live in all day: Gantt charts, boards, and scheduling views where the whole job is making a hard decision look obvious.

Frontend Developer · Data-Dense UI · Stockholm

Planning board

Week 34

Mon

Tue

Wed

Thu

Fri

Crew 01

InstallService

Crew 02

SurveyInstall

Crew 03

InstallSurvey

Route · by proximity

Alex Kostyniuk

Assigned

Alex Kostyniuk

React · TypeScript · Gantt & Kanban

Why we're a strong match

The posting asks for two of these

Five covered

  • Rapid growth journeys

    Building in a startup today

  • Kanban and Scrum

    Built the interfaces, and work this way

  • Next.js

    Daily, and I write articles about modern Next.js

  • Data visualization

    Gantt and timeline views for real schedules

  • Planning and scheduling UIs

    Shipped scheduling interfaces

  • Map integration

    Adjacent, not yet Mapbox in production

Why Aira should hire me

Modern Next.js, in depth
React and TypeScript are my daily stack, and I work in modern Next.js closely enough to write articles about it: App Router, server components, and the rendering trade-offs behind them.
Kanban, Gantt, and Scrum, built
I have built board, Gantt, and Scrum interfaces, the exact primitives a planning tool is made of. I know where they get slow, where they get confusing, and what to do about both.
Tooling that saves real hours
I turned a ten-minute core workflow into a twenty-second one by challenging the architecture, not merely tuning it. That is exactly the win a planner feels.
Scheduling interfaces already
I have worked on scheduling interfaces before, so the hard parts are familiar: overlapping constraints, dependent dates, and making the impact of a change visible before it is committed.
Range behind the UI
I work fluently across TypeScript, Node.js, PostgreSQL, and AWS, so when a scheduling view needs different data I can follow it into the API instead of filing a ticket.
Startup pace, and agile for real
I build in a startup today, working Kanban and Scrum rather than reading about them, and I introduced agentic workflows here to ship more per week without giving up review.

Why I want to join Aira

Software with a physical result
Most frontend work ends at the screen. Here a better schedule means more heat pumps installed and less gas burned, and the interface has consequences you can measure in homes.
Planning is genuinely hard
Proximity, travel time, availability, and constant rescheduling make this a real constraint problem.
Stockholm, in a scale-up
I am in Stockholm and want the pace and ownership of a company still building its core tooling, with the field force feeling every improvement.

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.

AIRA

Let's give planners tools worth the homes they heat.

Aira × Alex

Continue to my portfolio

Open Portfolio
Download CV