Farasat
Ali

Farasat Ali, agentic AI and revenue automation engineer
  • The report nobody owns

    I get called in when a revenue team's spreadsheet has quietly become the process — the Monday report three people rebuild by hand, the CRM hygiene nobody owns. The interesting part is rarely the model. It's deciding which call an agent gets to make on its own, and which one it hands back.

  • It worked in the demo

    Then it met real data, real users and a deadline. That gap is most of the job.

  • You have been burned by a pilot

    Four years in, eight open-source packages, twenty-odd write-ups. The failure I keep meeting is not model quality; it is a pilot with no owner and no boundary, so nobody can say whether it worked. I build the version that has both, then leave the team able to run it without me.

  • Agents are the easy part

    Deciding which call one gets to make on its own, and which it hands back, is not.

  • You need it shipped, not shown

    One workflow, one owner, one number it has to move. The rest waits its turn.

  • And then you need it to keep running

    Without me. A system the team cannot operate alone is not finished, it is borrowed.

The thread through the work

I started in web engineering. The problems kept pulling me toward revenue.

A slow screen led to API design. An API bottleneck led to event-driven architecture. Product questions led to AI agent experiments. Watching teams work by hand led me toward RevOps automation. An interest in markets pulled me toward quantitative finance. I still enjoy the details, I have just learned to judge them by what they make possible.

  • Open to research collaboration, speaking, mentorship, and university-facing opportunities.
  • Interested in FTE roles, consulting, contract work, and founder or operator collaborations.
  • Comfortable moving between product strategy, implementation detail, and platform-scale architecture.
Review Projects
2026 – Present

Senior Software Engineer

VentureDive

  • Own features end-to-end across frontend, backend, AI integration, and deployment rather than treating AI as a bolt-on layer.
  • Apply prompt and context engineering plus spec-driven development to make AI-assisted output predictable enough to ship.
  • Review AI-generated implementations against real architecture and maintainability constraints before they reach production.
Next.jsTypeScriptAWSLLM IntegrationAgentic Engineering
2026 – Present

Business Automation & AI Engineer

Dunzo

  • Designed workflows around verifiable completion states so automation gets judged on outcomes, not plausible-looking output.
  • Synchronized business and operational data across systems into machine-readable entities for retrieval and automation.
  • Shipped an AI-assisted advertising automation system that generates campaign assets and uses performance data to inform decisions.
n8nGoHighLevelLLM WorkflowsCRM IntegrationGTM Automation
2025 – 2026

Software Engineer Level II

Digital Dividend Global

  • Architected a custom agent framework chaining tool execution across ETL, documents, Teams, n8n, Zapier, and Outlook.
  • Modernized a legacy codebase into a clearer monorepo architecture with stronger workflows.
  • Optimized AWS Athena workloads across 300M+ events per tenant for roughly 12x faster queries.
TypeScriptReactNext.jsAWSTerraformYarn Workspaces
2023 – 2024

Software Engineer Level I

Digital Dividend Global

  • Built and improved CMS-backed platforms with payments, admin workflows, and reporting.
  • Integrated services such as Tamara, HyperPay, Apple Pay, Securiti.AI, and ZATCA.
  • Improved code quality through better indexing, query work, and deployment refinement.
JavaScriptNode.jsMongoDB.NETReactTerraform
2023 – 2023

Frontend Engineer

Star Marketing Pvt. Ltd.

  • Reduced initial load time by roughly 5x while supporting substantially more content.
  • Improved city-level SEO visibility for global-facing pages.
  • Saved infrastructure cost across ElastiCache, App Runner, and Amplify.
  • Supported migration from Payload CMS and MongoDB to Strapi and PostgreSQL.
Next.jsJavaScriptSSRSEOStrapiPostgreSQLAWS
2022 – 2023

Software Engineer

Divine Virtuality

  • Built reactive frontend experiences with TypeScript, Next.js, and component libraries.
  • Supported reliable deployments and uptime through AWS and Azure-oriented infrastructure work.
TypeScriptReactNext.jsReact NativeAWSAzure
2021 – 2021

Frontend Developer

Civar.com

  • Built scalable UI components for a growing e-commerce platform.
  • Worked with Next.js, GraphQL, NextAuth, and design handoff processes.
ReactNext.jsGraphQLNextAuthJavaScript

Where I am most useful

The problems teams usually bring me in to solve

Usually, something important has outgrown its first design. The team needs someone who can understand the existing system, make the trade-offs visible, and still ship.

  • 01

    AI-native product engineering

    Turning assistants, agent workflows, and retrieval systems into dependable product features—not demos that fall apart around real data or real users.

  • 02

    Cloud and data systems

    Finding the expensive path through serverless and event-driven systems, then improving throughput, reliability, and the ability to see what is actually happening.

  • 03

    Research-ready thinking

    Comfortable discussing experiments, methodology, modeling, and technical uncertainty with professors, labs, and academically minded teams.

  • 04

    Mentorship and standards

    Helping teammates raise code quality, architectural judgment, and development velocity without losing clarity.

Working Stack

Tools I use in real delivery

A practical stack shaped by shipped projects, not by trend-chasing.

43of 43

  • TypeScript
  • JavaScript
  • Python
  • C#
  • C++
  • Rust
  • Solidity
  • LaTeX

TypeScript180K lines migrated off JavaScript, and everything since

  • React
  • React Native
  • Next.js
  • Node.js
  • Express
  • FastAPI
  • .NET Core

Next.jsServer-rendered product and content surfaces

  • OpenAI
  • Gemini
  • LangChain
  • Vector Store
  • TensorFlow
  • Pandas
  • NumPy

OpenAILLM-powered assistants and workflows

  • n8n
  • Make
  • Zapier

n8nAutomation wiring for GTM and RevOps work

  • AWS Lambda
  • S3
  • Kinesis
  • Terraform
  • Docker
  • Azure DevOps

TerraformInfrastructure as code

  • PostgreSQL
  • MongoDB
  • DynamoDB
  • Athena
  • Redis

AthenaQuery tuning that took 300M+ event scans ~12x faster

  • Claude
  • Cursor
  • GitHub Copilot
  • Antigravity
  • Lovable
  • v0
  • Replit

CursorWhere the day-to-day implementation happens

Education

Academic direction with strong technical grounding

My education path blends core computer science, scholarship-backed advanced learning, and an increasing pull toward finance, research, and graduate study.

  1. 2019 - 2023

    Bachelor of Science in Computer Science

    Bahria University, Karachi. Graduated Cum Laude with a 3.76 / 4.0 CGPA and a 70% merit scholarship.

  2. 2023 - 2024

    Quantum Computing Scholarship Program

    The Coding School / Qubit by Qubit program supported by Google Quantum AI and IBM Quantum, taught with curriculum prepared by leading universities.

  3. 2024 - 2025

    Machine Learning in Finance

    WorldQuant University. Applied machine learning for financial data — feature design, validation, and the failure modes specific to non-stationary series.

  4. 2024

    McKinsey.org Forward Program

    McKinsey & Company. A selective leadership and problem-solving programme covering structured thinking, communication, and digital fundamentals.

  5. 2025 - 2026

    Foundations of Financial Engineering Certificate

    WorldQuant University. Studying quantitative finance, econometrics, modeling, and AI-driven decision systems as part of a pathway toward deeper finance-oriented work.

  6. Scholarship awarded

    Leadership and Management Scholarship

    Received a 75% merit scholarship for an MBA in Leadership and Management at Valar Institute.

Every certification and course

Operating Principles

How I approach engineering work

I care about clean systems, but I care even more about whether those systems serve real goals without creating unnecessary complexity.

  1. Build for durability

    Architecture decisions should still make sense after the first sprint, the first new hire, and the first unexpected scale problem.

  2. Prefer useful depth over surface-level breadth

    I would rather know a system well enough to improve it meaningfully than collect shallow familiarity for its own sake.

  3. Translate technical complexity clearly

    Strong engineering matters more when founders, researchers, hiring managers, and non-engineers can understand the trade-offs.

Collaboration Model

How I typically work with teams

Whether the context is a company, professor, founder, or startup team, the delivery model stays grounded in clarity and momentum.

  1. 01

    Clarify the real problem

    Define what success means, what constraints matter, and what type of collaboration actually fits.

  2. 02

    Shape the technical direction

    Turn requirements into an execution path with reasonable scope, architecture, and trade-offs.

  3. 03

    Ship with visible progress

    Keep communication clear, deliver incrementally, and reduce risk through steady implementation.

  4. 04

    Leave behind leverage

    Document, hand over context, and make the result maintainable for the next phase of growth.

Held opinions

The best engineering work is ambitious enough to matter and disciplined enough to hold up when reality gets messy.

FAQ

Questions people usually ask

The short version of how I think about opportunities and fit.

Are you open to research collaboration with professors or universities?
Yes. I am most useful when a research question also needs serious software: an experiment platform, a data pipeline, a reproducible prototype, or a path from a paper idea to something people can test.
Are you looking only for full-time roles?
No. I consider full-time roles, consulting, focused contracts, and founder or research collaborations. The common requirement is clear ownership and a problem substantial enough to justify doing the work properly.
Do you mentor or speak?
Yes. I am open to mentorship, tech talks, workshops, speaking opportunities, and conversations that create value for engineering communities or academic circles.
Which kinds of teams benefit most from working with you?
Teams that need someone who can move between architecture, implementation, debugging, AI integration, and platform thinking without losing delivery momentum.
How do you usually start an engagement?
By finding the real constraint, which is often not the one in the brief. A short read of the system, the data and the failure history, then a written view of what is actually expensive and what I would change first. That is useful on its own even if the work stops there.
What does a realistic AI project look like with you?
One workflow, one owner, one number it has to move. Grounded retrieval over sources you already trust, visible uncertainty, and a clear boundary on what the system decides alone. Demos are easy; the gap between a demo and something a team can operate is most of the job.
Do you work with existing codebases or only greenfield?
Mostly existing ones. The interesting problems are in systems that already work and have outgrown their first design — a Lambda path that got expensive, a monorepo nobody wants to touch, a query that quietly became the bottleneck.
How do you handle handover?
As part of the work, not as a final phase. Documentation, the reasoning behind the trade-offs, and enough tests that the next engineer can change things without being afraid. A system the team cannot operate without me is not finished, it is borrowed.
What are your rates, and how do you scope?
It depends on shape rather than hours: a review is a fixed scope, an implementation is a milestone, an ongoing advisory is a retainer. Tell me the constraint and the deadline and I will tell you what is realistic — including when the honest answer is that I am not the right person.
Where are you based, and how do you work with time zones?
Pakistan, working with teams across Europe and North America. I keep a real overlap window rather than promising full coverage, and I write things down so progress does not depend on catching me live.

Next Steps

Continue exploring

Why Research-Minded Engineers Build Better Products

A research mindset doesn't cost you speed — it sharpens the assumptions under everything you ship faster. Here's how that actually plays out on a product team.

Navigate

Remote Work Isolation: What Actually Helps?

23% of roughly 3,000 remote workers picked loneliness as a top struggle in Buffer's 2023 survey — self-reported, not measured, but real. A separate study of 61,000 Microsoft employees found the more precise mechanism: cross-group collaboration fell 25% under remote work while scheduled meeting hours barely moved. The isolation is real. The fix most teams reach for, more scheduled calls, is aimed at the wrong half of it.

Navigate

Will AI Cut Engineering Jobs, or Multiply Their Leverage?

Both answers are already true, for different people. The payroll data shows a 19% employment gap opening for 22-to-25-year-olds in AI-exposed jobs while experienced workers show no gap at all. That split is the actual story, and it is not the one either side of the argument is telling.

Navigate

Are Junior Developer Jobs Disappearing? What the Data Says

Entry-level hiring at the tech majors is down 65% since 2019 and Stanford measures a 19% employment gap for 22-to-25-year-olds. But an LSE paper covering 243 million hires found that when you control for remote work, the AI effect largely vanishes. The cause matters, because the two have opposite fixes.

Navigate

From Engineering to a PhD in Quantitative Finance: A Realistic Path

The leap from software engineering to a PhD in quantitative finance isn't traditional—but it's increasingly viable. Here's what the path actually looks like.

Navigate

What Financial Engineering Adds to Software Work

Working close to money forces habits most software teams can skip: real traceability, real correctness, real accountability for what breaks. Here's what carries over once you've built them.

Navigate

What Sitting All Day Actually Does to You

The honest version is less alarming and more actionable than the headlines. WHO looked at the evidence in 2020 and declined to set a sitting threshold at all — but a million-person meta-analysis found something much more useful about what offsets it.

Navigate

What Sleep Debt Does to Engineering Judgment

The finding that should worry you isn't that six hours of sleep degrades performance. It's that in the study which established it, subjective sleepiness stopped tracking objective decline — the impaired group did not know they were impaired.

Navigate