Technical Product Manager. The bridge between business growth and engineering.

1. 01
   Age 16 to 18

   The starting point — labor work, real-estate advising and odd jobs

   • ✓ Getting to know the work environment and responsibility from an early age
   • ✓ Learning the language of people on the ground — the marketplace
2. 02
   Age 18 to 20

   CEO's office manager — Sep (Saman Pardakht Kish)

   • ✓ The youngest member of the organization
   • ✓ Promoted from intern to managing the CEO's office
   • ✓ Sitting in on organizational and B2B meetings and negotiations
   • ✓ Mastering official correspondence, minutes and reporting
   • ✓ Seeing up close how power, decisions and organizations really work
3. 03
   Age 20 to 22

   Frontend → Full-stack developer — Flatlay

   • ✓ Promoted from junior frontend to full-stack
   • ✓ Getting into system architecture and problem-solving
   • ✓ Learning remote-team management and task definition
   • ✓ Becoming fluent in English
   • ✓ First deep experience of the startup world
4. 04
   Age 22 to 26

   Technical team lead & product manager — Droplinked

   • ✓ Early employee of a $1M startup
   • ✓ Leading a 12-person technical team
   • ✓ Designing a self-managed team system
   • ✓ Establishing documentation and systematic QA processes
   • ✓ Designing the sales funnel and customer journey
   • ✓ KPIs & OKRs, a Now/Next/Later roadmap, data-driven decisions
   • ✓ Taking a mission straight from the CEO → delivering the result
5. 05
   Age 26 (to today)

   Founder — vexelstudio / sinres / filet

   • ✓ Launching independent startups from zero
   • ✓ Learning marketing, sales and branding the hard way
   • ✓ Value discovery and content creation
   • ✓ Learning customer interviews and finding value inside the user's pain

What this path taught me: I speak both the language of business and the language of engineering — and I can translate between them — exactly where most startups burn their money and their months.