Frontend Developer Job at Disher
4h ago⚠️ Before applying, please carefully review all the job requirements
- Location:
- United States, United Kingdom, Europe
- Work Arrangement:
- Remote
- Job Type:
- Full Time
- Company:
- Disher LTD
- Salary:
- $25000 – $40000 USD
- Posted:
- 2026-10-18
Job Overview
- A new opening is available for a Frontend Developer Job at Disher. Work is remote, and the arrangement is listed as full time. The salary mentioned in the listing is $25000 – $40000 USD. Skills mentioned in the listing include TypeScript, React.js, Next.js, REST APIs, Git and GitHub and Artificial Intelligence. The experience level listed is 4-6 years. 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
- ★ 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.
- ★ Next.js: A React framework that adds routing, server rendering and API routes, so work often covers both pages and backend endpoints in one project.
- ★ 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.
- ★ .NET / C#: Building applications and web APIs with C# on the .NET platform.
- ★ HTML and CSS: Structuring web pages and styling them so they work well on different screen sizes.
- ★ Tailwind CSS: Styling interfaces by applying small utility classes directly in the markup.
Skills to Brush Up Before Applying
- ★ TypeScript: interfaces versus type aliases, generics basics, typing API responses
- ★ React.js: components, props and state, useState and useEffect, lists, forms and conditional rendering
- ★ Next.js: App Router basics, server versus client components, data fetching and caching
- ★ 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
- ★ .NET / C#: C# fundamentals, ASP.NET Core Web API, Entity Framework basics
- ★ HTML and CSS: semantic HTML, Flexbox and Grid, responsive design
- ★ Tailwind CSS: utility classes and responsive prefixes, customising the theme, reusable component patterns
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 TypeScript, React.js, Next.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.
Application Tips
- Applicants may want to highlight relevant experience with TypeScript, React.js, Next.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.
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 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 does routing work in the Next.js App Router?
- 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 would you build and secure a Web API in .NET?
- 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