I'm Sami. I've been working since 2018, and design and development have never been separate jobs for me. Brand and social design, UI/UX, video and motion, CMS and full stack builds, and the servers underneath — I do the ones a project needs, and I've done all of them for real clients. Right now I'm adding data science on top, with an MSc at the University of Primorska.
One person, the whole project — the brand, the interface, the code, and the box it runs on.
I started in 2018 doing product and UI/UX design for clients on Fiverr and Upwork. Then the same clients needed video, so I learned video. Then they needed the actual website, so I learned WordPress, Shopify and Wix. Then the sites outgrew page builders, so I learned PHP and Laravel, and then React and Node. Every step came from a real job that needed it.
The result is unusual and I know it: a designer who can deploy, and a developer who can draw. A layout I hand over is a layout I can already build, and a site I build looks the way it was drawn. Nothing gets translated twice, and nothing waits on someone else's queue.
Most projects need two or three of these at once. That's the whole reason I kept adding them.
Logos, identity systems, packaging and print. Social media campaigns — the steady monthly kind, where a brand needs thirty posts that still look like one brand. Ad creatives, seasonal campaigns, product graphics.
App and web interfaces from wireframe to handover: flows, states, components, and a design system small enough that it actually gets maintained. Presentation decks when a client needs to sell the idea internally.
Promo and social video, product reels, subtitles and versions for every aspect ratio. Motion graphics and animated titles when a still frame isn't enough — usually built from the same brand assets I designed.
CMS builds on WordPress, WooCommerce, Shopify and Wix. Custom work in PHP and Laravel, React and Node. And the unglamorous half: VM setup, deployment, DNS, backups and the pipelines that push it all live.
No handover gap between the design file and the server.
Logo, palette, type and the rules that keep them consistent across print, social and screen.
Flows and layouts drawn with real content in Figma, as a small system rather than a pile of screens.
Laravel, React or a CMS theme, with hand-written markup that stays responsive and accessible.
Server setup, deployment, content updates, campaigns and the fixes that only appear after launch.
More in the case studies, on Behance and on GitHub.
A fashion retailer's online store and its brand presence: product and category pages, seasonal campaign creatives, and the social design that runs alongside the shop. Built on WordPress and WooCommerce so their team can add products without me.
Visit the Site →A training and knowledge platform for the garments industry: course pages, a document library, member areas and a companion mobile app. Interface design plus the WordPress build behind it.
Visit the Site →A multi-tenant support desk built in TypeScript and React: ticket queues, roles and permissions, and an admin side designed to stay readable when the data gets heavy.
View the Repository →Stock and warehouse tracking with dashboards that answer the questions an operations team actually asks: what's low, what's moving, what's stuck.
View the Repository →Ongoing social media design for Crown Farms, Kacchi Khadok, EFG Fashion, Masala Bazaar and Apply Uni UK — campaign sets, seasonal posts and ad creatives, each kept inside its own brand rules.
View on Behance →An interactive dashboard built with R Shiny, Plotly and ggplot2, with a custom themed interface on top — MSc coursework turned into something I can actually show.
View the Repository →Every skill on this list arrived because a client needed it, in this order.
Where it started: app and web interface design for clients I never met in person, delivered against a brief and a deadline. Marketplaces are a hard school — the feedback is public and the revisions are free.
The same clients needed the campaign as a video, not just a post. Promo edits, product reels, animated titles and platform versions — built from brand assets I'd usually designed myself.
Running the campaigns I designed rather than handing them over: social planning, ad creatives, landing pages and reading the numbers afterwards to decide what to change.
Statistics, machine learning and visualization with Python and R. It's the natural next layer: I've spent years making interfaces that show information, and now I'm learning to work out what the information actually says.
Plus professional courses in design, development and marketing — the full list is in my CV.
Statistics, machine learning, data visualization and applied projects in R and Python.
An engineering foundation that taught me to break a system down before trying to fix it — which turns out to be most of software.
I write full stack lessons in Bengali, starting from HTML fundamentals. Explaining something is the fastest way to find the parts I only half understood.
Bengali and English every day, German in progress, and enough Slovenian to greet people properly without switching straight to English.
Frontend and full stack roles where design still counts, with data work as the thread that ties the MSc back to everything I did before it.
Design has been the constant since 2018 — everything else got added around it.
Logo, palette, typography and the rules that hold them together, delivered with a short guide so a client's own team can stay consistent after I'm gone. Packaging and print prepared for real production, not just a pretty PDF.
Monthly social sets, seasonal campaigns, ad creatives and product graphics. The hard part isn't one beautiful post — it's thirty posts across three months that still read as one brand.
App and web interfaces in Figma and Adobe XD: user flows, wireframes, states, components and a maintainable system. Because I build too, I design things that can actually be built on the given budget.
Promo edits, product reels and animated titles in Premiere Pro and After Effects, cut for each platform's aspect ratio — built from the same brand assets as everything else.
A running social set for a farm brand: product posts, seasonal pieces and announcement graphics, all sharing one template system so the feed stays consistent.
View on Behance →Social and announcement design for an industry learning platform, working in the same visual language as the website I built for them.
View on Behance →T-shirt and winter collection posts: product-led layouts where the garment has to stay the hero and the type still has to carry an offer.
View on Behance →Appetite-first layouts for restaurant and grocery brands, where photography, price and offer all fight for the same square.
View on Behance →Paid ad designs for an e-commerce brand and a study-abroad service — built as variations so the campaign has something to test, not one fixed image.
View on Behance →Mobile app interface work and the design for an e-commerce and LMS platform: flows, screens and a presentation deck the client could take to their own stakeholders.
View on Behance →Real text, real products, real constraints before any visual decision. Most layout problems turn out to be content problems.
Type scale, spacing, colour and components. Small enough to remember, strict enough to survive thirty posts and five pages.
Designs change once they're in the browser or on a phone screen. Because I build them, that loop takes hours instead of a round of emails.
I build scalable web applications and the CMS sites that pay for them, and I run the servers under both.
WordPress, WooCommerce, Shopify and Wix builds: themes customised properly, content modelled so the client's team can manage it, and the plugin work that keeps a store running day to day.
Laravel and PHP or Node and TypeScript on the server, React on the front, MySQL or PostgreSQL behind. Dashboards, portals, SaaS tools — the projects where a page builder stops being an option.
VM setup and management, deployments, DNS, SSL, backups and monitoring. Plus Microsoft 365 and Azure administration — users, access and licensing — from working inside a company's existing IT.
R and Shiny dashboards, and Python for analysis as the MSc goes on. The connective tissue between the years of building interfaces and the numbers those interfaces are supposed to explain.
A fashion retailer's online store and its brand presence: product and category pages, seasonal campaign creatives, and the social design that runs alongside the shop. Built on WordPress and WooCommerce so their team can add products without me.
Visit the Site →A training and knowledge platform for the garments industry: course pages, a document library, member areas and a companion mobile app. Interface design plus the WordPress build behind it.
Visit the Site →A multi-tenant support desk built in TypeScript and React: ticket queues, roles and permissions, and an admin side designed to stay readable when the data gets heavy.
View the Repository →Stock and warehouse tracking with dashboards that answer the questions an operations team actually asks: what's low, what's moving, what's stuck.
View the Repository →An interactive dashboard built with R Shiny, Plotly and ggplot2, with a custom themed interface on top — MSc coursework turned into something I can actually show.
View the Repository →Two operational tools: stock tracking with dashboards for what's low and what's moving, and an event-driven service that keeps its parts talking without tangling them together.
View the Repositories →A property and rental management application in PHP: tenants, units, payments and the reports a landlord actually opens at the end of the month.
View the Repository →Email is the fastest way to reach me. I read everything, and I answer within a day or two.