React Native Developer

We are seeking a Senior React Native Developer to lead the modernization of our enterprise mobile applications. This is not a standard feature-factory role. You will be tackling a complex legacy ecosystem (e.g., warehouse, spare parts, and workshop management software) and translating it into a modern, highly decoupled mobile architecture.

Using Domain-Driven Design (DDD) principles, you will untangle legacy business logic, build Anti-Corruption Layers, and strict-type our codebase. We need an engineer who doesn't just use React Native, but deeply understands how it works under the hood and can mold it to fit complex business needs.

Key Responsibilities

• User-Centric Domain Modeling: Deep-dive into real-world workflows to understand how end-users actually operate. You will reconstruct the business domain from the user's perspective, capturing rules and processes that may not be explicitly written in the legacy code.

• Independent Architecture: Model the domain independently from the legacy backend. You will use the existing legacy structures to understand the business, but you will not replicate its technical debt, naming conventions, or shortcuts in the new code.

• Strategic Refactoring: Analyze the existing codebase to identify recurring domain concepts. Extract these into atomic, single-responsibility components, hooks, and modules with minimal interfaces.

• System Decoupling: Strictly separate UI rendering from business logic.

• Anti-Corruption Layers: Design and implement robust Anti-Corruption Layers (ACL) to protect the mobile application from the legacy system and other external integrations.

• Code Quality & Typing: Strengthen the existing codebase with uncompromising, strict TypeScript typing.

• Framework Management: Lead the upgrading of frameworks and dependencies (React Native, Expo, native libraries) and confidently resolve complex compatibility issues.

• Custom Solutions: Intervene, extend, or patch the React Native framework when standard, out-of-the-box solutions are insufficient for our requirements.

• Technical Documentation: Write clear, concise documentation detailing your technical decisions, architecture choices, and the rationale behind them.