A year ago, Aleksandr Karbyshev deliberately refused to open Figma. Not because he had fallen out of love with digital design, but because design had driven him into chronic professional burnout. Four years inside an early-stage startup—which originated as an online education venture before pivoting into an ambiguous personal-growth portal—culminated in a prolonged crisis. A founding team that once felt like a close-knit family devolved into an endless revolving door of interim executives, while his product proposals were routinely dismissed. Karbyshev stepped away on a sabbatical lasting over twelve months. When he returned, he chose the very environment digital creators often flee: corporate employment inside a massive retail enterprise with structured processes, multi-stage approval cycles, and dedicated line-item budgets for every user flow.
Today, Karbyshev serves as a lead product designer at a major retail corporation operating retail store networks across Kazakhstan. He orchestrates autonomous AI agents that compress five business days of analytics research into a single afternoon—and articulates why no algorithm can replace his strategic seat at the table. For broader context on modern workforce adaptation, read our report on Kazakhstan’s IT labor market dynamics and developer competition ratios.
A Designer by Serendipity Rather Than a Master Plan
— How did you originally enter the digital design profession?
Growing up, the formal concept of a ‘digital designer’ barely existed in our everyday consciousness. I was around 13 or 14 when consumer internet access first proliferated. I simply enjoyed crafting raster graphics in Photoshop—custom avatars, forum banners, and stylized desktop wallpapers. In the forum culture and early social media communities of that era, anyone who demonstrated Photoshop fluency commanded immediate peer respect.
Everything grew organically from there. Acquaintances began asking for commercial commissions—booklet covers, print collateral, and marketing assets. I never formally sought out design employment; I became a practitioner out of circumstantial demand rather than deliberate intent.
Even when I enrolled in university to study economics, the thought of turning design into a lifelong career had not fully crystallized. That realization struck midway through my degree. Once I determined that my future lay in design rather than macroeconomic theory, I formally left my university studies behind.

— How did you refine your craft—bootcamps, mentors, or self-directed learning?
I never attended commercial design bootcamps, aside from early YouTube tutorials that were freely accessible at the time. Whenever I encountered a hard skill deficit—such as the pre-Figma era when the industry operated entirely inside Adobe Creative Suite—I simply searched technical documentation and solved the puzzle myself.
Later, as I transitioned into web and graphic design and began collaborating closely with growth marketing teams, commercial courses felt obsolete—either excessively introductory or exorbitantly priced relative to their practical utility. I continued developing through real-world commercial deliverables.
Freelancing: Balancing Early Client Engagements with University Life
— Did you immediately enter salaried corporate employment or explore independent contracting?
My initial in-house role occurred during my second university year—working as a junior marketing designer at an insurance company for roughly twelve months. It gave me my first concrete exposure to corporate operating structures, managerial hierarchies, and operational friction.
Afterward, I gravitated toward independent freelancing. Balancing on-site corporate hours with full-time university attendance was exhausting; commuting back and forth across town was untenable, and remote work policies were practically nonexistent at the time. Freelancing functioned as my decentralized office: I could bill against project deliverables rather than fixed clock-in schedules.
— What attracted you to independent consulting?
The breadth of exposure. Navigating different industries, business models, and operational domains forced me to understand varied commercial ecosystems from the ground up. Crucially, it provided direct access to startup founders rather than buffering me behind multiple layers of design managers.
When you remain embedded in a single company for years, your perspective narrows. On independent contracts, you constantly encounter novel challenges and expand your problem-solving velocity.
Later, I collaborated with creative agencies on project agreements. In practice, many agencies operated like chaotic startups: operational workflows were unrefined, client expectations shifted constantly, and formal design briefs were nonexistent. As an external designer, you had to perform multiple concurrent roles: product discovery, user research, and technical design—often doing five times the volume of work reflected in the baseline contract fee.
Four Years in an Early-Stage Startup: From Family Culture to Severe Burnout
— What characterized your longest startup tenure?
The most grueling chapter was a startup where I dedicated four continuous years. It launched as an ambitious ed-tech platform—analogous to Skillbox in Kazakhstan—and concluded as an ambiguous personal-development portal. Over those years, the product suffered from chronic identity crises: perpetual feature testing and daily directional pivots without strategic continuity. Sustaining that chaotic velocity year after year inevitably triggers debilitating burnout.
— If the strain was so severe, what kept you committed for four years?
During the first year, despite occasional cash-flow delays in payroll, the operational atmosphere was deeply collaborative. The core team was small, I established close rapport with the founder, and we functioned like an entrepreneurial family. At that stage of my life, psychological belonging mattered far more than maximizing compensation. That emotional bond anchored me.
Over time, motivation eroded. As the company scaled and headcount multiplied, the original camaraderie dissolved. I found myself surrounded by unfamiliar executives, executing identical tasks for flat compensation while organizational empathy vanished.

— What broke down specifically?
Hypothesis testing ceased. Ideas I proposed were rejected without review; completed design solutions were harshly criticized without constructive rationale. Decision-makers turned over constantly—interim directors replaced one another in rapid succession. I stagnated into a monotonous ‘design factory,’ rendering screens mechanically without intellectual growth. That starvation of purpose forced my departure.
Choosing Enterprise Stability Over Startup Volatility
— Why choose a major retail corporation after burnout?
After stepping away for more than a year, I deliberately chose enterprise in-house stability. While startups romanticize velocity, large corporations offer established engineering processes, structured user testing cohorts, and substantial capital allocated to execute proper user research. When an enterprise backs a redesign, they commit millions of tenge and rigorous cross-functional engineering to ensure deployment success.
AI Does Not Draw UI: Compressing a Week of Research into a Single Day
— How do you deploy autonomous AI in your daily enterprise operations?
I do not ask generative models to draw UI screens—models produce visually attractive mockups that break down immediately under real user interaction. Instead, I deploy AI agents as operational research amplifiers. By linking models via the Model Context Protocol (MCP) and secure APIs directly to Figma, Jira, and Amplitude analytics, I eliminate mechanical data plumbing.
For instance, when auditing an e-commerce checkout funnel, an agent can parse 50,000 anonymized session drop-off events, correlate them against our live Figma design system tokens, and identify interaction bottlenecks in two hours. What previously consumed five business days of spreadsheet analysis is resolved in an afternoon.

Grassroots Bottom-Up Adoption vs. Top-Down Mandates
— How does your enterprise govern AI adoption?
True productivity adoption occurs from the bottom up. Frontline engineers and designers experiment with personal subscriptions because tools solve immediate workflow pain points. Corporate management subsequently funds formalized tooling once practitioners demonstrate empirical ROI on sprint delivery.
At the same time, security governance is paramount. Non-disclosure agreements explicitly forbid feeding proprietary source code, customer PII, or internal trade secrets into public cloud models. Furthermore, we establish strict containment protocols: never grant autonomous CLI agents unrestricted root privileges or hypervisor access to corporate development workstations.
Pragmatic Implementation: Do Not Try to Automate Everything at Once
— What tactical advice do you offer designers beginning to integrate AI?
Do not attempt an immediate, sweeping overhaul of your entire workflow. Identify a single, highly repetitive micro-task—such as checking icon bounding boxes against your design system or summarizing customer feedback tickets. Prove measurable time savings on that isolated workflow, and gradually expand outward.
Ultimately, focus on loving the operational process rather than purely polishing aesthetic artifacts. When you understand frontend technical constraints and integrate generative tools into systems thinking, you transition into a Design Engineer—a professional capable of driving product strategy that no algorithm can displace.
Connect with Aleksandr Karbyshev: t.me/ntrglcrn | Instagram: @ntrglcrnn
Interview conducted by Raimbek Iskendirov, RAEM.kz. For empirical data on developer salaries, engineering compensation bands, and market trends across Central Asia, read our investigation into IT compensation benchmarks and hiring velocity in Kazakhstan.