Full Stack Engineer

7h ago

⚠️ Before applying, please carefully review all the job requirements

Job Overview

A new opening is available for a Full Stack Engineer. According to the listing, this is a remote full-time position. The salary mentioned in the listing is Rs 0. The listing places its emphasis on TypeScript, React.js, PostgreSQL, REST APIs, Git and GitHub and Artificial Intelligence. For general context: React is a popular library for building interactive user interfaces. REST APIs let the front end and back end of an application exchange data in a structured way. 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.
★ PostgreSQL: A relational database where data lives in related tables; the work usually involves writing SQL and designing schemas.
★ 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.
★ Python: Writing readable scripts and backend or data code using Python's standard library and common packages.
★ 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.

★ TypeScript: interfaces versus type aliases, generics basics, typing API responses
★ React.js: components, props and state, useState and useEffect, lists, forms and conditional rendering
★ PostgreSQL: joins, indexes, transactions and constraints
★ 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
★ Python: core data structures, functions and modules, virtual environments and pip
★ 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 match the skills and experience described in the requirements. Those who are comfortable with TypeScript, React.js, PostgreSQL, 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, PostgreSQL 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: What is a transaction, and why do ACID properties matter?
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: How do lists, tuples, sets, and dictionaries differ in Python, and when would you use each?
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: Apply Here