Senior Fullstack Engineer (React Native, Expo, TypeScript) | Weekend Schedule

Client: US social sports prediction platform Engagement: Contract, full time, remote (LATAM) Openings: 1 Schedule: Thursday through Monday. Tuesday and Wednesday off.

Schedule

This is a permanent weekend seat, not a rotation and not occasional weekend duty.

• Thursday, Friday, Monday: 9am to 5pm ET
• Saturday, Sunday: 12pm to 8pm ET
• On call: 6pm to 12am ET, 1 to 2 days per week, billed at 1.25x base rate for hours actually worked when called in

Thursday, Friday and Monday give you full overlap with the US team for planning, review and handoff. Saturday and Sunday you work independently. Do not apply unless this schedule works for you long term.

Why This Role Exists

Our client does not want to lose two days a week with no development happening. The product carries its heaviest real user traffic on weekends, and the roadmap keeps moving whether or not the weekday team is online.

Your job is feature throughput. You pick up work on Thursday, you build through the weekend, and on Monday the team logs in to review and ship what you finished. The measure of a good weekend is not hours logged, it is how much finished, reviewable work is waiting when everyone comes back.

The Focus of This Seat

We are hiring two engineers for this window with different weightings. This posting is the mobile weighted seat, but read the requirements carefully: the depth we are screening for is backend, data and infrastructure.

The existing team is well covered on frontend. What is thin is engineers who can own a service, design a schema, reason about a queue, and understand the infrastructure their code runs on. You will own mobile feature delivery in React Native and Expo, and you will be expected to build the API and data layer behind those features yourself rather than waiting on someone else.

If you are a mobile engineer who consumes APIs, this is not the right seat. If you are a backend engineer who ships confidently in React Native, it likely is.

What You'll Bring

Backend and data (the core of this role)

1. 4 to 7+ years building production software, with substantial backend ownership.
2. Node.js and TypeScript in production. Services you designed, built and operated, not endpoints you called. NestJS, Express or Fastify.
3. SQL and Postgres at a real level. Schema design, migrations, indexing, query optimization, and the judgment to know when the data model is the actual problem.
4. API design. REST at minimum, GraphQL or gRPC welcome.
5. Asynchronous and event driven patterns. Queues, workers, background jobs, retries and idempotency. SQS, RabbitMQ, Kafka or equivalents.
6. Caching in production. Redis or comparable, including invalidation strategy and what happens under concurrent load.

Infrastructure

1. AWS in day to day use: Lambda, SQS, RDS, S3, CloudWatch, IAM.
2. Docker, and comfort operating in a containerized environment.
3. CI/CD you have configured yourself, not just consumed.
4. Observability. Logs, metrics, traces, and the ability to diagnose a production issue from them.

Mobile and frontend

1. React Native and Expo in TypeScript. Navigation, state management, rendering performance.
2. Release engineering on mobile: EAS Build, EAS Submit, EAS Update, the call between an OTA push and a native release, App Store Connect and Google Play submission.
3. React on the web, with working command of component architecture and state.

Working style

1. Testing discipline. Integration and end to end coverage as a habit, not an afterthought.
2. Exceptional professional English, written and verbal. Communication here is largely asynchronous and directly with US stakeholders.
3. Self direction. On Saturday and Sunday you are prioritizing, deciding and finishing work without a lead online.

How Your Work Needs to Land

This matters as much as the technical bar, so we are stating it plainly. Weekend work only creates value if it is reviewable on Monday morning by someone who was not there when you wrote it. That means:

• Tests ship with the feature, not in a follow up
• Pull requests are small and self contained; large features arrive as a reviewable sequence
• PR descriptions explain the what and the why well enough to review cold
• Anything you could not finish is documented clearly enough for someone else to pick up
• Production risk is never taken unilaterally on a weekend

If your instinct is to hand off a large unexplained branch on Monday morning, this is not the right seat.

What Sets You Apart

1. Infrastructure as code: Terraform, Helm, Argo CD, Kubernetes.
2. Experience with low latency or performance sensitive systems, especially anything with sharp traffic peaks tied to live events.
3. Payment or third party integration work, including webhooks, idempotency and reconciliation.
4. Native iOS (Swift) or Android (Kotlin) depth, enough to debug a native module problem rather than route around it.
5. Push notifications across both platforms, including the policy and delivery differences.
6. Offline first architecture and sync strategy.
7. Monorepo and shared package experience.
8. Analytics tooling such as Amplitude or Segment.
9. Prior consulting or staff augmentation experience, comfortable embedded inside a client team.
10. Prior experience holding a fixed weekend or off hours schedule.
11. A background or genuine interest in sports.

Why You'll Love Working With Us

Remote first, working with a top tier US client on a product real users touch every weekend. Your Tuesdays and Wednesdays are yours. The stack is modern end to end, the team is small enough that your decisions stick, and you will finish most weekends with something concrete to show for it.