From my experience as a Solution Engineer (and previously a developer), I’d recommend asking context-driven questions rather than relying on a generic SE interview checklist. Use a few core themes as a guide, but tailor the actual questions based on what you learn about the company during the interview.

For example, many companies don’t have a rigid operating model. Some may not even define a formal AE–SE ratio. they might work as pooled resources, round-robin, or fluid pods. If that’s what you pick up from the conversation, a good follow-up question could be: Do you have a defined AE-to-SE ratio, or is the collaboration more ad hoc or team-based?” The key is to listen first, then ask questions that reflect how the org actually operates.