About a platform engineer who still answers the pager.
I am Muhammad Sharjeel, a Senior Software Engineer at wAI Industries in Islamabad, Pakistan. Five years in software, three and a half of them building and running multi-tenant platforms.
Experience
2019 to nowI like the unglamorous end of software. Tenant isolation, session bugs that only appear under load, pipelines that refuse to ship a vulnerable image.
Mar 2023 to now
Senior Software Engineer
wAI Industries, Islamabad
Platform and product engineering across PolyX, the Alara suite and ODIN, from design through production operations.
Aug 2021 to Feb 2023
Full Stack Developer
CodeFrenetics, Islamabad
Hallocasa, an international real-estate platform with real-time chat. The ONIT ERP system. IoT control on Raspberry Pi. Stripe payments for a marketplace.
2019 to 2020
Android Developer Intern
Kryptohive, Rawalpindi
Android applications in Java and mobile UI design.
2017 to 2021
BS Computer Science
National University of Modern Languages, Islamabad
Final-year project: neural style transfer on Android.
How I work
One workflow, every engineerHumans are architects. Agents are engineers.
When an agent can write the implementation faster than any one engineer, the rare skill is no longer typing the change. It is deciding what to build, in what order, with what guarantees. This is the workflow my team follows on every repository.
- 01
Product discovery
What and why
One living document for what the customer sees: screens, responses, status changes and edge cases. It never says how we build it.
- 02
Tech discovery
How, with options
One document per component: the problem, the options weighed, a recommendation and the open questions. No feature is written until it is complete.
- 03
ADRs and architecture
Decisions on record
One decision per record, never edited once accepted. The architecture document always describes what is, and changes in the same pull request as the code.
- 04
Implementation
Features and spikes
Every feature has acceptance criteria and test cases before anyone starts. Spikes answer one question in a fixed time, and a person signs the result.
- 05
Release
Ship and freeze
A release document generated from the work itself, a health check of the repository, then the merge.
- draftPlan being written
- readyTests defined
- in-progressOn a feature branch
- reviewPull request open
- doneMerged
The decisions
- Naming the problem clearly
- Writing acceptance criteria
- Picking between options
- Signing off on experiments
- Updating the rules when reality moves
- Reviewing what the agent ships
The execution
- Reading the brief and the rules
- Writing the tests first
- Implementing against the criteria
- Running checks and opening the pull request
- Fixing review comments
- Asking when the rules do not cover it
AGENTS.md
Standing orders at the root of the repository and in every folder that needs its own. People and agents read the same file.
Skills
Rulebooks that load themselves when an agent touches a matching folder, plus a few commands that move a step forward.
Connectors
Source control, pipelines and cloud state, so an agent can open a pull request and read a build. Read-only by default.
Allowlist
Routine, low-risk commands run without asking. Anything destructive still needs a person.
Stack
What I reach forBoring tools, used on purpose.
- Platform
- Kubernetes, ingress-nginx, autoscaling, network policies, Terraform, Azure, Docker
- Delivery
- Azure DevOps pipelines, tagged releases and rollback, TruffleHog and Trivy gates
- Identity
- SSO and identity providers, sessions, API keys, access tokens, rate limiting, module-based access control
- AI
- MCP servers, LLM features, speech-to-text pipelines, multi-agent development workflows
- Code
- TypeScript, Node.js, Next.js, React, Python, PostgreSQL, MongoDB, Redis, Kafka
Let’s work together on Upwork. For platform, identity and full-stack work with a clear scope.