Software Engineer

**Rubie** Software Engineer; $150K–$215K + equity; New York City (On-site)

**About Company** Rubie helps software companies win deals by making data migration automatic. Its computer-use and browser-use agents log into whatever system of record a customer is leaving, pull out and clean the data, and move it into the new system — turning what used to be weeks of manual work into a near one-click, end-to-end migration. Software vendors repackage this as part of their post-sales motion, removing the single biggest reason their own deals stall: customers who won't switch because migrating their data is too painful.

Rubie is growing fast. It raised a $15M Series A about six weeks ago (total raised to date; round otherwise unannounced), has nearly 4x'd ARR since the start of the year, runs ~60 active deals in flight, and books 80–100 new meetings a month. Net revenue retention is ~190% — once customers cross an initial trust gap, they hand Rubie their entire migration and post-sales data function. The beachhead market is vertical SaaS (software for fitness studios, dental practices, property managers, and the like), with a longer-term TAM of any software company that has a competitor.

Rubie's mission is to "make the internet liquid" — if you buy software, you should be able to pick up your data and move to a better product at any time. The team is deliberately small, senior, and high-performing; founder/CEO Jimmy McDermott was a CTO for nearly a decade before starting the company. HQ is in Union Square, NYC, in-person five days a week.

**About the Role** Product-minded full-stack engineers who own problems end-to-end — frontend, backend, infrastructure, performance, and security. Rubie calls its engineering team a "founders-in-training" program: you're expected to sit with customers, form a view on where the product should go, debate it with the team, and then ship it. The company just rebuilt its architecture to handle much larger data-movement workloads, opening new product surface — so there's a deep backlog of hard durability, security, workflow, and large-scale data problems to own.

**Responsibilities** - Own features end-to-end across frontend, backend, infrastructure, performance, and security. - Sit with customers, identify where the product needs to go, and drive it back into the roadmap. - Build on the new architecture for large-scale, reliable data movement. - Use AI heavily and agentically — while owning and standing behind everything that ships.

**Required Skills** A. 5–8 years of software engineering experience. B. Genuinely full-stack — can take a product slice from frontend through backend and infrastructure on their own. C. Proficient with the stack, or able to ramp fast: React, Tailwind, TypeScript (frontend); Remix/TypeScript (backend); AWS, Cloudflare. D. Track record of shipping production software end-to-end and owning the outcome.

**Bonus Skills** - Experience with large-scale data movement, migration, or systems-of-record integrations. - Comfort working in an AI-/agent-heavy engineering workflow.

**Logistical Info** - Location: New York City, in-person at the Union Square office 5 days/week. Candidate must already be in NYC.

Relocation is not disqualifying but raises the bar significantly, so only send a reloc if they are clearly above the line. - Compensation: $150K–$215K + meaningful equity (everyone at Rubie is an owner). The top of the band is for the 6–8 year profile. A four-year candidate asking $215K+ reads as mispriced. - Number of openings: 4+. - **Other:** Generous health insurance.

**Ideal Background** - Client-confirmed calibration (Jimmy McDermott, CEO, 8/21): big-tech-only resumes (e.g. Databricks, Datadog) ARE hireable if tenure is stable — startup experience is not itself the gate. The real gate is job-hopping: "we'd want it evened out by lack of jumpiness." Read "requires startup experience" as a soft signal, not a hard filter, provided the candidate's tenure history is clean. - Degree is not consistently open despite earlier framing — has been rejected specifically for lack of a degree. Don't lead with "open-minded on school and degree" when pitching; treat it as case-by-case. - What matters: can ship end-to-end and own the result, and can connect with the mission (customer empathy). - Calibration: ticket-takers who want fully-spec'd work are not a fit; this is a high-ownership, product-engineering environment.

**Green Flags** - High agency — debates product direction and then owns it. - Resonates with the "make the internet liquid" mission (a slightly pirate-y, take-on-the-incumbents motivation). - Deep interest or excellence in a non-work pursuit (music, photography, etc.) — well-rounded people tend to do well (nice-to-have, not required).

**Red Flags** - Ships "AI slop" / over-relies on AI without owning the output. - Only comfortable pulling pre-defined tickets; can't operate end-to-end. - Left a big company for a startup and bounced inside a year. - Job-hopping / short-stint pattern generally — this is the client's actual filter, more than company pedigree (confirmed 8/21).

**Interview Process** - Quick background conversation with the CEO. - ~1-hour take-home assessment (capture-the-flag style), in prep for the systems interview. - 60-min systems design / architecture review with the CEO and a team member. - On-site — ideally a 2–3 day paid work trial shipping with the team (flexible per candidate). Offer from there.