BACKEND. CLOUD. CONNECTED SYSTEMS.
Umair Qamar
I work across Node.js and Python services, AWS infrastructure and data platforms. I connect implementation details with the reliability and maintainability of the wider system.
AWS & serverless · Asynchronous systems · Data architecture
01 / CLOUD / BACKEND ENGINEER
My engineering work brings together APIs, asynchronous workflows, operational storage and analytical data. From startup infrastructure to an enterprise retail engagement, I stay close to the dependencies and decisions that shape delivery.
Customer-data platform work connected PostgreSQL on RDS with an S3-based lakehouse using Apache Iceberg and Athena. Different access patterns called for different storage responsibilities.
Explore the storage decisions ↗At Revcloud, my work spanned backend services, cloud infrastructure and data-platform engineering. I stayed hands-on as the startup grew.
View engineering experience ↗My SRG engagement through Convert Digital brings interconnected systems, customer-facing performance and safe change delivery into the same engineering conversation.
View the SRG engagement ↗02 / SELECTED ENGINEERING WORK
The context, my contribution,
and the decisions underneath.
03 / EXPERIENCE ACROSS STAGES
Scope changes.
Ownership still matters.
Senior Software Engineer / Tech Lead
I contribute hands-on engineering and technical leadership to SRG's Australian retail engagement through Convert Digital. Working within an established engineering ecosystem means connecting implementation decisions with the wider product, the teams around it and the systems already in use.
This is engineering with enterprise constraints: interconnected systems, performance-sensitive customer experiences and changes that need to be delivered safely. Reliability, maintainability and clear technical decisions shape how I approach the work.
A multi-brand retail group spanning Spotlight, Anaconda, Harris Scarfe and Mountain Designs. That breadth brings a different delivery context from building a startup's first product.
Group context, not a claim of ownership across every brand or system.
I joined as the first full-stack engineer from Pakistan before the startup had its first customers. My work spanned backend services, cloud infrastructure and data-platform engineering as the company grew.
Alongside hands-on development, I led engineering teams and helped connect technical decisions with product delivery.
Earlier roles built my foundation across frontend and backend development, from React interfaces and API integrations to Node.js services, authentication and application workflows.
04 / MY ENGINEERING TOOLKIT
Across the interface, the services
and the infrastructure underneath.
A toolkit, not a fixed recipe. I choose technologies around the product, the team's needs and the constraints of the system.
Serverless workflows, containers and infrastructure as code.
APIs, microservices and asynchronous systems.
Operational data, caching and analytical storage.
Interfaces, application state and connected workflows.
Connecting LLM applications with useful context through ingestion, chunking, embeddings and retrieval.
05 / HOW I LEAD DELIVERY
Good technical leadership makes
the next decision clearer.
Make the user need, constraints and success criteria explicit before choosing a solution.
Connect the interface, service boundaries, data model and infrastructure into a coherent plan.
Work through the difficult implementation details and help the team move with shared context.
Bring testing, rollout and operational feedback into the conversation, not just feature completion.
06 / ALWAYS BUILDING, ALWAYS LEARNING
Hands-on engineering experience, AWS credentials and formal study in AI.
Solutions Architect credential ↗
Cloud Practitioner credential ↗
Lahore University of Management Sciences (LUMS). In progress.
University of Engineering and Technology, Lahore.
