This is full time remote contract position. (So no freelancing or moonlighting allowed)

You MUST need to provide overlapping time with US timezone.

This is client facing role hence excellent communication in English language is MUST.

We are seeking a Technical Lead for a confidential client to own engineering and serve as the primary technical contact for prospective customers and partners who want to understand how the platform works. Both responsibilities are central to the role; this is not a heads-down engineering position with occasional demos.

The system is larger than the current team. A single monorepo runs a web app, a REST API, a mobile app,

and a fleet of background workers across roughly forty feature modules—contacts and pipelines; a unified inbox spanning email, SMS, WhatsApp, and five social channels; calendar and booking; invoicing; workflow automation; a website and landing-page builder; client portals; and vertical suites for nonprofits,

associations, and real estate. It runs in production on AWS for paying customers, with a staging environment cloned from production.

The successful candidate will be expected to develop and maintain a comprehensive understanding of this platform.

Responsibilities

Technical direction, and the consequences of it. Concretely:

● Architecture Decide how current modules fit the existing ones, where the seams are, and what the client should not build. The codebase has strong conventions — per-org data isolation on every query,

encrypted third-party tokens, activity logging, webhook dispatch with signing and retry — and a lead's first job is to keep them from eroding.

● Delivery Take a feature from a brief to production: schema, API, frontend, mobile where it applies, and the documentation and in-product knowledge base that has to change alongside it.

● Production Deploys go to staging first, then to prod behind a manual gate.



Database migrations run as isolated one-shot tasks before any service picks up new code. You would own that pipeline and be the person paged when something is wrong at 11pm.

● Integrations Payment, telephony, email, calendar, accounting and social APIs, each with its own auth model and its own ways of failing quietly. A large part of the work is making other people's systems behave.

● Judgement about quality. Knowing which bug is cosmetic and which one is silently losing a customer's messages — and fixing the second one first.

The client-facing half

You would be in front of people who are deciding whether to buy, partner or integrate. That means:

● Demos you drive yourself, on a live system with real data, answering whatever gets asked — including the questions a salesperson cannot answer, which are usually the ones that decide the deal.

● Scoping conversations. A prospect describes their business; you work out what the platform does today, what it would need, and what it should not try to be. Saying "we don't do that, and here's what I'd use instead" is part of the job.

● Partner and integration calls. When a partner's engineers want to know the platform's webhook shape and auth model or how attribution would work between two systems, you are the one on the call, and you leave it with a written answer.

● Turning those conversations into work. The point of being in the room is that what you heard reaches the roadmap without passing through three people first.





A candidate who can build this but not explain it to a stranger is not right for this role. Neither is one who presents well but cannot ship.

Language TypeScript, end to end

Repo Monorepo — Turborepo + pnpm

API Fastify 5

Web Next.js 16, App Router, React Query

Mobile React Native / Expo, shipped through EAS to iOS and Android

Data PostgreSQL + Prisma

Async BullMQ on Redis — email, SMS, AI, campaigns, automation, sync

Real-time Socket.io, Redis adapter across processes

AI Anthropic API and Bedrock, including bring-your-own-key per customer

Infra AWS ECS Fargate, RDS, ALB; Cloudflare and R2 for storage and edge

Integrations Stripe, Twilio, SES, Google Workspace, Microsoft 365, QuickBooks, Xero, Meta, WhatsApp,

LinkedIn, X

Required

● Several years building and running production web applications, with real ownership of at least one system that had paying users and could break in ways that mattered.

● Strong TypeScript across the stack, and enough comfort with SQL and a relational data model to design one that will still make sense in two years.

● You have operated what you built: deploys, migrations, logs, an incident at an inconvenient hour.

● You can explain a technical decision to someone non-technical without either talking down to them or hiding behind jargon — and you are willing to do it on a call with a client.

● Working across an unfamiliar codebase without rewriting it first.

● Availability during US business hours, and openness to starting on a fractional basis.

Good to have

● CRM, martech or another multi-tenant B2B SaaS product.

● Third-party integration work — OAuth flows, webhooks, other people's rate limits.

● Building product features on top of LLMs, as opposed to demos.

● React Native, AWS, or agency and consulting work where you met clients directly.

📌 CRMOwn - Tech Lead (India)
🏢 iKart Solutions
📍 India