Product engineer:
from database schema
to revenue
React and TypeScript on the front end, Node and Express on the back end, PostgreSQL and Redis underneath. I deploy my own code and watch the dashboards: a feature is done when the metric moves.
// products I worked on
// approach
I start by asking which number should grow. Then I own that number — from the data schema to the charts after release. A month later I bring the PM either growth or a breakdown of why it didn’t happen.
// numbers
- $0K/month
- across the services I built
- 0×
- lower API bill after the model cascade
- 0k rows in <1s
- lead table on react-window
- 0k+ leads/day
- through my scoring
- 0+ years
- shipping production software
- $0M/year
- revenue of the platform I worked on
~/cases
What I've shipped
// about
Ivan Shabanov
4+ years shipping production software: the push service brings in $75K/month, the AI assistant cut API costs 10×. I dig into the domain — the best solutions come out of a conversation with a marketer more often than out of a ticket.
// stack
Frontend
- React 18/19
- TypeScript
- Next.js
- Redux Toolkit
- Zustand
- RTK Query
- React Router
- Ant Design
- CSS Modules / Sass
- Feature-Sliced Design
- Vite
- Recharts
Backend
- Node.js
- NestJS
- Hono
- Express
- PostgreSQL
- Turso
- Redis
- Kafka
- Prisma
- Drizzle ORM
- Zod
- REST
- GraphQL
- WebSocket
Infra
- Docker
- GitHub Actions
- GitLab CI/CD
- Sentry
- Grafana
- OpenTelemetry
- Vitest / Cypress
- Supertest
- nginx
// how I work with AI
I keep AI on a short leash: I design the architecture myself and take generated code apart by hand, so my brain doesn't atrophy behind the model.
Production is still on me.
- Claude Code
- superpowers
- Council
- Context7
- Obsidian
- Chrome
Looking for an engineer
who owns features end-to-end?
Drop me a couple of lines about the role and the team. CV and GitHub links are in the contact section below.
~/contact