Product Software Engineering (QVAC) (100% remote)
6h ago⚠️ Before applying, please carefully review all the job requirements
- Location:
- Dubai (United Arab Emirates)
- Work Arrangement:
- Remote
- Experience:
- Required
- Job Type:
- Full Time
- Salary:
- Negotiable
- Posted:
- 2026-10-10
- Strong Product Sense:
- you can tell a good feature from a busy one.
- Bonus:
- Experience with local or on-device inference, LLM evals, cross-platform mobile and desktop apps, or open source.
Job Overview
- A new opening is available for a Product Engineering Lead (QVAC) (100% remote). The work arrangement is listed as remote. The salary mentioned in the listing is rs,. The requirements point towards JavaScript, React.js, REST APIs, Artificial Intelligence and LLMs. 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.
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.
- ★ React.js: Building user interfaces from reusable components and managing the data that changes on screen.
- ★ REST APIs: Designing and consuming HTTP endpoints so a front end, mobile app or another service can exchange data.
- ★ Artificial Intelligence: A general understanding of how AI systems learn from data, where they are useful, and where they can be unreliable.
- ★ LLMs: Understanding how large language models generate text from prompts, and why their output still needs to be checked.
Skills to Brush Up Before Applying
- ★ JavaScript: promises and async/await, array methods such as map, filter and reduce, closures and scope
- ★ React.js: components, props and state, useState and useEffect, lists, forms and conditional rendering
- ★ REST APIs: HTTP methods and status codes, authentication basics such as tokens, validation and error responses
- ★ Artificial Intelligence: supervised versus unsupervised learning, common real-world use cases, limitations and bias
- ★ LLMs: prompting basics, context limits and hallucinations, using an LLM API
Who May Be a Good Fit for This Role?
- This role may be suitable for candidates who bring substantial experience and are comfortable owning technical decisions and supporting other team members. Those who are comfortable with JavaScript, React.js, REST APIs, Artificial Intelligence and LLMs 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, React.js, REST APIs and Artificial Intelligence 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. Review the application page carefully and submit every document it asks for. 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: How do state and props differ in React, and how do you decide where state should live?
- Q: How would you handle authentication and input validation for a REST API you are building?
- Q: How would you explain the difference between traditional programming and machine learning to a non-technical person?
- Q: How would you design a prompt and validate the output when using an LLM inside an application?
- Q: How do closures, promises, and async/await work in JavaScript, and when would you use each?
- Q: How does useEffect work with its dependency array, and what mistakes do people commonly make with it?
- Q: What makes an API RESTful, and how do you choose HTTP methods and status codes for different operations?
- Q: How do you stay organised and communicate clearly when working remotely?
- Q: Tell us about a technical decision you owned and how you handled the trade-offs.
- Q: How do you review code and support less experienced teammates?
Apply through the Form Fill: Apply Here
