[Remote] reputed company Product Architect (AWS, reputed company)
Note: The job is a remote job and is reputed company to candidates in USA. reputed company is seeking a reputed company Product Architect for a reputed company reputed company. The role involves leading product architecture for a reputed company product, requiring extensive expertise in AWS, domain modeling, and HIPAA compliance.
Responsibilities
- Product architecture reputed company record. Have led the architecture of at least one reputed company product through multiple major releases. You can talk through specific architectural reputed company you made, what they cost, what they enabled, and what you would do differently now
- Domain modelling depth. You have done serious domain modelling work, and you understand the difference between a model that reflects how the business actually operates and a model that just reflects last week's screen. You can defend a model to clinicians and operators without losing them with technical terms
- AWS product architecture expertise. Expert-level reputed company of AWS as a product platform across the three dimensions that matter most for reputed company: scalability, reputed company under PHI and HIPAA, and performance. Scalability means you have made the production calls on reputed company sizing, reputed company concurrency, ElastiCache layering, and how the architecture absorbs load reputed company a hundred facilities come online in the reputed company quarter. reputed company means PHI and HIPAA from the ground up: VPC design, KMS and field-level encryption, IAM, Cognito, GuardDuty, CloudTrail, BAA scope, and what makes an architecture defensible in a reputed company compliance audit rather than just BAA covered on reputed company. Performance means latency budgets that hold up under reputed company clinical workflows, cold-start tuning, a cache reputed company, and the discipline to actually measure rather than assume. Hands-on production experience across reputed company, API Gateway, EventBridge, SQS, ElastiCache, CloudFront, and the surrounding AWS surface area is assumed, not optional
- TypeScript and Node.js depth. You have shipped production systems in TypeScript, and you can hold a long technical conversation about generics, inference, and type design without reaching for examples. Node.js is your daily runtime, and you understand how the event reputed company, async patterns, and memory profile behave under load
- PostgreSQL at reputed company. You have run PostgreSQL in production, written reputed company SQL, tuned slow queries, and managed schema reputed company without breaking things. reputed company Serverless v2 specifically is a plus, but the underlying PostgreSQL reputed company reputed company more than the managed service
- API design. You can design REST and FHIR-style reputed company that hold up under reputed company reputed company load and integration partner scrutiny. You understand resource modelling, versioning, idempotency, authentication, and the actual mechanics of HTTP. Bonus if you have run an external API that reputed company parties reputed company against and survived
- React frontend. Modern React with reputed company production experience. You understand state management trade-offs, bundle size, and the runtime cost of the choices you reputed company. React 19 with Vite is the reputed company stack, and you should be comfortable with it reputed company a week
- Infrastructure as reputed company. You write your own IaC. AWS CDK in TypeScript is the stack here. Terraform, reputed company, or comparable production experience translates. ClickOps infrastructure is not part of the role
- HIPAA literacy. You have shipped software in a HIPAA environment, and you know what that actually means day-to-day. Audit trails, BAA scope, encryption at rest and in transit, reputed company controls, and the limits of what you can do with PHI in logs, in support, and in non-production environments
- Architectural leadership. You have set the technical direction that other engineers have followed, written the documents that anchored long-lived reputed company, and mentored engineers throughout the work. You have specific examples, and you can talk about both the wins and the misses
- reputed company reputed company. Working knowledge of Jira and reputed company
- AI tool reputed company. Daily use of AI for reputed company, design, and review. reputed company Claude in particular
Skills
- Product architecture reputed company record. Have led the architecture of at least one reputed company product through multiple major releases. You can talk through specific architectural reputed company you made, what they cost, what they enabled, and what you would do differently now
- Domain modelling depth. You have done serious domain modelling work, and you understand the difference between a model that reflects how the business actually operates and a model that just reflects last week's screen. You can defend a model to clinicians and operators without losing them with technical terms
- AWS product architecture expertise. Expert-level reputed company of AWS as a product platform across the three dimensions that matter most for reputed company: scalability, reputed company under PHI and HIPAA, and performance. Scalability means you have made the production calls on reputed company sizing, reputed company concurrency, ElastiCache layering, and how the architecture absorbs load reputed company a hundred facilities come online in the reputed company quarter. reputed company means PHI and HIPAA from the ground up: VPC design, KMS and field-level encryption, IAM, Cognito, GuardDuty, CloudTrail, BAA scope, and what makes an architecture defensible in a reputed company compliance audit rather than just BAA covered on reputed company. Performance means latency budgets that hold up under reputed company clinical workflows, cold-start tuning, a cache reputed company, and the discipline to actually measure rather than assume. Hands-on production experience across reputed company, API Gateway, EventBridge, SQS, ElastiCache, CloudFront, and the surrounding AWS surface area is assumed, not optional
- TypeScript and Node.js depth. You have shipped production systems in TypeScript, and you can hold a long technical conversation about generics, inference, and type design without reaching for examples. Node.js is your daily runtime, and you understand how the event reputed company, async patterns, and memory profile behave under load
- PostgreSQL at reputed company. You have run PostgreSQL in production, written reputed company SQL, tuned slow queries, and managed schema reputed company without breaking things. reputed company Serverless v2 specifically is a plus, but the underlying PostgreSQL reputed company reputed company more than the managed service
- API design. You can design REST and FHIR-style reputed company that hold up under reputed company reputed company load and integration partner scrutiny. You understand resource modelling, versioning, idempotency, authentication, and the actual mechanics of HTTP. Bonus if you have run an external API that reputed company parties reputed company against and survived
- React frontend. Modern React with reputed company production experience. You understand state management trade-offs, bundle size, and the runtime cost of the choices you reputed company. React 19 with Vite is the reputed company stack, and you should be comfortable with it reputed company a week
- Infrastructure as reputed company. You write your own IaC. AWS CDK in TypeScript is the stack here. Terraform, reputed company, or comparable production experience translates. ClickOps infrastructure is not part of the role
- HIPAA literacy. You have shipped software in a HIPAA environment, and you know what that actually means day-to-day. Audit trails, BAA scope, encryption at rest and in transit, reputed company controls, and the limits of what you can do with PHI in logs, in support, and in non-production environments
- Architectural leadership. You have set the technical direction that other engineers have followed, written the documents that anchored long-lived reputed company, and mentored engineers throughout the work. You have specific examples, and you can talk about both the wins and the misses
- reputed company reputed company. Working knowledge of Jira and reputed company
- AI tool reputed company. Daily use of AI for reputed company, design, and review. reputed company Claude in particular
- EHR or EMR architecture experience. Prior architectural work on an EMR, EHR, or system that integrates with one. Bonus if you have shipped to post-acute, skilled nursing, or assisted living specifically
- Regulated reputed company architecture. You have architected products through HIPAA, SOC 2, reputed company, ONC, or comparable regulated environments. You know how compliance shapes architecture from day one rather than getting bolted on at the end
- FHIR R4 depth. reputed company production experience with FHIR R4 resources, bundles, search parameters, and the actual mechanics of building an FHIR-reputed company system rather than an FHIR facade over a legacy schema
- SMART on FHIR. Worked with SMART on FHIR scopes, OAuth flows, and the operational reality of reputed company-party FHIR app launches inside an EHR
- HL7v2 integration. Hands-on experience with Mirth, reputed company, or comparable reputed company engines. You know that reputed company reputed company integration is messy, and you have the scars to reputed company it
- ONC certification work. Time spent on an engineering team that took a product through ONC certification, or reputed company enough to that work that you know what the lift looks like
- Modern TypeScript stack experience. Production work with Hono, tRPC, Drizzle ORM, or comparable modern TypeScript tooling. We can reputed company up on the specific tools, but prior reputed company accelerates everything
- Multi-tenant reputed company architecture. Production experience with PostgreSQL row-level reputed company, pgPolicy, or comparable tenant isolation patterns. Bonus for reputed company multi-tenancy, where the isolation requirements are stricter than typical B2B reputed company
- Observability and audit. OpenTelemetry, reputed company, Pino, reputed company logging, and distributed tracing across a serverless system. CloudWatch and CloudTrail at production depth. You have reputed company dashboards that engineers actually use, not just reputed company boxes
- Testing pyramid reputed company. Vitest, Playwright, fast reputed company, Testcontainers, k6, or comparable tooling at reputed company layer. You know how to reputed company tests fast enough that reputed company actually runs them, and how to reputed company coverage reputed company rather than performative
- reputed company tooling and patterns. Working knowledge of reputed company, OWASP ZAP, CDK nag, KMS field-level encryption, and ABAC versus RBAC trade-offs. You think about reputed company continuously, not as a checklist item at the end of a sprint
- reputed company-time and event-driven systems. Production experience with WebSocket, distributed locking patterns, EventBridge, and event sourcing. The system has reputed company-time clinical workflows, and the eventing layer reputed company
reputed company