Frontend Engineer

Solvd Inc.

Get hot jobs first on Telegram

New positions appear faster in our channel

Location: Argentina, Brazil, Colombia, Poland, Ukraine, Georgia
Job Type: full-time
Salary: Unknown
Posted: January 20, 2026

Job Description

Solvd Inc. is a rapidly growing AI-native consulting and technology services firm delivering enterprise transformation across cloud, data, software engineering, and artificial intelligence. We work with industry-leading organizations to design, build, and operationalize technology solutions that drive measurable business outcomes.

Following the acquisition of Tooploox, a premier AI and product development company, Solvd now offers true end-to-end delivery—from strategic advisory and solution design to custom AI development and enterprise-scale implementation. Our capability centers combine deep technical expertise, proven delivery methodologies, and sector-specific knowledge to address complex business challenges quickly and effectively.

Solvd is looking for a Mid-Senior Frontend Engineer to join a cross-functional team working within a large-scale enterprise initiative. The team is responsible for designing and delivering components of the Entity / Party Management domain, a foundational capability used across multiple business systems.

You will work in a 5–7 person Solvd team, embedded in the client’s broader engineering organization, collaborating closely with backend engineers, QA, UX/design partners, and client platform teams.

This role is ideal for an engineer who enjoys working in modern React ecosystems, navigating micro-frontend architectures, and incrementally modernizing legacy frontend components.

What you will do

Design and implement frontend components for the Entity / Party Management domain within a micro-frontend architecture.
Build user interfaces using React and Next.js in a monorepo environment.
Contribute to shared UI patterns and frontend architecture using modern tooling.
Integrate frontend applications with backend services via REST APIs.
Work with JavaScript and TypeScript, ensuring high code quality and maintainability.
Collaborate with designers and stakeholders using Figma, Visio, and Miro.
Maintain and incrementally modernize legacy frontend components (AngularJS, jQuery) when required.
Write and maintain frontend tests using Playwright and Vitest.
Participate in code reviews, design discussions, and technical planning sessions.
Document decisions and flows in Confluence and related tooling.

What we’re looking for

4+ years of experience in frontend or full-stack software development.
Strong hands-on experience with React and modern JavaScript / TypeScript.
Experience working in monorepo setups and/or micro-frontend architectures.
Solid understanding of frontend performance, state management, and component design.
Experience integrating frontend applications with RESTful APIs.
Comfortable working in complex enterprise environments with both modern and legacy systems.
Experience collaborating in cross-functional, client-facing teams.
Strong communication skills and a pragmatic, delivery-focused mindset.

Nice to have

Experience with Next.js in production environments.
Familiarity with TanStack libraries (Query, Router, etc.).
Exposure to design systems or shared UI libraries.
Experience modernizing or migrating legacy frontend codebases.
Some backend exposure (C#, .NET, or API design) for smoother collaboration.

Tech stack (you will work with)

Frontend
- JavaScript / TypeScript
- React, Next.js
- Micro-frontend architecture
- Monorepo (Nx, pnpm)
- TanStack, shadcn/ui, Vite, Tailwind CSS
Legacy exposure
- AngularJS
- jQuery
Testing
- Playwright
- Vitest
Engineering & Delivery
- GitHub
- Jira, Confluence
- Rapid prototyping tools (V0)
- Diagrams and documentation: Miro, Mermaid, Visio
Infrastructure
- CI/CD, deployment, API gateways, and edge services are managed by the client’s platform and infrastructure teams.

When you join Solvd, you'll…

Shape real-world AI-driven projects across key industries, working with clients from startup innovation to enterprise transformation.
Be part of a global team with equal opportunities for collaboration across continents and cultures.
Thrive in an inclusive environment that prioritizes continuous learning, innovation, and ethical AI standards.

Ready to make an impact?

If you're excited to build things that matter, champion responsible AI, and grow with some of the industry’s sharpest minds. Apply today and let’s innovate together.

🎯 Who is this job for?

This role is best suited for a mid-to-senior Frontend Engineer with strong hands-on experience in React and TypeScript who is comfortable working in complex enterprise environments. It will appeal to engineers experienced with micro-frontend architectures, monorepos, and incremental modernization of legacy systems, who enjoy collaborating closely with backend, QA, and design teams. The position fits someone pragmatic and delivery-focused, confident integrating REST APIs, writing frontend tests, and contributing to shared UI patterns, while being adaptable enough to balance modern React/Next.js development with occasional legacy AngularJS or jQuery work in large-scale, client-facing projects.

💬 Potential Interview Questions

How do you structure a React + Next.js application inside a monorepo (e.g. Nx) for a large enterprise project?
I group code by domains/features, keep shared UI and utilities in separate libraries, and rely on Nx to enforce module boundaries, incremental builds, and caching so teams can work independently while reusing components safely.
How do you approach state management and server data fetching when using TanStack Query in a micro-frontend environment?
I treat TanStack Query as the source of truth for server state per micro-frontend, share query keys and client configuration via a common library when needed, and keep local UI state in component or lightweight stores to avoid cross-micro-frontend coupling.
What is your strategy for integrating React frontends with RESTful APIs in a complex enterprise system?
I centralize API clients in a dedicated layer, define strong TypeScript types for request/response contracts, handle errors and authentication concerns there, and expose simple hooks (e.g. useEntities()) so components stay focused on rendering and UX.
How do you ensure good performance in a React/Next.js UI that deals with large datasets in the Entity / Party Management domain?
I use pagination, server-side filtering, and virtualization for large lists, memoize expensive computations, split bundles when appropriate, and profile rendering to eliminate unnecessary re-renders or heavy logic in render paths.
Describe how you would gradually modernize a legacy AngularJS/jQuery screen into a React micro-frontend.
I’d start by isolating the legacy module behind a stable route or container, introduce a small React micro-frontend alongside it, progressively move functionality into React while bridging data where needed, and keep behavior parity with automated tests before fully decommissioning the old code.
How do you design reusable frontend components for an enterprise design system using React, Tailwind, and shadcn/ui?
I wrap shadcn primitives with domain-specific abstractions, use Tailwind utility classes via a consistent set of design tokens, and ensure each component has clear props, accessibility baked in, and Storybook-style documentation for discoverability.
What is your experience testing frontend applications with Playwright and Vitest?
I use Vitest for fast unit and component tests, and Playwright for end-to-end flows like entity creation or search, focusing on critical paths, realistic data, and stable selectors so tests are reliable and provide good coverage of both logic and UX.
How do you handle routing and navigation when building micro-frontends with Next.js and TanStack Router or similar tooling?
I define routes at the micro-frontend boundary, use a shared navigation contract where needed, and ensure each micro-frontend owns its internal routing while integrating cleanly with the host shell for global navigation and layout.
Can you describe a situation where you had to collaborate with backend engineers to improve a REST API for better frontend integration?
I’ve worked with backend teams to adjust payload structures, add pagination or filtering parameters, and standardize error formats, often proposing changes based on concrete UI needs and performance concerns, then validating them together via shared API specs.
How do you stay productive and maintain high code quality when working in a large, client-facing enterprise environment with both modern and legacy stacks?
I rely on clear coding standards, TypeScript, automated tests, and code reviews, communicate frequently with the team and stakeholders, and balance refactoring with delivery by prioritizing changes that reduce complexity and improve maintainability over the long term.

📋 Job Summary

This position is a strong match for a mid-to-senior React/TypeScript frontend engineer in LATAM or Eastern Europe who enjoys working in modern React/Next.js monorepos and micro-frontend architectures, is comfortable integrating with REST APIs and occasionally touching legacy AngularJS/jQuery, and wants to be embedded in a cross-functional, enterprise environment where you’ll design and build Entity/Party Management UIs, contribute to shared UI patterns (TanStack, Tailwind, shadcn/ui), write robust tests (Playwright, Vitest), and help gradually modernize a large-scale platform as part of a globally distributed AI-native consultancy.