Fullstack JavaScript Developer - Latin America - Remote

Level: Senior Full-Stack JavaScript Developer with 7+ years of software development experience and at least 5 years working with React and GraphQL.

Required skills: Strong JavaScript, TypeScript, HTML, CSS, Node.js, React, GraphQL, REST APIs, SQL/NoSQL databases, automated testing, CI/CD, and application architecture skills.

Suitable tasks: Designing client- and server-side systems, enhancing existing codebases, integrating third-party services, building authentication and error-handling frameworks, developing deployment pipelines, and delivering well-tested features independently in remote, time-zone-aligned teams.

How would you structure a React and TypeScript application to keep components maintainable as it grows?

I would organize the application by feature or domain, separating presentation, business logic, data access, and shared utilities. Strong typing, focused components, predictable state management, and clear dependency boundaries help reduce coupling and improve maintainability.

How would you design a GraphQL schema and resolve common performance issues such as the N+1 problem?

I would model the schema around domain concepts with explicit types, inputs, pagination, and authorization rules. DataLoader or an equivalent batching and caching strategy can consolidate related database requests and prevent N+1 queries.

How would you implement authentication and authorization across a React frontend and Node.js backend?

I would use short-lived access tokens with securely managed refresh tokens, preferably stored in HTTP-only cookies when appropriate. Authorization must be enforced on the server through middleware or GraphQL resolvers, while the frontend should only control the user experience rather than act as the security boundary.

What approach would you take to integrating a third-party API into a Node.js application?

I would isolate the integration behind a service or adapter layer, validate external responses, configure timeouts, and handle retries with exponential backoff where safe. Secrets should be managed through environment or secret-management systems, and the integration should include logging, monitoring, and contract-focused tests.

How would you design error handling for a full-stack JavaScript application?

I would define consistent error categories and response formats on the backend, avoiding leakage of sensitive implementation details. The frontend would map expected errors to useful user messages, while unexpected failures would be logged with correlation identifiers for troubleshooting.

How would you optimize a React application that has slow rendering or large amounts of data?

I would first measure the issue using browser profiling and React DevTools rather than optimizing prematurely. Typical improvements include memoizing expensive calculations, reducing unnecessary state updates, code splitting, virtualization for large lists, and moving data fetching closer to the components that need it.

How would you design a RESTful service alongside a GraphQL API?

I would use resource-oriented REST endpoints with appropriate HTTP methods, status codes, validation, pagination, and idempotency where required. GraphQL can provide flexible client queries while REST may remain useful for webhooks, file transfers, public integrations, or simple resource operations.

How would you choose between SQL and NoSQL databases for a new feature?

I would choose SQL when relationships, transactions, constraints, and complex querying are central to the domain. NoSQL is useful for flexible document structures, high-scale access patterns, or data that naturally maps to aggregate documents, but the decision should be driven by access patterns and consistency requirements.

What testing strategy would you use for a React, Node.js, and GraphQL application?

I would combine unit tests for isolated business logic, component tests for user-facing behavior, and integration tests covering GraphQL resolvers, services, and database boundaries. A smaller set of end-to-end tests should validate critical workflows, with mocks used selectively to avoid hiding integration problems.

How would you build a reliable frontend CI/CD pipeline?

The pipeline should install dependencies deterministically, run formatting and lint checks, execute unit and integration tests, perform a production build, and optionally run security and type checks. Deployments should use environment-specific configuration, artifact promotion, automated rollback, and post-deployment health checks.

Azumo, a San Francisco–based software development firm specializing in AI, is seeking a Senior Fullstack JavaScript Developer to build intelligent SaaS and data applications. You’ll enhance TypeScript and JavaScript codebases, architect client- and server-side solutions, integrate APIs, and develop front-end deployment and CI pipelines using React, Node.js, GraphQL, JavaScript, TypeScript, REST, SQL, and NoSQL. This is a 100% remote, full-time role for candidates in Latin America, working EST/PST hours, with USD remuneration (salary amount not disclosed), paid time off, U.S. holidays, profit sharing, maternity coverage, and career mentoring. Apply for the chance to collaborate with talented engineers, work on modern AI solutions, and grow with an innovative global technology company.