Staff Software Engineer

Staff Software Engineer Location: Remote — US, with core hours overlapping Central Time Partnership: EQL Tech has partnered with Planoly to appoint a mission-critical Staff Software Engineer to lead a product squad and own the shared foundations — auth, permissions, notifications and billing — that every surface of the platform depends on. About the Company & The Mission EQL Tech is proud to represent Planoly, the social content platform built for creators and solopreneurs. Planoly is where a creator plans, schedules and publishes across every major channel — one workspace instead of six tabs and a reminder app. Planoly is profitable and bootstrapped. No VC money, no runway clock, no board steering the roadmap. Product decisions are made because customers asked for them, and the company has the rare freedom to build for the long term. It was recently acquired, and is now nearing the end of a ground-up rebuild on a modern TypeScript stack — the kind of clean slate most engineers wait an entire career to get near. The mission is simple: give independent creators the tooling that until recently only a marketing department could afford. The Team You will be joining a small, senior engineering team where every person's work is visible in the product. The Core Team: Engineering is led by Mouad Belbah, previously Head of Engineering at Snipfeed. The team is deliberately small and deliberately senior — no layers, no ticket queue, no waiting for permission. Work runs in squads: a staff-level lead, a product partner, and one or two engineers. Squads own their scope end to end, from the first conversation about what to build through to what ships. The Role: Staff Software Engineer As Staff Software Engineer, you will lead a squad and build alongside it. You will scope the work, set the timeline, keep your engineers unblocked — and then write the code with them. This is a hands-on staff role, not a step away from the keyboard. As Staff Software Engineer, you will: Ship end to end: take features from database schema and GraphQL resolvers through to React components and mobile screens, owning the whole vertical slice rather than a layer of it Own the shared core: build and maintain the authentication, permissions, notifications and billing logic that every other surface depends on — the work that has to be right Complete the mobile experience: finish and refine the React Native app, bringing it to the same standard as the web product Design durable background workflows: build the scheduling, payments and integration pipelines that have to run reliably at 3am without anyone watching them Lead a squad without managing it: set direction, unblock people, raise the technical bar by example — the influence comes from the work, not a title Shape what gets built: work directly with product, design and marketing on the problem, not just the implementation The Stack: Next.js, React 19, TypeScript, Tailwind and a custom Radix design system.…