Understand the system.
Trace the relationships around a component before changing the component itself.
+ About / Sina Qasempour
Engineering practice, technical responsibility, and an interest in what lies beneath familiar tools.
Sina Qasempour / EngineerSoftware was the starting point. Over six years, my work expanded from implementing features into understanding complete systems — their architecture, data flows, operational boundaries, and failure modes. Enterprise platforms taught me engineering under real-world constraints.
Serving as CTO at Danobin widened that technical responsibility from implementation to architectural ownership and broader decision-making. Alongside hands-on delivery, engineering became about defining reliable boundaries and anticipating how components behave in production.
Beyond immediate production requirements, I invest continuous study into advanced computation and Quantum Computing. Whether analyzing algorithmic complexity, statevector simulations, or classical versus quantum kernels, curiosity drives me to understand what happens beneath standard abstractions.
The direction is deeper understanding — grounded in production engineering, proven through practice, and expanded through study.
Trace the relationships around a component before changing the component itself.
Make an idea executable. Use its behavior to test your understanding.
Look beneath the interface when a useful abstraction starts hiding an important constraint.
My role on each project.
CTO
StartupProject lead / Data Scientist / Full-stack Developer
Enterprise work and performance managementFull-stack Developer
Municipal payment and management systemsFrontend Developer
Citizen-services interfaceFrontend Developer
Fleet tire management product01 Education
A computer engineering degree in progress, alongside professional work.
Islamic Azad University, Kerman Branch
Discrete Mathematics 100 / 100 · Advanced Programming 100 / 100 · Software Engineering Laboratory 100 / 100Chamran, Kerman
02 Engineering journey
Chapters in how I think about engineering, rather than a dated employment timeline.
Chapter 01 · Learning by building
Turning requirements into working products established my foundation in software. Interfaces, application logic, and data became connected parts of the same problem.
Working software · Product behavior
Make the idea concrete enough to examine.
A growing engineering perspective
03 Engineering domains
Engineering domains first. Languages and frameworks are tools within them.
How components relate and behave together.
Representing problems and evaluating approaches.
The environment in which software operates.
Implementation tools, selected for the problem.
04 Continued learning
Computing, mathematics, and communication. Each record links to its verification page.
EF SET
IBM
Credential ID LOSS6SVKXJ6UIBM
Credential ID N8SV4CJK4GSCJohns Hopkins University
Credential ID FLMQTAHOHTT6Saylor Academy
Credential ID 6648683555SQIBM
Credential ID MARE5AZHZBLLIBM
Credential ID 6MJ4A9AO1X9SIBM
Credential ID DH5T428I0P00IBM
Credential ID OKQRU153EE4NIBM
Credential ID MEIWLIR4MCN0IBM
Credential ID 1ZABQFE1Z910IBM
Credential ID 2V65LR27IYV9IBM
Credential ID 2LO9YUTRCTNTUniversity of Michigan
Credential ID 2YZ8UWRUX5C4IBM
Credential ID WO6524QETVT8IBM
Credential ID 4VCWBVON4N9ZIBM
Credential ID 2ZXBTUHZ2R44University of California, Irvine
Credential ID 99R22SP9LW0FIBM
Credential ID H83DCQULEO4KLanguages
Professional working proficiency
Duolingo score 129 · Jul 2026Elementary proficiency
Duolingo score 11 · Jul 2026