About Envnt:
Envnt builds Enspct, a field service management platform that powers large scale inspection operations. Our product includes workflow builder, form builder, and report builder tools used by enterprise field teams and the administrators who support them. We are at a turning point moving to the cloud, expanding globally, and aiming for Gartner recognition. The technical choices we make now will shape how we scale.
Role Overview:
You will work on Enspct's mobile app, the app inspectors use in the field to complete tasks, fill forms, and collaborate with their teams in real time.
Responsibilities:
- Forms renderer engine: The web-based form builder lets non-technical users design complex inspection forms. The mobile app includes the renderer that interprets those schemas and generates the UI. You will help extend this engine.
- Mobile experience: You will work on offline first workflows, real time collaboration features, task management, and gamification modules building a reliable tool for inspectors working in the field
- Day to day, you will build well designed, reusable components within our design system. You will write styles that are responsive and fluid, and TypeScript types that enforce contracts across the codebase. You will optimize performance across iOS and Android.
- You will join the Enspct engineering team working alongside backend, frontend, mobile, and QA engineers. We value clear thinking over heroics, and simple solutions over clever ones.
Requirements
- The Candidate must be graduated from Faculty of Engineering / Computer Science
- 3-5 years of professional experience in mobile app development, with at least 2+ years working with React Native
- Deep understanding of React Native internals: JS thread vs UI thread, bridging, performance implications
- Platform specific handling: you know the iOS and Android gotchas and how to handle them cleanly
- Performance optimization: debug janky scrolls, optimize FlatList rendering, reduce unnecessary re-renders
- TypeScript as contracts: you understand the difference between compiling time guarantees and runtime reality
- JavaScript primitives: closures, references, mutation, async behavior you can predict what code will do before running it
- Experience with design system development: building reusable, composable components with clear APIs
- Modular thinking: break complex problems into simple, well bounded modules You consider operability: logging, crash reporting, failure modes, and long-term maintenance when building mobile features
