Questions recruiters ask

Either works for me.

As a B2B contractor, or through an EOR such as Deel or Remote.com.

Yes, I am open to relocation.

Yes, depending on the role.

Through the contact form on this page: the message goes straight to my inbox, and I reply as soon as I can.

I work full stack: the frontend, the backend and LLM features. My deepest experience is on the frontend, and it is still the part I enjoy most, but at a senior level you have to see web development as a whole rather than one layer of it.

From 2025 to mid-2026 I worked at BechaCant on a social app built around challenges between users: a Next.js PWA that also runs inside the product's iOS and Android apps. There I built the client side of the premium subscription and shipped the product's first LLM features. Before that, from 2021 to 2024, I worked at eTeam on nedyx, a low-code platform for business reporting, where I built the widget system, undo/redo, archives, PDF export and the platform's own formula language.

Yes, constantly. I worked most closely with the CEO, who set the project's priorities and brought ideas for tasks, and we discussed upcoming features together. With clients in the EU and the US, I took features end to end: from deciding what to build, through the trade-offs, to the release.

I have worked in small, flat teams where everyone helps each other. I did code review, helped new developers get up to speed on the project, and wrote specs and shared rules for working with AI coding tools. In 2020, I taught an introductory frontend course at dan.it and took a group of 25 beginners from zero to a working knowledge of HTML, CSS and Git.

I took on every task that came from the client and implemented almost all of them myself. On nedyx, that meant the widget system, undo/redo, archives, PDF export and the platform's own formula language, from the grammar and parser to the editor with autocomplete. At BechaCant, it meant the client side of the premium subscription with in-app purchases, the product's first LLM features, including the assistant panel, and the PWA's product features: challenges, the feed, notifications, profiles and the wallet.

Mostly small teams of 5 to 15 people. Over my career I grew from junior to senior, and in recent years I have worked as a Senior Full Stack Engineer.

The two hardest were both on nedyx. The first was the platform's own formula language, so analysts could write formulas themselves instead of filing tickets: I wrote the grammar, the parser (Chevrotain, Lezer) and the evaluator, and built them into a CodeMirror editor with autocomplete and inline errors as you type. The second was app-wide undo/redo: widget moves, formulas and styles share one history, a change across several pages is undone in one step, and the history lives in IndexedDB, so it survives a reload.

Often, early in my career. Later I mostly built MVPs and startup products from scratch, where legacy code had no time to pile up. There I shaped the architecture around each product's specific goals.

Both. I started at a product company, Software MacKiev, and later worked mostly in outsourcing: Ukrainian companies building products for startups abroad.

Quite a range: business reporting and low-code (nedyx), a social app built around challenges (BechaCant), legal tech for contract management (LinkSquares, through U-Genius), a site generator with a back office, e-commerce for events and a speaker platform (Adraba), and product sites for a software company (Software MacKiev).

The project I was on has wrapped up: the product is built and is now looking for customers, so it does not need development right now. I am looking for a new project with more room to grow. Low-code and no-code platforms pair well with AI: I have already combined them in products and want to keep doing that in new projects.

One where I can keep growing, especially in AI, and do interesting work for fair pay. I have enjoyed every project I worked on, and I still get real satisfaction from web development, so I want to keep going in this direction and, over time, move into a lead or management role without giving up writing code.

That it keeps growing and works with new technology: I keep learning and want the work to grow with me. The areas closest to my experience are low-code platforms, back-office systems and AI. Games and graphics interest me too, both 3D and D3.js: I have little experience there, but I would be glad to try. I am moving toward web engineering as a whole, not only writing code.

A small, friendly team that builds its own product step by step, one that many people can use, rather than turning out the same sites over and over. When I see people using and liking a product I helped build, the work means much more to me. The team matters as much as the product: I want to work with people I enjoy talking to.

Ones with plenty of logic, visualization and non-trivial integrations: AI, PDF services, image and video processing. Most of all, anything around data: processing it and presenting it clearly through statistics and charts. This is exactly where AI helps most right now, which is why it is one of my main focus areas.

Finish my MSc in Computer Science, AI and Machine Learning at Neoversity and widen what I can do in web development. There is still room to grow: in particular, I want to go deeper into Kubernetes and other infrastructure tools.

Right now I am looking for a development role. At the same time, as AI advances, management skills matter more, so over time I would like to move into a Tech Lead role and later an Engineering Manager role, if the opportunity comes on the right terms.

Mostly startups, apart from my first job at a company of more than 200 people. I work best in small, friendly teams, and those exist at companies of any size: a large company is still made up of small teams. So what matters to me is not the size of the company but how the team works and where the manager takes it.

Frontend: React, Next.js, TypeScript, GraphQL with Apollo Client, PWA. State: Redux, Zustand, React Query. Backend: Node.js, Express, NestJS, PostgreSQL, TypeORM, Redis, WebSockets. AI: LLM APIs, RAG, agents, OpenRouter.

AI has been my main area of growth for the last two years: I use it every day and build it into products. I have taken LLM features from prototype to production: retrieval over the product's own documents (RAG), streaming responses, tool calling and agent flows, all through OpenRouter rather than a single vendor. For the theory, I am doing an MSc in Computer Science, AI and Machine Learning at Neoversity.

I measure first and optimize second. For diagnosis, I use Lighthouse, the Performance panel in Chrome DevTools, a bundle analyzer (@next/bundle-analyzer) and the React DevTools Profiler to find unnecessary re-renders. Core Web Vitals (LCP, INP, CLS) are the target. The usual fixes are code splitting and lazy-loaded routes, optimized images and fonts, request caching, and virtualization for long lists and tables. That is how I kept heavy tables and charts responsive in large applications: virtualized the tables, trimmed the bundle and cut repeat GraphQL requests with fragment-level caching. With React Compiler, manual memoization through useMemo and useCallback is needed far less often.

Jest and Vitest with React Testing Library, plus Enzyme on the U-Genius projects.

I have a working knowledge of DevOps and hold the AWS Cloud Technical Essentials certificate, though it is not my main role. I have deployed sites and services with Docker, including a standalone PDF service, and worked with CI pipelines in Jenkins and GitHub Actions. For my own and smaller projects, I set up the cloud infrastructure myself; at larger companies, DevOps engineers handled it. I understand how the pieces fit together and keep deepening that knowledge.

TypeScript is my main language on both the frontend and the backend. Types make the code easier to read and reason about.

I worked with Next.js at BechaCant, and this site is built on it too. BechaCant ran on an earlier version, while I now work with the latest one. The approach to rendering and caching has changed noticeably between versions, so I am going deeper into the new model.

Anything that comes from the server stays server state: React Query or Apollo Client caches it and keeps it in sync, and in Next.js some of it is rendered on the server right away. On the client I keep only UI state: open panels, form input, user selections, with Zustand or Redux once that state grows. If state has to survive a reload or be shared via a link, it goes into the URL.

I have used Node.js for five years, mostly with Express, NestJS and TypeORM. I have worked with both SQL and NoSQL databases, mainly PostgreSQL, and built many integrations with external APIs, including Microsoft services such as Azure, and Google services. Integrating a new API is routine work for me.

Yes, at my last two jobs, both startups built from the ground up. I handled almost all the frontend and worked with the backend developers on parts of the server code and its architecture.

I have not worked with React Native, but I have built mobile PWAs that behave like native apps. At BechaCant, the PWA also runs inside the product's iOS and Android apps.

I worked with Vue a long time ago, on version 2. It has changed substantially since then, and going back would mean relearning it, so I do not treat it as my main framework. I have not worked with Angular. I enjoy React, and it is what I write now.

I follow the core accessibility principles and build them into the markup from the start.

I think about security from the start: in the architecture, the choice of libraries and individual decisions in the code. I pick secure defaults up front so that I do not have to patch problems in production later: httpOnly cookies, parameterized queries, secrets kept on the server, validation at every layer.

Constantly. My main tool is Claude Code, but I work with others as well and keep trying new ones. I set them up per project with skills, shared rules and configurations, and I understand how agents, task queues, automated code review and n8n automations work. AI helps me optimize code, debug and review changes.

I have implemented authentication with OAuth, JWT and sessions, including sign-in with Google and Microsoft accounts.

Yes: I have built WebSocket connections for real-time features such as chats.

I have been studying for an MSc in Computer Science, AI and Machine Learning at Neoversity IT University since 2025 and will graduate in 2027. Before that, I earned a master's degree in Project Management from Kyiv Aviation Institute and a bachelor's degree in Hydrometeorology from Taras Shevchenko National University of Kyiv, and did postgraduate studies in Environmental Safety at the National Academy of Sciences of Ukraine.

Machine learning, neural networks, statistics and algorithms. It is the theoretical side of the AI work I do in production. I started at Neoversity IT University in 2025 and will graduate in 2027.

My bachelor's in hydrometeorology gave me a grounding in science: physics, statistics and modeling complex systems. During my postgraduate studies at the National Academy of Sciences of Ukraine, I worked on environmental safety, mostly its chemical and radiation side. I also did research on pollution monitoring there and published papers. In my master's in project management, I developed and defended my own projects and took part in student conferences.

AWS Cloud Technical Essentials (2025), English C1 Advanced from EF SET (2024), and the AlgoExpert and FrontendExpert certificates.

Ukrainian is my native language, and I also speak Russian. I use English every day at work, with clients and the team. I am not a native speaker, so I describe my level as B2, professional working proficiency, although my EF SET certificate (2024) rates it C1.

Yes, with German, American, Israeli and Ukrainian teams. I have been working remotely for over six years.

I take a task from the first discussion to the release. I put quality over speed: work done right the first time does not need redoing. And at work, understanding and respect come first for me: I have been to more than 45 countries and know how much people and their values differ.

Gym, running, mountain hikes and long walks. I like learning new things: I watch tutorials on YouTube, take certifications and, alongside work, study for an MSc at Neoversity, which takes up much of my time. I unwind with an audiobook, music, anime, cartoons, manga or games like Dark Souls. My cat waits for me at home.

I have not had serious conflicts in a team. I settle disagreements at work by talking them through: first I listen to the other side and find out what the problem really is, then look for a solution that works for both sides. I keep the discussion on the task and the facts, not the people. A lot depends on the culture: I have worked with teams from different countries, and what sounds normal in one can land quite differently in another, so I adapt my approach to the person. If we still cannot agree, I weigh the options by what they give the product, make the call, explain to the team why, and own the outcome. Disagreement is a normal part of the work for me, not something personal.

Code review is a daily practice for me, in both directions. My changes get reviewed by teammates and AI tools, including GitHub Copilot, and in other people's code I look for mistakes and suggest better solutions. The discussion happens in GitHub comments or in chat.

First I make sure I understand the task and discuss it with the team, then I estimate it in story points or hours. My estimates are mostly relative, because estimates in hours always carry some error: a familiar task can be estimated fairly accurately, an unfamiliar one to within about 20%. Deadlines have not been a problem: when a task does not fit, we discuss it, and the manager either reschedules it or gives it more time and moves the rest to the next sprint.

I test new things on my own projects first and only then use them at work. Alongside that, I am doing an MSc in AI at Neoversity and follow the releases of the tools I use. In this field there is no way around it.

Right now it is DevOps, especially Kubernetes. I also want to keep growing in AI and build more applications with it. Robotics interests me too, but for now it stays a hobby.

Agile, mostly Scrum and Kanban, with Jira for tasks and Figma for designs.