From early startup to growing team
At Revcloud, I worked across backend, cloud and data-platform engineering and led teams as the company grew. Technical direction stayed connected to implementation.
View the startup story ↗TECHNICAL DIRECTION. HANDS-ON DELIVERY.
Umair Qamar
I help connect product intent, technical decisions and the people doing the work. I lead engineering delivery while staying hands-on across the stack.
Architecture & tradeoffs · Team leadership · End-to-end ownership

01 / HANDS-ON TECH LEAD
I joined Revcloud as its first full-stack engineer from Pakistan before its first customers, and later led engineering teams alongside implementation work. My experience also includes an enterprise retail engagement through Convert Digital, bringing a different set of delivery constraints.
At Revcloud, I worked across backend, cloud and data-platform engineering and led teams as the company grew. Technical direction stayed connected to implementation.
View the startup story ↗The SRG engagement places the work in an established retail engineering ecosystem. Reliability, maintainability and safe changes shape how I approach delivery.
View enterprise experience ↗With JobSprint OS, I drove requirements, iteration and review for a workflow I needed myself. Approval boundaries and continuity of records were deliberate product choices.
Explore ownership in practice ↗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.
APIs, microservices and asynchronous systems.
Interfaces, application state and connected workflows.
Serverless workflows, containers and infrastructure as code.
Operational data, caching and analytical storage.
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 ↗