📍 Remote – India

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

🕒 Full-time

Node.js | TypeScript | React | Full Stack Engineering | Multi-Tenant SaaS | Enterprise SaaS | Technical Leadership

Own a major product area. Lead the engineering. Stay deeply involved in the code.

Script Assist is looking for a hands-on Lead Software Engineer with deep production experience in Node.js, TypeScript and React to take technical ownership of a substantial part of our platform.

We are particularly interested in engineers who have built and evolved large, complex, multi-tenant B2B SaaS products with:

• Multiple interconnected product modules
• Customer-specific configurations
• Complex workflows and state transitions
• Roles and permissions
• Large integration surfaces
• APIs and webhooks
• Significant production data
• Different customer behaviours and requirements
• Years of accumulated product complexity

This is not simply a senior developer position.

We need someone who can own an area technically, make important engineering decisions, maintain very high standards across the code written by others, mentor engineers and remain capable of personally solving the hardest technical problems.

You may currently be a:

• Lead Software Engineer
• Lead Full Stack Engineer
• Technical Lead
• Tech Lead
• Senior Software Engineer
• Senior Full Stack Engineer
• Hands-on Staff Engineer
• Full Stack Technical Lead

Your current title matters less than the level at which you already operate.

About Script Assist

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

Our platform connects:

• Clinics
• Pharmacies
• Prescribers
• Patients
• Operational teams
• External technology providers

and supports tens of thousands of structured clinical and pharmacy transactions every month.

The platform includes complex functionality across:

• Clinical workflows
• Prescribing
• Medication management
• Pharmacy operations
• Inventory
• Dispensing
• Payments
• Subscriptions
• Fulfilment
• Communications
• Reporting
• Permissions
• Integrations
• Customer-specific configuration
• Operational automation

Healthcare experience is not required.

What matters is that you have already built sophisticated software products where many features, workflows, integrations and customer configurations interact with each other.

The Engineering Problem

Script Assist is not a simple CRUD application.

Different customers may use the same underlying platform in different ways.

A new feature can interact with:

• Existing workflows
• Different user roles
• Tenant-specific configuration
• External integrations
• Payment states
• Operational processes
• Existing customer data
• Historical product decisions

We need engineers who understand how to extend a mature shared product without creating an unmaintainable collection of exceptions.

You should be comfortable thinking about questions such as:

• How should customer-specific behaviour be represented?
• Should this be configuration or code?
• How should workflows be versioned?
• What happens to processes already in progress?
• How do we prevent duplicate actions when events retry?
• How do we maintain data integrity across several systems?
• How do we change one module without breaking another?
• How do we make increasingly complicated software easier—not harder—to maintain?

🔧 What you will ownTechnical ownership

You will take responsibility for a substantial product domain.

That will include:

• Technical design
• Backend services
• Data models
• React applications
• APIs
• Integrations
• Testing strategy
• Deployment
• Production behaviour
• Technical debt
• Reliability

You should become the person who can say:

“I understand this area end-to-end and I am responsible for its technical quality.”

Hands-on engineering

You will remain deeply involved in implementation.

You will:

• Write production Node.js / TypeScript backend code
• Build and review React / TypeScript applications
• Design APIs and service contracts
• Work directly with databases
• Debug difficult production behaviour
• Refactor problematic areas
• Implement technically difficult functionality
• Review and improve existing architecture

This is not an architecture-only role.

Technical leadership

You will:

• Lead design discussions
• Break large engineering problems into sensible pieces
• Review important pull requests
• Maintain high coding standards
• Challenge poor abstractions
• Identify hidden dependencies
• Mentor engineers
• Improve testing and release discipline
• Establish reusable patterns
• Help engineers make better technical decisions

The goal is not for you to personally write every difficult piece of code.

The goal is for the engineering around you to become better because you are there.

The SaaS experience we care about

We want engineers who have genuinely worked on shared multi-tenant software products.

Relevant experience may include:

Multi-tenancy

• Tenant isolation
• Tenant-aware data models
• Customer configuration
• Entitlements
• Feature flags
• Organisation structures
• Multi-company / multi-entity architecture

Complex workflows

• Workflow engines
• Rules engines
• Approval processes
• State machines
• Status transitions
• Long-running processes
• Workflow configuration
• Exception handling

Permissions and governance

• RBAC
• Roles and permissions
• Organisational hierarchies
• Audit trails
• Access control

Integrations

• REST APIs
• GraphQL
• Webhooks
• External services
• Background jobs
• Message queues
• Event-driven systems
• Third-party integration failures

Production complexity

• Idempotency
• Retries
• Concurrency
• Reconciliation
• Transactions
• Data migrations
• Backward compatibility
• Incident investigation
• Observability
• Safe releases

You do not need every item above.

You do need evidence that you have already worked inside a genuinely complex shared software product.

Essential technical experience

You should have substantial recent experience with:

• Node.js
• TypeScript
• React / React.js
• Backend service development
• API design
• Database design
• Production software
• Automated testing
• Git
• CI/CD
• Docker
• Cloud-deployed systems

Experience with the following is particularly useful:

• NestJS
• Express
• Fastify
• PostgreSQL
• MongoDB
• Redis
• GraphQL
• Kafka
• RabbitMQ
• SQS or other queues
• Kubernetes
• AWS / Azure / GCP
• Observability and monitoring

We do not require one particular database or cloud provider.

Important

Your Node.js experience must include real backend business logic and production services.

Node used only for:

• Front-end tooling
• SSR
• Build systems
• Very thin BFF layers

will not be enough by itself.

Relevant backgrounds

We are particularly interested in engineers from mature B2B SaaS and enterprise software product companies.

Relevant environments may include teams at:

• Freshworks
• Okta / Auth0
• Blue Yonder / JDA Software
• LeadSquared
• Diligent
• Postman
• Other enterprise SaaS, workflow, CRM, identity, automation or operational-software companies

These companies are examples, not requirements.

We care about what you personally built and owned, not simply the logo on your CV.

How we expect you to lead

We want somebody who:

• Is obsessive about code quality
• Reviews other engineers’ work carefully
• Understands architectural consequences
• Spots complexity before it becomes technical debt
• Can challenge Product constructively
• Makes pragmatic trade-offs
• Writes difficult code when necessary
• Helps others solve difficult problems
• Does not create dependency on themselves
• Takes responsibility for production outcomes

Strong written and spoken English is important.

Experience

We expect most strong candidates will have approximately 8–14+ years of software engineering experience.

But years alone are not the deciding factor.

An exceptional engineer with fewer years but substantial ownership can be more interesting than someone with a longer but narrower career.

📈 Why join Script Assist?

This is an opportunity to move from being one senior engineer inside a very large organisation to owning a meaningful part of an entire product platform.

You will have genuine influence over:

• Architecture
• Product behaviour
• Code quality
• Engineering standards
• Production reliability
• Technical strategy
• How other engineers work

You will remain hands-on.

But your impact should increasingly come not only from the code you write yourself, but from the quality of the entire area you lead.