Shape the right thing
Clarify ambiguous requests into usable flows and explicit trade-offs.
My path runs from deciding what should be built to backend and platform engineering, release automation and production feedback. The selected work below shows the systems, trade-offs and outcomes.
I was born in North Macedonia, grew up in Italy and later moved to Switzerland. That movement taught me to adapt quickly without pretending the route was linear.
Software became the place where curiosity could turn concrete. I care less about technology as status than about whether a system makes sense, can be operated and deserves to exist.
I bridge product intent and engineering reality, from the first useful question to a system someone else can operate.
Clarify ambiguous requests into usable flows and explicit trade-offs.
Connect interfaces, services and data while protecting compatibility and operability.
Turn fragile release steps into delivery that can be repeated, inspected and improved.
«Punta alle stelle e se fallisci arriverai comunque sulla Luna»
I have always read it as an invitation to act. Trying does not guarantee the destination, but it changes what becomes possible. Remaining still guarantees only that nothing changes.
Each chapter added a different kind of responsibility: make the environment repeatable, protect a legacy dependency, listen to the operator, own the release and check the system after it ships.
I trace platform changes across services, infrastructure and release pipelines. The job is not finished when the code compiles; I turn one-off steps into repeatable delivery and leave enough operational evidence to understand the release in production.
Since relocating to Switzerland, I have taken on temporary operational roles outside software to support the move.
I worked directly with clients on an established ERP, then traced each request through the web application, shared data model and release. Compatibility mattered because older desktop software relied on the same database; every change had to improve the requested flow without breaking the one already in use.
Cloud environments, automated web and mobile checks, load tests and R&D prototypes were my first paid software work. It taught me to turn a successful experiment into a procedure someone else could repeat and diagnose.
The applied programme joined software, systems, networks and telecommunications. Graduating with 92/100 gave me the technical foundation for the projects and professional systems that followed.
Three working tools, each with a product surface and a technical case study. The write-ups include the choices, evidence and limits, not just the polished outcome.
A private desktop workspace that uses a local language model to compare roles, prepare applications and keep the reasoning on the user’s machine.
A Rust workbench for classifiers that can admit uncertainty, with calibrated abstention and reproducible model artifacts.
A self-hosted placement operations workspace for schools, with versioned programme rules, role-scoped access and an audit trail for sensitive actions.
A project, a technical question, an open-source contribution or a role worth discussing. A few concrete lines are enough; commercial enquiries belong at Ejupi Labs.