Remundo

more about project

Remundo is a B2B2C SaaS platform transforming global recruitment and workforce management through automated Employer of Record (EOR) services. The platform enables companies to hire international talent in under 30 minutes while ensuring full legal compliance and minimal complexity.

Remundo connects companies, workers, and service partners within a centralized digital ecosystem, streamlining cross border hiring, contracts, documentation, and operational workflows. It features three dedicated interfaces: Client, for seamless hiring; Worker, for a transparent employment experience and Admin, for centralized control and compliance management.

Attention: The work presented here represents my personal redesigns inspired by projects I contributed to at Remundo. Due to company policy and confidentiality agreements, I cannot share the original design files.

1) Problem research & analysis

  • Gather context through stakeholder alignment and analysis of the existing product and constraints.

  • Translate business goals into measurable outcomes (e.g., reduced drop off, higher conversion, fewer support tickets).

  • Identify user pain points via feedback, support insights, analytics, or existing research.

  • Define a clear problem statement and success criteria before moving into solutions.

2) User story exploration

  • Review and break down user stories into concrete use cases, scenarios, and edge cases.

  • Map user flows (happy paths + failure states) and clarify behavior at each step.

  • Align requirements with real user behavior and team priorities to avoid building the wrong thing.

3) Sketching & brainstorming

  • Generate multiple early solution directions (sketches / low-fidelity wireframes) to avoid locking into the first idea.

  • Quickly evaluate options for clarity, simplicity, feasibility, and implementation cost.

  • Involve the team early to catch issues before investing time in high-fidelity work.

4) Component creation

  • Design reusable UI components that stay consistent across the product.

  • Align components with the design system (typography, spacing, states, interaction patterns).

  • Define component states: default, hover/pressed, disabled, loading, error, success.

  • Ensure components are implementation-friendly, not just visually polished.

5) UI design (high-fidelity)

  • Produce high-fidelity screens with strong visual hierarchy and usability-first decisions.

  • Refine layout, microcopy, and interactions so users understand what to do without friction.

  • Maintain consistency across screens (grid, spacing, typography, iconography).

  • Consider accessibility basics (contrast, tap targets, readability, focus/keyboard behavior where relevant).

6) Prototyping

  • Build interactive prototypes to validate flow, behavior, and key interactions.

  • Use prototypes to align stakeholders and speed up decision-making.

  • Cover real-life states: empty, error, loading, slow network, interrupted actions.

7) Team presentation

  • Present solutions clearly: problem → goals → key decisions → trade-offs → expected impact.

  • Run internal reviews and incorporate feedback without losing scope or clarity.

  • Defend design decisions with reasoning (user needs, metrics, constraints), not taste.

8) Developer handoff or bug documentation

  • Prepare handoff specs: layout, spacing, component states, interactions, responsive rules.

  • Add annotations and acceptance criteria for areas prone to misinterpretation.

  • Support implementation through QA, log UX/UI bugs, and iterate based on findings.