Engineer IV - Full Stack Developer

About the role

This role shapes the user experience of a global planning platform. You join a focused workstream building the front end and back end of customer-facing features.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

A cross-functional team delivers reliable software by iterating with product to solve user problems.

Customer needs drive daily work so that solutions address real problems and sustainable user value.

The team builds and releases award-winning planning tools that professionals use to improve decisions globally.

Continuous integration and deployment practices are refined to streamline how the team releases software.

An agile process supports high autonomy and accountability while the team follows a structured development rhythm.

Full-stack work spans front-end and back-end layers as specialists apply experience and expand skills to complete work.

Requirements

The posting states a bachelor's degree requirement. A degree is required as part of the qualification criteria.

Exceptional problem-solving skills craft well-architected, scalable, and maintainable systems.

A robust toolkit of design patterns is applied using SOLID principles to choose the right solution for each problem.

The candidate delivers complex solutions using JavaScript (ES2015+), HTML, and CSS.

Expertise with TypeScript and React is essential for building the user interface.

Back-end services are written using a JVM language such as Java or Kotlin, often with Spring Boot.

Deployment tools and technologies such as Docker, Kubernetes, and Terraform are used to release software.

Collaboration and leadership communicate ideas clearly, influence thinking, and make difficult decisions while preserving relationships.

Nice to have

Hands-on experience with the listed front-end technologies: React, TypeScript, CSS, Redux, Jest, Vite, Enzyme, Cypress.

Hands-on experience with the listed back-end and infrastructure technologies: Java, Kotlin, Spring Framework, MySQL, Docker, Kubernetes, Jenkins, Git, Helm.

Practical notes

This role is based in Gurugram and operates within global compliance and security expectations.

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Full-stack work connects user interface behavior with server-side logic and infrastructure.

Modern JavaScript and TypeScript power interactive interfaces while Java and Kotlin handle backend services.

Container orchestration with Kubernetes and infrastructure as code with Terraform are central to deployment workflows.

Testing practices such as unit, integration, and end-to-end tests help ensure quality before release.

Agile methods support fast feedback, clear ownership, and continuous improvement in a high‑autonomy environment.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.