About the Role
Most companies hire engineers to close tickets. We hire them to solve problems.
Uscreen is looking for a Product Engineer who starts with the creator's experience and works backward to the tech that delivers it. Someone hands you a half-formed problem. You turn it into something creators can actually use, and you own the whole thing: the design call, the code, the ugly edge cases, and the metric that proves it worked.
This is not a ticket-taking role, and it is not a place to wait for someone to tell you what to build. You take a fuzzy customer pain and ship the value, end to end. The outcome is what matters to you.
This role is fully remote, worldwide. You report to the
CTO.
What You'll Do
- Take ambiguous, half-formed customer problems and turn them into shipped product creators can actually use
- Own the full path of a solution: the design decision, the code, the edge cases, and the metric that proves it worked
- Talk directly to creators rather than waiting for a PM to translate their needs
- Work across our stack - Ruby on Rails, React, and Flutter, with native bits where it counts (yes, even BrightScript)
- Measure success in outcomes that move the business, not tickets closed
- Throw out yesterday's work the moment a better answer shows up, and delete more code than you add
- Hold the bar between "working" and "solved" - and keep fixing until good becomes right
You'll Likely Succeed If
- You've shipped something real, and you can send us the link.
- You'd rather talk to a creator than wait for a PM to translate.
- You measure success in outcomes, not tickets closed.
- You'll throw out yesterday's work the second a better answer shows up.
- You delete more code than you add, at least sometimes.
- You can tell good from almost-good - and it bugs you until you fix it.
- You have judgment about which problem actually matters, then ship the thing that moves it.
Why This Matters
Code that runs is table stakes. Working software isn't the same as a solved business problem, and the engineer we want feels that difference in their gut.
Anyone can rent a machine that spits out working code now, so that's not the edge anymore. The edge is judgment: knowing which problem actually matters to a creator, then shipping the thing that moves it. We hire for how you think, not what you've memorized.
How to Apply
Take an ambiguous prompt and ship a sharp answer: write to our CTO at [redacted] and show one problem you owned end to end - the problem and why it mattered, what you shipped to kill it (and what you chose not to build), how you knew it worked, and something you've built that we can click right now.
The best applications don't read like applications.
