Software Engineer, Platform Engineering
21h ago⚠️ Before applying, please carefully review all the job requirements
- Location:
- United States
- Work Arrangement:
- Remote
- Experience:
- 4+ years
- Job Type:
- Full-time
- Company:
- Xperteez Technology
- Salary:
- Negotiable
- Posted:
- 2026-10-15
Job Overview
- This listing is for a Software Engineer, Platform Engineering position. The role is remote and is classified as full-time. The requirements point towards JavaScript, TypeScript, React.js, Node.js, PostgreSQL, Artificial Intelligence and AI tools. The listing is aimed at the following profile: 4+ years. For general context: React is a popular library for building interactive user interfaces. Node.js lets developers run JavaScript on the server. Interested candidates can review the full details below and apply using the link provided on this page.
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.
- ★ 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.
- ★ 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.
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
- ★ PostgreSQL: joins, indexes, transactions and constraints
- ★ REST APIs: HTTP methods and status codes, authentication basics such as tokens, validation and error responses
- ★ 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
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. Applicants with working knowledge of JavaScript, TypeScript, React.js, Node.js, PostgreSQL, Artificial Intelligence and AI tools may feel well prepared for what the listing describes. 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. If you have used AI tools or built small projects with language models, briefly describe what you built and how you checked the results. Keep your CV to the point and tailor the summary to this role rather than sending a generic version. 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: 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 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: How do joins and indexes affect query performance in PostgreSQL?
- Q: How would you handle authentication and input validation for a REST API you are building?
- 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 do you stay organised and communicate clearly when working remotely?
Ideal Candidates Fill the Application Form: Apply Here