Full-Stack Engineer

5h ago

Company not listed

RemoteFull-time$140K – $220K

Job Overview

A new opening is available for a Full-Stack Engineer. Work is remote, and the arrangement is listed as full-time. The salary mentioned in the listing is $140. Skills mentioned in the listing include TypeScript, React.js, Node.js, REST APIs, Git and GitHub and Artificial Intelligence. The experience level listed is 5+ 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.

★ 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.
★ REST APIs: Designing and consuming HTTP endpoints so a front end, mobile app or another service can exchange data.
★ Git and GitHub: Tracking changes, working on branches, opening pull requests and resolving conflicts so a team can share code safely.
★ AWS: Using cloud platform services for hosting, storage and databases instead of managing physical servers.
★ Artificial Intelligence: A general understanding of how AI systems learn from data, where they are useful, and where they can be unreliable.

★ 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
★ REST APIs: HTTP methods and status codes, authentication basics such as tokens, validation and error responses
★ Git and GitHub: branching and merging, pull requests and code review, resolving merge conflicts
★ AWS: core compute and storage services, permissions and access control, basic deployment
★ Artificial Intelligence: supervised versus unsupervised learning, common real-world use cases, limitations and bias

This role may be suitable for candidates who match the skills and experience described in the requirements. Those who are comfortable with TypeScript, React.js, Node.js, REST APIs, Git and GitHub 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.

Applicants may want to highlight relevant experience with TypeScript, React.js, Node.js and REST APIs 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.

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 do interfaces and type aliases differ, and when would you choose one over the other?
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 makes an API RESTful, and how do you choose HTTP methods and status codes for different operations?
Q: How do you resolve a merge conflict in a shared repository?
Q: Which cloud services have you used for hosting or storage, and how did you choose them?
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 do you stay organised and communicate clearly when working remotely?

Interested Candidates Fill the Application Form: