I’m a frontend developer who spends most of every day writing React components, tweaking SpringBoot APIs, and hunting for the fastest library that fits the problem.
At the same time, I’m drawn to the bigger picture – shaping product direction, working with data pipelines, or diving deeper into server‑side architecture.
I am a frontend developer (React, Django) as of 10 Oct 2026 and am exploring a career switch to product management, data engineering, or a more backend‑heavy role. I love building snappy UI, seeing tests pass, and thriving under tight deadlines with loud music and a collaborative team.
Decision: Test my readiness before committing to a career switch to mitigate risk of skill regression and slow value delivery.
Decision why: Choosing a side‑project that spans both front‑ and back‑end creates a low‑risk simulation of the new role’s responsibilities.
- Skill audit – List daily tasks (JS/TS, React, Redux, Django, REST, CI/CD) and annotate missing competencies for the target role (product vision, data pipelines, stakeholder management).
I’m seeking community input: real‑world stories of big shifts, concrete first‑30‑day plan advice, and resources (books, courses, podcasts).
As of 10 Oct 2026. I’m a frontend developer who spends most of every day writing React components, tweaking Django APIs, and hunting for the fastest library that fits the problem.
Lately I’ve been feeling the pull to switch tracks – maybe toward product management, data engineering, or a more backend‑heavy role.
- Mini‑project – Build a small product requiring a frontend UI and backend data processing to mirror responsibilities of the desired role.
- Feedback loops – Identify peers who have transitioned, request specific “what surprised you” feedback, and document responses.