The work
Our interfaces support everyday work: creating a quote, finding an order, updating a claim or checking a customer record. A good screen helps someone finish the task accurately and with less effort. You will build and improve these workflows in custom ERP systems, internal tools and customer portals.
What you will do
- Turn a business process into clear navigation, forms, tables and reusable components.
- Build with Angular / TypeScript or Blazor / C#, depending on the project, and integrate with our .NET APIs.
- Handle validation, loading, empty states and failures so users know what happened and what to do next.
- Make keyboard interaction, focus, readable labels and responsive layouts part of everyday delivery.
- Work with back-end engineers on permissions, pagination and data contracts; test critical journeys and use feedback to improve them.
What you will bring
- Experience shipping web applications with Angular or Blazor. Strength in one and willingness to learn the other is enough.
- A solid grounding in HTML, CSS and browser behaviour, plus TypeScript or C# for your main framework.
- Examples of forms or data-heavy interfaces you have made easier to use.
- The ability to work with APIs, debug a problem across the browser and network, and collaborate through Git and code review.
Useful, but not essential
Component libraries, accessibility testing, end-to-end tests, front-end performance or experience with business software. You do not need to be a visual designer, but you should care about spacing, interaction and consistency.
A possible first 90 days
Learn a user journey and the existing UI conventions, deliver an improvement to a form or table, then own a complete workflow from API integration through testing and release. Explain what became clearer or easier for the person using it.
How we work
Full time, 100% remote. Design discussions, user demos and collaboration with clients happen online; there is no requirement to work from an office or client premises. We discuss time-zone overlap during selection and use written feedback and focused calls to keep delivery moving.
Your work will be used repeatedly in real operations, with opportunities to improve it after launch. Send a portfolio, repository or a written case study explaining a problem you solved. A public code portfolio is helpful, not required.