KM // PORTFOLIO
00%
Kareem Malaeb
Software Engineer / Full-Stack & Systems Architecture

Engineering software that carries real weight.

Designing and shipping full-stack systems, from business requirements through architecture, implementation, and the deploy that actually holds under production load.

SCROLL
ABOUT

Business analyst and software engineer, same person.

Most of the cost in software isn't the code, it's building the wrong thing correctly. Before a service or schema gets written, I want to understand the operation it's supporting: what breaks today, and what "done" means to the business.

Day to day that's Java and Spring Boot on the backend, React on the frontend, and cloud infrastructure that doesn't fall over the first time it matters.

0
Systems Shipped
0%
Uptime Target
EXPERTISE

Core competencies

The full path from requirement to running system, not just the parts that are fun to build.

▼

Software Architecture

Scalable, loosely-coupled systems designed to last well beyond the demo.

>_

Backend Development

High-performance, concurrent server-side logic built on Java and the Spring ecosystem.

</>

Frontend Development

React interfaces that make backend complexity feel simple, not bolted on afterward.

{ }

API Design

Secure, well-documented REST interfaces that don't leave the frontend team guessing.

◇

Cloud & DevOps

Containerized, CI/CD-driven deployment on AWS built to survive real traffic.

SELECTED WORK

Systems built for real operations

FULL-STACKOPERATIONS

Freight Forwarding Operation System

A Spring Boot API paired with a React front end for agent management, inquiry intake, and authenticated access. It replaces a workflow that used to run on spreadsheets and email.

Case study →
ARCHITECTURE

Project Meridian

Backend modernization that decomposes a monolith into services with clear ownership and contracts.

Details →
PROCESS

How a build moves, start to finish

01

Discovery

Understand the operation before touching the stack.

02

Business Analysis

Translate requirements into rules that hold up under real use.

03

Architecture

Decide the shape of the system before writing the code.

04

Development

Backend and frontend built in step with each other.

05

Testing

Break it before a user does.

06

Deployment & Support

Ship it, then watch it. Support doesn't end at deploy.

"Handed over a spreadsheet-and-email process and got back a real system, on time, and it hasn't gone down once."

OPERATIONS LEAD · LOGISTICS CLIENT
CONTACT

Have an operation that needs software?

Tell me what's breaking, or what you're trying to build.