Software Engineer

Software Developer — Full-Stack(TypeScript + GCP)Location Mumbai — on-siteExperience 3–5 yearsType Full-timeReports to Engineering lead / founding teamThe roleYou own features end to end — database schema, API, screen, deploy — across a NestJSbackend and a React frontend running on Google Cloud. Small team, direct productownership, no ticket queue.The platform is mid-migration from a single Ubuntu VM to a proper GCP footprint (CloudRun, Cloud SQL, Cloud Storage, Secret Manager, Vertex AI). You will build on that stackand help move things onto it, so cloud fluency is part of the job rather than someoneelse's department.Because we handle medical reports and patient identity data, correctness and accesscontrol carry more weight here than on a typical CRUD product.StackBackend NestJS 10, TypeScript, Prisma 5, PostgreSQL, Passport/JWT, class-validator, SwaggerFrontend React 18, Vite 5, Redux Toolkit, React Router 6, Tailwind CSS, i18next(English + Arabic/RTL)Cloud Google Cloud — Cloud Run, Cloud SQL for PostgreSQL, Cloud Storage,Cloud Tasks, Cloud Scheduler, Secret Manager, Cloud Build + ArtifactRegistry, Cloud Logging & Monitoring, Vertex AIAI Gemini on Vertex AI with an ordered multi-provider fallback chain,behind one internal serviceIntegrations Razorpay, Google OAuth, Jitsi teleconsults, OCR/PDF pipelines,transactional emailWhat you will actually work onProduct featuresDomain modules across hospitals, bookings, journeys, payments, recovery, uploads andthe admin / hospital-partner consoles — controller, service, DTO, schema, migration,screen.FrontendReact screens against the existing design system (Tailwind tokens, one typeface, Lucideicons), mobile-first, and correct in Arabic RTL as well as English.AI featuresReport analysis, treatment matching, the pre-signup assistant, lead classification. Promptsand provider tiers — not model training.Cloud & deliveryContainerising and shipping services to Cloud Run, wiring Cloud SQL and Cloud Storage,moving secrets into Secret Manager, Cloud Build pipelines, and reading Cloud Logging /Monitoring when something breaks at 11pm.ReliabilityPayload sizes on list endpoints, background jobs that do not block the request path,idempotent payment handling, and an ownership check on every route that touchespatient data.Responsibilities• Ship features across backend and frontend, including the schema changes and migrationsthey need.• Enforce authentication and per-record ownership on every patient-data endpoint. Neverweaken auth, hardcode a secret, or loosen CORS / rate limits to unblock yourself.• Keep work inside the design system and the module conventions already in thecodebase.• Deploy and operate what you build on GCP — build, release, roll back, read the logs.• Verify before calling it done: lint, type-check, build, and the actual screen or endpoint.• Review pull requests and leave the short "why" comments this codebase expects.• Debug production issues across API, database, cloud services and browser.RequirementsMust have• 3–5 years building and shipping production web applications.• Strong TypeScript on both server and client.• Node.js backend experience with a structured framework — NestJS preferred; Express orFastify with a modular architecture is fine.• React 18 with hooks, a real state library (Redux Toolkit here), and React Router.• PostgreSQL and a typed ORM — Prisma preferred; TypeORM, Drizzle or Sequelizeacceptable. You can read a schema, write a migration, and reason about a slow query.• Hands-on Google Cloud: deploying and running services (Cloud Run, GKE, App Engine orGCE), a managed database, object storage and secret management. Comfortable ingcloud and able to find your way around IAM.• Docker — writing a Dockerfile and debugging a container that works locally but not inthe cloud.• REST API design: JWT authentication, validation, error handling, pagination.• Tailwind CSS and responsive, accessible UI work.• Git-based workflow and code review.Good to have• CI/CD on Cloud Build or GitHub Actions; infrastructure-as-code (Terraform).• Vertex AI or any LLM API integration — prompt design, structured JSON output, fallbackhandling.• Payment gateway integration (Razorpay, Stripe) and webhook / idempotency handling.• Internationalisation and RTL layouts.• A regulated domain — healthcare or fintech — or exposure to HIPAA / GDPR / DPDP.• File handling at scale: uploads, OCR, PDF parsing, media storage.