Software Engineer
Application Architect
Enterprise Application Developer
Technical Author & Educator
Software Engineer
Application Architect
Enterprise Application Developer
Technical Author & Educator
My professional path has developed over nearly two decades at the intersection of software engineering, enterprise systems, data, infrastructure, automation, and practical technology.
I did not begin with software alone. My early technical background grew out of hands-on work with computer hardware, office systems, printing technologies, electronics, photography and video, digital design, and technical services. Over time, that practical foundation evolved into software development, database engineering, IT administration, application architecture, automation, and technical project leadership.
This combination has shaped the way I approach technology today: I do not see software as an isolated layer. I see it as part of a larger operational system involving people, processes, data, infrastructure, interfaces, and real-world constraints.
My professional work began in a family technical environment and later expanded into independent technical activity, software development, consulting-style problem solving, and a large number of practical projects across different domains.
Over the years, I have worked on systems involving:
Many of these projects originated not from abstract technical exercises, but from concrete problems that needed to be understood, modeled, and converted into working systems.
That process — understanding the domain first and then translating it into software architecture — has become one of the central themes of my work.
A major part of my professional development took place at Astan Quds Razavi, where I worked between 2013 and 2021 across software development, full-stack engineering, database work, IT administration, infrastructure, automation, and technical architecture.
During this period, my responsibilities expanded from implementing individual software components to understanding complete operational workflows and designing systems around them.
The work covered a broad range of technical problems, including internal applications, information systems, database-backed platforms, workflow automation, digital content, research-oriented systems, and technical support for organizational processes.
This period was particularly important because it strengthened my ability to move between different technical layers — from user requirements and business logic to application code, databases, infrastructure, and deployment.
After leaving Iran, I continued working on research-oriented software and information-system concepts connected with an academic environment, including a platform for structured clinical case-report data, publication workflows, advanced search, and research-oriented information management.
That work further strengthened my interest in systems where software engineering and structured knowledge meet.
I am especially interested in applications where complex information must be transformed into a model that users can search, analyze, compare, publish, or use for decision making.
In Germany, I worked in an enterprise Java environment at SLA Niedersachsen, developing and maintaining applications using technologies including Java, Spring Boot, JSF, PrimeFaces, JUnit, Maven, Jenkins, SoapUI, and Swagger.
This experience added another layer to my background: working inside a structured enterprise software environment with established development processes, testing, documentation, requirements, and deployment workflows.
I later joined Steffel KKS GmbH as an IT Administrator, where my work expanded across enterprise IT operations and internal software development.
The role combines software engineering with the practical realities of an operating company: internal applications, databases, ERP/DMS-related systems, reporting, automation, infrastructure, backups, access management, data protection, technical support, and management-facing technical advice.
Working in this environment has reinforced a principle that has followed me throughout my career:
Good software is not only code that works. It must also fit the organization, the workflow, the infrastructure, the users, and the operational reality around it.
My portfolio reflects a deliberately broad technical background.
Alongside enterprise software, I have worked on projects involving:
The value of this breadth is not simply the number of technologies involved.
It allows me to approach a problem from several directions at once: software, architecture, data, infrastructure, workflow, user experience, and business context.
Teaching and technical documentation have also been a recurring part of my professional work.
I have taught and delivered workshops in software and digital technologies, and I have created technical learning material covering programming, infrastructure, software tools, office automation, and other technology subjects.
I have also worked extensively on Persian-language technical documentation and educational content.
This experience has influenced the way I design systems: a solution should not only be technically correct; it should also be understandable enough that other people can use it, maintain it, and build on it.
My preferred way of working begins with the problem rather than the framework.
I try to understand:
Only after that do implementation choices become meaningful.
This is why many of my projects sit naturally between software engineering, application architecture, business-process modeling, automation, and decision support.
Today, I position my work primarily around:
My strongest contribution is usually in projects where the problem is larger than a single screen or isolated piece of code — where a real process must be understood, structured, and converted into a coherent technical system.
I consider myself a software architect and multidisciplinary technology specialist whose background connects practical engineering with software, data, infrastructure, automation, and organizational systems.
My career has not followed a single narrow technology stack. Instead, it has been built around solving different kinds of technical problems and continuously moving toward larger system-level responsibility.
The common thread across that work is simple:
Understand the real problem, structure it correctly, and build technology that makes the process clearer, more reliable, and more useful.
That is the perspective I bring to software architecture, enterprise applications, technical leadership, and the systems I build.