Senior React Engineer (TypeScript) - 6 to 12 months - - Immediate Hire

This role is suitable for a Senior React Engineer with 7+ years of software development experience and strong recent hands-on expertise in React and TypeScript.

The candidate should be skilled in front-end architecture, reusable components, state management, REST API integration, automated testing, Git, Azure DevOps, CI/CD, accessibility, performance, security, and responsive design.

They should be familiar with owning production applications from technical design through deployment and stabilization, conducting code reviews, resolving technical debt, making architectural decisions, collaborating across Agile teams, and mentoring developers.

How would you structure a scalable React and TypeScript application for multiple teams?

I would organize the application by business domains, with clear boundaries between features, shared UI components, services, hooks, and state management. I would enforce TypeScript contracts, consistent dependency direction, and reusable patterns through documentation, linting, and code reviews.

How do you decide whether state belongs in React component state, context, or a dedicated state management solution?

I keep transient, local UI state inside components and use context for stable cross-cutting concerns such as themes or authentication. I use a dedicated state library when state is shared across many features, requires caching or synchronization, or has complex update and debugging requirements.

How would you integrate a React application with REST APIs and handle asynchronous operations?

I would encapsulate API calls in typed service modules or query hooks, including loading, error, cancellation, retry, and cache behavior. Responses should be validated where appropriate, and the UI should expose predictable states without coupling components directly to HTTP implementation details.

How would you secure authentication and authorization when integrating with Microsoft services?

I would use Microsoft Entra ID with standards-based OAuth 2.0 or OpenID Connect flows, relying on established libraries rather than handling tokens manually. Access tokens must be scoped appropriately, stored safely, refreshed securely, and supported by server-side authorization because client-side checks alone are not sufficient.

What is your approach to designing accessible React components?

I start with semantic HTML, keyboard navigation, visible focus states, correct labeling, and appropriate ARIA only where necessary. I validate components with automated tools such as axe and with manual keyboard and screen-reader testing against WCAG requirements.

How would you diagnose and improve the performance of a production React application?

I would measure first using browser performance tools, React Profiler, and application telemetry, then address issues such as unnecessary re-renders, large bundles, slow API calls, and inefficient lists. Typical improvements include memoization when justified, code splitting, virtualization, request caching, optimized assets, and reducing the critical rendering path.

How would you test a React and TypeScript application at unit, component, and end-to-end levels?

Unit tests cover isolated utilities and business logic, component tests verify user-visible behavior and interactions, and end-to-end tests validate critical workflows in a realistic environment. I would use tools such as Jest or Vitest, React Testing Library, and Playwright or Cypress, while avoiding excessive tests of implementation details.

What should a robust Azure DevOps CI/CD pipeline for a React application include?

The pipeline should install locked dependencies, run type checking, linting, unit and component tests, build the application, scan for security issues, and publish artifacts. Deployment stages should use environment-specific configuration, approval or quality gates, automated smoke tests, and rollback or recovery procedures.

How would you design a reusable component library for a product team?

I would define consistent APIs, composition patterns, accessibility requirements, visual tokens, and documented usage examples. Components should be independently tested, versioned, and published with a workflow that supports backward compatibility and visual regression testing.

How do you approach code reviews, technical debt, and architectural decisions as a senior engineer?

I focus reviews on correctness, maintainability, security, accessibility, performance, and alignment with agreed standards rather than personal style preferences. I document significant decisions and make technical debt visible, prioritizing it according to risk, user impact, delivery cost, and likely future change.

Octopus by RTG is hiring a Senior React Engineer to support an international technology platform through remote work from Egypt. You’ll design and deliver scalable, accessible React and TypeScript applications, build reusable components, integrate REST and Microsoft services, implement automated testing, support Azure DevOps CI/CD, and mentor developers. The stack includes React, TypeScript, REST APIs, Git, Azure DevOps, Microsoft Entra ID, and related Azure services; the role is fully telecommuting for 6–12 months with an immediate start. Salary is not disclosed, but this is a strong opportunity to own production architecture, influence engineering standards, and work with an international Agile team.