Senior Full-Stack Engineer (NestJS/React) | US Pacific Hours | No Agencies

Summary We are seeking a high-ownership Full-Stack Engineer to join our core team. This is a full-time senior level role. You must have experience designing and developing in large apps with distributed services. You will be reporting directly to the CTO, which means there is no middle management—just direct collaboration and high expectations for your output. This position will become a team lead position where you will review PRs from other devs as well as help write and design code. The Reality of the Role • Total Ownership: You own the task in-flight. If it breaks in production, you are the one who fixes it. • Magnitude Experience: We work on a large, interconnected ecosystem. We are looking for someone who understands that a "small" change in a shared provider or a database schema migration can have cascading effects. • Regression Mindset: You treat every bug fix as a potential source of two new bugs. You proactively check logs, health checks, and metrics after every deploy. • No "Sandbox" Developers: If you have only worked on greenfield projects or small "Todo" apps, this role is not for you. We need someone comfortable navigating complex, existing codebases with 50+ services/modules. Strict Availability Requirements • Timezone: You must be online and active during the 8:00 AM – 4:00 PM US Pacific window. This is non-negotiable for team synchronization. • Communication: Fluent English (written and verbal) is required. Technical Stack • Backend: Heavy NestJS (v10+) and Node.js. • Frontend: ReactJS (Vite-based). • Testing: Proficiency in writing/maintaining E2E and unit tests is a core requirement. • Infrastructure: AWS (ECS/RDS), Docker, and standard CI/CD practices. • Database: Deep proficiency in SQL, schema design, and migration management. Technical Competencies for Interview Our interview will focus on your ability to handle scale, not syntax memorization. Be prepared to discuss: • SOLID Principles: How you apply them to keep a large codebase maintainable. • Database Optimization: How you handle migrations on live systems without downtime. • Debugging at Scale: How you trace a bug that starts in the frontend but originates in a deeply nested backend service. • Testing Strategies: Your philosophy on balancing test coverage vs. velocity. The Contract We will start with a task-based trial. If the fit is right, we will transition to a 40-hour-per-week engagement. How to Apply (The "Human" & "Magnitude" Test) We do not hire agencies. If you are an agency, please do not apply. To ensure you have read this and aren't using an AI-generated response, please include the following in your proposal: 1. Subject Line: Must be exactly: "I am an individual dev for US Pacific hours." 2. The "Magnitude" Question: Describe a time you performed a significant refactor or a database migration on a live system with active users. How did you ensure 100% up-time and verify that your changes didn't break downstream dependencies? (Note: If you mention "manual testing" as your primary strategy here, we will not be moving forward.)