About
I build the systems institutions actually run on.
Not demos. Not prototypes. The day-to-day systems used by faculty, students, reviewers, and operators — and the engineering team behind them.
I'm a Computer Science undergraduate at Azerbaijan Technical University and Software Developer Team Lead at Dithari. At AzTU I serve as a Software Developer on the platforms team. Together these roles put me at the intersection of institutional engineering and team leadership.
My work spans production-grade systems that quietly run things: a yearly academic planning and reporting platform, an e-grant submission and review pipeline, a researcher portal that integrates with Scopus, Web of Science, and Google Scholar, a majors and curriculum portal, the university's public website, and a multi-surface e-commerce platform for a UAE trading group.
I care about the parts most engineering portfolios skip — data models that survive organisational change, audit trails that hold up under review, integration layers that don't break when a third-party API drifts, and role-based systems that grow without permission sprawl.
The direction I'm moving toward is research software engineering — designing the infrastructure that institutional systems and research labs depend on, not just the applications that sit on top.
How I work
Operating principles.
Production over prototype.
Systems that handle real users, real edge cases, real audit requirements. Demos are easy; the second year of running something is where engineering shows.
Model the domain, not the screen.
Faculties, cafedras, rubrics, plans, reviewers, syllabi — the data model is the product. UI follows.
Boring tech, deliberate boundaries.
PostgreSQL, Spring Boot, FastAPI, Next.js, Docker. The interesting decisions live in service boundaries, not framework choices.
Lead by writing the hard parts.
Leading a team means owning the schema, the contracts, and the failure modes — not just the standups.