Staff Software Engineer – Full Stack | Node.js, TypeScript, React | Multi-Tenant B2B SaaS

📍 Remote – India

💰 ₹25–50 LPA total CTC, depending on experience and scope

🕒 Full-time

**Staff Engineer Node.js TypeScript React Multi-Tenant SaaS Software Architecture Technical Leadership**

Shape the architecture. Control the quality. Stay hands-on.

Script Assist is looking for a hands-on Staff Software Engineer with deep production experience in Node.js, TypeScript and React to help shape the architecture and technical direction of a complex multi-tenant healthcare SaaS platform.

We are looking for someone who has already worked on a substantial enterprise B2B SaaS product and understands what happens as that product becomes large:

• More modules
• More integrations
• More customer configuration
• More workflow variation
• More roles and permissions
• More historical data
• More dependencies
• More engineers
• More opportunities for seemingly small changes to have unexpected consequences

You may currently be a:

• Staff Software Engineer
• Staff Engineer
• Staff Full Stack Engineer
• Lead Software Engineer
• Principal-level IC
• Senior Technical Lead
• Experienced Senior Software Engineer already operating beyond your formal title

This is not an Engineering Manager position.

It is also not an architect role where you stop working in production code.

You will remain technically hands-on while influencing the quality and direction of engineering well beyond your own implementation work.

About Script Assist

Script Assist is a UK healthcare technology company providing the technology and operating infrastructure behind complex private clinical and pharmacy services.

Our platform connects clinics, pharmacies, prescribers, patients and operational teams.

It supports substantial functionality across:

• Clinical workflows
• Prescribing
• Medication management
• Pharmacy workflows
• Inventory
• Dispensing
• Payments
• Subscriptions
• Fulfilment
• Communications
• Reporting
• Permissions
• Customer configuration
• Third-party integrations

The difficult engineering problem is not any one of these features.

It is how they interact .

A workflow may behave differently depending on:

• Customer
• Clinical service
• User role
• Pharmacy
• Medication
• Configuration
• Integration
• Payment status
• Previous actions
• Operational exceptions

The product therefore needs engineers who can understand local implementation details while simultaneously protecting the coherence of the wider platform.

🧭 Your role

You will take deep technical ownership of a substantial part of Script Assist while helping establish engineering patterns that scale beyond it.

You will move comfortably between:

• Architecture
• Product behaviour
• Node.js services
• React applications
• Databases
• Integrations
• Code review
• Production incidents
• Mentoring
• Technical strategy

You should be able to understand the hardest parts of the codebase without becoming the only person capable of changing them.

Architecture and system design

You will:

• Define domain and module boundaries
• Design backend services and APIs
• Define data ownership
• Review database models
• Design integration patterns
• Establish appropriate shared abstractions
• Improve configuration architecture
• Challenge unnecessary coupling
• Reduce fragile customer-specific behaviour
• Lead important technical migrations
• Help simplify accumulated complexity

You should understand when to introduce:

• Configuration
• Shared services
• Events
• Queues
• Transactions
• APIs
• Feature flags
• Migration layers

and equally importantly, when not to introduce them.

Hands-on engineering

You will remain capable of personally implementing difficult production changes.

That includes:

• Node.js / TypeScript backend development
• React / TypeScript frontend development
• API design
• Database work
• Integration development
• Debugging
• Performance investigation
• Refactoring
• Testing
• Production incident investigation

You should still enjoy working directly with code.

Multi-tenant SaaS complexity

The strongest candidates will have experience with products where many customers share the same platform while behaving differently.

Relevant problems include:

Tenant architecture

• Tenant isolation
• Tenant-aware data models
• Customer-specific configuration
• Organisations and sub-organisations
• Entitlements
• Feature flags

Workflow complexity

• Workflow engines
• State machines -…