What you'll do
- Run and improve our Supabase backend: Postgres schema and migrations, row-level security (RLS) policies, and edge functions written in Deno and TypeScript.
- Operate our Cloudflare setup: Workers, R2 storage and the static marketing site, including caching, routing and deploys.
- Finish moving files from legacy AWS S3 and CloudFront to R2 without downtime or lost data.
- Make background uploads from iOS, Android and the web reliable: resumable transfers, sensible retries and clear failure reporting.
- Own monitoring and error alerting, so problems reach us before they reach users.
- Keep Postgres fast on a small plan: query plans, indexes, connection limits and data retention.
- Keep costs under control across storage, egress and compute, and write down the trade-offs.
- Run backups and disaster recovery, and prove restores work by testing them.
- Harden security: RLS reviews, signed URLs, rate limits and least-privilege keys.
- Respond to incidents: restore service first, then write the incident report. We keep one for every incident.
Must-haves
- Production experience with Postgres: schema design, migrations, query tuning and access control.
- Hands-on work with object storage and CDNs (AWS S3, R2 or similar): signed URLs, caching and lifecycle rules.
- Strong TypeScript, and comfort reading and writing server-side code.
- You have owned production incidents and can write a clear, blameless incident report.
- Security habits: least privilege, careful handling of secrets, and reviewing access rules before they ship.
- Clear written English and the ability to work independently and asynchronously.
- You are based in the United States and can work as an independent contractor.
Nice-to-haves
- Supabase in production: auth, RLS and edge functions.
- Cloudflare Workers and R2.
- Migrating large amounts of data between storage providers.
- Deno.
- Knowing how iOS and Android schedule and limit background transfers.
- Reading cloud bills: egress, storage classes and capacity planning.
How we work
- Asynchronous and written first. Few meetings; plans and decisions live in writing.
- Small team, no layers. You work directly with the person who owns the decision.
- High craft. Changes are reviewed, tested and reversible. We would rather ship a small fix right than a big one twice.
- Users first. No ads and no data mining, so reliability and privacy are the product.
Pay and terms
- USD $35–60 per hour. Your rate is agreed in writing before work starts.
- Independent contractor engagement, not employment, so there are no employee benefits.
- Fully remote within the United States. Our HQ is in Florida, so we coordinate in US Eastern Time.
- Hours and scope are agreed up front and reviewed as the work changes.
Hiring process
- Email us using the steps below.
- A short call about your experience and the kind of work you want.
- A technical conversation: we walk through a real problem from our stack together.
- A decision, then written terms and a start date.
How to apply
Send one email with the subject “Cloud System Engineer”. Plain text is fine.
- Where in the US you are based.
- Your hourly rate within the USD $35–60 range.
- A link to your résumé, GitHub or LinkedIn.
- A few lines about production infrastructure you have run, and one incident you handled.
No mail app? Write to support@virtualdrive.us with the subject “Cloud System Engineer”.