Job Type: Full-time

? Remote – India ? ₹25–50 LPA total CTC, depending on experience and scope ? Full-timeStaff Engineer | Node.Js | TypeScript | React | Multi-Tenant SaaS | Software Architecture | Technical LeadershipShape 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 modulesMore integrationsMore customer configurationMore workflow variationMore roles and permissionsMore historical dataMore dependenciesMore engineersMore opportunities for seemingly small changes to have unexpected consequencesYou may currently be a:Staff Software EngineerStaff EngineerStaff Full Stack EngineerLead Software EngineerPrincipal-level ICSenior Technical LeadExperienced Senior Software Engineer already operating beyond your formal titleThis 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 AssistScript 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 workflowsPrescribingMedication managementPharmacy workflowsInventoryDispensingPaymentsSubscriptionsFulfilmentCommunicationsReportingPermissionsCustomer configurationThird-party integrationsThe difficult engineering problem is not any one of these features.It is how they interact.A workflow may behave differently depending on:CustomerClinical serviceUser rolePharmacyMedicationConfigurationIntegrationPayment statusPrevious actionsOperational exceptionsThe product therefore needs engineers who can understand local implementation details while simultaneously protecting the coherence of the wider platform.? Your roleYou 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:ArchitectureProduct behaviourNode.Js servicesReact applicationsDatabasesIntegrationsCode reviewProduction incidentsMentoringTechnical strategyYou should be able to understand the hardest parts of the codebase without becoming the only person capable of changing them.Architecture and system designYou will:Define domain and module boundariesDesign backend services and APIsDefine data ownershipReview database modelsDesign integration patternsEstablish appropriate shared abstractionsImprove configuration architectureChallenge unnecessary couplingReduce fragile customer-specific behaviourLead important technical migrationsHelp simplify accumulated complexityYou should understand when to introduce:ConfigurationShared servicesEventsQueuesTransactionsAPIsFeature flagsMigration layersand equally importantly,



when not to introduce them.Hands-on engineeringYou will remain capable of personally implementing difficult production changes.That includes:Node.Js / TypeScript backend developmentReact / TypeScript frontend developmentAPI designDatabase workIntegration developmentDebuggingPerformance investigationRefactoringTestingProduction incident investigationYou should still enjoy working directly with code.Multi-tenant SaaS complexityThe strongest candidates will have experience with products where many customers share the same platform while behaving differently.Relevant problems include:Tenant architectureTenant isolationTenant-aware data modelsCustomer-specific configurationOrganisations and sub-organisationsEntitlementsFeature flagsWorkflow complexityWorkflow enginesState machinesRules enginesConfigurable business logicApproval flowsLong-running workflowsVersioned workflowsException handlingPermissionsRBACUser rolesOrganisation-level accessFine-grained permissionsAuditabilityIntegrationsREST APIsGraphQLWebhooksPublic APIsExternal systemsBackground jobsAsynchronous processingEvent-driven architectureDistributed-system behaviourIdempotencyRetriesPartial failuresTransactionsOutbox patternsQueuesDead-letter handlingConcurrencyReconciliationCorrelation IDsProduct evolutionSchema changesData migrationsBackward compatibilitySafe rolloutsFeature flagsProgressive migrationsProduction monitoringIncident recoveryYou do not need to have implemented every specific pattern.We care about whether you have actually solved these kinds of problems.Technical leadershipA Staff Engineer at Script Assist should improve the work of other engineers.You will:Lead important design reviewsReview difficult codeChallenge poor technical decisionsEstablish engineering patternsMentor Senior and mid-level engineersHelp engineers decompose complex problemsDocument major technical decisionsImprove testing strategyImprove observabilityHelp identify technical debt worth solvingResolve architectural disagreementsWork with Product on technical trade-offsRaise the quality of engineering across your areaWe do not want someone who responds to every difficult problem by saying:“I'll just build it myself.”You should be capable of solving the hardest problems while making the people around you increasingly capable of solving them too.Production ownershipYou will take responsibility beyond merge and deployment.You should care about:What happened in productionWhether customers are seeing unexpected behaviourPerformanceErrorsFailed integrationsOperational recoveryLoggingMonitoringReconciliationIncident preventionA major production incident should result not merely in a patch,



but in a better system afterwards.Essential technical backgroundWe need substantial recent production experience with:Node.JsTypeScriptReact / React.JsBackend systemsAPI designDatabasesDistributed applicationsAutomated testingGitDockerCI/CDCloud environmentsProduction observabilityParticularly relevant:NestJSExpressFastifyPostgreSQLMongoDBRedisGraphQLKafkaRabbitMQSQSKubernetesAWS / Azure / GCPIntegration testingEvent-driven systemsOne particular database, message broker or cloud provider is not mandatory.Node.Js requirementWe need genuine backend Node.Js ownership.Experience limited to:Front-end build toolingServer-side renderingSimple proxy servicesThin BFF layersis insufficient unless you also have substantial Node.Js backend experience elsewhere.Relevant product backgroundsThe most interesting candidates will often come from mature enterprise SaaS products involving:Workflow managementAutomationCRMIdentityPermissionsGovernanceAPIsDeveloper platformsOperational systemsEnterprise configurationPotentially relevant engineering environments include:Okta / Auth0Blue Yonder / JDA SoftwareFreshworksDiligentPostmanLeadSquaredComparable enterprise SaaS businessesThese are examples only.We assess your actual product ownership, not your employer's brand.How you should thinkWe are interested in engineers who ask questions such as:What is the real domain boundary here?Is this customer-specific or product behaviour?Should this become configuration?What happens to existing tenants?What happens to workflows already underway?What happens if the event arrives twice?How do we recover from partial failure?How do we prove this migration is safe?How will another engineer understand this in two years?How do we make this simpler rather than merely making it work?That style of reasoning matters enormously.Communication and judgementYou will work directly with senior Product and Engineering colleagues across the UK and India.You should be able to:Explain difficult technical concepts clearlyChallenge assumptions constructivelyDefend technical decisions with evidenceUnderstand commercial/product constraintsAvoid overengineeringMake pragmatic trade-offsCommunicate clearly in written EnglishMentor without patronising or micromanagingExperienceWe expect solid candidates will typically have approximately 8–14+ years of software engineering experience.However, Staff-level scope matters more than calendar years.You do not necessarily need to hold a Staff title today.A Lead or exceptional Senior engineer who is already:Leading architectureInfluencing several engineersReviewing critical workOwning production behaviourTaking responsibility beyond individual featurescan absolutely be relevant.? Why join Script Assist?At a very large organisation, a Staff Engineer may own one layer or one subsystem of a much bigger machine.At Script Assist, you can have meaningful influence across a significant part of the product.You will help determine:How major areas are designedHow the platform handles customer variationHow engineers structure new functionalityHow code quality is maintainedHow technical debt is reducedHow production issues are preventedHow engineering scales as the company growsYou will remain hands-on.But the objective is not simply to become the person who can write the most difficult code.The objective is to make a substantial part of the platform — and the engineers responsible for it — better because of your technical leadership.

📌 Staff Software Engineer – Full Stack | Node.Js, Typescript, React | Multi-Tenantb Saas (Ahmedabad)
🏢 Script Assist
📍 Ahmedabad