Email me

Data Analyst · Pristina, Kosovo

Altin Murtezaj

I work with data, and I build software because I can't leave a good idea alone.

Analytics is my profession. I spend my days in SQL, Power BI and Python, turning messy numbers into something a team can actually decide on. Software is the part I do for myself. Most evenings you'll find me building an app that started as a small annoyance and turned into a real product.

Open to analytics roles and interesting collaborations

Focus
Analytics, reporting, dashboards
Daily tools
SQL · Power BI · Python
Also builds
Web apps, APIs, internal tools
Based in
Pristina, Kosovo
01About

A data person who kept picking up engineering.

I'm Altin, an analyst by profession and a builder by habit. The two have never really stayed in separate boxes for me.

Altin Murtezaj

I work as a Data Analyst. My days are spent close to the numbers: writing SQL against production databases, modelling data into something coherent, and building Power BI reports that people open on a Monday morning and actually use. I like the part of the job where a vague question turns into a clear answer, and I like it even more when that answer changes what someone decides to do.

Outside of work, building is simply what I do for fun. Ideas pile up faster than I can ship them, and every so often one is good enough to become a real, working product. None of it started as a business plan. It started because I wanted to see if I could make the thing exist.

01

Start with the question

A dashboard nobody asked for is decoration. I work backwards from the decision someone needs to make, then figure out which numbers actually answer it.

02

Trust the data first

Most of the work is cleaning, joining and sanity-checking before anything gets visualised. If the underlying data is wrong, a beautiful chart just makes the mistake more convincing.

03

Build the thing

When a report keeps getting rebuilt by hand, I'd rather write the tool that removes the work. That instinct is what pulled me into software in the first place.

02Skills

Analytics is the craft. Engineering is the range.

The first list is what I'm hired for. The second is what lets me build the tools around it, and what I reach for on my own time.

Data & Analytics

What I work with day to day.

  • SQLQuerying, modelling, optimisation
  • Power BIReports, DAX, data models
  • PythonAnalysis and automation
  • pandas / NumPyCleaning and transformation
  • TableauExploratory dashboards
  • ExcelModelling, pivots, ad-hoc analysis
  • Data visualisationCharts that answer a question
  • ReportingRecurring and self-serve

Software Development

What I build products with.

Frontend

  • React
  • Angular
  • TypeScript
  • JavaScript
  • Tailwind CSS

Backend

  • .NET / C#
  • Node.js
  • Express
  • Java / Spring Boot
  • REST APIs

Databases

  • PostgreSQL
  • SQL Server
  • MongoDB
  • DynamoDB

Tooling

  • Git
  • Docker
  • AWS
  • Postman
  • Figma
03Projects

Things I've built, and why I built them.

Each of these started with a real problem someone had, usually one I found interesting enough to keep working on after hours.

01

Themeli

A construction marketplace for Kosovo

The problem
Buying construction material in Kosovo still runs on phone calls and word of mouth. There's no single place to compare what a supplier stocks, what it costs, or whether the business on the other end is one you can trust. Finding a plumber or a civil engineer works the same way.
What I built
A marketplace with three sides to it: a catalogue of materials and tools from verified suppliers, a searchable directory of professionals by trade and city, and a request-for-quote flow where someone posts what their project needs and suppliers come back with offers. An admin panel sits behind all of it for supplier verification, moderation and orders.
My role
Built it end to end: the data model, catalogue and search, the RFQ flow, the verification pipeline, and the admin dashboard. That last part is where both halves of what I do meet: I shipped the product, then built the reporting layer to actually understand what was happening inside it.
  • Next.js
  • Node.js
  • PostgreSQL
02

LindiDoors

Order and production management for a door factory

The problem
A door manufacturer was running orders on paper and spreadsheets. Nobody could say which order sat at which production stage without walking the floor and asking.
What I built
A CMS and CRM that digitises the whole order lifecycle: customer records, specifications, inventory and production stages, all with role-based access so the office, the workshop and management each see what belongs to them.
My role
Designed the data model and built the full stack.
  • React
  • Node.js
  • Express
  • PostgreSQL
  • JWT
03

AgFerm

Production tracking and analytics for agriculture

The problem
Producers were tracking fermentation cycles in notebooks. Nothing could be compared across batches, so the same mistakes repeated season after season.
What I built
A platform for recording every cycle, monitoring it live, and reading the results back as dashboards, so a producer can finally see which conditions actually produced the better batch.
My role
Full-stack build, including the reporting and analytics layer.
  • React
  • Node.js
  • PostgreSQL
  • REST API
  • Dashboards
04

Food Delivery

Ordering with real-time delivery tracking

The problem
Restaurant ordering falls apart at the moment the customer wants to know where their food is, and the kitchen wants to know what's next in the queue.
What I built
A full-stack ordering platform with live order state pushed to both sides, complex menu handling, and map-based tracking from the kitchen to the door.
My role
Built the frontend and the .NET backend, including the real-time layer.
  • React
  • .NET Core
  • SignalR
  • MSSQL
  • Google Maps API
Frontend repoBackend repo
05

Zabeli Architects

Portfolio site with a self-service CMS

The problem
An architecture studio needed its work presented properly, but every update meant going back to a developer.
What I built
A restrained, image-led site backed by a custom admin panel, so the studio adds and reorders projects themselves without touching code.
My role
Designed and built both the public site and the admin dashboard.
  • React
  • .NET
  • AWS DynamoDB
  • Admin panel
Frontend repoBackend repo
06

GlobESIM

Buying and activating eSIM data plans

The problem
Getting mobile data abroad still means hunting for a shop. eSIM solves it technically, but the buying experience is usually the hard part.
What I built
An e-commerce flow wired directly into telecom provider APIs, so a plan bought online is provisioned and usable within seconds of payment.
My role
Worked on the storefront and the provider and payment integrations.
  • React
  • Node.js
  • Payment gateways
  • Telecom APIs
Repository
04Contact

Say hello.

Whether it's an analytics role, a question about something I've built, or an idea you want a second opinion on, I read everything that comes in.