Senior Software Engineer

Senior Software Engineer will design, build, and maintain production backend features across internal Type Script SDKs distributed as versioned npm packages and the client microservices that consume them, often using NestJS deployed on Google Cloud Platform services such as Cloud Run, Cloud Functions, and Cloud Tasks. The role includes owning day-to-day maintenance and feature delivery across multiple codebases, ensuring production health through logging, tracing, debugging, performance tuning, and on-call support, and building event-driven workflows with Pub/Sub, Cloud Tasks, and Cloud Functions.

Responsibilities also cover evolving hybrid data layers spanning SQL (Postgre

SQL or MSSQL via Knex/Objection) and No

SQL (Firestore) with safe schema migrations and strong query performance, writing unit and integration tests with Jest and Firebase emulators, and following disciplined release/versioning practices using conventional commits, build/test gates, semver, and scoped package releases. The engineer will review pull requests, contribute to architectural decisions—particularly around shared SDK API design and ergonomics—and communicate trade-offs clearly in PRs, design docs, and async channels to keep teams aligned while meeting delivery timelines.

• Strong Type Script experience shipping production-grade backend services
• Experience building and maintaining shared internal libraries or SDKs distributed as versioned npm packages
• Proficiency with NestJS for backend development
• Experience deploying and operating services on Google Cloud Platform (e.g., Cloud Run, Cloud Functions, Cloud Tasks)
• Solid understanding of SQL and No
  
  SQL data modeling and access patterns, including schema design and query performance
• Experience with Postgre
  
  SQL or MSSQL using Knex/Objection, and with Firestore as a No
  
  SQL datastore
• Experience with database migrations and evolving schemas safely
• Ability to design and implement event-driven workflows using Pub/Sub, Cloud Tasks, and Cloud Functions
• Strong testing skills, including unit and integration testing with Jest and use of Firebase emulators
• Experience with logging, tracing, debugging, performance tuning, and participating in on-call/production support
• Ability to take ownership of day-to-day maintenance and feature delivery across multiple codebases
• Demonstrated ability to context-switch effectively across several client projects while meeting delivery timelines
• Experience with PR review and contributing to architectural decisions, particularly around shared SDK API design and ergonomics
• Familiarity with release/versioning practices such as conventional commits, build/test gates, semver, and scoped package releases
• Strong async communication skills and ability to clearly explain trade-offs in PRs and design docs

• Design, build, and maintain features in internal Type Script SDKs (@engineering
  11/*) released as versioned npm packages for downstream client projects
• Ship production features in client microservices (typically NestJS services deployed to Cloud Run, Cloud Functions, or Cloud Tasks) that consume the internal SDKs
• Take ownership of day-to-day maintenance and feature work across both the SDK and client-service tracks
• Jump between multiple codebases and context-switch cleanly across several client projects while meeting delivery timelines
• Own production health for the services you ship, including logging, tracing, debugging, performance tuning, and participating in on-call
• Design and evolve hybrid data layers spanning SQL (Postgre
  
  SQL/MSSQL via Knex/Objection) and No
  
  SQL (Firestore), including schema design, query performance, and migrations
• Build event-driven workflows using Pub/Sub, Cloud Tasks, and Cloud Functions where appropriate
• Review pull requests and contribute to architectural decisions, especially around shared SDK API design and ergonomics
• Write and maintain unit and integration tests (Jest, Firebase emulators) to prevent regressions in code other engineers depend on
• Follow release and versioning discipline (conventional commits, build/test gates, semver, and scoped package releases) before publishing
• Communicate trade-offs and decisions clearly in PRs,…