It's not impossible that a Java programmer who used the built-in containers exclusively wouldn't give an answer immediately.
I disagree... granted, I've written plenty of my own linked list structures in Pascal, C, C++ and before all that, the first real compiler based (vs interpreted) programming SDK implementation in an AGOL 68-like (which also influenced C++) language called "Action!" on an 8-bit Motorola 6502 Atari 800 (Spoiler: 2^8=256, but I would have failed the test because I'd have just written: 11111111!).
Nevertheless, I would say that I think any Java developer, may even offer a solution quicker than a developer who's used to creating their own linked list structures.
I could easily imagine a scenario where someone used to creating their own list structure will say something akin to:
"well, if I had a standard, singly-linked list structure, I'd modify the list structure to use a doubly linked list. The extra overhead in creating the list would be more than made up for by the flexibility in reading the list in reverse."
or even:
"to minimize the lines of code, I will use recursion to read each element of the list, from the beginning, and as I rewind the stack, print each element in reverse."
Both are "correct" but represent different ways that actually will take more time to develop than using the standard java.lang and java.util class libraries.