Skip to content
Faizuddin Shaik

Software engineer

Faizuddin Shaik

I build backend systems and tools, and I’ve been spending more time on ML and LLM-based features lately: search over documents, automations, and the usual APIs and data work that holds it together.

About

I’m a software engineer. Most of my experience is on the backend: services, integrations, and keeping production stable. When I work with AI, it’s usually the same idea—something has to run every day without surprises.

Below is a short list of projects where that showed up. For jobs and dates, my resume and LinkedIn match; use whichever you prefer.

Projects

A few things I’ve built where AI or retrieval was the point. Titles are placeholders until I hook up the real repos and demos.

View more on GitHub

RAG

Knowledge Base Assistant

Ask questions against internal docs; answers stick to sources and include citations where possible.

  • Chunking, embeddings, hybrid search
  • Tight prompts and checks so the model doesn’t invent facts
  • Offline tests so regressions show up before users do

Automation

Workflow automations

Turn noisy inputs into summaries, tasks, or briefs; a human still signs off when it matters.

  • Structured outputs with validation
  • Sensible defaults when the model isn’t sure
  • Watch latency and cost while iterating prompts

Analytics

Monitoring dashboard

Small UI to see whether answers are getting worse, and why (prompt change, data drift, bad feedback).

  • Compare prompt versions side by side
  • Collect thumbs-up/down and short notes
  • Alerts when quality drops or traffic spikes

Writing

Occasional notes on shipping ML-backed features and not breaking production. I’ll wire these buttons once the posts live somewhere stable.

Draft

RAG without the fiction

How I split documents, retrieve chunks, and test answers so users get citations they can trust.

Read post

Draft

Shipping LLM features without surprises

Fallbacks, checks, and a bit of monitoring so a new prompt doesn’t quietly wreck the week.

Read post

Contact

Hiring, contract work, or a technical question—email is best. I read everything; response time depends on the week.