Review the job details below and click Apply Now to get started.
Software Engineer
Rubie
New York City, New York, United States
$215,000 / yr
We are seeking a highly skilled Software Engineer to join our team in New York City. In this full-time role, you will play a critical part in developing innovative software solutions that drive our business forward. The successful candidate will work in a collaborative environment, focusing on both frontend and backend development to deliver high-quality applications.Key ResponsibilitiesOwn 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. Must-Have RequirementsCritical4–5+ years of software engineering experience (most hires are closer to 6–8 years); strong less-experienced candidates considered if they ramp exceptionally fast.Genuinely full-stack — can take a product slice from frontend through backend and infrastructure on their own.Proficient with the stack, or able to ramp fast: React, Tailwind, TypeScript (frontend); Remix/TypeScript (backend); AWS, Cloudflare.Track record of shipping production software end-to-end and owning the outcome. Required and preferred qualificationsBachelor's degree in Computer Science.Proficiency in full-stack development, covering both frontend and backend aspects.Strong experience with React, Tailwind, and TypeScript.Familiarity with AWS and Cloudflare.Solid understanding of software development best practices and methodologies.Years of experience: 5+ years in software development is preferred.About this RoleProduct-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.