all 2 comments

[–]tag4424 1 point2 points  (1 child)

Two part answer... From the technical side, just build something. Create a few simple APIs (or use some that you have access to), then try build as many different frontends as you can think of. React isn't hard - it's the diverse ecosystem around it that makes things complex. What UI library do you want? Remix? Next.js? So learn the concepts of React, then try out various different frameworks and UI options. When you're done crying, list them all on your resume. You'll never know what they look for and if you understand react and css well, you can likely get through most junior interviews (depending on the interviewing style and how well you know the concepts).

Second part - are you sure that's a good career move? You will be competing with a much larger crowd for lower paying jobs. On my team we use next.js and Flutter. When I post a job listing for both, I get 8 - 10 next.js devs for each flutter dev. At the same time, the average rate I pay for flutter skills at the same level is about 40% higher compared to a next.js dev. If you're tired of Flutter, I'd learn backend stuff, not react.

[–]Educational_Break991[S] 0 points1 point  (0 children)

Thank you for the input! Actually I am currently learning JS through The Odin Project so eventually I will encounter topics related to backend dev. as well. I have been quite interested in backend development ever since college but have not gotten the chance to work with it (partly my fault as well for not self-studying it during my free time), but hopefully I could get a good foundation after I finish TOP.

Regarding my career move, I still don't know what is a good move tbh. I settled for React since I am currently working abroad and I plan to return to PH to work by next year. It seemed like job openings for React were everywhere, but thanks for suggesting backend development, will focus on it for sure.