I build because an idea deserves to become something real.
And technology only matters when it changes what someone can do.
Engineering, to me, is the work of turning something complicated into something that feels obvious. A process that used to take a week becomes a single screen. A record that used to get lost becomes a system people can trust.
The code itself is temporary. What stays is what it made possible a service someone can finally reach, a course someone can finally finish, an hour someone gets back.
What I'm working toward
One day I hope the most meaningful review of my work isn't a benchmark. It's a sentence:
You changed my life.
The why
Before I ask how to build it, I ask who it is for and why it should exist at all.
Architecture is the second question. It has never been the first.
How I think
My mind rarely moves in straight lines. It moves through relationships between systems, between people, between ideas that shouldn't obviously connect.
Engineering evidence
Experience
03+
Years
Backend engineering
Experience
02+
Years
Flutter engineering
Performance
80%
Up to
Faster API response and data retrieval
Education
CS50
Harvard
Computer science, certified
Enough about what I believe.
Let me show you what I built.
02 — What I stand for
Every system I build begins with a decision about what it should stand for.
Not everything that can be built should be built. The harder question is deciding what deserves to exist and then being disciplined enough to build it properly.
Vision
Technology should reduce the distance between people and possibility.
01Technology
02Access
03Opportunity
04Impact
Education, healthcare and opportunity are all, underneath, access problems. Systems decide who gets there.
Mission
I turn complicated requirements into systems that are structured enough to scale, secure enough to trust, and clear enough to use.
That means architecture with defined boundaries, data models that hold up under growth, services that fail predictably, and performance treated as a requirement rather than a later optimization.
These are not values on a wall. They are the checks I run before and while I write anything.
01
Purpose first
Before architecture comes intent. I need to understand the problem, the people it affects, and the reason the system deserves to exist at all.
problem framingstakeholder mapping
02
Precision as a standard
Correctness, maintainability and security are not a phase at the end. They are decisions made in every function, schema and endpoint on the way there.
clean architectureSOLIDcode reviews
03
Integrity in engineering
I would rather report an honest constraint than ship a confident guess. Secure coding, validation and accountability are the same value expressed in code.
secure codinginput validationdata protection
04
Curiosity without a ceiling
I keep asking what the system is actually doing underneath. New architectures are not threats to my habits, they are corrections to my assumptions.
new architecturesquestioning assumptions
05
Human centered engineering
Technical quality only counts once it becomes usefulness. A system that is elegant and unusable has failed twice.
And architecture is where the way I think becomes visible.
03 — How I think
I rarely design a feature in isolation. I look for the system behind it.
Its dependencies, constraints, data, users, failure points and future scale. The feature is the visible part of a decision that reaches much further back.
The decision pipeline
Ten stages, in the order I actually work through them.
01
Problem framing
Define the actual problem, not merely the requested feature.
system analysisrequirements
The question
What are we really solving?
02
System discovery
Users, constraints, existing systems, dependencies, data flows and operational reality.
dependenciesdata flowsintegrations
The question
What already exists that this has to live with?
03
Architectural design
Boundaries, responsibilities, API contracts, data models, security and scale decided before implementation.
system architecturemicroservicesJWTOAuthRBAC
Iraqi Ministry of Higher Education
National-scale LMS
Roles and permissions, video delivery, assessments and analytics designed as one system.
The question
Who is allowed to access this?
04
Engineering strategy
Break the architecture into increments that are realistic, measurable and shippable.
Architecture, platforms, products, automation. Each project below is a complex engineering problem, taken from the constraint that defined it through to the system that resolved it.
Chapter 01
I architect systems.
01Enterprise systems2024
University Management System
Engineering the backbone of a digital university.
A production-oriented enterprise backend engineered to unify academic, administrative, and user-facing operations within a secure and scalable university ecosystem. Students, faculty, and super administrators operate inside one centralized architecture registration, enrollment, course management, attendance, assignments, results, announcements, and administrative workflows all resolve against the same services, permissions, and academic data.
My role
I engineered the backend layer that translates complex university workflows into structured, secure, maintainable services the infrastructure connecting people, processes, permissions, and academic data.
Three audiences. One architecture underneath them.
Student
Course enrollment
Attendance
Assignments
Academic results
Announcements
Academic workflows
Faculty
Course management
Attendance management
Assignments
Student evaluation
Academic operations
Super admin
Users
Roles & permissions
Academic configuration
Administrative workflows
System management
Centralized FastAPI backend
Architecture
Every request passes through the same disciplined path.
Client applicationsWeb · Mobile
FastAPI API layerAsynchronous REST · OpenAPI
Authentication / authorizationJWT · RBAC
Business servicesAcademic domain logic
Data accessRepositories · migrations
PostgreSQLNormalized relational schema
Supporting infrastructure
Redis — caching
RabbitMQ — message-driven processing
Celery — background jobs
Docker — containerized services
GitHub Actions — CI/CD
Asynchronous APIs, JWT authentication, RBAC, caching, background processing, database optimization, automated testing and production deployment are properties of the architecture, not additions to it.
The engineering challenge
A university is not a CRUD application.
Permissions, academic records, attendance, assessments, registrations, announcements, users and administrative workflows form one interconnected domain. Every one of them has to stay consistent and reliable while the others change.
Data integritySecurityScalabilityPerformanceMaintainabilityReliability
Up to
80%
improvement in API response times and data retrieval efficiency.
How it was achieved
Query tuning across high-traffic academic operations
Complexity was not something to hide. It was something to architect.
View the full engineering case study.
Chapter 02
I build platforms.
02Platform engineering2023
Educational LMS Platform
Building an education marketplace beyond the classroom.
A scalable Django-based learning marketplace engineered around online course commerce and the operations of learning itself — purchasing, course management, secure payment workflows, instructor dashboards, student progress, and role-based permissions held together by an optimized data layer.
My role
The backend was engineered to serve three journeys at once: instructor, student, and platform operations — each with its own permissions, data, and workflows.
Role-based permissions and secure backend modules decide what each account can reach — controlled access enforced server-side.
Secure course commerce
Course purchasing
Payment workflows
Secure backend modules
Transaction-oriented workflows
Purchases move through backend workflows built to treat money as a transaction, not a form submission.
Student progress
Learning tracked as state, not as a feeling.
Course→Content→Learning→Progress→Completion
Each step in the journey is backed by user state in the database, which is what makes progress trackable for the student and visible to the instructor.
Built to make learning scalable, measurable, and accessible.
View the full engineering case study.
Chapter 03
I connect technology to people.
03Digital services2025
FOMS — Martyrs Foundation
Engineering digital access to essential services.
A real-world cross-platform product giving beneficiaries streamlined access to foundation services mobile UX, secure API communication, structured data handling, backend integration, and multi-screen workflows delivered as one experience across Android and iOS.
My role
The work ran end to end: from the first screen a beneficiary sees to the backend services answering behind it.
Flutter→REST APIs→Backend services→Structured data
Secure API communication
Structured data handling
Multi-screen workflows
Backend integration
Built to stay responsive
Responsive layouts across screen sizes
Cross-platform performance
Structured workflows
Optimized user experience
Technology
FlutterDartREST APIsRiverpodFirebase
Technology becomes meaningful when it reaches the people who need it.
View the product and engineering details.
Chapter 04
I eliminate operational complexity.
04Workflow automation2024
Data Automation System
Turning operational complexity into reliable automation.
An internal engineering automation system that moves large Excel datasets through a structured pipeline ingest, validate, clean, transform, generate, report replacing repetitive manual work with a process that runs the same way every time.
My role
I designed the pipeline and the operational thinking around it: find the process that repeats, then engineer it out of existence.
Repetitive manual data entry and reporting consumed operational effort across departments and created room for inconsistency the same work, redone by hand, with a new chance to diverge each time.
The pipeline
Raw spreadsheets in. Finished reports out.
Raw Excel dataOperational files, as they arrive
Data ingestionRead at scale, structure applied
ValidationRules before anything downstream
CleaningInconsistencies resolved once
TransformationShaped into the reporting model
Report generationStructured Excel output
Ready-to-use reportDelivered to the department
Data you can trust
Data cleaning
Structured processing
Consistency
Accuracy
Confidentiality
Automation improved data accuracy while reducing the manual workload behind it.
Automated execution
Runs on a schedule, not on a reminder.
Schedule→Process→Generate→Deliver
Multi-department use
Many inputs, one pipeline, standardized output.
Department A
Department B
Department C
Automation pipeline
Standardized reports
Reduced manual work
Repetitive data entry and reporting no longer done by hand.
Improved data accuracy
Validation and cleaning applied consistently, every run.
Accelerated operations
Reporting moves at pipeline speed across departments.
If a process repeats, it can probably be engineered better.
View the engineering details.
06 — Case study
University Management System
The problem. Universities run on tangled, slow, role-blind software — admissions, registration, grading and finance each trapped in their own silo, none of it built to scale.
The approach. One coherent backend on FastAPI, designed clean-architecture first: async APIs for throughput, JWT with role-based authorization for trust, and a message-driven layer so heavy work never blocks a request.
RoleSole architect & engineer
Timeline2024
ScopeEnterprise platform
PatternClean Architecture
System architecture
Web clientMobile client
FastAPI · async gateway
JWT auth · role-based authorization · Swagger
PostgreSQL
System of record
Redis
Caching layer
RabbitMQ → Celery
Background jobs
Containerized with Docker · one-command deploy
80%
Faster API retrieval
Async
Non-blocking by default
RBAC
Every route guarded
1×
Command to deploy
What it taught me. Architecture is a kindness you pay forward the discipline of separating concerns early is what lets a system grow without fear. The cleanest code isn't the cleverest; it's the code the next engineer can trust.
07 — The path
Where the work has taken me so far.
2023 — 2026CURRENT
Software Engineer · Ta3leem
Baghdad, Iraq
Built Ta3leem V2, an education app for children of martyrs, and a full LMS for the Iraqi Ministry of Higher Education — shipped across Android, iOS & Web.
Designed server-side systems in Python, Django & FastAPI; optimized REST APIs for up to 80% faster retrieval.
Led system analysis & documentation in Figma and drove delivery with Agile workflows.
2019-2023
B.Sc. Computer Engineering
University of Technology, Baghdad · Network Engineering
A foundation in systems thinking — from networks and hardware to the software that ties them together.
Certification
Harvard CS50 · Computer Science
Six comprehensive projects across HTML, CSS, JavaScript, Python and Django — rigor from first principles.
08 — The next step
“She doesn't just develop software. She engineers ideas, leads with purpose, and builds technology that creates real impact.”
