Role
Software Engineer
Softzino Technologies
Copenhagen — Entry § 01 — Opening
Opener /
I build the small, careful pieces software is made of — components, packages, services — and occasionally I publish research on the side. Before any of it, I guided groups through the Bandarban hills. The through‑line is the same: figure out what the terrain actually is, then document it for whoever comes next.¹
Frontend code for a component library shipped inside Apple. Backend services in Node, Laravel, Postgres. TypeScript packages for teams that shouldn't have to care how the sausage is made. And a machine‑learning paper on plant disease, published in IJEECS. The work is not one thing. It never was.¹
On any given week I am shipping a Vue 3 component, a Node service, a TypeScript package, and sometimes a paragraph of a research paper. Engineers are supposed to pick a lane. I pick the one that needs the work done — and I keep a careful log of what I learned there.¹
¹ The tour-guide years — Bandarban, Rangamati, Sylhet, Sunamganj — are not a detour from the engineering work. They are where the habit of careful documentation was first formed.