Full Stack Engineer
What This Role Is
This is a hands-on, mid-level full stack seat (4 to 6 years), not a lead role. Roughly 70% backend and systems, 30% front-end. You own your work end to end on a lean senior team that ships in two-week sprints. The team recently rebuilt the platform on a clean, modern stack, so you inherit ownership, not years of tech debt. You will build the tooling that keeps a large education platform running for real customers: the customer service admin suite that fixes accounts in one click, the Circle member experience members touch every day, and the affiliate system that drives growth. This is tooling and integration work with real leverage, not ticket-shuffling. The person who fits is organized and autonomous, asks why before building, ships clean through peer review, and genuinely rolls with change when priorities pivot fast. This a pure build seat, pointed where it creates the most value.
What This Role Is Not
Not a lead or management seat. You architect and ship, not run a team or defend a roadmap in meetings.
Not a DevOps or platform-ops seat. No pagers, no babysitting deploys, so you spend your time building instead of firefighting.
Not a solo builder's gig. If your entire background is personal projects with no professional team or code review, this is not a fit.
Not an "AI writes it, I ship it" role. We want engineers who make sure what AI gives them actually works, not people who hand it off unchecked. If You Can...
Why This Role
Most full stack roles bury you in the parts of the job nobody planned for: legacy sprawl, undocumented systems, and infrastructure that fights you before you write a line of product code. That's not this. Our team just retired an entire legacy stack and rebuilt the platform on a lean, modern foundation with zero customer disruption. There is no decade of tech debt waiting for you, no tangle to reverse-engineer before you can ship. The stack is current, the team is senior, and the path from your branch to production is short: you own your work end to end, ship through peer review, and see it go live without wading through layers of process. What you get to do with all of that is build. Real tooling, real ownership, and a small team where what you ship actually matters.
What You'll Own
Customer Service Admin Suite (Primary)
The Circle member experience (login, billing, account management, lead flows) and the plumbing that connects our commerce stack to it, running smoothly end to end.
Affiliate System (Ongoing)
How You Ship (Every Sprint)
Own your work all the way to production: validate it yourself, walk a reviewer through your test cases, and ship through peer review.
Keep clean progress and surface blockers early.
What We're Looking For
4 to 6 years building production full stack applications inside a professional engineering team with code review
Front-end: Next.js, React, TypeScript, Tailwind, iframes
Backend: Node, Express, MySQL, Redis
Cloud and hosting: Heroku and GCP
Collaborative problem solving: you think fast with the team and pressure-test the plan before building, no rogue players
Real AI fluency: you use AI as a craftsman's tool and make sure what it produces actually works
US citizens and green card holders only. No visa sponsorship.
Strong Differentiators
AI coding tools used well (Claude Code, Cursor), with the judgment to verify and own the output
n8n or workflow automation experience
Based in Scottsdale or Greater Phoenix (on-site preferred)
1 to 2 prior roles of roughly two years each, ownership. No job hopping
The Core Skill
Change Resilience
Priorities here can pivot fast, and sometimes weeks of work get shelved the same day. Everyone says they are fine with that. Almost nobody is.
The engineers who thrive treat a scrapped project as a redirect, not a loss.
How to Apply
Apply through the application link in this post. You will be asked focused questions about your experience, how you use AI tools in your workflow, and how you think about shipping clean, reviewable work on a fast-moving team. Example: one question will ask you to describe the toughest technical problem you solved recently, what made it hard, and how you worked through it.