Open to the right Full-Stack AI opportunity

Nikhil Rajput Full-Stack AI Engineer

I build AI products that move from conversation to production.

I turn business requirements into reliable agents, automation systems, full-stack platforms, data pipelines, and SaaS products — then help them survive real users, real integrations, and real operational constraints.

Doing this
2+ years, hands on
Based in
Madhya Pradesh, India
Scope
Discovery → production

Fig. 1One request, all the way through

01The actual workflowpeople, data, edge cases
02Rules, then the modelwhat must never bend
03Tools and live databounded, logged, reversible
04Checks, then shipand a human exit

the boring parts are the product

Keep reading

100+development applications captured dailydata acquisition · Australia

20+council portals tracked overnightdata acquisition · Australia

250+property listings ingested monthlyPropTech SaaS · South Africa

<500msto first audio on live PSTN callsvoice AI · India

16+safety guardrails on every model calllegal intake · Australia

1,000+students managed per academic sessioneducational ERP · India

The intelligence layer is the easy half.Everything it touches is the job.

My best work happens in the overlap — where AI, full-stack engineering, integrations and somebody's actual working day all have to agree with each other.

I’m a Full-Stack AI Engineer with 2+ years of hands-on experience building AI-powered products, automation systems, full-stack SaaS platforms, data pipelines, and production integrations for international clients.

I work from the first confused conversation through architecture, build, testing, deployment and the long tail of changes that follow. I'd rather carry that line end to end than hand off half of it.

Read my complete résumé
01

I start where the job actually happens

Not the one in the process document. I map the people, the spreadsheets, the WhatsApp group where the real decisions happen, and the edge cases nobody mentions until week three.

02

I own the connected build

Interfaces, APIs, databases, agents, workers, integrations, tests and the deploy pipeline. One person holding all of it means fewer seams for things to fall through.

03

I design for the day it misbehaves

Structured outputs, validation, bounded tools, retries, fallbacks, logging and a clean human handoff. Not features bolted on later — the shape of the thing from the start.

Shipped systems, with theengineering story attached.

Client delivery across AI, automation, data acquisition and SaaS — then my own products, where I get to make the architecture calls and live with them.

Useful AI startslong before the model call.

The model is one component. The workflow, the data it's allowed to see, the controls around it and the recovery path decide whether anyone keeps using the thing in month two.

four habits, in order

  1. 01

    Sit with the process before the stack

    Before choosing a model or a framework, I map who does the job today, what they actually touch, where the handoffs break, and what the business is really paying for.

    no architecture on day one
  2. 02

    Draw the line between rules and reasoning

    Money, eligibility, compliance and anything irreversible stay deterministic. The model gets the messy, language-shaped middle — and a short leash of allowed tools.

    the leash is the design
  3. 03

    Build the full path, not the clever part

    Interfaces, APIs, workers, queues, databases, integrations, logging and deploys are one problem. A great agent behind a broken webhook is still a broken product.

    one problem, not seven
  4. 04

    Ship it into the working week

    I test the ugly paths, release in slices, watch what production does to my assumptions, then change the system with the people using it.

    assumptions lose

Grouped by the part of the systemthey hold up.

I pick the stack around the workflow, the deployment environment and the reliability bar — not around whatever I used last time.

01

AI & GenAI

LLM APIsAI AgentsRAGStructured OutputsEmbeddingsVector SearchGuardrailsTool CallingLangChainLangGraphLangSmithLiteLLMOpenAIGeminiAnthropicAWS Bedrock
02

Backend

PythonFastAPINode.jsExpress.jsREST APIsWebSocketsWebhooksAsync ProcessingBackground WorkersAuthentication
03

Frontend

React.jsNext.jsTypeScriptJavaScriptReact NativeTailwind CSSResponsive DashboardsOpenLayers
04

Automation

n8nPlaywrightBrowser AutomationWorkflow OrchestrationWhatsApp AutomationVoice AITwilioData PipelinesWeb Scraping
05

Data

PostgreSQLMySQLMongoDBChromaDBWeaviatepgvectorRedisSQLAlchemy
06

Cloud & DevOps

AWS EC2S3App RunnerCloudFrontSQSLambdaTextractGCP Cloud RunDockerGitHub ActionsCI/CDTerraformBitbucketVercel
07

Integrations

HubSpotMonday.comMetaTikTokYouTubeLinkedInXWhatsAppPayment GatewaysABR APIRP DataBrevoFirebaseSentinel Hub

Quality first. Then software.Now complete AI systems.

It explains how I work now: I still hunt edge cases like a tester, build like an engineer, and keep the product in view the entire time.

Singaji Software SolutionsJuly 2024 — present

Three roles in two years, each one further up the stack and further into ownership.

03
Nov 2025 - Present

Full-Stack AI Engineer

I lead the development of AI-powered automation and full-stack systems across architecture, LLM workflows, backend services, integrations, testing, deployment, and production iteration.

  • LLM applications, AI agents, RAG pipelines, structured extraction, tool calling, guardrails, and human-in-the-loop workflows
  • Production systems with Python, FastAPI, Node.js, PostgreSQL, n8n, Playwright, Redis, AWS, and third-party APIs
02
Nov 2024 - Nov 2025

Software Engineer

I developed backend and full-stack applications for international clients across Australia, South Africa, and other markets.

  • Node.js, Express.js, Python, FastAPI, React, Next.js, PostgreSQL, and MySQL
  • REST APIs, webhooks, integrations, dashboards, scraping pipelines, data workflows, deployment, and production support
01
Jul 2024 - Oct 2024

QA Tester + Developer

I started close to product quality: testing real workflows while contributing to development, debugging, and application reliability.

  • Functional, API, regression, and workflow testing
  • Defect reproduction, edge-case validation, fix verification, and collaboration with developers

Give me a real problem,not an isolated demo.

I'm looking for a team where engineering ownership, AI capability and actual business context sit in the same room.

01AI product engineering

Agents that understand, decide, and act without going off the rails

Full-Stack AI Engineer · GenAI Engineer · AI Automation Engineer

02Full-stack + intelligence

The complete product wrapped around the intelligent part

Full-Stack Developer · AI Product Engineer · Applied AI Engineer

03Solution ownership

Business friction on Monday, something shipped by the end of the quarter

AI Solutions Engineer · Automation Engineer · Product-minded Engineer

I don't stop at“the AI part.”

01Business clarity

I can sit with the people doing the job, turn a vague complaint into a decision, and keep the engineering pointed at the outcome instead of the ticket.

02Engineering depth

System boundaries and schema design through to APIs, agents, dashboards, automation, integrations and the deploy. I go all the way down.

03Production judgement

I know when plain code beats a model, where AI genuinely earns its cost, and where validation, fallback, observability or a human has to be in the loop.

Got a process thateats everyone's week?

I'm in Madhya Pradesh, India, open to Full-Stack AI, GenAI, full-stack, automation and AI solutions roles, and happy to work with teams in other timezones. Tell me what your team is trying to make faster, cheaper or less painful.

Nikhil Rajput
Usually replies the same day