Architecture design
Product structure, module boundaries, integrations, and a development plan that survives changing requirements.
Software Engineer
Collaboration
I build software products and security systems. Behind me are more than ten years of engineering work: Sberbank, Yandex, government systems, and my own projects.
I work at the intersection of engineering, product, and user experience: from analyzing the task to architecture and a working solution in production.
Ways of working
I take on work where a systematic approach and ownership of the result matter.
Building a new product
From an idea and a first version to launch: technical decisions, implementation, and shipping to production.
Audit and recovery of an existing project
A close look at an existing system: what blocks its development, where the risks are, and how to make it manageable again.
Complex interfaces and integrations
Multilingual services, data-heavy interfaces, integrations with external systems and APIs.
Long-term engineering work
Ongoing participation in a product's development: architecture, code, reviews, engineering practices.
Consulting and systematic analysis
Help with finding the real task and a strong solution: facts, contradictions, resources, testing against reality.
Core stack: React, TypeScript, Next.js, Astro, React Native, Node.js, PostgreSQL.
Projects
Toqen.app
Authorization infrastructure built around access control: QR-based authorization with device-bound cryptographic verification.
Role: Founder: architecture, security model, mobile client.
Litseller
A multilingual reading platform: structured content and cross-language reading with translation.
Role: Product and engineering: platform architecture and content pipeline.
Start4Drive
Preparation for the driving theory exam in Argentina: interactive practice and a clear presentation of official materials.
Role: Product and engineering.
Working principles
- the task first, the tools second
- transparency: clear decisions with clear reasons
- small verifiable steps instead of big promises
- code and architecture that can be maintained without their author
- honest constraints instead of optimistic estimates
If this approach resonates with you, write to me and let's discuss the task.
Contact
Tell me about your product or problem — I'll reply with how I can help and in what format.