Associate Full Stack Software Engineer

4h ago

Company not listed

RemoteFull-timeNegotiable

Job Overview

A new opening is available for an Associate Full Stack Software Engineer. The position is listed as full-time. The salary mentioned in the listing is rs,. The listing places its emphasis on React.js, Node.js, SQL databases, REST APIs, Python, Artificial Intelligence and LLMs. The experience level listed is 1+ years. For general context: React is a popular library for building interactive user interfaces. Node.js lets developers run JavaScript on the server. Read the details below carefully and use the application link on this page if the role matches your profile.

★ React.js: Building user interfaces from reusable components and managing the data that changes on screen.
★ Node.js: Running JavaScript on the server to build APIs, handle requests and talk to databases.
★ SQL databases: Working with tables, relationships and queries to store and retrieve structured data.
★ REST APIs: Designing and consuming HTTP endpoints so a front end, mobile app or another service can exchange data.
★ Python: Writing readable scripts and backend or data code using Python's standard library and common packages.
★ Java: Object-oriented development on the JVM; Spring Boot is commonly used to build web services.
★ Docker: Packaging an application and its dependencies into containers so it runs the same way everywhere.
★ AWS: Using cloud platform services for hosting, storage and databases instead of managing physical servers.

★ React.js: components, props and state, useState and useEffect, lists, forms and conditional rendering
★ Node.js: npm and modules, building a simple REST API, asynchronous file and network operations
★ SQL databases: SELECT, JOIN and GROUP BY, primary and foreign keys, normalisation basics
★ REST APIs: HTTP methods and status codes, authentication basics such as tokens, validation and error responses
★ Python: core data structures, functions and modules, virtual environments and pip
★ Java: object-oriented principles, collections and streams, Spring Boot basics
★ Docker: Dockerfile basics, images versus containers, docker compose
★ AWS: core compute and storage services, permissions and access control, basic deployment

This role may be suitable for candidates who have some early professional or project experience and want to keep building their skills. Those who are comfortable with React.js, Node.js, SQL databases, REST APIs, Python, Artificial Intelligence and LLMs and enjoy building practical projects may find the requirements a good match. This is editorial guidance only, and the employer makes the final decision on suitability.

★ All Telecommuters will be required to adhere to UnitedHealth Group's Telecommuter Policy.

Applicants may want to highlight relevant experience with React.js, Node.js, SQL databases and REST APIs in their CV. If you have used AI tools or built small projects with language models, briefly describe what you built and how you checked the results. If you have limited work history, academic projects, personal builds, and open-source contributions can demonstrate practical ability. A short, role-specific summary at the top of your CV usually reads better than a generic profile. These are general tips, not requirements stated by the employer.

These suggested questions can help you prepare for an interview by focusing on the skills, responsibilities, and technical areas relevant to this role. They are for preparation only and are not confirmed employer questions.
Q: How does useEffect work with its dependency array, and what mistakes do people commonly make with it?
Q: How does the Node.js event loop handle asynchronous operations?
Q: How would you design tables and relationships for a simple job-board application?
Q: What makes an API RESTful, and how do you choose HTTP methods and status codes for different operations?
Q: How do decorators and generators work in Python?
Q: How does Spring Boot simplify building a REST service, and what does dependency injection do for you?
Q: How do state and props differ in React, and how do you decide where state should live?
Q: How would you structure a Node.js project so that routes, business logic, and data access stay separate?
Q: What are you hoping to learn in this role, and how have you prepared so far?

Select privacy Agreement and apply as Guest: