I had the same question when I applied. The recruiter shared a really good video with me that helped me decide which route to go. I'm sure they could share it with you as you are not the first person to run into this conundrum.

The key takeaway of the video for me was this: \
\
*If you build systems using common cloud solution products (AWS), you should consider product; however, if you build those components, then you should consider infra.*

As others have pointed out, infra is going to be building the systems that the production engineers use. Since my background was building API's that clients consume, using tools like queues, pub/sys systems, caches, etc., I went the product route. I would struggle to build those components from the ground up. \
\
I had a really frank conversation with my recruiter about my background and interest. They were really good about helping me find the right path and setting me up for success. I would encourage you to do the same. \
\
Best of luck! 

Senior Software Engineer [E5] at Meta

Blaine Anderson

I think that what you suggesting is very well worded. Furthermore, I think it is important that you tell them this sooner than later. If you don't say anything, they won't know that it is having an impact on you. I really like how you are approaching this from a "me" perspective, rather than a "them" perspective. I think that other people could use this as a template for how to request feedback differently. 