2x Senior Software Engineer, Node.js (Serverless & Containers) Remote with Preference

Preference shown to Phoenix, Philadelphia or Northern Virginia but Remote Bring the cape. The people we help need us every day. Somewhere right now, a missing child is closer to home than anyone realizes. Somewhere else, a person wanted on a violent felony warrant just walked into a venue full of families. And those people depend on software that works at 3 a.m. on a holiday weekend, when nobody is staring at the dashboards. Safience builds identity intelligence for public safety. We help identify two kinds of people: those who pose a real threat, and those who need to be found. Every record we work from is sourced from law enforcement. There is no video. If law enforcement isn't already looking for you, you pass through and leave no trace. The services you ship carry an image from the field to a human reviewer, and a confirmed alert from that reviewer to the people who can act on it. If a service holds onto data it shouldn't, someone's privacy pays the price. You'll report to our Director of Product Architecture and help set the technical direction for everything we run on serverless and containers. Design, build, and run production Node.js services in TypeScript on AWS Lambda and ECS/Fargate. You own them end to end: code, infrastructure, pipelines, monitoring, and production support. Own infrastructure-as-code in Terraform (CDK or SAM where they fit), modular, with remote state and peer-reviewed changes. Ship lean, hardened Docker images: multi-stage builds, pinned base images, non-root users, deterministic installs, managed in ECR with scanning and retention policies. Run GitHub Actions pipelines with OIDC federation to AWS (no long-lived keys), weighted traffic shifting, blue/green deploys, and automatic rollback on alarm. Keep the supply chain clean with lockfiles, private registries, and automated vulnerability and license scanning. Instrument everything: structured logs, metrics, and distributed tracing (CloudWatch, X-Ray, OpenTelemetry, Powertools for AWS Lambda). Lock down VPC networking for Lambda and Fargate. Work across multiple AWS accounts with least-privilege, cross-account IAM. Watch the AWS bill for what you own, and make it smaller. You catch the race condition before it ships. Data you shouldn't keep, you don't keep. 6+ years of professional software development, including 4+ years building and running production Node.js services ~3+ years running production workloads on AWS Lambda and containers (ECS/Fargate, EKS, or equivalent) ~ Deep Node.js and TypeScript: the event loop, async patterns, streams, memory behavior, CommonJS and ESM, and strong typing habits ~ Core AWS: IAM, API Gateway, SQS, SNS, EventBridge, Step Functions, DynamoDB, S3, CloudWatch, ECR, ECS/Fargate, and VPC fundamentals ~ AWS SDK for JavaScript v3: modular clients, middleware, pagination, and retry configuration ~ Testing: unit, integration, and contract tests (Jest, Vitest, or similar), plus local Lambda emulation (SAM CLI, LocalStack, or equivalent) ~ Working proficiency with at least one NoSQL store (DynamoDB, MongoDB/DocumentDB) and one relational database AWS certifications: Developer Associate, Solutions Architect Associate or Professional, or DevOps Engineer Professional AWS Organizations and multi-account landing zone patterns Regulated or security-sensitive environments (SOC 2, PCI, gaming compliance) Go, Python, Java, or Scala Your access is set up, you've shipped your first production change through the full pipeline, and you've written up the gaps you found in our existing Lambda and container services. ~You own at least one service end to end, on-call included, and you've made it measurably better on observability, deployment safety, or cost. ~You've led the design and delivery of a new service or a major refactor, and you've set a team standard others build on, like a Lambda project template, a base Docker image, or a Terraform module. Fully remote. When the system holds up, a child goes home. A team that treats privacy as an engineering requirement, not a legal afterthought Participation in an on-call rotation. The people we help can't wait for a ticket to work its way out of the backlog.