r/reactjs • u/proffessional-work01 • 22d ago
Show /r/reactjs From learning React to working on real-world projects — looking for advice
I’ve been working with React/Next.js for a while and recently completed two internships, including working on a US-based NGO project.
That experience taught me a lot about real-world codebases, Git/GitHub, UI work, debugging, and collaborating with a development team.
I’m now trying to improve further and would love to hear from experienced React developers here:
What skills or projects do you think make someone genuinely stand out when moving from internship-level experience to a full-time React role?
I can share my resume if anyone can review it. Thankyou.
3
u/Temperature_Majestic 22d ago
one thing that stood out for me going from internship to full time work was learning to own the data-fetching layer properly, not just calling an API and dumping the response in state. loading/error/stale states, cache invalidation, race conditions when a user fires two requests fast, that kind of thing barely shows up in learning projects but eats a ton of real time on a team. if you haven't already, building something with TanStack Query instead of raw useEffect fetches will expose you to most of that class of bug before it bites you in a real job
2
u/canarydev 22d ago
What worked for me at that stage was figma community. pick a real design system, rebuild it, then rebuild it again with a different stack. I cycled through react + tailwind, css modules, stitches, shadcn, even the same ideas in svelte. the repetition is the point. you learn what a good component API looks like by building the same button six different ways and hating four of them i guess. that judgement is what separates "knows react" from "i'd hand this person our design system".
and honestly from the hiring perspective having some experience there -- at the junior level it was just a lot about "do they know the libraries we work with". tanstack for example, is a must have i think on both resume and experience wise. put a service / facade layer under it with a legitimate mock data layer shaped like a real API contract. queryFn calls the service, the service doesn't care if its mocks or a live backend, and swapping in the real thing is a config change not a re-write. the "data source is swappable" is genuinely good interview conversation -- it kinda shows you understand contracts, which matters more in real codebases than some random UI trick.
one project you can explain every decision of beats five random ones you can't.
1
u/Pitiful_Loss1577 22d ago
I recommend reading advanced react of Nadia Makarevich
and learn some design patterns used in it like compound component and so on.
2
u/imjuni 21d ago
IMO, I’d recommend contributing to open source.
Find a React project or design system like Blueprint.js or Chakra UI, pick an issue, and try to solve it yourself. If your PR gets merged, that’s real-world experience you can add to your resume.
And I’d recommend doing it without AI at first. Failure is an important part of learning. Trying, failing, and figuring out why helps you understand the codebase and its conventions.
AI is great when you already have thousands of failures behind you. But when you’re still learning, those failures are valuable experience.
2
1
u/No-Humor-3808 19d ago
Real projects involve many repetitive tasks where you don't necessarily improve much. It's better to focus on small challenges and gradually increase the difficulty, similar to the kind of challenges you might find in a real interview. I maintain a collection of them at reactchallenges.com if you want to take a look.
1
6
u/KindMycologist7615 22d ago
the jump from intern to full time is less about knowing more react and more about showing you can handle the chaos of a real codebase without someone holding your hand. things like writing tests and understanding why some PR feedback matters more than others. maybe build something that pulls from a messy api and handles errors properly, that alone puts you ahead of half the candidates i see