Mohamed ElHawary
Discuss a project

Services

Bring me in where decisions and delivery meet.

I work as a senior full-stack engineer, CTO, and tech lead hands-on when the code needs it, strategic when the decisions carry more weight than the implementation.

Start a projectSee the work
Technical editorial collage combining architecture notes, a decision record, code, deployment logs, and production signals

How I help

Senior engineering, shaped around the problem.

The engagement can be narrow or ongoing. The constant is direct ownership: understand the system, make the tradeoffs explicit, do the work, and leave the team in a stronger position.

  1. 01

    Full-stack architecture & development

    Editorial architecture sketch showing connected application, service, and data layers on graph paper

    Design and ship serious product work across web, mobile, backend, data, payments, admin, and integrations with architecture and implementation owned together.

    Useful when

    • The build crosses several layers of the product.
    • A feature or MVP needs one senior technical owner.
    • The first serious version needs to hold up after launch.

    What you get

    • Delivery plan
    • Architecture decisions
    • Implementation
    • Deployment and handoff
  2. 02

    CTO guidance & technical strategy

    Editorial decision collage balancing architecture, team, risk, and delivery trade-offs

    Senior technical judgment for founders and small teams that need clear decisions before they need a full-time CTO.

    Useful when

    • Architecture choices need technical translation.
    • The roadmap needs sequencing around risk and capacity.
    • Tools, vendors, or hiring decisions need a technical owner.

    What you get

    • Technical roadmap
    • Architecture decisions
    • Risk priorities
    • Tool and vendor guidance
  3. 03

    Tech leadership & delivery

    Editorial delivery roadmap moving from team alignment through focus and execution

    Bring rhythm, review, and senior guardrails to a team while staying close enough to the code to unblock the work that matters.

    Useful when

    • Delivery is moving but technical ownership is fragmented.
    • The team needs sharper review and engineering direction.
    • Product goals and implementation keep drifting apart.

    What you get

    • Delivery structure
    • Repo and PR review
    • Engineering mentoring
    • Decision and handoff notes
  4. 04

    Systems rescue & modernization

    Editorial system rescue collage reconnecting a broken architecture through diagnosis and recovery

    Find the real failure points in rushed, fragile, or AI-assisted code, then stabilize the system without turning the work into an endless rewrite.

    Useful when

    • The product works but feels fragile.
    • Auth, data, payments, or deployment carry unclear risk.
    • The team needs technical truth before investing more.

    What you get

    • Architecture and risk map
    • Fix-now vs. fix-later plan
    • Critical implementation
    • Production-readiness notes

Engagement shapes

Use the amount of leadership the work actually needs.

01

Focused intervention

A bounded audit, rescue, architecture decision, release blocker, or product slice with a clear finish line.

02

Build + lead

Hands-on implementation with technical ownership across the decisions, delivery, verification, and handoff.

03

Ongoing leadership

Fractional CTO or tech-lead support for teams that need continuity without making a full-time hire yet.

Start with the real problem

Tell me what is stuck, risky, or ready to build.

I’ll help you determine the right shape of engagement before we turn it into a scope.

Start a project