Thanks for the reply and the valuable feedback!
>If you plan to spend some years in reading and implementing papers to become a researcher anyway.. You can probably go back to school and get a PhD, this will be way more efficient than randomly reading without guidance.
Well the core question is just that: if my goal is to become a researcher, should I just go for a PhD, or is there another way. And also the reason I resigned from my work, to first see how far I can improve my understanding on my own (and how much that can amount to finding a research opportunity).
>Furthermore, a researcher do not spend his days to implement state of the art algorithms, he tries to push science a little further in very small steps, implementing is just part of the process.
I'm aware that implementing SoTA is not necessarily research, but still often something done by PhD while PhD to understand/test/reproduce/get insight of a certain SoTA approach, to build/modify on it.
>Even when you have a PhD, pure research jobs are pretty rare
I'm also aware of this fact, as I met plenty of PhD people at my previous start up(mostly doing the implementation I mentioned above, in their respective field of expertise), although most of them wasn't that interested in research anymore.
I use research to cover both the process of discovering new and noble things, and finding a suitable SoTA for a specific engineering problem (usually what PhD going to industry end up doing, it seems) because as I see it, it is also valuable "research" in the field of robotics. (For context, my particular interest is in Reinforcement Learning application in Robotics) Engineering application of theory in industries seems like a good "feedback" to the academic community too =)
But I'm aware that my view of things is limited/naive, and that's why I'm asking for others experience. Maybe I should've been a bit more specific, though!