Lead Full Stack Engineer – Node.js, Java & AWS

Candidate Checklist :-

• Strong hands-on Node.js developer (5+ years preferred)
• Experience as a Technical Lead or Lead Full Stack Engineer
• Strong Java backend experience
• Hands-on with AWS, Lambda, and DynamoDB
• Experience with Angular or React
• Built scalable REST APIs/Microservices
• Excellent verbal communication (must clear client interview)
• Comfortable taking a technical TORC assessment

NODEJS, Java, Angular (or React) , AWS, Lambda, dynamoDB

There will be a tech lead TORC test. Must have excellent communication skills

We are seeking a hands-on Tech Lead to act as the technical authority for one or more strategic initiatives. The Tech Lead will define architecture, service contracts, and technical roadmaps while providing strong engineering leadership across backend, cloud, and frontend concerns.
The short-term emphasis of this role is technical discovery, solution design, and planning, laying the foundation for successful downstream delivery and team scaling.

Key Responsibilities

Technical Leadership & Architecture

Serve as the lead developer and technical authority for the initiative(s)
Design system architectures and define technical roadmaps
Decompose ambiguous problem spaces into clear, actionable technical plans
Define, document, and negotiate service and API contracts with partner teams
Ensure solutions meet enterprise standards for security, resiliency, and maintainability
Identify technical dependencies, risks, sequencing, and trade-offs

Hands-On Engineering

Remain hands-on in development, particularly during implementation phases
Review code and enforce engineering best practices and quality standards
Support complex technical problem-solving across the stack

Collaboration & Planning

Work closely with product, partner teams, and stakeholders to shape scope and priorities
Help determine which initiative to start first based on technical readiness and risk
Inform decisions on future team composition and required skillsets

Team & Delivery Model

Work within a single cross-functional team supporting multiple initiatives (initially not in parallel)
Support a flexible staffing model with engineers rotating in or out based on phase and needs
Contribute to APIs that are primarily internal-facing, with some UI components potentially external-facing
Influence when and how additional engineers are added as scope and priorities become clearer