That's sounds like a great interview that I'd probably pass. But I'm a terrible developer.
You're virtually guaranteed to not be terrible given this self-evaluation. You might not be some senior-level elite developer, but I'm not sure I've ever met someone who said this who was truly awful.
I feel it's hard to fake convincing answers to these kind of "getting things done in the real world" questions.
Like if i was to answer that honestly, it was fixing an obscure i18n bug for an underserved language group. I felt it was cool because it was such a small amount of work but made some people inordinately happy. In many ways i am much more proud of this 20 min bug fix than all the big technical projects i've done. But if you asked me any technical questions about it, the answer would almost entirely be - i used the architecture that already existed, because i was fixing a bug not rewriting the code base.
Fixing a bug isn't the same as building something, though.
The point is to see if the experience you claim matches what you have actually done.
I work for a finance company. The vast majority of the devs, including seniors, haven't released any software outside of work. Maybe 10% have. It seems this is true for other non-tech industries too.
Even on here, do you think more than 50% have released something they made by themself, that is more advanced than a simple Android app? Obviously there's a lot of talent here. I would be surprised if the number is higher than that.
If you’re been working 5-10 years or more and you’ve never built anything at all that you’re excited about, that’s a red flag.
Made me think the other questions are follow-ups to these.
Eh, when you work on large systems in a large and highly regulated company, it's not very exciting. There have been some interesting components to those systems, but in general they have been mundane business topics with tight guiderails and little freedom. I mean, the majority of people in the world don't get "excited" about work - it's just the means of survival.