Production Ownership
I like work where correctness is visible: financial records reconcile, integrations recover, operators can understand failures, and performance is measured instead of assumed.
~/about/

Hey! I'm Ismaeel Akram, a Computer Engineering student at New York University and a software engineer.
Most of my shipped work has been in backend platforms, financial workflows, cloud infrastructure, and systems that still have to behave correctly when the happy path ends. Outside work, I build Linux drivers and lower-level C and C++ projects and spend more time thinking about profiling, synchronization, data layout, and numerical behavior.
I'm building the evidence to move further into low-level performance and quantitative engineering. This site is the record of both halves: the production work I've shipped and the lower-level direction I'm earning through projects and study.
Bachelor of Science in Computer Engineering · Mathematics minor
Aug 2024 – May 2028
Coursework includes computer architecture, algorithms, linear algebra, probability and statistics, and circuits. I use projects to connect those foundations to real software behavior.
C++, C, Python, Linux, libFUSE, POSIX interfaces, perf, flame graphs
Python, Go, SQL, REST, GraphQL, billing and ledger workflows, integrations
AWS, Google Cloud, event-driven services, Docker, Terraform, Kubernetes
Algorithms, linear algebra, probability and statistics, profiling, measurement
Next.js, React, TypeScript, Shopify, Liquid, responsive product interfaces
GitHub Actions, scripting, agent tooling, Obsidian, reproducible workflows
I like work where correctness is visible: financial records reconcile, integrations recover, operators can understand failures, and performance is measured instead of assumed.
My current project work centers on filesystems, C and C++, data movement, profiling, and the mathematical foundations behind performance-sensitive software.
Storage operations, financial workflows, marketplace infrastructure, and external integrations
An open-source Linux/libFUSE filesystem with persistent caching, background hydration, synchronization, and real community use
Coursework in architecture, algorithms, linear algebra, probability and statistics, and circuits
Built a student-query language model prototype as a team project
I like technical writing that starts with a real failure or decision, then explains what changed. The same applies to code: I care more about measured behavior and explicit tradeoffs than impressive labels.
If you're working on systems, infrastructure, performance, or quantitative software and want someone who already knows how to own production work, reach out.