CS01
Amazon seller operations · 2026
Amazon Portal
I built a secure operations portal for an Amazon seller management agency, bringing client work, reports, files, product trackers, and conversations into one accountable workflow.
Complete product systems.From interface to infrastructure.
I’m Ayan, a full-stack product engineer working across web, cloud, desktop, and mobile. I carry product decisions, interface work, infrastructure, integrations, and delivery as one connected system.
Selected work
Complete systems documented from working code, measured outcomes, and the decisions behind them.
CS02
Children’s occasion wear · 2026
Aks-e-Gul
I designed and built a mobile-first storefront and operations system for a children’s occasion-wear brand, from product discovery and custom sizing to COD fulfillment and first-party insight.
More systems
A quieter index of original work across local software, systems tooling, and realtime products.
01
Restaurant operations · 2026
Countertop
Local-first point-of-sale desktop and Android app built for a home-based restaurant: menu, orders, receipts, expenses, profit reporting, search, backups, and data migration without an account or network.
02
Systems utility · 2026
Blitzer
Rust terminal downloader with parallel range requests, worker pooling, verified resume manifests, retry backoff, speculative overlap for no-range servers, and a full interactive TUI.
03
Realtime multiplayer · 2026
Ludo
Server-authoritative multiplayer Ludo with Socket.IO rooms, reconnect survival, match history and replay, first-party authentication, rate limits, runtime schemas, and a multiplayer smoke test.
Working position
The operating principles behind the systems above.
The useful distinction is not frontend versus backend. It is whether one person can hold the product, the failure modes, and the delivery path in the same mental model. That is the work I take on.
i
One engineer, the whole delivery path.
I can move from product modeling and interface work through authentication, data, integrations, deployment, desktop packaging, and operational handoff without losing the thread between disciplines.
ii
Boundaries and failure modes are part of the product.
Passkeys, role-aware mutations, runtime validation, idempotent background work, atomic imports, and verified resumes are designed into the system rather than applied after the interface is finished.
iii
Communication stays close to the code.
You work directly with the person modeling, implementing, testing, and shipping the system. Decisions remain explainable, and handoff artifacts are part of the build.
Field notes
Short records of decisions that mattered after the interface was finished.
Authorization Belongs at the Mutation
A hidden button is not a permission boundary. Desk Portal re-checks the active session, role, and granular permission where each mutation executes, so a stale screen cannot replay authority it no longer has.
A Backup Is a Transaction
Countertop validates a versioned import before it replaces local state, creates a safety backup first, and keeps recovery behavior testable. “Local-first” only earns trust when restoration is designed as carefully as storage.
When a Server Refuses Ranges
Parallel downloaders usually assume byte ranges. Blitzer probes that capability, uses verified overlap when speculation is safe, and falls back to a single stream rather than pretending unsupported concurrency is reliable.
Back Office Is Part of the Storefront
A polished catalog is unfinished if every order creates manual chaos. The store and its administration share one commerce model for variants, shipping, coupons, COD totals, reviews, communication, and fulfillment.
Evidence
One source invariant and a live index of original public work.
src/lib/auth.ts
TypeScript
export async function requireActionPermission(permission: AdminPermissionKey) {
const user = await requireActionRole('ADMIN');
if (!hasAdminPermission(user, permission)) {
throw new Error('Unauthorized');
}
return user;
}Complete source specimens and implementation notes live inside the case files.
Connecting to GitHub
Stars
Loading
Forks
Loading
Repositories
Loading
Followers
Loading
Available for selected work
Have a system to ship? Tell me where it is stuck.
Send the problem, the current constraints, and the outcome you need. A prepared brief is not required. I will reply with focused questions and a practical next step, usually within 24 hours.
Response time
Usually within 24h
Working mode
Remote · asynchronous
Timezone
UTC+5 · Pakistan