Automation, agents, and the interfaces around them.
Most of what I build at work runs inside client systems and cannot be shown. What follows is the shape of it instead: how a process ran before, what I automated, and what I deliberately left to people. Alongside that, the agents and interfaces I build in my own time.Software robots that run business processes end to end for some of the largest companies in Slovenia, Triglav and Petrol among them. So far they have removed 100+ manual steps and over 100 hours of repetitive work, and processed 100+ documents in production. They run on daily and weekly schedules, unattended and overnight, and I keep them healthy once they are live. Built in Power Automate Desktop against SAP and the custom applications each client has built for itself — systems with no API, where the interface is the only way in. Most of the work happens before any code: mapping how the process really runs, and deciding what to automate and what stays with people.
An agent that takes over a task I used to do by hand every evening. On a nightly cron schedule it drives a headless browser across sites that publish nothing through an API, reads what has changed since the last run, scores it against criteria held in a file rather than in the prompt, and posts a short ranked summary to Discord. It runs unattended as a systemd service on an Ubuntu VM, and reports a failed run rather than returning an unverified result.
Scrapes EU and Slovenian tender portals, translates every notice to English, and embeds it so you can search by meaning rather than by keyword — a search for road maintenance also returns a notice about resurfacing works, which shares none of those words. I built the frontend: browsing by country or by EU procurement code, with the active filter kept in the URL so a filtered view can be shared, and infinite scroll over the paginated endpoint I added to the API. Postgres with pgvector ranks what comes back by cosine distance.
A complete storefront journey for a consumer brand — browsing, filtering, cart and checkout — built on a design system rather than page by page: one colour palette, one type scale, and a component set reused across every view. Built in Vue.js and TypeScript, designed in Figma, so the look holds as the catalogue and pages grow.