Database performance
Slow reports, blocking, deadlocks, and queries that fall over at month end.
Available — 2 contract slots this quarter
Senior Database Developer
& Automation Specialist
I fix slow databases, build the reporting your team actually opens, and automate the manual work between your systems — on the same foundation.
10+ yearsproduction data
Healthcareclaims & EDI
PostgreSQLSQL Server · MySQL
PKTUS / EU overlap
Production shape
illustrative
Apps & forms
web · mobile · WhatsApp
API & queue
validation · idempotency
PostgreSQL / SQL Server
indexed · partitioned
Reports & dashboards
SSRS · Power BI
Alerts & automations
n8n · scheduled jobs
No silent failures, everfailure → alert → context
Where the work happened
MDVision — healthcare revenue-cycle databases
Autymate — automation platform
Own products — four live systems, two private builds
01 — Services
What I do
Six kinds of work, usually in this order: the database first, then the reporting on top of it, then the automation that removes the manual steps in between.
Reporting & analytics
Dashboards and scheduled reports that leadership actually opens.
Data integration
Systems that disagree, reconciled on a schedule instead of by hand.
Automation & workflow
Manual steps between your tools, removed and monitored.
AI document & data extraction
PDFs, invoices and claims turned into validated rows.
Application builds
Small internal tools that replace a spreadsheet and a WhatsApp thread.
02 — Selected work
Systems in production
Six systems I built and still maintain — four live today, two private builds. Use the arrows, the dots, or your keyboard to move through them.
01 / 06
03 — Case studies
What changed
Three engagements, written the way I would explain them on a call: what was broken, what I did about it, and what is different now.
CASE 01
Month-end reporting on a revenue-cycle database
SQL ServerindexingSSRS
Problem
A healthcare reporting database that was fine on a quiet Tuesday and unusable at month end. Reports blocked each other, the finance close queued behind them, and nobody trusted the timing.
Work
Profiled the slowest queries and their plans, rebuilt the index set around the actual predicates, moved heavy aggregation into pre-computed tables refreshed on a schedule, and split reporting reads away from the write path.
Result
Month-end reports now run on a predictable schedule and finish before the morning review instead of holding it up. The team stopped planning its day around a query.
CASE 02
Commission ledger for a mandi agent
MySQLledger designbilingual UI
Problem
Daily business lived in spreadsheets carried forward by hand. Two clerks could produce two different balances for the same dealer, and end-of-day reconciliation was a ritual argument.
Work
Modelled the ledger properly in MySQL — bookings, cash, expenses and dealer accounts with explicit allocation rules — then wrapped it in a bilingual UI the clerks could actually use on a counter phone.
Result
One ledger both the agent and the clerks read from. Disputes are resolved by opening a record instead of rebuilding a day's arithmetic.
CASE 03
Replacing a spreadsheet-and-copy-paste workflow
ETLvalidationalerts
Problem
A recurring batch of documents and code lookups was hand-keyed every week. It was small enough to survive and boring enough that errors were normalised.
Work
Built an import pipeline with validation, an exception queue for anything that failed a rule, and alerts that say what broke rather than that something broke. Delivered with a runbook and a rollback path.
Result
Routine rows land without a person touching them, and the exceptions arrive with enough context to fix in minutes rather than an afternoon.
04 — Skills & stack
What I work with
Deep in the database, comfortable across the systems around it. The automation work is only credible because the data underneath it is engineered properly.
Databases & performance
Reporting & analytics
Integrations
AI & automation
Also
PHPLaravelReactJavaScriptGitLinuxDockerSSRS expressions
05 — Experience
Ten years of production data
Not a list of every role — the two that shaped how I work, plus the long tail before them.
2024 — present
Automation & Database Engineer
Autymate
Building automation pipelines and integrations on top of production databases — scheduled jobs, AI-assisted workflows, reporting, and the validation layers that keep automated rows trustworthy.
— 2023
Database Developer
MDVision
Healthcare revenue-cycle databases: claims and EDI data, reporting for billing and operations teams, and the query and index tuning that made month-end survivable.
Earlier
SQL Server reporting & data work
Enterprise & agency projects
Reporting systems, data cleanups and application databases across logistics, retail and services.
06 — Process
How a job runs
Every stage ends with something you can hold: a report, a plan, a working change, or documentation.
01
Scope
I look at the actual tables, feeds and reports you depend on — where the rows come from, what breaks between systems, and what each report has to prove.
You getA short written scope: what I would build first, what it depends on, and the risks I would not touch yet.
02
Diagnose
We agree what “better” means before anything changes — latency, freshness, or trust in the numbers.
You getA corrected model, an index or schema plan, and the cost of each option in effort and downtime.
03
Build
Changes are built and tested on a copy, with a rollback path and a window that suits your team.
You getA working change, a before/after comparison, and a migration or deploy script you can re-run.
04
Handover & care
Documentation and a runbook so the system is yours, not mine.
You getDocs, monitoring, and an optional monthly care plan for tuning and small changes.
07 — What I work on
Three sides of the same job
Database development is the core. Analytics and finance reporting sit on top of it, and healthcare is where most of the last ten years went. Switch tabs to see the detail.
The core of the work: schema, procedures and the reports and reconciliations that sit on top of them.
Schema, views & procedures
Tables, views, procedures and constraints designed for the application that has to live on them.
Report packs & reconciliations
One deliverable, scoped and finished — a report pack, a reconciliation, or a data fix with a rollback path.
Query & index work
Slow reports and month-end jobs brought back to a predictable runtime.
Automation of manual steps
The copy-paste between tools replaced by a scheduled job that validates and alerts.
Analytical and finance reporting, and the warehouse layers behind them — including the AR, revenue and margin numbers.
Analytical reports
Analysis that answers a question instead of a chart that looks busy — cohorts, trends, exceptions.
Finance reports
Revenue, AR aging, cost and margin reporting that ties back to the ledger line by line.
Data warehouse
Staging, cleansed and modelled layers with a load you can re-run and a model you can explain.
Dashboards & KPI definitions
One agreed definition per metric, so two teams stop reporting two different numbers.
Where most of my ten years went: revenue-cycle and clinical data, and the interface feeds that have to reconcile.
Billing & AR data
Claims, payments, adjustments and AR aging across the revenue cycle.
Lab orders application
Order, specimen and result data and the workflow around it.
EHR data migration
Mappings, validation and reconciliation from the source EHR to the target system.
Interface & difference feeds
Athena and Vision daily feeds checked, diffed and reconciled to the row.
How to start
Fixed scope
A defined piece of work — a report pack, a module, a migration, or a feed that has to reconcile.
Build sprint
One deliverable, scoped and finished: a report pack, a reconciliation, an automation, or a performance fix.
Monthly care plan
For systems that keep growing: health check, monitoring, and a small monthly allowance of changes.
08 — About
Who you would be hiring
I am a database developer first. Ten years of it, mostly inside healthcare revenue-cycle systems where the reports have to be right because somebody gets paid — or does not — on the number.
In the last few years the same skill has turned into automation work: the database is where the truth lives, so it is the right place to hang scheduled jobs, AI extraction and alerts off. That combination is what I sell — someone who can fix the query and then remove the manual step around it.
I work in small, well-scoped engagements, hand over documentation as standard, and would rather tell you a problem is not worth fixing than bill for fixing it.
09 — FAQ
Fair questions
The things clients ask on the first call, answered before the call.
Yes. Most of my work is alongside an in-house developer or DBA — I take a scoped piece, follow your branch, review and deploy process, and hand back with documentation. I am comfortable working from tickets, a shared repo, or a standing weekly call.
Least privilege by default: read-only access for analysis, a named account rather than a shared one, and no copies of production data leaving your environment. I am happy to work under your NDA and BAA, and to sign off on your security policy before touching anything.
Scoping calls usually start within a week of agreeing what we are looking at. Build work depends on the queue — I take a limited number of contracts per quarter so the dates I give are real rather than optimistic.
Fixed-scope pieces and build sprints are fixed fee against an agreed scope, because that is the number you can budget. Care plans are a monthly retainer. Hourly only for genuinely open-ended support.
That is the thing I try hardest to avoid. Every engagement ends with documentation, a runbook, and the reasoning behind the changes. If you want to keep the work in-house after handover, that is a success.
10 — Contact
Book a free 20-minute review.
Tell me the bottleneck. I will tell you what I would look at first, whether it is worth fixing, and whether I am the right person to do it.
mwaqassshahid@gmail.com- One reply within one business day, Mon–Sat PKT
- No newsletter, no sales sequence
- NDA and BAA signed before any access