Bosscoder Academy
A scalable design system for Bosscoder Academy and BST, built to improve UI consistency, streamline development, and support product growth through reusable components and clear design guidelines.
Year
2022 - Present
Client
Bosscoder Academy PVT. LTD.
Tools In Use
Figma + Illustrator + ChatGPT + Adobe Suit
Role
Senior UI/UX Designer
01. Project Overview
Bosscoder Academy is an online upskilling platform launched in 2021 to help engineering graduates and working professionals transition into product-based technology companies. As the platform expanded from one software engineering charter to five or six active charters, its product complexity and design requirements grew significantly. In 2026, the ecosystem expanded with Boskoder School of Technology (BST), introducing a four-year B.Tech program in Computer Science and AI/ML through an academic partnership.
My focus was to establish and scale a consistent design system that could support evolving product requirements, improve design-to-development collaboration, and accelerate feature delivery across both platforms.
02. My Role
As a Senior UI/UX Designer, I led end-to-end product design at Bosscoder Academy from 2023 to December 2025, contributing to two major platform revamps and six to seven major features. In early 2026, I took ownership of BST's campus branding requirements and LMS design
I collaborated closely with the Product Manager, engineering, QA, operations, and doubt-support teams. My responsibilities included design strategy, user flows, UI design, design systems, documentation, developer handoff, mentoring, and post-development UI audits.
03. The Challenge
The original platform suffered from outdated visuals, inconsistent components, confusing navigation, fragmented user flows, and recurring UI issues. These problems affected the learning experience, reduced visual consistency, and increased development and testing time.
With multiple features being developed under tight deadlines, the team needed a scalable design system that would reduce duplication, establish reusable patterns, and maintain product quality without disrupting the existing user experience.
04. The Approach to Solution
I followed the design thinking process—Empathize, Define, Ideate, Prototype, and Test—combined with UX psychology and usability heuristics inspired by Don Norman's principles.
I gathered insights through direct user feedback, biweekly team discussions, and Microsoft Clarity. Secondary research and competitor analysis helped identify established patterns and common user expectations. Working within an Agile/Scrum environment, I prioritized iterative releases, user feedback, and continuous improvements.
05. Building the Design System
I established the Bosscoder Academy design system from the ground up, covering:
Foundations: Brand principles, colors, typography, spacing, radius, icons, grids, and layouts.
Components: Buttons, inputs, navigation bars, badges, status cards, overlays, and media components.
Documentation: Usage guidelines, accessibility considerations, component specifications, and change logs.
Development alignment: Reusable component definitions, developer handoff, implementation reviews, and UI audits.
The system created a shared foundation for designers and developers, helping reduce duplication, maintain consistency, and improve delivery efficiency.
06. Scaling the System to BST
In early 2026, I created a separate design system for BST by adapting and extending reusable components from Bosscoder Academy. This preserved established design patterns while allowing the new Learning Management System to meet its own requirements.
I collaborated with developers to define and document components, used AI to explore UI variations and identify gaps, and conducted UI audits before wider implementation. Cross-functional communication helped maintain consistency and meet deadlines.
07. Design System in Practice
The system supported the design and evolution of student dashboards, curriculum and course modules, chapter pages, coding practice, assignments, assessments, doubt support, mentorship, referrals, leaderboards, rewards, and payment flows.
These product experiences provided practical applications for the component library and helped establish consistent interaction patterns across the education platforms.
08. Measurable Impact
Design and delivery efficiency
Feature development reduced from 3–4 weeks to approximately 1.5–2 weeks.
UI audits reduced from 3–4 days to 1–2 days.
Reusable components improved consistency and reduced UI defects and implementation rework.
Bosscoder Academy
6,700+ registered learners
2,900+ monthly active users
Expanded from one software engineering charter to five or six active charters
Monthly revenue grew from approximately ₹50 lakh to ₹5–7 crore
Boskoder School of Technology
350+ active student users
Approximately ₹20 crore ARR, as reported internally; the reporting basis and attribution should be verified before publication.
These figures reflect the broader product and business environment in which the design work took place, rather than outcomes attributable to the design system alone.
09. Key Learnings
Deploy fast, learn fast.
In a fast-paced product environment, secondary research, competitor analysis, and established UX patterns help teams understand common requirements quickly. Rather than delaying releases in pursuit of perfection, deliver a functional initial version, gather real user feedback, and improve continuously. Testing remains essential, especially for usability, accessibility, and critical workflows; the goal is to make it continuous and proportionate to risk.
Design is strategic, not subjective.
Every decision should support user needs, business goals, and technical constraints. Listen to stakeholder feedback, but balance it against priorities, evidence, and delivery requirements. Unclear decisions can delay milestones and create unnecessary rework.
Build the system before scaling.
Establish foundations, component architecture, and clear product requirements before expanding the interface. Resolving small design decisions early reduces ambiguity, accelerates development, and makes UI audits more reliable.
Functionality comes first; refinement follows.
Prioritize a usable, reliable product before adding visual polish. Improve progressively without compromising usability or quality.
Consistency needs flexibility.
Design guidelines establish shared standards, but a scalable system must allow adaptation as products, users, and requirements evolve.
Balance speed with quality.
Fast delivery works best when supported by clear documentation, reusable components, continuous validation, and strong collaboration across design, engineering, product, and business teams.