Frontend Engineer at Persist Ventures

About the role

We are looking for a passionate Frontend Engineer with a strong eye for design and exceptional attention to detail. You will build modern, responsive, and highly polished user interfaces that deliver outstanding user experiences.

The ideal candidate enjoys transforming product ideas and Figma designs into beautiful, performant, and accessible web applications.

What you'll do

Develop responsive, accessible, and visually appealing web applications.
Convert Figma designs into pixel-perfect, production-ready interfaces.
Build reusable UI components and contribute to scalable design systems.
Ensure consistency in typography, spacing, color, animations, and overall user experience.
Optimize applications for speed, responsiveness, and cross-browser compatibility.
Work closely with designers to improve usability and user interactions.
Implement smooth animations and transitions that enhance user engagement.
Maintain high standards for UI quality, accessibility, and frontend architecture.
Identify and resolve frontend performance bottlenecks.
Participate in code reviews and continuously improve frontend development practices.

Nice to have

Experience building and maintaining design systems.
Strong understanding of UI/UX principles and accessibility (WCAG) standards.
Familiarity with animation libraries such as Framer Motion.
Experience optimizing frontend performance using Lighthouse or Core Web Vitals.
Knowledge of testing frameworks such as Jest or React Testing Library.
Experience working closely with designers in Figma.
Personal portfolio or GitHub showcasing polished frontend projects.

Hiring process

Apply, complete the assignment, then hear back from the team.

Apply → Assignment → Offer

Assignment

Front-end engineer

Intermediate

Build a working "Repo Explorer" web app. Given a GitHub username or organization, it fetches and displays their public

repositories with search, sorting, and filtering. No backend or auth needed — the focus is on clean front-end engineering

and intentional, non-generic UI.

What to build

The user types a GitHub username or org and sees their public repos — name, description, stars, primary language, and last updated. They can sort and filter the results and page through them. It's a small, self-contained problem, but it covers the daily reality of front-end work: API integration, state management, edge-case handling, responsive design, and design judgment.

Expectations

The app should feel polished and considered, not like a default AI template. Handle loading, empty, and error states distinctly — invalid username, rate limit, and network failure should each read differently. Search should be debounced, the layout responsive and keyboard-accessible. We care as much about how you direct your tools toward a deliberate result as about whether it works — a functional app that still looks generic tells us less than a thoughtful one. Be ready to walk through and defend your decisions.

Skills

ReactTypeScriptNext.jsREST APIsUI DevelopmentUX DesignResponsive DesignState ManagementComponent Libraries

Resources

Apply to unlock resources

6/6 attempts15 days after applying

You have 6 attempts in 15 days. Ship a first version early so you have time to work on reviewer feedback with your remaining attempts. After the last attempt, there are no more revisions.

How we evaluate

UI/UX Quality: How intentional, polished, and coherent the interface feels — not a generic, default-styled AI template.
Design Direction: How well the candidate pushes tools past their defaults and recognizes and fixes generic "slop" output.
Component & Architecture: How sensibly logic is decomposed, and whether any component library used was customized rather than dropped in raw.
Edge-Case Handling: How distinctly loading, empty, and error states (invalid user, rate limit, network failure) are handled.
State Management: How cleanly search, sort, filter, and pagination state is structured.
Accessibility & Responsiveness: How well the app works via keyboard, screen reader, and across screen sizes.
Code Quality & Communication: How readable the code is and how clearly decisions and trade-offs are explained in the README.