React Native Developer with NextJS experience needed to build out mobile app Offline

We seek an intermediate web developer for ongoing work as part of a small team working on a React Native application to develop a mobile application. The scope of this app is fairly small, but we will continue to add additional features after launch, so this contract could be extended indefinitely if it's a good fit.

We are especially interested in candidates who have experience working with Expo and/or Solito. Solito is a framework that will allow us to share some UI elements between ReactNative and NextJs.

We're looking to hire someone with the following skill sets:

— React Native with Expo (we use Context API for state management);

— NextJS;

— MongoDB;

— Firebase;

— TailwindCSS;

— Auth0;

— Experience with Git and GitHub;

— Strong written communication skills.

Nice to have:

— Experience with Storybook;

— Familiarity with i18n;

— CI/CD experience;

— An eye for design.

Candidates will also have the opportunity to work on our NextJS marketing site if interested.

About the project:

We are revamping an old mobile application that's heavily outdated. We've chosen to go the React route where we can use Solito to share some UI elements with NextJS. Both apps live in a monolith and are currently mostly set up and running. As a secondary project, we're moving our marketing site off of Hugo into NextJS. Additional things we want to set up are shared i18n, MongoDB integration, firebase analytics on the mobile app, and automated testing through CI/CD

How we run things:

Our team is 100% remote and keeps in contact primarily via Slack. We use GitHub Issues to assign and keep track of tasks. We like to set very clear goals in our issue tracker and managers are almost always online and available to answer questions and give guidance on current tasks.

We add code the our front-end and back-end repositories via a standard PR process where your submitted code is reviewed by other members of the team and you likewise review PRs from other team members. We also believe strongly in writing clean, well commented, code and use internal wikis to help with additional documentation.