E-commerce and payments
Checkouts and order flows that never double-charge or lose an order.
- Checkout and payment gateway integration
- Webhooks that run exactly once, plus reconciliation
- Subscriptions, referrals and shipping
- Operations dashboards
Open to contract and full-time remote work
I'm Abhijeet Maharana. I build production AI agents (tool calling, MCP and live voice), e-commerce and payment systems, and fast React and Next.js apps, from the database to the UI. Contract at 20 to 30 hrs/week, or full-time remote with US and EU teams.
// Simplified: nothing is sent unless a person approved this exact content.
const seal = hmac(key, `${item.kind}:${item.id}:${stable(item.approved)}`);
if (!timingSafeEqual(seal, item.seal)) {
throw new Error("Not approved");
}
await send(item.approved);In plain words
The agent works on its own and asks before it acts.
tara-agent drafts work around the clock. Anything that leaves the machine waits as an approval card, and a sealed check makes sure only the approved version goes out.
Read the tara-agent project// Simplified: verify, then claim the event before doing any work.
if (!timingSafeEqual(expected, received)) return res.status(401).end();
const claimed = await redis.set(
`webhook:${provider}:${event.id}`, "1", "EX", 86_400, "NX",
);
if (!claimed) return res.status(200).end(); // already handled
await applyPaymentEvent(event);In plain words
A payment is never applied twice.
Payment providers resend the same webhook when they don't hear back. Each one is checked, then claimed once in Redis, so a retry stops before it can charge or ship again.
Read the e-commerce project// Simplified: the chart's code downloads only when it nears the screen.
const Chart = lazy(() => import("./charts/UsageChart"));
function ChartSlot() {
const [ref, near] = useInView({ rootMargin: "200px" });
if (!near) return <ChartSkeleton ref={ref} />;
return <Suspense fallback={<ChartSkeleton />}><Chart /></Suspense>;
}In plain words
Core pages load 40% faster.
Heavy pieces like charts and editors download only when someone scrolls to them or opens them, and each page ships only its own code. The first load carries far less.
Read the component library projectExperience: 5 years shipping production React and Node.js, at Muvi.com (50,000+ monthly users) and in my current role at an enterprise product company. Full experience
Full-stack, end to end. Most of what startups hire me for falls into three areas.
Checkouts and order flows that never double-charge or lose an order.
Agents that do real work and stop for a human when it matters.
Faster pages and a UI your team can reuse.
Real systems I built, two of them AI agents. Each is written up as the problem, the design and the result.
Independent build, 2025 to 2026
A payment can't be applied twice, and missed confirmations reconcile on their own.
Storefront, two payment gateways, subscriptions, referrals, four shipping carriers, an ops dashboard and a Claude-powered WhatsApp support agent. Exactly-once webhooks, Redis locks and queues on AWS.
Open source (MIT) on GitHub, 2026
Runs scheduled work around the clock, and nothing leaves the machine without a person's approval.
A self-hosted agent that drives Claude Code from Slack and cron, with sealed approval cards, exactly-once scheduling and no secrets in the model's reach.
Open source (MIT) on GitHub, 2026
One engine runs any spoken evaluation from markdown files: live voice, visible tool calls, and Claude grading against your own reference answers.
An open-source voice agent on Gemini Live that runs structured spoken sessions, calls server tools mid-conversation, and hands the transcript to Claude for scored, typed reports.
Enterprise product company (current role), 2023 to present
One shared library cut frontend development time by 30%, and code splitting made core pages load 40% faster.
A reusable React component library adopted by 5+ enterprise apps, plus lazy loading and code splitting that cut load times by 40%.
Notes from the projects above: what broke, what I chose and why.
· 8 min read
How I run a personal AI agent around the clock on one small machine: scheduled jobs, Slack threads, approval cards before anything leaves the box, and no secrets in the model's reach.
· 9 min read
How the parts of an open-source voice agent fit together: 16 kHz and 24 kHz AudioWorklets over a WebSocket to Gemini Live, tool calls run on a Node.js server, and Claude grading the call into a Zod-checked report.
· 8 min read
Payment providers resend webhooks, and a handler that runs twice charges, ships or emails twice. Signature checks, Redis claims, locks and a reconciliation job that close the gap.
· 7 min read
What made a shared React library stick across 5+ apps: small typed APIs, accessibility inside the components, tests that check behaviour, versioned releases, and code splitting that cut load time by 40%.
The usual worries with a remote hire are overlap, communication and reliability. This is how I handle each one.
I set my working hours around your team's core hours and fix them in advance, so standups and pairing land in your day. Up to 4 hours with US East mornings, and most of the UK and EU workday.
Decisions go in a short design note or the PR description before the code, so the reasoning survives the meeting.
Tickets ship as reviewable pull requests with tests, not a week of work landing at once.
A daily written update covers done, next and blocked. Calls are for decisions, not status.
A short demo of shipped work every week, so you see each feature running in the product.
I use Claude Code daily and review every line it writes. tara-agent, my open-source agent, is how I automate my own work.
How tara-agent worksThe intro call is 30 minutes on your product and where I can help first. I reply to every message within 24 hours.
For startups that need senior hands without a full-time hire.
Step 1
30 minutes on your product, your backlog, and where I can help first.
Step 2
1 to 2 weeks on a real ticket, so you judge the work, not a pitch.
Step 3
20 to 30 hrs/week as a B2B contractor, with direct ticket ownership.
I set my hours around your team's core hours and fix them in advance: up to 4 hours of overlap with US East mornings, and most of the UK and EU workday.
A B2B contract, invoiced monthly in USD or EUR, paid by bank transfer through Wise or through your contractor platform, such as Deel or Remote.
You do. I sign your NDA and IP assignment before I start.
A written daily update in Slack or your tracker, small pull requests, a short demo every week, and calls for decisions.
Yes. We start with a paid 1 to 2 week sprint on a real ticket, before any retainer.
I work only inside your systems, with access you grant and can revoke, and I'm happy to sign your DPA.
Yes, for remote senior engineer roles with US or EU teams. My notice period is 30 days, and it is negotiable.
I share them on the intro call, once I understand the scope.
Tell me what you are building. If it is a fit, we start with a short paid sprint.