Skip to content
HomeAt Splunk, that means pairing React product work with Python services, operational data, permissions, evaluation, and release controls. Earlier at Deloitte, I built extraction, storage, API, and visualization systems; two removed more than 36,000 hours of annual manual work and cut investment-processing time by 66%.WritingTechnical writing on software engineering, AI engineering, system design, and the trade-offs behind production systems.ProjectsA growing collection of systems and products I’ve built—from current infrastructure work to earlier projects that shaped how I build today.Abdul AhadI’m an AI full-stack engineer with more than five years of experience building data-intensive enterprise software and production AI systems. At Splunk, I drove AI Service and KPI Discovery from an early prototype through technical design, validation, and production delivery. The capability analyzes operational data and recommends service models and health signals within Splunk IT Service Intelligence.Let’s talk.If you’re hiring, building something interesting, or want to compare notes on a difficult engineering problem, send me a message. A few lines is plenty.ColophonHow this portfolio handles static publishing, search, contact delivery, analytics, and releases.Capacity Planning Before Architecture DiagramsA practical method for turning workload assumptions into request, storage, bandwidth, concurrency, and failure-capacity budgets before choosing an architecture.Design Modules Around Change, Not LayersA practical guide to information hiding, volatile decisions, coupling, cohesion, dependency direction, and avoiding abstractions that preserve the wrong boundaries.From Model Call to Reliable AI WorkflowHow one model request grows into retrieval, tools, deterministic workflows, agents, evaluation, observability, and human escalation.Queues, Backpressure, and Idempotency: Designing for FailureHow bounded queues, admission control, idempotency keys, retry budgets, and dead-letter handling turn asynchronous delivery into a controlled reliability system.Refactoring a Legacy Backend Without a Big-Bang RewriteA staged method for understanding, testing, isolating, replacing, observing, and finally deleting legacy backend behavior without one irreversible cutover.MCP in Production: Trust Boundaries, Permissions, and Tool DesignA production-focused guide to MCP hosts, clients, servers, capability discovery, authorization, consent, token audiences, and safely designed tools.How this portfolio worksA walkthrough of how an edit becomes a published page, what happens after someone presses Send, and how the site avoids losing or saving the same message twice.ThreadsPosts, nested replies, profiles, and communities share the same records. This follows one conversation from creation to deletion.Prompt NexusGoogle sign-in leads to a local user, then one saved prompt powers the feed, profile, search, and edit screens.SeedEditors publish articles in HyGraph, readers receive prepared pages, and new comments remain private until they are approved.CactaOne published video creates a media asset, a post record, and temporary browser state. This follows that upload across the product.System DesignCapacity, queues, failure handling, and distributed-system trade-offs.AI EngineeringLLM workflows, tools, evaluation, permissions, and operations.Software EngineeringModules, testing, refactoring, interfaces, and maintainability.System Design from First PrinciplesCapacity planning, queues, backpressure, retries, and failure handling.Production AI EngineeringModel calls, workflows, tools, evaluation, permissions, and operations.

Software Engineer 3 · Splunk

I build production AI and full-stack systems.

At Splunk, I build AI-assisted product workflows across React, Python, operational data, authorization, evaluation, and observability. Earlier systems at Deloitte removed more than 36,000 hours of annual manual work.

Selected projects

Independent work, with the difficult parts left in

A growing collection of products and systems I’ve built, with the decisions, trade-offs, and lessons behind each one.

Explore all projects →
system
2026 — present

How this portfolio works

A walkthrough of how an edit becomes a published page, what happens after someone presses Send, and how the site avoids losing or saving the same message twice.

Turned versioned content files into complete pages during deployment, with broken fields and relationships stopping the release.

View case study →
productPrevious work
2023

Threads

Posts, nested replies, profiles, and communities share the same records. This follows one conversation from creation to deletion.

Represented both posts and replies with one record shape, allowing a reply to contain further replies.

View case study →
productPrevious work
2023

Prompt Nexus

Google sign-in leads to a local user, then one saved prompt powers the feed, profile, search, and edit screens.

Built the feed, contributor profiles, and edit pages from two main record types: users and prompts.

View case study →

Recent writing

Latest writing

All writing →
System Designfoundations

Capacity Planning Before Architecture Diagrams

A practical method for turning workload assumptions into request, storage, bandwidth, concurrency, and failure-capacity budgets before choosing an architecture.

·10 min read
Software Engineeringfoundations

Design Modules Around Change, Not Layers

A practical guide to information hiding, volatile decisions, coupling, cohesion, dependency direction, and avoiding abstractions that preserve the wrong boundaries.

·10 min read
AI Engineeringfoundations

From Model Call to Reliable AI Workflow

How one model request grows into retrieval, tools, deterministic workflows, agents, evaluation, observability, and human escalation.

·10 min read

Article series

Engineering series

Where I work

I work across the boundaries where systems usually fail.

At Splunk, that means pairing React product work with Python services, operational data, permissions, evaluation, and release controls. Earlier at Deloitte, I built extraction, storage, API, and visualization systems; two removed more than 36,000 hours of annual manual work and cut investment-processing time by 66%.

Explore projects and systems →
36,000+
manual hours removed each year
66%
reduction in investment-processing time
1st
Developer Productivity, Splunk AI Hackathon

Selected experience

From prototypes to production systems

Full background →

Software Engineer 3

Splunk

Nov 2025 — Present

Own end-to-end engineering for production Generative AI and full-stack capabilities in Splunk IT Service Intelligence (ITSI), spanning React/TypeScript, Python, REST APIs, LangGraph and LLM orchestration, operational data, authorization, evaluation, and observability.

Originated AI Service and KPI Discovery in ITSI as a hackathon idea, built the initial prototype and demos, and drove its evolution through design, validation, and productionization into a shipped product capability.

Software Engineer 2

Splunk

May 2024 — Oct 2025

Built and shipped full-stack capabilities for Splunk IT Service Intelligence (ITSI), an enterprise observability and AIOps platform, across React and TypeScript applications, Redux/Redux-Saga state architecture, REST APIs, Splunk SPL, data workflows, reliability, and automated testing.

Built complex product experiences for third-party integrations, incident operations, backup and recovery, scheduled maintenance, and service-health analytics.

Analyst (Software Engineer)

Deloitte

Jul 2021 — Apr 2024

Designed and developed a full stack metrics extraction tool, resulting in a 99% increase in productivity and saving 36,000+ manual hours per year.

Spearheaded the development of an automated investment tracking application that resulted in a 66% reduction in processing time and saved over 2,000 project hours per year.

Have something interesting in mind?

I’m always happy to hear about thoughtful roles, ambitious projects, and difficult engineering problems.