Sr Software Engineer (Costa Rica)

What You'll Do8

• Own the user, role and organization domains, and shape the APIs and SDK contracts other teams build against.
• Port logic out of legacy serverless and GraphQL services into NestJS domain services without breaking existing consumers.
• Design and run data lifecycle work driven by SAP data: archival, transfers, backfills, reconciliations and large account migrations.
• Review a large share of the team's pull requests, roughly 35 to 65 percent, and coach engineers through the feedback.
• Act as the reference point for consumer SDK, user API, data integrity and auth questions, then write the RFCs and migration plans that follow.
• Keep the platform healthy through runtime upgrades, CI hardening, test infrastructure and performance tuning.
• Build REST and OpenAPI contracts with generated typed SDKs, plus GraphQL where older services still need it.
• Implement auth flows across role-based access, Okta, service-to-service calls through central IAM and token-based partner access with DPoP.

Requirements8

• Production experience with TypeScript and Node.js, plus hands-on NestJS for domain services.
• Deep PostgreSQL work: schema design, migrations, indexing and query plan analysis with EXPLAIN ANALYZE, using TypeORM.
• AWS serverless and event-driven design covering Lambda, SQS with FIFO queues and dead-letter queues, SNS and Parameter Store.
• API design across REST and OpenAPI with generated typed SDKs, and GraphQL for legacy services.
• Auth and permission modeling: role-based access, Okta, service-to-service auth through central IAM and token-based partner access with DPoP.
• Testing discipline with Jest and Testcontainers-backed integration tests.
• A track record of replacing a legacy system step by step with feature flags, fallbacks or parallel runs, and the ability to explain those trade-offs.
• Clear writing for RFCs and migration plans that other teams act on.

Preferred Qualifications5

• Temporal or another durable-workflow engine
• Terraform
• Kubernetes enough to deploy and debug, including Kustomize overlays and IAM roles for service accounts (IRSA)
• Datadog for observability
• GitHub Actions and ArgoCD for CI/CD

Who Should Apply

A senior engineer who treats a backfill or migration as a production change, complete with a written plan, dry runs, reconciliation and a rollback path. You have moved a legacy system off piece by piece and can explain why you picked feature flags or parallel runs. Comfort with PostgreSQL internals and NestJS service design matters more here than broad tool trivia.

Salary Insight