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. That means the measure of a good weekend is not hours logged, it is how much finished, reviewable work is waiting when everyone comes back.

This is not an incident response or on call firefighting seat. You will investigate production issues when they land in front of you, but the core of the job is shipping features.

The Focus of This Seat

We are hiring two engineers for this window with deliberately different weightings. This posting is the mobile weighted seat.

You own mobile feature delivery. React Native and Expo in TypeScript, including the release mechanics that get work in front of users. You should also carry enough Node and Postgres to take a ticket from schema change through API to screen without waiting on anyone. Web React work will come your way and you should be capable there, but mobile is where we are screening for depth.

What You'll Bring

1. 4 to 7+ years building production software, with the majority of that time on mobile.
2. Deep React Native and Expo in TypeScript. Navigation, state management, rendering performance, and the judgment to know which of those a given problem actually needs.
3. 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, versioning.
4. Production apps shipped to both stores and maintained afterward, not just launched.
5. Node.js and Express in production. Enough real API work to close out a feature end to end.
6. SQL and Postgres in production. Schema changes and queries you wrote yourself. Prisma or a comparable ORM.
7. React on the web, with working command of component architecture and state.
8. Testing discipline. Integration and end to end coverage as a habit, not an afterthought. Jest, Detox, Playwright or equivalents.
9. Exceptional professional English, written and verbal. You will communicate directly with US stakeholders and much of it will be asynchronous.
10. 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
• Commits are self contained and tell a coherent story
• Pull request 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

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. Native iOS (Swift) or Android (Kotlin) depth, enough to debug a native module problem rather than route around it.
2. Push notifications across both platforms, including the policy and delivery differences.
3. Offline first architecture and sync strategy.
4. Docker and comfort in a containerized environment.
5. Redis, or caching and queue work more broadly.
6. Payment or third party integration experience, including webhooks and idempotency.
7. Comfort in AWS: Lambda, SQS, RDS, CloudWatch, IAM.
8. Monorepo and shared package experience.
9. CI/CD with GitHub Actions.
10. Analytics tooling such as Amplitude or Segment.
11. Prior consulting or staff augmentation experience, comfortable embedded inside a client team.
12. Prior experience holding a fixed weekend or off hours schedule.
13. 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.