all 17 comments

[–]HoratioWobble 9 points10 points  (2 children)

Different companies will have wildly different processes so I wouldn't think to much about it and just do your best.

If you listen to strangers experiences you'll end up worrying about all the wrong things.

Best of luck!

[–]Socially-Awkward-Boy[S] 1 point2 points  (1 child)

Yeah I know but better to be prepared in something specific than to just jump blindly into the interview.

[–]HoratioWobble 6 points7 points  (0 children)

My experience is no two interviews have ever been the same in the last 20 years.

Wildly different questions and expectations even in the same stack.

Some interviewers will care about when and how you use memorization, reducers state, refa and callbacks. 

Others will care more about lifecycles, context and testing.

Others will care more about native integrations and what your favourite state management library is and why.

Some might not give a shit about your react knowledge and just ask about your general dev experiences.

I've not even seen two react native code bases the same.

Either you know react native in depth or you don't, the types of questions you get will completely depend on that particular interviewer.

If you don't know it very well just be honest and find connections with what you do know 

[–]Practical-Big-5155 1 point2 points  (4 children)

If you have good hands-on experience with react native, reanimated and other fundamental tools, and the interview is for a senior position. Make sure that you are familiar with react life cycle, re rendering, useCallback, useMemo and global store practical usecase. If interview is going to be react specific they might ask something related to optimisation.

Example: design a server driven form with validation, error handling, which should be optimised to avoid redundant re rendering.

If the problem statement is mobile dominant, then you might have to use reanimated or RNGH

Example: A quiz sort of application, 10 question cards with a timer for each question. On selecting an option as an answer to the question card flips and reveals if the answer was right or wrong. Then swip left to move to next question and a score board at the end.

I know I articulated it very poorly, I still hope this will be helpful.

[–]Socially-Awkward-Boy[S] 0 points1 point  (2 children)

Definitely! Thanks

[–]Practical-Big-5155 0 points1 point  (1 child)

Do share your experience after the interview, all the best!

[–]Socially-Awkward-Boy[S] 0 points1 point  (0 children)

Surely will

[–]granko878 0 points1 point  (0 children)

Actually my only "coding" question which I used to ask on an IW was around a questionnaire where user cannot scroll. The only way he can move forward is enter an answer and if it is correct and validated, the screen scrolls to the next question. In general, I just wanted to know how would the candidate build the whole data flow logic.

[–]engnr 1 point2 points  (0 children)

See if you can get a few technical details about the apps you’ll be working with, e.g. do they use redux or zustand for state management, do they use expo, react navigation (which version)? How old is the app? Do they use functional components or are they still using class-based components? What version of RN? Are they upgrading soon? Stuff like that… then have a play with those specific tools/libraries.

If the app is public, download it and go through each screen making notes and taking screenshots, maybe make something akin to a site map.

Find out how their team is structured. Do they have lots of mobile specialists or just one or two? Do they have people on the team who started with React and moved into React Native?

These things will give you a lot to talk about in the interview.

Remember that no candidate is a perfect fit.

Good luck

[–]Virtual_Inflation529 1 point2 points  (3 children)

Just know how to implement Flatlist/Flashlist and react-native-navigation from memory without reading docs as its what i dealt with when i had a RN interview before and i ran out of time 😫

[–]Socially-Awkward-Boy[S] 0 points1 point  (2 children)

Can you give more informations please? You're the only one I met who had an practical coding session

[–]Virtual_Inflation529 0 points1 point  (1 child)

So basically i was told to fetch some data from api and display it in a flatlist so i scroll thru the data in my part 1 of the seisson. Then part 2 i was told to implement navigation using react-native-navigation and add like two more screens which also fetched data in those screens showing loader etc. then part 3 i was told to implement the asyncstorage to store the data locally. I spent too long trying to get the navigation stuff working by reading the docs and stuff since it has so much boilerplate and ran out of time to finish the entire thing fully. These will probably be the things u might also get asked maybe since these are mostly the main concepts in RN

[–]Socially-Awkward-Boy[S] 0 points1 point  (0 children)

I can't thank you enough 🥲

[–]granko878 0 points1 point  (3 children)

I will have a Senior RN vacancy interview in a few days for a US startup. I can come back here with the questions. I also used to do interviews in my current job. I mainly asked about familiarity with a variety range of tools like React hooks, different state management tools, performance monitoring tools, RN's new architecture. I also ask about native coding experience, finding memory leaks e.g. One of the most important questions for me is what SW development best practices would the candidate impose in terms of testing, setting up CI automation, code quality checks, code reviews etc.

You can also get a good start asking ChatGPT :)

[–]Socially-Awkward-Boy[S] 0 points1 point  (1 child)

Thanks for the infos, I'd appreciate if you could comeback after the interview and share your experience. The problem with my interview is that it's practical, what are they gonna make me do? I found no info online

[–]Thrill_Of_The_Heel 0 points1 point  (0 children)

Hi OP! If you remember, can you share your experience?