One-time gig
Try an Error Inbox with Sample Apps in Four Stacks
ServerInspector
ServerInspector also catches application errors. An app can send its crashes to us with the error SDK it already has, by changing one setting, or with a few lines of code and no package at all. We want to know how that holds up outside our own test bench.
You build small sample apps in at least four stacks, chosen from Next.js, Node.js, Ruby on Rails, Django, Flask, Laravel and Supabase Edge Functions, then send real crashes through both routes.
Deliverable: a Git repository of the sample apps, a table of what arrived correctly (stack traces, grouping, environment, release), and suggested edits to our docs.
Done means each stack has a working sample, every mismatch has a bug report, and a stranger could repeat your test from the repository README.
Mandatory: JavaScript or TypeScript, Python, Ruby or PHP, Git, experience with error tracking such as Sentry. Nice to have: Supabase, source maps, technical writing.
What it asks for
- Next.js
- PHP
- Supabase Edge Functions
- Django
- Node.js
- Sentry
- JavaScript
- Flask
- TypeScript
- GitOps
- Ruby
- Laravel
- Python
Nice to have
- Technical writing
- Source maps
- Supabase