Skip to content
Dálcio Garcia

Career and recruitment platform · SaaS · Careers · Frontend platform

Mirantes Platform

A career and recruitment platform connecting professionals with opportunities.

Role
Frontend Developer & Frontend Team Lead
Organisation
Mirantes Technologies
Period · status
Nov 2022 – Feb 2024 · Completed
  • Next.js
  • TypeScript
  • React
  • React Query
  • Tailwind CSS
Mirantes platform — public landing page
Public landing page of mirantes.io, captured 19 Sep 2026

Overview

mirantes.io is the main product of Mirantes Technologies: professionals create a profile, find job opportunities, apply and follow their applications; companies publish vacancies, recruit and manage employees. It runs as a web application with companion mobile apps.

Problem

The platform serves users in Angola and other African countries on mixed devices and low-bandwidth connections. The frontend had to render fast, keep data fresh without heavy re-fetching and give job seekers and recruiters reliable forms and flows.

Role

I built and maintained the Next.js/TypeScript web application and led the frontend team's technical work: code review, technical guidance and consistency across the codebase.

I owned platform performance on the frontend — rendering strategy, caching and production debugging. Backend work in this period is not claimed.

Architecture

  • Next.js with TypeScript, using SSR/SSG rendering strategies per page type and lazy loading to keep first render fast.
  • Data fetching and caching with React Query so lists, applications and profile data stay consistent across the app.
  • Forms and validation flows for profiles, applications and recruiter workflows, styled with Tailwind CSS.

Technical decisions

Rendering strategy per page
Public and SEO-relevant pages use server rendering or static generation; authenticated, data-heavy views are client-rendered with cached queries, which balanced speed and freshness on slow connections.
Caching as the performance lever
Rather than optimising individual components, the biggest wins came from caching data retrieval and avoiding redundant requests across navigation.
Consistency through review
As team lead the priority was a coherent codebase: shared patterns for forms, data access and layout enforced through code review.

Stack

  • Next.js
  • TypeScript
  • React
  • React Query
  • Tailwind CSS

Engineering challenges

  • Keeping the application fast on low-bandwidth connections while the product grew in scope.
  • Coordinating a frontend team on one codebase while shipping continuously.

Outcome

The platform is live at mirantes.io and remains the core product of Mirantes Technologies; this engagement ended in February 2024 when my role moved towards technical coordination and, later, Mirantes for Creators.

What I learned

  • Performance on a real user base is mostly data-flow discipline, not micro-optimisation.
  • Leading a frontend team is largely about making the right pattern the easy pattern.