Software Engineer · Research Software Engineer

Building production systems for institutions — and the research infrastructure behind them.

I'm Firdovsi Rzaev — Software Developer at Azerbaijan Technical University and Software Developer Team Lead at Dithari, where I lead the team building the Buyology e-commerce platform. I architect institutional systems used daily across faculties, departments, and commerce surfaces.

My work spans distributed systems, education technology, and research infrastructure — the kind of platforms institutions quietly rely on every day. Academic planning and reporting, grant competitions and expert review, an open-access journal with a double-blind peer review pipeline, researcher profiles reconciled across Scopus, Web of Science and Google Scholar.

Trusted by

  • Dithari
  • Buyology Trading FZ-LLC
  • Azerbaijan Technical University

Current

Where I'm working right now.

Software Developer Team Lead

Dithari

Leading the team building the Buyology e-commerce platform — web storefront, mobile app, and operations dashboard.

Software Developer

Azerbaijan Technical University

Designing and shipping institutional platforms: the Machine Science journal, Plan-Report, E-Grant, Researchers Portal, Majors Portal, the AzTU website.

Selected work

Production institutional systems.

Approach

What institutional engineering actually demands.

Model the institution, not the screen

A faculty is not a folder and a peer review is not a status field. Before any interface exists, the organisational hierarchy, the review states, and the publication units have to be modelled the way the institution genuinely works — including the parts that vary between one faculty, journal, or competition and the next. Get that wrong and every feature afterwards is a workaround.

Design for the record, not the demo

These systems are systems of record. A grant decision, a peer review, a published article, a submitted yearly plan — each has to remain reconstructable years later, after the org chart changed, after the reviewers moved on, after the rubric was revised. That means versioned definitions, explicit state transitions, and an audit trail that is a first-class feature rather than a log file.

Ship something people can run

Institutional software is maintained by whoever inherits it. So the deployment story matters as much as the architecture: containerised services, reproducible environments, boring dependency choices, and documentation an incoming engineer can act on. The measure of the work is whether it is still running — and still being changed safely — long after handover.

Stack

What I build with.

Frontend

  • React.js
  • Next.js
  • TypeScript
  • Tailwind CSS

Backend

  • Spring Boot
  • FastAPI
  • Django
  • REST
  • WebSocket

Platform

  • PostgreSQL
  • MySQL
  • Docker
  • Nginx
  • Linux
  • GitHub Actions

FAQ

Frequently asked questions.

Who is Firdovsi Rzaev?
Firdovsi Rzaev is a software engineer based in Baku, Azerbaijan. He is a Software Developer at Azerbaijan Technical University and Software Developer Team Lead at Dithari, where he leads the team building the Buyology e-commerce platform. His work is concentrated on production institutional systems — the platforms universities, editorial boards, and commerce operations use every day.
What kind of systems does Firdovsi Rzaev build?
Production institutional platforms rather than prototypes: academic planning and reporting systems, a grant competition and expert review pipeline, an open-access academic journal and peer-review platform, a researcher profile portal integrating Scopus, Web of Science and Google Scholar, a learning management system, and a multi-surface e-commerce platform spanning web, mobile, and an operations dashboard.
What is research software engineering, and why does it matter here?
Research software engineering is the practice of applying professional software engineering — version control, testing, deployment, data modelling, reproducibility — to the software that research and academic institutions depend on. It matters because research infrastructure is usually built once, under deadline, and then relied on for years; treating it as engineering rather than scripting is what keeps the results reproducible and the systems maintainable.
What technologies does Firdovsi Rzaev work with?
On the frontend: React, Next.js, TypeScript, and Tailwind CSS. On the backend: Spring Boot, FastAPI, Django, REST and WebSocket APIs. On the platform side: PostgreSQL, MySQL, Docker, Nginx, Linux, and GitHub Actions for continuous delivery.
What has he built for Azerbaijan Technical University?
Six production systems: the Machine Science journal and peer-review platform, the Plan-Report Information System for yearly academic planning across faculties and cafedras, the E-Grant Portal for grant submission and expert evaluation, the Researchers Portal that synchronises publication data from major academic indices, the Majors Portal covering programme learning outcomes and syllabi, and the public AzTU institutional website.
Where is Firdovsi Rzaev based, and does he work remotely?
He is based in Baku, Azerbaijan, and works with institutions and teams both locally and remotely. Correspondence is in English or Azerbaijani.
Is he available for engineering work or research collaboration?
Yes — he is open to engineering work and research collaborations in distributed systems, research software engineering, education technology, and data infrastructure. The contact page has a message form and links to LinkedIn and GitHub.
How can I get in touch?
Use the form on the contact page, or reach out through LinkedIn or GitHub. His CV is available to preview or download from the header of every page.

Next

Open to engineering work and research collaborations.

If you're working on distributed systems, research software, education technology, or data infrastructure — I'd like to hear from you.

Contact me →firdovsirz [at] gmail [dot] comLinkedIn ↗GitHub ↗