About · Engineering profile

Product Engineering · AI Systems · Frontend Architecture

A software engineer who works from system behavior back to the interface.

Mohammad's strongest work sits between product engineering and systems integration: translating APIs, asynchronous jobs, live events, and imperfect data into software people can understand and operate.

01 · Working approach

How he approaches a build.

01
Define the boundary
Separate product concerns, backend contracts, and compute-heavy services before shaping the UI.
02
Model every state
Loading, progress, partial results, empty data, failure, and recovery are part of the feature—not cleanup work.
03
Make complexity inspectable
Use typed data, visible system states, and documentation so another engineer can reason about the code.
04
Optimize with evidence
Reduce rendering and data work where the product exposes a real bottleneck, especially maps and media timelines.

02 · Experience

Mariana Express Lines

Software Engineering Intern / Frontend Engineering

6-week summer training

A real-time shipment tracking interface designed for maritime logistics, bringing route data, operational status, delays and analytics into one coherent frontend.

Google Maps / route visualization

Worked with vessel route visualization using polylines, port markers, route status, delayed route states, skipped route points, marker clustering and route simplification.

Real-time event experience

WebSocket-powered shipment updates allowed the interface to refresh shipment events without reloading the page. The frontend had to update frequently without overwhelming the user.

Data resilience

Shipping systems frequently contain missing coordinates, incomplete route paths, malformed IDs, null values and inconsistent timestamps. The interface implemented validation, fallbacks, warnings and safe states rather than assuming perfect backend data.

Performance

Rendering many simultaneous routes and map points caused Google Maps performance degradation. Marker clustering and route simplification were used to reduce rendering load.

Analytics

Interactive visualization included shipment volume, delay rate, port activity, filters, date ranges and congestion information.

Testing

Included API integration testing, edge cases, invalid shipment IDs, delayed backend responses, regression testing and mobile behavior.

03 · Capability map

Breadth anchored in product delivery.

Product Engineering

Interfaces that remain understandable even when the underlying system is complex.

React
TypeScript
Frontend architecture
Design systems
State management
Responsive applications

Real-Time Systems

Interfaces that continuously respond to changing backend state.

WebSockets
Event-driven UI
Live updates
Loading / error states

Data & Visualization

Turning operational data into interfaces people can actually use.

Charts
Analytics
Dashboards
Maps
Filtering
Information architecture

AI-enabled Products

Integrating machine-learning systems into usable software.

AI APIs
Inference UX
Transcription
Multimodal workflows
Long-running jobs

Engineering Quality

Software designed beyond the happy path.

Validation
Performance optimization
Fallback behavior
Testing
Documentation
Git workflows

Collaboration & Delivery

Working inside real teams, real codebases and real deadlines.

Code review
Cross-functional teams
Agile delivery
Technical communication

04 · Technical foundation

Tools used in context.

Frontend

React · TypeScript / JavaScript · Vite · Tailwind CSS · React Router

Data / API

REST APIs · Axios · WebSockets · JSON · CSV

Visualization

Chart.js · Google Maps API · Data visualization · Geospatial UI

AI / Media

AI inference integration · Speech transcription · Media processing · Multimodal workflows

Engineering

Git · GitHub · Performance optimization · Testing · Documentation · Responsive design

05 · Credentials

Verified learning records.

06 · Education

Bahçeşehir University

Department of Software Engineering

Faculty of Engineering and Natural Sciences

Discuss an opportunity