Gateway ICT · FIB & FastLink
Interfaces for everyday operations
Frontend work across banking services, business automation, and data-heavy telecom operations.
- React
- TypeScript
- Tailwind CSS
- Figma
Tishk International University / Enterprise platform · Education
Making a university’s interconnected workflows understandable—from an applicant’s first step to academic administration.
Approximate codebase snapshot supplied for this case study.
01 / overview
The Student Information System is a centralized, multi-tenant university platform spanning marketing and prospects, applications, admissions, entrance examinations, academic programs, curriculum, scheduling, grading, examinations, and student administration.
I lead frontend development and help guide the team’s technical direction. My work connects requirements, interface structure, API integration, permission-aware experiences, and the people delivering the product.
02 / problem
University processes cross departments, roles, academic periods, and approval chains. A change in an application’s status affects what someone can do next; curriculum decisions connect to scheduling and examinations. Historical information and exceptions complicate even familiar tasks.
The frontend has to make those relationships understandable while remaining maintainable as the system grows. That requires understanding the business workflow before deciding which components to build.
03 / role
Frontend architecture, feature decomposition, UI workflow design, API integration, and role and permission-aware interfaces.
Work with business analysis, product, UI/UX, backend, QA, and university stakeholders to turn operational needs into user flows and prioritized work.
Review implementation approaches, coordinate the team, improve sprint readiness and design handoff, and contribute to release planning.
04 / context
Staff need administrative tools for connected academic and operational tasks. Applicants need a focused application and admissions experience. Student-facing experiences extend that lifecycle as the platform develops.
The constraints include different institutional roles, permissions, approval steps, and on-premise delivery across development, staging, and production environments. Public examples here deliberately omit internal data and policies.
05 / workflow
Admissions is a useful way to explain the challenge: prospect information, applications, entrance examinations, and admissions are connected areas. Each needs a clear purpose, visible status, and an understandable next step.
Curriculum management adds a different set of relationships between academic programs, periods, scheduling, and exams. Understanding those relationships is part of frontend engineering, not a step to skip before implementation.
06 / architecture
The frontend uses React, TypeScript, React Router, Tailwind CSS, and Radix UI, with a NestJS and PostgreSQL backend. Its 13 major feature areas and 34 API service modules give a sense of the breadth of the application.
My architectural focus is how application areas, interface patterns, API integration, and permission-aware behavior fit together. Navigation, forms, loading and error states, and role differences need to be considered together as features are broken down.
The diagram is a public, conceptual stack overview based on the project brief. It does not represent internal source structure, authentication protocols, or deployment topology.
07 / decisions
Clarify the role, the workflow state, and the available actions together. A permission-aware interface should help users understand their responsibilities.
Break down large requirements around coherent user tasks and dependencies, then review the approach with the people responsible for design, APIs, and delivery.
Use backlog refinement and design handoff to surface missing requirements, edge cases, and cross-team dependencies early.
08 / delivery
The delivery environment includes Docker, Nginx, GitHub Actions, and on-premise virtual machines. I help define release and deployment workflows across development, staging, and production.
Alongside implementation, I work on team coordination, requirements clarity, technical reviews, and scope and rollout discussions with university leadership and operational departments.
09 / impact
The codebase has grown to approximately 531 frontend source files and 73,700 lines of code across 13 feature areas. Those numbers describe the application’s scale; they are not a measure of user adoption or business impact.
The work demonstrates my experience translating a large institutional domain into a frontend product while helping a cross-functional team deliver it. The system is ongoing, and no public adoption or efficiency metrics are claimed here.
10 / lessons
The central lesson is that interface decisions depend on understanding the system around them: users, rules, APIs, academic processes, and the team maintaining the software.
My strongest contribution is connecting those concerns—making a complicated requirement understandable enough to discuss, break down, and implement.
Tools for the work
Keep exploring
Gateway ICT · FIB & FastLink
Frontend work across banking services, business automation, and data-heavy telecom operations.
Hymn.krd
Building and shipping a music streaming experience for the web, from frontend implementation through delivery.
A good next conversation
I’m open to full-time opportunities, selected freelance projects, and thoughtful collaborations.