You can see it on the copilot's side here by the trim wheel.
Still wondering whether MCAS and other automatation systems have a representation of that position indication. I can't currently come up with an idea of how to implement that in an easy, yet error-resilient way. Usually you would initially drive into a reference position, then integrate the motor's actions to arive at an absolute value, but integration would potentially add up subsequent errors, and obviously you can't re-do the referencing step while in the air.
https://reports.aviation-safety.net/2018/20181029-0_B38M_PK-...
These two are very different but very important pieces of information.
AIUI, runaway trim has always been a possibility and the trim wheel design helps to surface that it’s happening.
Thinking about that I wonder whether there was even a measurement signal that the computers could rely on to determine the current state of the trim angle in absolute terms.
Given how the MCAS did incremental changes without stopping before reaching the mechanical limits, I do imagine that there might have been no hardware feedback to assess the current trim state, thereby making it impossible hardware-wise to limit MCAS to a sensible (and safe) range of angles.
[edit] Looking at the lion air crash report [1] p.14 ff it seems like also the black box only recorded trim changes, not absolute trim state.
[1] https://reports.aviation-safety.net/2018/20181029-0_B38M_PK-...