SDE-1 Full Stack Engineer (HighAdvocacy)

Experience Level: 1–3 yearsCore Focus: Full-stack feature development across Node.js and React, with strong fundamentals and an AI-first workflow.Tech Stack: Node.js, TypeScript, MySQL, React, TailwindCSS, Redux Toolkit/RTK Query, shadcn/ui, AWS, TypeORM, Redis, BullMQUseful experience: queues, webhooks, LLM APIs, scrapingAbout High AdvocacyHigh Advocacy turns a B2B SaaS company's silent happy customers into its loudest marketing channel. When a customer hits a milestone, closes a big deal on the back of your product, or drops a 9/10 NPS, we make it effortless for them to share that win publicly as a review, a social post, or a text or video testimonial verify it actually happened, and get rewarded on the spot.Teams run all of it from one workflow: AI-assisted drafts written for the customer, a single clean approval queue, email and Slack notifications, and a Proof Library that stores every approved asset to reuse in a sales deck, a landing page, or a comparison page in seconds. It's an early, fast-moving product built by the team behind Saleshandy which means real ownership early, and AI baked into both how we build and what we ship.What's the Role AboutYou'll build features end-to-end on High Advocacy , backend services in Node.js, data modeled in MySQL, and clean React UIs with TailwindCSS and shadcn/ui, deployed on AWS. The full vertical slice, one feature at a time, a campaign flow, an approval queue, a piece of the Proof Library. You'll learn how a real product behaves under load, write code the team can build on, and take on more ownership as you earn it.Three things matter more than years of experience:- High agency. You act when the spec is unclear instead of waiting to be told. You pick up the broken thing next to your ticket. You stay on the hook for what you ship until it actually works for the user not just until it's merged.- Systems thinking. You don't just make it pass locally. You ask how it behaves at 10x, where it fails silently, and which edge cases are empty, error, loading, permissions you need to handle before anyone points them out.- AI fluency. You use AI across the whole loop building, debugging, testing, docs and you review what it writes as hard as you'd review a junior's PR. AI is a multiplier for your judgment, not a replacement for it.Why Join Us

• Purpose: You're building an early product from close to the ground up your features ship to real users fast, not into a backlog.
• Growth: Learn system design and full-stack craft by building real things, next to senior engineers who review to teach.
• Leverage: We're serious about AI-first engineering and the product itself is AI-native. You'll build a workflow here that makes you noticeably faster every quarter, a skill that compounds for the rest of your career.Your Main Goals
• Ship your first features (within 20–35 days)Learn the codebase and ship your first full-stack features with guidance. You run what you build in staging against real edge cases before calling it done.Outcome: first features live in production, tested by you first.
• Build independently (within 60 days)Deliver features end-to-end with less hand-holding clarifying questions upfront, obvious edge cases handled, clean PRs that say what and why.Outcome: features shipped on your own, with good quality and no surprises.
• Strengthen reliability (within 60–90 days)Handle errors and failure paths, and lift code quality through real tests that actually exercise the code. Respond to alerts on your own code.Outcome: a measurably more reliable slice of the system.
• Own a component (within 90–120 days)Take ownership of a feature area, join design discussions, and start spotting the non-obvious edge cases in review, not just the happy path.Outcome: clear ownership of one component, and a workflow others start borrowing from.Culture Fit
  
  

Are You One of Us

• You're hungry to learn and grow fast.
• You care about fundamentals and clean code and you can spot bad code (huge functions, dead code, copy-paste) when you see it.
• You take feedback well and give it constructively.
• You move fast, ask sharp questions, and raise a "yellow" early instead of hiding it until it's red.
• You use AI tools as a multiplier, not a crutch and you can explain why you reach for a given tool and where it breaks down.