Makar Korolenko

The old promo site was heavy, and every text change had to be shipped by a developer.

• Proposed moving landing pages into a separate Astro service, and the proposal was accepted
• Built the service from scratch: GitLab CI, nginx, a UI kit in Storybook
• Set up landing page generation from Markdown with content checks in CI
• Used Webvisor session replays to find where the landing page was losing visitors and added a sign-up form to the first screen
• Set up an AI agent that builds landing pages from Figma mockups

ResultThe content team publishes landing pages on its own, without a developer.

The assistant answers in chat and performs actions in the CRM by itself via MCP.

• Worked on the chat: SSE streaming, the AG-UI protocol
• Built an onboarding tour in which the assistant helps a new customer set up their account through a dialogue
• Built an AI agent widget for websites

ResultThe assistant and the tour are in production.

The messenger had no calls.

• Broke the feature down and wrote the spec myself
• Calls, conferences and screen sharing on Jitsi, on web and desktop
• Designed video preprocessing with codec licensing in mind

ResultCalls have been in production since 2025.

Messenger features I built on my own or together with a colleague.

• Channel access permissions
• Pinned messages and reactions
• With a colleague: a dark theme built on design tokens and Tailwind

ResultNew screens are built from tokens and shared components.

The build was slow, the linter was broken, and tests were optional.

• Together with a colleague, moved the build from Create React App to Rsbuild
• Brought the linter back and made tests required in CI
• Started the migration to TypeScript

ResultBuild time went down from 10–20 to 3–5 seconds.

The previous frontend team had left.

• Hired four developers
• Led them as a tech lead: tasks, onboarding, code review
• Review and test my colleagues’ work before release

ResultTwo of the developers I hired still work with me.