Writing / Personal Account

How I Got Here

Building a
career that
wasn't supposed
to exist

I wish I could tell you there was a plan. There wasn't. Most people pick a lane. I ended up in three — and I'm still figuring out what that means.

In this piece

IThe advantage of having no roadmap
IIStudying two worlds at once
IIIThe years that looked messy from outside
IVBuilding before confidence arrived
VThings I'd do differently
VIWhat I still don't know

The starting point

The advantage of having no roadmap

When I started looking into AI governance and legal technology, I kept searching for people who had already done it in Pakistan. I wanted the checklist. The guide. The sequence.

I found almost nothing.

No senior from my university doing exactly this. No established pipeline. No one saying: start here, do this, avoid that.

When nobody gives you a roadmap, you stop asking for permission. You start building your own.

That absence turned out to matter. It meant there was no orthodoxy to defer to. No conventional sequence to follow. The work I've done — at Lex Lata, on The Digital Gavel, on the Land Revenue Act chatbot, on this site — all of it started as a kind of improvisation. Not recklessness. Improvisation. The difference is that improvisation still has intent.

The dual degree

Studying two worlds at once

Law taught me how institutions think. Data science taught me that institutions are often making decisions about systems they barely understand.

The more I studied both, the harder it became to stay in only one. Law without technology felt incomplete. Technology without governance felt dangerous. Policy discussions lacked technical grounding. Technical discussions ignored legal consequences.

The actual reason I enrolled in data science

I couldn't afford to be the person in the room who had to take the technical claims on faith. Understanding enough to ask the right questions is a different threshold than understanding enough to build the systems — and the first threshold is what this work actually requires.

I became interested in the space between those conversations. That space — where regulatory text meets model architecture, where constitutional rights meet algorithmic outputs — is where most of my work now lives.

It's also still underbuilt. Which means there's room.

The honest version

The years that looked messy from outside

My career strategy looked less like a roadmap and more like opening twenty browser tabs and refusing to close any of them.

If someone looks at my CV quickly, they might see internships, research projects, certifications, publications, scholarships, competitions — and assume there was a grand strategy behind all of it.

The truth is less glamorous. A lot of it came from curiosity. A lot came from saying yes before I felt ready. Some applications were rejected. Many emails were ignored. Some projects quietly failed.

Most people only see the successful version of a journey because failure rarely gets a LinkedIn post. This page is trying to be a different kind of document.

The pattern that held

Building before confidence arrived

One of the strangest parts of this journey is that I've spent most of it building things before feeling qualified to build them.

The website. The writing. The Digital Gavel. The legal-tech experiments. The research at Lex Lata. None of them arrived after confidence. They arrived before it. The confidence showed up later — sometimes much later — as a consequence of having shipped something real into the world and had it tested by actual stakes.

Working on live IHC filings calibrated my attention in ways that academic exercises never could. When a wrong citation has consequences for a real client, precision stops being a virtue and becomes a minimum.

Waiting for a project to be "ready" before sharing it is how good work stays invisible.

The cross-jurisdictional work — Pakistan, India, UAE, US legal frameworks — started as a byproduct of different opportunities. It became deliberate once I realized how rare it was. Most people in AI governance come from a single legal tradition. Someone who can map GDPR onto Pakistani data protection bills, or connect an Indian court's reasoning on algorithmic accountability to EU precedent — that's a much smaller group.

The South Asian regulatory context is underrepresented in the conversations that matter. I treat that as a positioning advantage, not an obstacle.

Correctable mistakes

Things I'd do differently

Four things. Specific ones, not general wisdom.

Four correctable mistakes Retrospective — written honestly
1

Start publishing sooner.

Writing publicly forces a kind of intellectual honesty that private notes don't. The Digital Gavel should have existed a year earlier than it did. The discipline of committing a position to something other people can read is not the same as knowing what you think.

2

Read the primary texts, not the summaries.

Most commentary on the EU AI Act, GDPR, and NIST frameworks is imprecise at the margins — and the margins are where the interesting questions live. The annexes to the EU AI Act define what "high-risk" actually means in practice. The summaries don't. This habit takes longer to build than it sounds.

3

Build in public, even when the work feels incomplete.

The Land Revenue Act chatbot, the portfolio site, the legal drafting samples — shipping them mattered more than perfecting them. Feedback from real users and real readers is a different class of information than internal revision.

4

Treat credentials as proof, not currency.

The Google and McKinsey certifications are useful for signaling, not for the knowledge itself. That distinction matters: signaling gets you in the room. What you do in the room is something else entirely.

Still open

What I still don't know

What keeps me going isn't ambition. Ambition sounds neat. What I have is closer to intellectual restlessness — a set of questions I find impossible to ignore.

How should AI be governed when the regulator is the FIA, not the ICO?
What happens when automated decision systems meet legal frameworks that predate the internet?
Can countries like Pakistan shape the future of AI regulation instead of just adapting to it?
Can someone from Faisalabad contribute meaningfully to conversations happening in Washington, Brussels, and Singapore?

I don't know. But I intend to find out.

How to scale the work without losing quality. How to position for opportunities that don't exist yet in my immediate geography. How to build institutional presence that makes research matter beyond the people who already follow it. These are still open.

This page will stay honest about what I know and what I don't.

A note, if you're in a similar position

Every meaningful opportunity appeared after I started moving, not before.

If you're navigating something similar — law school alongside technical ambitions, South Asian context, AI governance interest with no clear entry point, or just the general chaos of building something that doesn't have a template yet — I'm reachable. I don't have all the answers. But I'll give you an honest account of what I've tried.

Get in touch
Back to Writing