OmniTechs publishing platform
The bilingual site, typed content, search contracts, automated tests and guarded Windows publication form one maintained production system. It demonstrates building and delivery, not customer outcomes by itself.
Founder of OmniTechs · Groningen
Sina Esfahani — engineer, software builder and founder.
I combine structural engineering, full-stack software development and practical experience in logistics and production. This is the work history, skill set and visible project evidence behind what I build.
Founder profileGroningen · NL
A background without inflated proof
I founded OmniTechs in Groningen in March 2023. My path runs from civil and structural engineering through Python/Django and full-stack product development into digital operations, while warehouse and production work keeps my view of real processes grounded.
The project cards show work from the studio I lead. Each one states what actually exists and does not turn a demonstration, production system or closed project into a customer result.
Project status
View the live result
Servana
A live hospitality service flow with QR entry, ephemeral sessions, staff access and a shared status lifecycle. It is a working demonstration, not a claim of a customer installation or commercial result.
3D printing for architectural designs
Within the separate 3D route, three large architectural designs were printed. The public Trustpilot review supports quality, progress updates and delivery for that work only—not the Operations service.
BeeBusy
An earlier platform direction for connecting local demand and supply. The case records lessons about focus, repeat demand, density and adoption without claiming current availability, revenue or scale.
From structural engineering to digital products
My education started with physical systems: a BSc in Civil Engineering at Urmia University and an MSc in Structural & Earthquake Engineering at Semnan University. Structural dynamics, modelling and working with uncertainty still shape how I break down technical questions.
The focus then moved into software: first backend and platform work, then complete products, integrations and operational workflows. I do not treat these as separate identities; they share one question: what needs to work reliably under real conditions?
Software and technical leadership timeline
Some roles overlapped because remote projects and entrepreneurship ran alongside one another. The timeline makes that visible instead of polishing it into a single linear story.
- OmniTechs — founder and full-stack/product engineer · March 2023–present
- Clever Safety — full-stack developer · August–December 2023
- irn-clever — CTO and technical lead · March 2022–September 2023
- Leadpaka — Django backend and full-stack developer · July 2021–May 2023
- Sharif Maktab — programming instructor and Java developer · January–December 2023
Operational experience alongside software
Digital operations stays credible when you also see what a scanner, queue, handoff or awkward system does on the shop floor. That is why my operational work belongs in this portfolio.
- Warehouse, automation and dispatch operations · 2024–June 2026
- Production and forklift operations · June 2026–present
- Practical areas: WMS and scanners, warehouse robots, order and dispatch flows, production handoffs and physical safety
Software and systems skills
My stack is a toolbox, not a menu every project must use. I choose the smallest combination that fits the process, risk and ownership model.
- Backend: Python, Django, Django REST Framework, Celery, Redis, Java and Spring, NestJS
- Frontend and apps: TypeScript, JavaScript, React, Next.js, React Native and Angular
- Data and integration: PostgreSQL, REST APIs, validation, scraping, automation and OpenAI integrations
- Delivery: Docker and Compose, Git, automated tests, Playwright, accessibility checks and guarded releases
What the current OmniTechs system demonstrates
The current founder-led OmniTechs system demonstrates how operational questions, roles and boundaries are modelled, how interfaces and backends are built, and how delivery remains verifiable. This is system and studio evidence; specialist knowledge or extra capacity still belongs explicitly in each project scope.
- Process analysis, product scope and acceptance criteria
- Domain contracts, APIs, databases, queues and reliable state transitions
- Responsive interfaces, accessibility and bilingual content architecture
- Test strategy, privacy-conscious observability, publication, rollback and handover
- Physical-digital prototypes and 3D-printing workflows
The problem chooses the technology
That is my working rule. Sometimes the right outcome is configuring an existing tool better. Sometimes one integration, portal or workflow is missing. And sometimes an idea belongs in the Lab or a project should stop. Quality is not how much technology gets added; it is how precisely the real problem is solved and proven.
Bring one problem that needs to work better.
The free fit check first determines whether OmniTechs fits and which small, verifiable next step makes sense.