Backend Engineer

Linc'well

Backend

Healthtech

TypeScript

About this role

This backend engineering role develops a shared identity and authentication foundation for multiple healthcare services connecting patients, medical professionals, and medical institutions. The product domain includes online medical consultation, clinic digital transformation support, and healthcare e-commerce services.

The role leads specification changes and improvements for authentication and authorization. Responsibilities include considering the architecture of a common identity and authentication platform, designing a phased migration plan, and implementing, testing, and releasing changes while existing services remain operational. The engineer works with individual product teams to organize authentication requirements, assess impact areas, and build agreement. The role also includes design reviews for technically difficult problems and participation in technical decisions concerning the authentication platform.

The current authentication functions have been separately implemented and maintained by each service. This makes login changes affect several platforms at once, makes security, availability, and audit-log quality difficult to standardize, and increases the cost of adding new services. The platform must be improved without interrupting services already used by patients and medical institutions, while addressing the healthcare domain's high security, availability, and reliability requirements. Planned work includes separating the common identity and authentication platform, improving security, availability, and ease of change over the medium to long term, and considering new authentication approaches such as passkeys while balancing usability and security for medical institutions.

The development environment includes Rust, Ruby, Ruby on Rails, TypeScript, React, Vite, Dart, Flutter, GraphQL, and Actix Web. Infrastructure and monitoring use AWS, including ECS Fargate, CloudFront, and Lambda, as well as GCP, mainly BigQuery for the data analysis platform, and Datadog. The database is PostgreSQL. CI/CD tools are CircleCI, Autify, AWS CodePipeline, and GitHub Actions. Terraform is used for infrastructure as code, while data analysis uses Metabase, Amplitude, and BigQuery. The named design, source-control, communication, and information-sharing tools are Figma, GitHub, Slack, and Notion.

The team tracks progress through weekly regular meetings and daily stand-ups. It uses asynchronous communication through Slack and synchronous communication through Slack Huddles and Google Meet, with Gather used as a virtual office. The listed work location is the Tokyo office in Hamamatsucho, or remote work; the position is described as fully remote with flexible work.

This is an AI-generated summary of the employer's original posting — details can be incomplete, out of date or simply wrong. Always confirm everything on the official posting before applying.