AI Engineer Islamabad · Pakistan

Evidence first. Systems second. Hype never.

Building intelligent systems that turn scattered signals into clear action.

I design AI-powered workflows, RAG systems, web intelligence tools, and product experiences that reduce ambiguity, automate heavy lifting, and keep real-world decisions grounded in evidence.

  • 10+ public repositories
  • Python FastAPI · RAG · scraping
  • Product-minded engineering with buyer psychology
Portrait of Qasim Jalil
What I focus on Automation + intelligence systems
How I work Calm, structured, execution-heavy engineering

More than an AI engineer. I build systems with product instincts.

My work sits where automation, intelligence, and decision-making meet. The pattern across my strongest projects is consistent: gather noisy public information, structure it carefully, add reasoning only where it helps, and ship the result as something operational.

That pattern shows up across competitive intelligence, knowledge systems, B2B OSINT, and applied ML work. It also shapes how I think about products: trust signals, cognitive fluency, deployment discipline, and interfaces that make complexity feel manageable.

Selected projects that best represent how I build.

These are the projects that best show how I think: evidence handling, automation depth, applied AI, and systems architecture that can survive real use.

01 Flagship platform

Competitive Intelligence Engine

I built this to turn public web data into source-cited intelligence, decision-ready reports, and structured business evidence.

  • Problem: research is slow and weakly sourced.
  • Solution: normalize sources, validate citations, and add AI only where it helps.
  • Why it matters: it reflects how I think about evidence and production boundaries.
PythonFastAPIPostgresDockerOpenRouter
Open repository
02 Knowledge system

WhatsAppRAG

I designed this as a searchable second brain with semantic search, full-text search, and automated ingestion.

  • Problem: useful knowledge gets buried fast.
  • Solution: combine embeddings, FTS, and ingestion into one usable memory layer.
  • Why it matters: it shows how I build RAG for daily use, not demos.
PythonTypeScriptSQLiteChromaDBStreamlit
Open repository
03 Data + OSINT

B2B OSINT Tool

I turned B2B research workflows into a web-ready intelligence stack for discovering and enriching company data at scale.

  • Problem: market mapping does not scale cleanly.
  • Solution: reshape it into a SaaS-style system with APIs, workers, auth, and services.
  • Why it matters: it shows how I think beyond scripts toward product architecture.
FastAPIMongoDBRedisCeleryDocker
Open repository
04 Applied AI media

Story2Audio

I built an emotion-aware text-to-speech service combining Bark generation, emotion detection, and async serving.

  • Problem: plain TTS feels flat in product settings.
  • Solution: use detected emotion to shape prompts, then expose the system cleanly.
  • Why it matters: it reflects my comfort with AI infra and end-to-end service design.
PythonBarkRoBERTagRPCGradio
Open repository
05 Applied ML research

M2N2 Model Fusion

I explored a hybrid vision setup using EfficientNet-Lite0, a tiny recursive model, and weight fusion.

  • Problem: standard models can leave performance on the table.
  • Solution: test a hybrid architecture with reproducible configs and fusion logic.
  • Why it matters: it shows my research curiosity below the product layer.
PythonComputer VisionPyTorchCIFAR-10
Open repository
06 Security demo

Post-Quantum Flask App

I built this as a compact demo of hybrid encryption with Kyber512 and AES-GCM.

  • Problem: advanced cryptography often feels inaccessible.
  • Solution: expose key generation and encryption through a simple interface.
  • Why it matters: it shows my range from product systems to security concepts.
PythonFlaskKyber512AES-GCM
Open repository

How I tend to think when the work is real.

01

Evidence before narrative

Facts get normalized, cited, and verified before intelligence becomes opinion. That habit shows up in both product design and backend architecture.

02

Automation with boundaries

The best systems do heavy lifting without becoming reckless. Clear limits, guarded workflows, and observable failure modes matter.

03

Product instinct inside engineering

Technical systems should also reduce friction, communicate trust, and make decisions easier for the person on the other side.

04

Structured execution

Ship, verify, audit, refine. The process is methodical because reliability matters more than looking clever in the first pass.

Built around practical AI engineering.

My workflow is Python-heavy and API-first, with strong comfort around automation, data extraction, retrieval, and production deployment.

Core

  • Python
  • FastAPI
  • Docker / Compose
  • Git

AI + data

  • RAG systems
  • LLM integrations
  • Scraping / OSINT
  • MLOps workflows

Operating style

  • Evidence-backed reasoning
  • Multi-agent orchestration
  • Deployment analysis
  • Conversion-aware product thinking

AI tooling

  • Claude Code
  • OpenAI Codex
  • Hermes Agent
  • Gemini CLI
  • Cursor
  • MCP + Google ADK

Have a problem worth structuring?

I do my best work on systems that need intelligence, automation, and grounded product thinking — especially when the input is messy and the output needs to be trustworthy.