Principal Engineer

We’re hiring our founding engineer.Right now, our product’s being built with a top consultancy;they’ve done the heavy lifting, and it’s looking great. But we need someone to come in-house, own it, and take it to the next level. What’s the gig? You’ll be our Principal Engineer, basically the grown‑up in the room when it comes to tech. You’ll work alongside the consultancy (they’re solid), learn the system inside‑out, and then run the show. You’ll decide how we scale, what gets built, and how we build it. Day one: hands‑on Rails work. Day two and beyond: setting standards, mentoring future hires, making big calls. Stack’s simple and solid: Ruby on Rails | Postgres | Tailwind | Mini.Js | Heroku Why bother? You won’t just be “joining a dev team.” You’ll be building the dev team. You’ll have direct impact with zero corporate nonsense. You’ll get exposure to big clients (banks, pharma, agencies) who are already using the product. Pay’s competitive, equity’s meaningful, and the growth path is real (Head of Eng / CTO is on the table). What we’re after? Rails chops. Postgres comfort. Enough frontend skills to not panic at Tailwind/JS. Someone who’s scaled an app before, thought about performance, security, architecture. A pragmatic builder: you ship, but you care about quality. Bonus points if you’ve seen SaaS, HRTech, or startup chaos before. The Bottom Line If you’re a senior Ruby engineer and you want your fingerprints on an entire product (instead of one ticket in Jira), this is your shot. #J-18808-Ljbffr