I’d run a self assessment about which testers are involved and how your company works. For me, implementation details have been vital to my success as a tester. I say that because my various seniorities of Quality Engineer, have required I have domain knowledge about the tool and discuss/explain that knowledge to others.
Imagine your company manages an inventory app for grocery stores. One feature you’ve worked on is the ability to scan a UPC and get all of the locations in the store. Sales is working on a whale grocery chain and is doing discovery. You, knowing the implementation details can surface something like “well, end caps aren’t implemented the same way as shelves; if we want to do this for Client X, we have to address that or do a big lift”. You’ve spotted a risk well ahead of the actual code development just by having that information to share.
As always, theres a risk reward. Ideally, the code/tests are going to give you those details without you having to hold them in your head, but your company might not have a human readable test suite making it easy for Product owners to get those answers themselves. Further, you knowing more about implementations might pigeonhole your thinking and cause you to not test other areas because you know too much about this one area to remember the small other places the code touches.
So, to reiterate, do a self assessment. How easy is it for business teams in your org to get answers to those risks? How much are you allowed to learn about the implementation details? How senior are you relative to who you talk to? Are there bugs/risks you might’ve flagged had you known a detail, or had you been able to share something you knew ahead of time? Lastly, do you just want to know? Its ok to be curious. Your growth is also of value.