About the role

Senior Full Stack Software Engineer at SalesJack creating impactful solutions in the construction supply industry. Engaging directly with customers and leading full-stack development on critical features.

Responsibilities

Own entire product features from "this is a problem worth solving" to "this is live in customers' hands" — scoping, designing, building, shipping, iterating
Talk to customers directly: discovery calls, support tickets, ride-alongs with sales reps in lumberyards. Use what you learn to make better product decisions
Make the architectural calls on new systems — data model, API surface, frontend composition — and document the reasoning so the team can build on it
Build across our Node.js stack: Next.js on the frontend, Node services on the backend, BullMQ for background jobs and workflows, PostgreSQL as the system of record
Design and operate authentication, authorization, and multi-tenant RBAC systems that hold up under real customer load
Build durable, queue-driven automation with BullMQ — orchestrating long-running processes, retries, and integrations against external ERPs and third-party APIs
Set technical standards (testing, code review, CI/CD, observability) and raise the bar for everyone around you, including the founders
Mentor engineers and lead design reviews

8–10 years of full stack engineering experience, including time spent owning systems in production at meaningful scale
Deep expertise in React and Next.js, with a strong point of view on component architecture, state management, and performance
Strong backend chops in Node.js — you've designed and operated services, not just built features inside them
Advanced PostgreSQL — schema design, query optimization, migrations under load, multi-tenant patterns
Production experience with auth/RBAC systems, especially in multi-tenant B2B contexts
Hands-on experience with BullMQ or comparable queue/job systems (Sidekiq, RabbitMQ, SQS, Temporal) — and a clear sense of when to reach for them vs. simpler patterns
A real product brain. You can be handed a fuzzy customer problem and come back with a scoped, shippable plan - not a Jira ticket asking for specs
Strong product taste. You push back on bad designs, come up with better ones, and have opinions about what "good" looks like in B2B software
Customer instinct. You actually want to talk to users, watch them work, and let what you learn shape the product. You don't need to be shielded from messy customer feedback
Ability to make tradeoff calls — what to cut, what to defer, what to over-invest in — without needing a PM to break the tie.