Problem first
Who needs the system, which data it can use, and what a useful result looks like - before any tool is chosen.
02 / About
I’m Pankaj Kumar Pramanik, an AI and data engineer with a background in full-stack web and mobile development. I work where data, intelligent applications and everyday business processes meet.

01 / My approach
Who needs the system, which data it can use, and what a useful result looks like - before any tool is chosen.
A background in full-stack web and mobile development means AI work ends as an application people can use and maintain.
Architecture, prototypes and releases arrive in small pieces you can test, question and steer.
02 / Career journey
From full-stack products and 3D web to machine learning, generative AI and RAG systems. Hover a milestone to see the stack.
Full experienceAnekonnect Incorporated · until 2021
React · Next.js · Node.js · Redux-Saga · Ant Design · SQL
Breaker Nation · until 2022
React Native · Redux Saga · Push Notifications · App Store Deployment
Vircadia · until 2022
Solidity · Web3.js · Three.js · Babylon.js · WebGL
Crewfare.com · until 2023
Node.js · AWS Lambda · Serverless · React · Storybook
Most Loved Workplace · until 2023
Text Analytics · Statistical ML · Data Mining · Python
Subhub · until 2025
LangChain · PineconeDB · Supabase · Twilio · Eleven Labs
Upwork · Present
LangChain · AI Workflow Automation (n8n) · RAG · Voice & Chat Agents
03 / Education
-
Practical, industry-aligned curriculum across data engineering, MLOps, and applied AI at one of India's premier technology institutes.
-
Studied Mechanical Engineering before transitioning into software and technology. I later pursued a professional career in software engineering, data engineering, automation, and AI.
-
GPA 5.00/5.00 - strongest subjects: Mathematics, Physics, and English.
04 / How I work
Define the users, constraints, available data and acceptance criteria before choosing a tool.
Build a focused prototype so the difficult assumptions get tested early.
Develop in iterations, review behaviour on real inputs and document the trade-offs.
Prepare deployment, monitoring and operating notes so the system can be supported.
05 / Principles
Useful>impressive
A small system people rely on beats a demo that only works on stage.
Simple>over-engineered
Start with the least machinery that solves the problem; add complexity when it pays.
Observable>mysterious
Logs, traces and evaluations make it possible to trust - and fix - what the system does.
Production>prototype
Deployment, monitoring and handover are part of the work, not an afterthought.
Human oversight>blind automation
People approve what is costly or irreversible; automation handles the rest.
06 / Tools & capabilities
Next step
Share what you’re working on and where it’s stuck. I’ll reply with questions, a suggested approach and whether I’m the right fit.