Senior AI-native Fullstack Engineer

Senior Fullstack Engineer role focusing on AI-native development, owning full-stack features across backend (PHP/Laravel, Node.js/NestJS) and frontend (React/TypeScript) on AWS. The role emphasizes AI-assisted coding, automated testing, and lean team rituals.

• Own and deliver features end-to-end across the full stack (backend services, APIs, frontend interfaces, and data layers)
• Design, build, and operate production systems in a payroll domain where correctness and reliability are non-negotiable
• Use AI coding tools (e.g., Claude Code, Cursor, Copilot) as a daily force multiplier for writing, reviewing, and refactoring code
• Write and maintain automated tests with AI-assisted generation, aiming for high coverage with minimal manual effort
• Participate in lean team rituals: async-first communication, lightweight code reviews, and continuous deployment
• Collaborate closely with product and design in a small squad to scope, estimate, and prioritize work
• Contribute to defining and evolving our AI-augmented engineering practices and toolchain
• Take shared ownership of operational concerns: monitoring, alerting, incident response, and on-call rotations

• 5+ years of professional software engineering experience with meaningful exposure to both backend (PHP or Node.js) and frontend (React/TypeScript) development
• Strong proficiency in our core stack: PHP/Laravel and/or Node.js/NestJS on the backend, React with TypeScript on the frontend
• Hands-on experience with AWS cloud infrastructure, relational databases, and API design (REST or GraphQL)
• Demonstrated comfort with AI-assisted development workflows—you already use AI tools regularly and can articulate how they change your process
• Strong fundamentals in testing: you know when to write a unit test, an integration test, or lean on AI-generated test suites
• Excellent async written communication—you document decisions, write clear PRs, and can drive alignment without meetings
• Ownership mindset: you do not wait for someone else to write the migration, fix the flaky test, or update the runbook

• You will not hand off work to a separate QA team—you own quality, aided by AI-powered testing and code review
• You will not wait on a backend engineer to build your API—you build the whole feature
• You will have real input into the tools and workflows the team adopts—this transformation is being built collaboratively
• You will work in a team of 2–3, not 5+, which means less coordination overhead and more building time