Company
Rilla
Annual salary
$193k – $258k/yr
Location
New York, NY
Listed
732d ago
- Experience:
- 1 to 3 years
- Workplace:
- In-person in NYC
- Visa:
- Visa sponsorship available
- Equity:
- Competitive
On-site in New York, NY. Visa sponsorship available.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this Role
Rilla engineers architect and ship features across the stack at lightning speed. On a daily basis, you will build end-to-end workflows, take them to production, and solve real world problems across an out-sized scale.
As an early technical steward, you will raise the bar for code quality and decision‑making, setting patterns that cement a world‑class engineering culture as we scale. While the company 10×’s, your scope and ownership will grow just as fast, building the tools, mental models, and platforms that let both you and Rilla accelerate exponentially.
Do you describe yourself as "obsessive"? Do you aspire to be a founder or a leader in applying AI to the physical world? We believe Rilla is the best place, with the best peers, to learn how.
Technologies We Use
Different languages and frameworks, including React, React Native, Typescript and Python
Open-source technologies like Node.js, PostgreSQL, Turborepo, Lodash, and Zod
Industry-standard build tooling, including GitHub Actions, Terraform, and Spacelift
What We Value
An** infinite learner**. Someone who is relentless in their curiosity.
A customer obsessive. Someone who deeply care about delighting customers and solving real pains, not vanity metrics.
A winning attitude. You thrive with extreme accountability, learning as a team, and both giving and receiving rapid feedback.
Extreme empathy. Our customers are not tech companies. They live and work in the real world. Empathy is critical to arriving at correct solutions.
Unafraid of failure. You take risks. You see failure as an opportunity to learn, grow, and be better the next time. In a weird way, you trick your brain into being excited when you fail, because it means you got a new opportunity to learn more.
Frequently Asked Questions
How do I apply for the Software Engineer (US) role at Rilla? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this Rilla role pay? +
The listing gives $193k – $258k/yr.
Is this role remote? +
The listing gives the location as New York, NY. In-person in NYC. Visa sponsorship available.
Interview Prep
Sample questions for a Software Engineer role, written in-house to help you prepare.
How do you approach designing a system when the requirements are still likely to change?
I design around the parts of the problem I'm confident are stable, like the core data model, and keep the parts most likely to change, like specific business rules, isolated behind clear interfaces. Over-engineering flexibility everywhere just adds complexity to parts of the system that were never going to change.
What's your process for debugging an issue that only reproduces in production, not locally?
I add targeted logging around the suspected area and compare production data or configuration against my local setup, since an issue that's environment-specific usually traces back to a real difference between the two rather than a fundamentally different bug. I avoid making speculative changes without first confirming where the divergence is.
How do you decide when a piece of code needs a test versus when it's low-risk enough to skip?
I prioritize tests for logic with real business consequences if it breaks, or code that's likely to be touched again later by someone unfamiliar with it. Simple, rarely-changed glue code gets less coverage, since the cost of a thorough test there often exceeds the risk it's protecting against.
How do you evaluate a proposed technical solution's trade-offs, like performance versus maintainability?
I start from the actual constraint that matters for this specific system, whether that's genuinely performance-critical or whether maintainability is the bigger long-term cost, rather than defaulting to whichever trade-off I personally prefer. Optimizing for performance the system doesn't need just adds complexity nobody benefits from.
Related Roles
Browse all startup roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
View all startup roles →