# Dmytro Zavada

> Dmytro Zavada, Senior Full-Stack Engineer / Software Engineer. 11+ years in tech, Master's in Computer Science. Production web apps on React, Next.js, Node.js, NestJS — SaaS, MVPs, Telegram Mini Apps, AI, Web3. Available to start now.

Dmytro Zavada (Дмитро Завада) is a Senior Full-Stack Engineer / Software Engineer in Kyiv, Ukraine. Available to start now — remote B2B globally.

## Identity

- Name: Dmytro Zavada / Дмитро Завада
- Role: Senior Full-Stack Engineer / Software Engineer
- Location: Kyiv, Ukraine (UA-30, 50.4501;30.5234)
- Site: https://zavada.dev
- Profiles: https://www.linkedin.com/in/dmitry-zavada, https://github.com/zavada123, https://www.upwork.com/freelancers/~01a5630f97766796d4

## Keywords

Senior Full Stack Engineering • React Development • Next.js Development • Node.js Development • MERN Stack Development • SaaS Development • Product Development • Startup MVP Development • AI Integrations • TypeScript • JavaScript • Scalable Web Applications • Enterprise Applications • "Senior Full Stack Developer" React Next.js Node.js • "Next.js Developer" TypeScript AI • "AI Integration" React Next.js • "AI Engineer" "Next.js" Node.js • "Product Engineer" React TypeScript • "Senior React Developer" Next.js • Senior Software Engineer • Full Stack AI Developer • AI Full Stack Developer • FinTech Developer

## Skills

### Backend
- Node.js (NestJS), GraphQL, REST, Prisma ORM, Supabase, microservices
- Robust, high-performance architecture — from a single API to distributed services

### Frontend (React ecosystem)
- React.js / Next.js (SSR, SSG, ISR, Hybrid) — TypeScript-first
- React Native for iOS & Android, code sharing with web
- State: React Query, MobX, Zustand, Redux Toolkit, Context API
- Performance: code splitting, lazy loading, memoization, Suspense
- Testing: Jest, Cypress, Vitest
- UI: Alpine.js, Tailwind, MUI, SCSS — pixel-perfect, mobile-first

### AI
- AI chatbot creation, LLM integrations (OpenAI, Anthropic)
- Text-to-Speech (StyleTTS2), audiobook generation, AI-driven automation

### MERN & data
- MongoDB, Postgres, Express.js, React.js, Node.js — full-stack with seamless integration
- Web scraping: Playwright, Puppeteer

### CI/CD & DevOps
- Vite, Webpack, Gulp, Docker, GitHub/GitLab CI, Vercel / Netlify

### Products & Web3
- SaaS, dashboards, marketplaces, fintech, e-learning, CRM/ERP, DeFi/GameFi
- MVPs that scale: raw idea → production-ready product
- Web3: Ethers.js, Web3.js, Crossmint, Blockradar, Nexus

## Services

- [Website development](https://zavada.dev/website-development/): I build marketing and product sites as a senior engineer — Next.js by default, pixel-accurate from Figma, fast enough that Core Web Vitals are not a later project. Direct contractor, not an agency. 11+ years in tech.
- [Web app development](https://zavada.dev/web-apps/): I build web apps as a senior engineer — Next.js, React, NestJS, Prisma. This is not a marketing site: login, state, payments, ops. Full product ownership from the database to the UI. 11+ years in tech.
- [Telegram bots and Mini Apps](https://zavada.dev/telegram-mini-apps/): I build Telegram products as a senior engineer — Mini Apps, payment bots, TWA. Last shipped: a Mini App under NDA (2025–2026). The user is already in the chat. The product should not send them to a new account they will forget.
- [AI solutions](https://zavada.dev/ai-solutions/): I wire AI into an existing product: LLM integrations (OpenAI, Anthropic), RAG on your documents, TTS (StyleTTS2) and audiobook pipelines, workflow automation, and a Next.js UI. 11+ years shipping software — the model is a step, not the product.

## Key pages

- [Home](https://zavada.dev/)
- [Experience](https://zavada.dev/experience/)
- [Projects](https://zavada.dev/projects/)
- [Contacts](https://zavada.dev/contacts/)
- [Blog](https://zavada.dev/blog/)
- Ukrainian: https://zavada.dev/ua/

## Selected writing

- [How I scope an MVP — and what I refuse to add](https://zavada.dev/blog/how-i-scope-an-mvp/): A first version is one action in production, not a platform. The five filters I use before I open the repo.
- [What a senior frontend actually owns in a product team](https://zavada.dev/blog/what-a-senior-frontend-owns/): Not the pixel. The path: data, states, tests, and the night someone will page you.