Aarhus, Denmark · Open to Backend / Software Engineering Roles

Mehedi Hasan

Java Backend & Software Engineer

I build and evaluate backend systems with Java and Spring Boot — from REST APIs, databases and security to CI/CD, cloud deployment, load testing and architecture trade-offs.

See Engineering Work Contact Me

GitHub ↗ LinkedIn ↗ CV ↗

01 — About

I care about why a system is designed a certain way — not only whether it runs.

I have a Computer Science background and a Master's in Technology-Based Business Development from Aarhus University. My focus is backend engineering with Java and Spring Boot, supported by hands-on work with databases, Docker, automated testing, cloud deployment and distributed systems.

My recent work spans two complementary directions: StockWatch, where I am taking a Spring Boot application through deployment and delivery automation, and my master's thesis, where I built equivalent monolithic and microservice systems to measure when added architectural complexity creates enough technical and business value to be justified.

AWS EC2 production deployment

CI/CD test, build, deploy & rollback

5 services microservice thesis prototype

p95 / p99 latency, MTTR & cost analysis

02 — Projects

Production-Deployed · Featured Project

StockWatch

A stock-monitoring application built around a Spring Boot REST backend and persistent watchlists. It integrates market-price data, evaluates target-price rules, and is deployed with an automated delivery pipeline rather than being limited to a local demo.

Web UI→Spring Boot API→MySQL Market Data→Scheduled Monitoring→Target Rules

GitHub Actions runs backend tests and builds both backend and frontend artifacts.
Backend releases are deployed automatically to AWS EC2.
Deployment includes health checks and rollback when a new release is unhealthy.
REST-based CRUD and persisted stock-monitoring rules backed by MySQL.

Java 21 · Spring Boot · MySQL · JPA/Hibernate · GitHub Actions · AWS EC2 · Gradle

Live App ↗ Source Code ↗

Master's Thesis · Grade 10

Monolith vs Microservices

A controlled architecture experiment comparing equivalent e-commerce implementations to answer a practical question: when do microservices create enough technical and business value to justify their additional operational complexity?

Monolith↔Same Workload↔5 Microservices

Measured response time, p95/p99 latency, throughput and error rate with k6.
Compared CPU/memory usage, MTTR, failure isolation and diagnosis time.
Simulated payment failures, inventory failures and artificial service latency.
Extended technical results into deployment, labor, downtime and infrastructure cost estimates.

Java 17 · Spring Boot 3 · Docker Compose · k6 · Actuator · Python

Research Prototype ↗

03 — Engineering Approach

Build it. Measure it. Operate it.

I want my portfolio to show engineering decisions and evidence, not only technology names. These are the habits I am deliberately developing in each project.

Build clearly

Design focused APIs, persistence models and service boundaries with maintainability in mind.

Test assumptions

Use load tests, failure scenarios and measurable KPIs instead of assuming one architecture is better.

Ship reliably

Automate tests, builds and deployments, then verify releases with health checks and recovery paths.

04 — Skills

Backend

Java · Spring Boot · REST APIs · JPA/Hibernate · Spring Security

Data

MySQL · PostgreSQL · Redis · SQL · Data Modelling

Delivery & Operations

Git · GitHub Actions · CI/CD · AWS EC2 · Docker · Linux · Gradle

Architecture & Analysis

Microservices · Load Testing · Failure Testing · Performance Metrics · Cost Trade-offs

Let's connect

Open to junior and graduate backend / software engineering roles in Denmark.

I am especially interested in teams working with Java, Spring Boot, APIs, cloud systems or distributed backend services — and in environments where I can keep growing through real production engineering.

connect@mehedi.dk