01
Software engineering
React, TypeScript, Node.js, FastAPI, PostgreSQL, APIs, integrations, testing, and deployment.
Full-stack
Software engineer · Applied AI · Full-stack products
I’m Sufiyan Khan, a full-stack software engineer working across product interfaces, backend systems, and applied AI. I take ideas from rough direction to working software — with the architecture, integrations, testing, and details handled along the way.
About
I work across the parts of a product that often get split between different people — interface, APIs, backend systems, databases, AI workflows, integrations, testing, and deployment. That range matters because good product decisions rarely stop at the screen.
React, TypeScript, Node.js, FastAPI, PostgreSQL, APIs, integrations, testing, and deployment.
RAG, LangGraph, vector search, model APIs, MCP, and workflows designed around a real product problem.
Architecture, edge cases, reliability, and the practical decisions that determine whether the build actually holds together.
Selected work
Each of these solves a specific business problem: following up with every lead, answering questions from your own documents, turning a website visit into an inquiry. Pick the one closest to yours and I'll build something like it.
When a new lead comes in, an AI agent writes a personal follow-up, emails it, and logs the lead in a Google Sheet. Nobody has to chase. It runs on n8n, with Groq writing the reply and Gmail and Google Sheets handling sending and tracking.
A 24/7 AI sales system built for roofing contractors. It picks up every call and form, qualifies the homeowner, books the inspection straight to the calendar, and logs the lead — built to keep up when storm season sends 100 leads in 48 hours.
Guests browse retreats, send inquiries and chat with an AI assistant. Every inquiry lands in a lead-management view, so the owner can follow up and nothing gets missed.
Upload PDFs, docs or notes. Groundwork searches by keyword and by meaning, re-ranks the results, then writes an answer that cites where it came from. When free hosting kept wiping the search index, I moved storage to Qdrant Cloud so it stays online.
Ragas — 1.00 faithfulness · 0.71 answer relevancy
Instead of one oversized model response, the review runs as coordinated steps: triage, review, and escalation of risky changes (like auth or payments) to a human. It comes with a React dashboard, sign-in and live monitoring.
Every claim in the draft is checked against your source notes. If the faithfulness score falls under 0.85, the report is blocked instead of being sent on. Open source, with an MCP connection to SuperDocs.
Have a problem like one of these? Tell me about it on a 30-minute call.
Book a callFrom first call to final ship
Same view, different question at every stage. Scroll to move from what the business needs to what actually gets shipped — discovery, design, engineering, polish, launch.
Understand the business, the audience, the problem and what the finished experience must change.
Questions before we start
I build. I work across the interface, backend, APIs, databases, integrations, testing, and AI layer rather than stopping at the design file.
Yes. I can start from a rough idea, an existing design, a specification, a repository, or a partial product and take the work through implementation, testing, and delivery.
We start by understanding the problem and desired outcome, then move through scope, design, engineering, testing, deployment, and iteration. The pace changes with the project; the discipline stays the same.
It depends on the surface area and constraints. I prefer breaking the work into clear milestones, validating the risky parts early, then shipping in useful increments instead of waiting for one large final handoff.
That is enough to start. We can use the first conversation to clarify the audience, problem, desired outcome, constraints, and the smallest useful version worth building.
Yes. I can work inside an existing repository, design system, API surface, or delivery process and contribute without forcing the team into a completely new stack.
For selected builds, yes. That can include fixes, measurement, small improvements, and the next iteration after real users start interacting with the product.
I’m open to full-time software engineering roles and selected product builds where I can take meaningful ownership. Remote-first works best, with Pune also possible for a strong fit.
Contact
Tell me what you’re building, who it is for, and where things stand today. For full-time opportunities or a focused product build, the easiest next step is a conversation.
Schedule a 30-minute call