BACKEND-FOCUSED FULL-STACK ENGINEER / 001

Building the
systems behind
what’s next.

NODE.JS✳TYPESCRIPT✳POSTGRESQL✳AWS CLOUD✳DOCKER✳REST APIS✳DISTRIBUTED FLOWS✳BACKEND ARCHITECTURE✳

01 / ABOUT

Engineering for the real world.

I work where product complexity meets technical responsibility: payments, subscriptions, content platforms, integrations, and cloud operations.

5+YEARS BUILDING SOFTWARE

I care about the details that make software dependable — clear APIs, consistent data, predictable failure handling, and systems the next engineer can understand. My work spans backend-heavy product development and hands-on AWS operations.

Backend systems

APIs, business logic, integrations, stateful workflows

AWS & infrastructure

Cloud services, deployments, troubleshooting, monitoring

Production reliability

Webhooks, recovery flows, operational resilience

02 / SELECTED WORK

Complex problems.
Considered solutions.

Selected professional engineering themes. These are high-level case studies, not public employer source code.

/01

PAYMENTS / SUBSCRIPTIONS

Designing resilient subscription payment flows

Integrating checkout, recurring payments, renewal recovery, and payment webhooks into a coherent backend experience.

THE CHALLENGE

A subscription system must handle asynchronous confirmations, failed renewals, and retries without losing track of the customer’s entitlement.

ENGINEERING APPROACH

Separate payment initiation from asynchronous settlement
Use state-aware renewal and reactivation flows
Build clear failure diagnostics and operational visibility

Node.jsTypeScriptPostgreSQLPayment APIsWebhooks

Experience-inspired overview. Sensitive client details and proprietary architecture intentionally omitted.

/02

CONTENT / INTEGRATIONS

Keeping a streaming catalog in sync

Ingestion pipelines for episodic and live content, with external identifiers, metadata mapping, and content consistency safeguards.

THE CHALLENGE

Upstream metadata can evolve, arrive incomplete, or change its relationships across series, seasons, and episodes.

ENGINEERING APPROACH

Normalize external metadata into stable internal models
Account for changing API response structures
Make repeat ingestion predictable and diagnosable

Node.jsTypeScriptPostgreSQLREST APIsData Modeling

Conceptual representation of professional work; not a claim that code or data is open source.

/03

CLOUD / OPERATIONS

Running and troubleshooting backend infrastructure

Operating backend services in AWS, diagnosing service failures, and improving the reliability of cloud-integrated systems.

THE CHALLENGE

Production failures require tracing behavior across application logs, AWS permissions, network boundaries, and cloud services.

ENGINEERING APPROACH

Investigate errors with CloudWatch and application context
Reason about IAM and S3 access controls
Validate fixes across environments before release

AWSECSS3CloudWatchDockerIAM

Illustrative case study drawn from broad engineering responsibilities.

03 / SYSTEMS LAB

Under the hood.

An interactive look at how I reason about reliable backend systems. Click through a conceptual service architecture or explore the terminal.

INTERACTIVE SYSTEM EXPLORER Conceptual architecture · not a production diagram

ARCHITECTURE NOTE / SERVICE

Services

Business rules live in separately testable services with clear state transitions and reliable background work.

Select a component to explore its role.

A SMALL INTERACTIVE DETAIL

Curiosity is
a feature.

Prefer a command line? There's one here, too. Try help, stack, or projects.

● ● ● zahraa@portfolio:~INTERACTIVE

Welcome to ZahraaOS · type help to get started.

04 / ENGINEERING NOTES

Notes from
the backend.

Short technical reflections on systems, trade-offs, and lessons from building for production.

05 / CONTACT

Let’s build
something meaningful.

Working on a challenging backend problem, looking for a senior engineer, or want to talk architecture? I’d love to hear from you.

zahraamahmood222@gmail.com GitHub

Building the
systems behind
what’s next.

Engineering for the real world.

Complex problems.
Considered solutions.

Designing resilient subscription payment flows

Keeping a streaming catalog in sync

Running and troubleshooting backend infrastructure

Under the hood.

Services

Curiosity is
a feature.

Notes from
the backend.

A webhook is not a transaction

Treat external metadata as an evolving contract

Debugging a cloud failure from symptom to root cause

Let’s build
something meaningful.

Building thesystems behindwhat’s next.

Engineering for the real world.

Complex problems.Considered solutions.

Designing resilient subscription payment flows

Keeping a streaming catalog in sync

Running and troubleshooting backend infrastructure

Under the hood.

Services

Curiosity isa feature.

Notes fromthe backend.

A webhook is not a transaction

Treat external metadata as an evolving contract

Debugging a cloud failure from symptom to root cause

Let’s buildsomething meaningful.

Building the
systems behind
what’s next.

Complex problems.
Considered solutions.

Curiosity is
a feature.

Notes from
the backend.

Let’s build
something meaningful.