That's far from a perfect statement, but it's not the worst that you see. As an interviewer, the difference is between junior and senior developers. It's an indication that they they understand the currency and some metrics for an area/business, but more than that, it sets out their position.

That position is something I should be challenging in the interview with questions to probe deeper:

* Can you tell more about the GraphQL API? Was this new or replacing an API? Tell me about the constraints and goals you were working towards?

* What issues did you have getting to that level of performance? What trade-offs did you make when you hit issues?

* What are the challenges with running your API in production?

* Can the API you implemented scale higher? If so, what would need to be changed with it as you scale to 400 and 1200 queries per second?

If this person has done the work this should be a good discussion and you can start to bring in some of your business or technical problems. It will be very evident whether someone has just invented metrics, or the statement is describing the work of others.

I feel it's important for technical interviewers to have some experience with STAR/behavioral interviewing. This assists with screening/selecting resumes and exploring these areas in interviews.

Even if it doesn't answer every question it gives you at least some insight into the scale and scope of what they did. Sure numbers can always be fudged but it's better than no numbers.

How would you write that line?

Thanks for the comments. Perhaps I can be helpful by walking backwards from something you do perceive as valuable? For hiring conversations, what's a great one look like to you?