Back to writing
engineering1 min read

Open to work: remote, senior, full-stack. Here's the filter. If these things annoy you, we won't fit.

Open to work, remote, senior, full-stack

Rob Vasquez·

Open to work: remote, senior, full-stack. Instead of the usual pitch, let me hand you the filter. If a few things about how I work would annoy you, we're not a fit, and that saves us both time.

I care about the boring correctness. Money as integers, inputs treated as adversarial, tenants isolated by the platform instead of by hope. If "just ship it, we'll fix the edge cases later" is the culture, I'll be friction.

I want to own the whole slice, from schema to deployed UI. Put me in a narrow lane where I never see the outcome of my work and you'll get an underused engineer.

I default to shared over duplicated. I'll push to extract the common core rather than copy it a fourth time. If the team prizes speed by copy-paste, I'll keep raising my hand.

If those read as green flags, we'll probably work well together. I've built and shipped a suite of 20+ apps solo, so I bring the range and the judgment about when to slow down.

Remote-first, senior full-stack or AI-engineering. If that's your team, DM me and let's talk specifics.

OpenToWorkRemoteWorkFullStackHiringAIEngineering

Need a practical path to AI-enabled delivery?

Start with a fixed-price AI-readiness audit and leave with a concrete roadmap.

View the AI-readiness audit