Full Stack Developer
1h ago⚠️ Before applying, please carefully review all the job requirements
- Location:
- United States
- Work Arrangement:
- Remote
- Experience:
- 8-10 years
- Job Type:
- Full-time
- Salary:
- $104,000-$156,000
- Posted:
- 2026-10-10
- Job ID:
- 664062 Openings Alpharetta, Chicago
- Role Location:
- Remote - USA
- Compensation Range:
- $ 104,000.00 to 156,000.00 per year
Job Overview
- A new opening is available for a Full Stack Developer. The role is remote and is classified as full-time. The salary mentioned in the listing is $104,000-$156,000. The requirements point towards JavaScript, TypeScript, React.js, Node.js, Express.js and Artificial Intelligence. The experience level listed is 8-10 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.
Key Responsibilities
- ★ Build modular, responsive, and highly interactive user interfaces using React JS, Redux/Context API, and modern CSS frameworks.
- ★ Design and scale robust backend services and microservices using either Python (FastAPI, Django, Flask) or Node.js (Express, NestJS).
- ★ Architect and secure RESTful or GraphQL APIs, ensuring strict protection against vulnerabilities like injection and broken object-level authorization.
- ★ Deploy and manage application components natively within AWS using containerized environments.
- ★ Own and manage deployment workflows by writing Infrastructure as Code (IaC) and building automated CI/CD validation gates.
- ★ Write optimized queries and design schemas for both relational databases (PostgreSQL, MySQL) and NoSQL stores (DynamoDB, MongoDB).
Required Skills and Qualifications
- ★ Experience & Qualifications
- ★ 8-10 years of professional full-stack software development experience in a production environment
- ★ Strong grasp of serverless architectures, event-driven systems, and microservices patterns
- ★ Experience writing comprehensive unit, integration, and end-to-end tests for both frontend and backend systems
- ★ Frontend
- ★ React JS
- ★ JavaScript (ES6+)
- ★ TypeScript
- ★ HTML5
- ★ CSS3
- ★ Webpack/Vite
- ★ Backend
- ★ Python (FastAPI/Django) OR Node.js (Express/NestJS)
- ★ AWS Cloud
- ★ EC2
- ★ S3
- ★ Lambda
- ★ ECS/EKS
- ★ API Gateway
- ★ CloudWatch
- ★ RDS
- ★ Security
- ★ OAuth 2.0
- ★ OIDC
- ★ JWT
- ★ IAM policies
- ★ CORS configuration
- ★ Encryption (HTTPS, KMS)
- ★ DevOps
- ★ Docker
- ★ Git
- ★ GitHub Actions/GitLab CI
- ★ Terraform or AWS CloudFormation
- ★ Databases
- ★ PostgreSQL or MySQL
- ★ DynamoDB or MongoDB
- ★ Security Practices React, REST, AWS, Python, Amazon ECS, AWS Secrets Manager, AWS Lambda, AWS IAM, Express.js, FastAPI, OAuth 2.0
What These Requirements Mean in Practice
- ★ JavaScript: Typically means writing and debugging everyday JavaScript, including asynchronous code, array and object handling, and modern ES6+ syntax.
- ★ TypeScript: Adds types to JavaScript so mistakes are caught earlier; day to day it means defining interfaces and typing function inputs and outputs.
- ★ 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.
- ★ Express.js: A minimal Node.js framework used to define routes and middleware for web servers and APIs.
- ★ MongoDB: Storing data as flexible documents inside collections; the work usually involves schema design, queries and indexes.
- ★ PostgreSQL: A relational database where data lives in related tables; the work usually involves writing SQL and designing schemas.
- ★ SQL databases: Working with tables, relationships and queries to store and retrieve structured data.
Skills to Brush Up Before Applying
- ★ JavaScript: promises and async/await, array methods such as map, filter and reduce, closures and scope
- ★ TypeScript: interfaces versus type aliases, generics basics, typing API responses
- ★ 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
- ★ Express.js: routing and middleware, error handling, request validation
- ★ MongoDB: CRUD queries, schema design choices, indexes and aggregation basics
- ★ PostgreSQL: joins, indexes, transactions and constraints
- ★ SQL databases: SELECT, JOIN and GROUP BY, primary and foreign keys, normalisation basics
Who May Be a Good Fit for This Role?
- This role may be suitable for candidates who match the skills and experience described in the requirements. Those who are comfortable with JavaScript, TypeScript, React.js, Node.js, Express.js and Artificial Intelligence and enjoy building practical projects may find the requirements a good match. A remote arrangement may suit people who work well independently and communicate clearly in writing. This is editorial guidance only, and the employer makes the final decision on suitability.
Application Tips
- Applicants may want to highlight relevant experience with JavaScript, TypeScript, React.js and Node.js in their CV. Because version control is mentioned, a GitHub profile with a few well-described repositories can make your skills easier to verify. If you have used AI tools or built small projects with language models, briefly describe what you built and how you checked the results. 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.
Prepare for Your Interview
- 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: What is the difference between var, let, and const, and how does hoisting affect your code?
- Q: What benefits does TypeScript give over plain JavaScript on a team project, and what trade-offs have you noticed?
- 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 organise routes and controllers in a growing Express application?
- Q: When would you embed documents in MongoDB versus referencing them, and why?
- Q: How do closures, promises, and async/await work in JavaScript, and when would you use each?
- Q: How do interfaces and type aliases differ, and when would you choose one over the other?
- Q: How do you stay organised and communicate clearly when working remotely?
Ideal Candidates Fill the Job Form: Apply Here
