Fullstack Lead
1. Role Overview
WalkingTree is hiring a Full Stack Lead to own the design and delivery of enterprise web platforms built on Java microservices and Angular microfrontends.
You will lead a team of full-stack engineers, act as the technical voice to US-based stakeholders and customer teams, and stay hands-on in code, reviews and architecture.
The platforms you will work on are data-heavy, workflow-driven products used by operations and planning teams: real-time dashboards, rule-based decision engines, integrations with ERP and telematics systems, and event-driven backends.
Domain knowledge is picked up on the job; engineering depth and customer-facing maturity are what we hire for.
2. Job Details
| Attribute | Detail |
|---|---|
| Role | Full Stack Lead (Java and Angular) |
| Reports To | Delivery Head / Engineering Head |
| Team Size | 5 to 10 engineers (frontend, backend, QA) |
| Experience | 9 to 14 years total, with at least 3 years leading a team |
| Location | Hyderabad (hybrid); overlap with US Eastern / Central hours required |
| Employment | Full time |
3. Key Responsibilities
A. Technical Leadership
-
Own the architecture of Java (Spring Boot) microservices and Angular microfrontends, including service boundaries, API contracts, shell and remote composition, and shared design systems.
-
Lead design reviews, code reviews and technical decision-making; set coding standards, testing strategy and definition of done.
-
Stay hands-on: build critical components, prototype solutions, and unblock the team on hard problems.
-
Drive non-functional quality: performance, security, observability, resilience and scalability.
B. Delivery and Team Management
-
Plan sprints, break down epics, estimate with the team, and commit to delivery dates you can keep.
-
Mentor engineers, run hiring interviews, and grow senior developers into future leads.
-
Own CI/CD, release readiness and production support practices with the DevOps team.
-
Track risks, dependencies and technical debt, and raise them early.
C. Customer and USA Stakeholder Engagement
-
Work directly with US-based counterparts (product owners, architects, program managers) in regular working-hour overlaps, including daily or weekly calls, demos and sprint reviews.
-
Work with customer team members to gather requirements, clarify integration points, walk through designs, and resolve issues together.
-
Present architecture, progress and trade-offs clearly to both technical and business audiences.
-
Communicate status, blockers and change requests in writing with clear, concise updates that a US stakeholder can act on without a follow-up call.
4. Mandatory Requirements
Candidates who do not meet the first three points below will not be shortlisted.
1. Direct USA counterpart exposure: At least 3 years of working daily with US-based clients, product owners or architects, including regular calls in US time-zone overlap, demos, and written status communication. Candidates must be able to describe specific engagements.
2. Direct customer team collaboration: Proven experience working side by side with customer engineering, QA and business team members on requirements, integrations, UAT and production issues, not only through a project manager.
3. Microservices and microfrontends as daily work: Hands-on delivery of Spring Boot microservices and Angular microfrontends in production, treated as the normal way of building, not a recent experiment.
4. Overall experience: 9 to 14 years of total software experience, with at least 5 years in Java and 4 years in Angular (version 12 or later).
5. Team leadership: At least 3 years leading a team of 5 or more engineers, with ownership of design, delivery and mentoring.
6. Communication: Strong spoken and written English, suitable for customer-facing and executive communication.
5. Technical Skills
| Area | Expectations |
|---|---|
| Backend | Java 17+, Spring Boot, Spring Cloud, REST and OpenAPI, JPA/Hibernate, async processing, Kafka or RabbitMQ |
| Microservices | Domain-driven design, API gateway, service discovery, resilience patterns (circuit breaker, retry, idempotency), saga and event-driven patterns |
| Frontend | Angular 14+, TypeScript, RxJS, NgRx or similar state management, reactive forms, Angular Material or equivalent |
| Microfrontends | Module Federation or Native Federation, shell and remote apps, shared libraries and design system, independent versioning and deployment |
| Data | PostgreSQL or similar relational database, query tuning, Redis or other caching, familiarity with time-series or analytical data |
| Integration | ERP, telematics or third-party REST and event integrations, contract-first design, adapter patterns |
| DevOps | Docker, Kubernetes, CI/CD (Jenkins, GitLab or Azure DevOps), Git branching strategy, environment promotion |
| Quality | JUnit and Mockito, Jasmine/Jest, Cypress or Playwright, contract testing, SonarQube, static analysis |
| Security and Ops | OAuth2 / OIDC, JWT, role-based access, logging, metrics and tracing (ELK, Prometheus, Grafana, OpenTelemetry) |
| Cloud | AWS, Azure or GCP fundamentals for deploying and operating containerised services |
6. Good to Have
-
Experience with optimisation, forecasting or rule-engine-backed products, or with map and real-time dashboard UIs.
-
Exposure to open-source, monorepo-based platforms and multi-team release management.
-
Familiarity with Python-based services that your Java services consume.
-
Cloud or Kubernetes certification; experience with GitOps.
-
Prior experience as a technical interface on enterprise accounts in logistics, manufacturing or supply chain.
7. Behavioural Competencies
-
Clear communicator who can explain a design trade-off to a US product owner and a customer developer in the same week.
-
Ownership mindset: raises risks early, follows through, and does not wait to be chased.
-
Calm under production pressure, with a blameless, root-cause-first approach.
-
Coaches rather than dictates; builds a team that can ship without the lead in every review.
8. What Success Looks Like in the First Year
Within 90 days:
-
Understands the platform, the customer landscape and the delivery rhythm.
-
Is trusted as the main technical contact by the US counterparts.
Within 6 months:
– Microservice and microfrontend standards, CI/CD and review practices are documented and followed by the whole team.
Within 12 months:
-
Releases are predictable.
-
Customer escalations fall.
-
At least one engineer has grown into a tech-lead role under you.