Senior Web Platform Engineer

Advice Media; Bengaluru; On-site; INR 4,200,000 - 6,600,000; Full time

Job summary

Advice Media is building a high-scale, multi-tenant website platform to automate site creation and maintenance for healthcare practices. The role centers on owning the platform architecture from data models to deployment, with emphasis on security, performance, and scale.

You will work with TypeScript, React, Next.js, and Node.js, designing an architecture that supports per-tenant isolation, robust APIs, and an efficient rendering pipeline on AWS.

Qualifications

• Production experience with TS, React, and Next.js.
• Strong backend in Node.js and API design.
• Proven multi-tenant security and data isolation experience.
• Architectural ownership from concept to deployment.

Responsibilities

• Own platform architecture and multi-tenant design.
• Lead infra and deployment strategies on AWS.
• Design and implement a scalable rendering pipeline.
• Collaborate with DevOps and AI teams to ship securely.

Skills

TypeScript

React

Next.js

Node.js

PostgreSQL

Multi-tenant security

Cloud architecture

Tools

AWS

PostgreSQL

Docker

CI/CD

Job description

The Opportunity

We're building a multi-tenant website platform that generates, publishes, and maintains client websites at fleet scale — and we're building it from the foundation up, starting now.

MyAdvice powers the digital presence of thousands of healthcare practices. Today those sites live on a fragmented legacy stack: individually built, individually maintained, individually patched. We're replacing all of it with a single platform on Payload — self-hosted, MIT-licensed, entirely under our control — where a new client site is provisioned by an API call in minutes rather than assembled by hand over weeks.

The interesting part is what sits on top. We're pairing that platform with a generative AI pipeline that designs, lays out, and populates sites: a practice's brand and content in, a complete, on-brand, SEO-clean website out. Not a template picker — actual generation, at scale, with quality high enough to put a real business's front door on it.

Nobody has fully solved this. We're going to find the limits ourselves — of fleet-scale site creation, of generative design and content, of multi-tenant security and healthcare compliance, of maintaining and performance-tuning an enormous number of sites from one codebase. Those limits are the job.

This is a cornerstone of MyAdvice's product going forward, and it's being built now, by a small senior team, with the architecture still open. You would be the engineer who owns the platform itself — not configuring someone else's, not maintaining someone else's decisions. Yours, from the first migration onward, with your judgment in the load-bearing parts.

Foundational seats on a platform this consequential don't come up often.

What you'll own

Multi-tenancy — the heart of it.

You'll build on Payload's multi-tenant foundation and harden it for scale: per-query tenant scoping, access control, tenant-aware routing, custom domains. Isolation is enforced in our own application code, which makes its correctness the most important thing you'll own. Every site on the platform belongs to a real healthcare business with real patients' trust attached. You'll design the guardrails, the test strategy, and the review discipline that make failure here structurally hard — not just carefully avoided.

The data model. The Postgres schema and access patterns behind an ever-growing tenant fleet: modeling, indexing, migrations, and query performance that stays flat as the fleet grows.

The infrastructure architecture. You are the primary architect of the infrastructure this platform runs on: environments, deployment topology, scaling strategy, the data layer, and the cost model that comes with them. You plan it and you build it. Our DevOps team then provisions, operates, and maintains it — so your design has to be good enough that someone else can run it.

A visual editing experience people actually enjoy. Payload's admin is developer-facing, and there's no client-ready page builder out of the box — so we build one. Real product engineering: a block-based editor (Puck or similar) that non-technical marketers and delivery teams can move fast in without breaking anything.

Automated provisioning. Tenant creation driven entirely by API — create, seed a template, apply per-tenant design tokens, publish — fully unattended, in minutes, no manual steps. This is the hook our AI onboarding pipeline calls, and it's what makes the economics of the whole platform work.

The theming engine. One codebase, per-tenant design tokens, genuinely distinct sites, zero per-tenant code. The mechanism that lets every client look bespoke without a single fork.

Rendering, SEO, and performance. These sites exist to be found. You'll own the Next.js rendering strategy, Core Web Vitals across the fleet, and valid schema.org structured data — performance work where a single improvement compounds across every site at once.

Its long-term health. This isn't build-and-hand-off. You'll be the platform's owner: instrumenting it so problems surface before anyone reports them, triaging and fixing what does, tracking upstream Payload releases and owning the upgrade path, keeping code-level security and compliance sharp, and holding the quality bar as the fleet and the team grow around you.

Integration with our internal systems. The abstraction layer that syncs live practice data — providers, locations, reviews — into every site that needs it, built alongside the architect who knows those systems best.

How The Team Works

You'd join a small, high-trust Website Platform team — a fellow builder, a senior architect who knows our existing systems deeply and will advise, and an AI specialist on the generation pipeline — reporting to our VP of Engineering.

You architect it; DevOps runs it.

This is how our engineering team already works: engineers plan and build, DevOps supports and sustains. You'll own the architecture of the platform and the infrastructure underneath it — the decisions, the design, the build. Our established DevOps team then operates and maintains it and carries infra-level incident response, so the pager isn't yours. Our senior architect is a close advisor here, with deep historical knowledge of the systems you'll be integrating with. What you get is real architectural authority without an on-call rotation — and the accountability that comes with it, because your design is what someone else has to keep running.

We work AI-native. Cursor and AI assistants are standard here, and we expect you to use them to raise what you can build — while owning the judgment about what's safe to ship to a live fleet of client websites.

We also work in phases and prove things before we scale them: a de-risking proof-of-concept that validates multi-tenancy, provisioning, rendering, and cost with real numbers — then the full build. You'd be central to both.

What We're Looking For

We're looking for an expert-level engineer in this stack. Specifically:

• Deep, current, production experience with TypeScript, React, and Next.js. You've shipped and operated real applications here, at scale — not prototyped.
• Strong Node.js backend engineering — APIs, access control, data modeling, and integration work in production systems.
• Strong PostgreSQL and relational data modeling — schema design, indexing, migrations, and query performance under real load.
• You've owned a multi-tenant or security-critical system, where application-level data isolation and access control were genuinely your responsibility. This is the one we won't compromise on.
• You've architected cloud infrastructure and handed it to an ops team to run. Deployment topology, scaling, environments, and the data layer on AWS — designed by you, documented well enough for someone else to operate, and still yours to answer for after it ships.
• You've lived with what you built.