This year I was waitlisted for EAG London, and then promptly rejected. I didn’t assign it much importance as the time because I assumed it was caused by capacity limits and I had applied relatively late.
How does having a waitlist make sense if every applicant is considered by a uniform bar independent of capacity?
The rejection email did say I could update my application, but I didn’t understand it at the time and only noticed it after reading this thread. I think maybe the communication around this could be improved, although I’m only one data point. The main point is that it only appears after a bunch of other text and can be easily ignored when you already know that the main message is “you got rejected”.
Hi Guy — thanks for the feedback. I’m not entirely sure what happened re your London application, as I wasn’t on the team then. However we didn’t really use the waitlist for SF and I don’t expect us to use it for the foreseeable future. We’ve since updated a lot of our email templates, so I’m hoping the issue you mentioned is at least partially resolved.
Hi Eli, Thanks for your detailed replies here!
This year I was waitlisted for EAG London, and then promptly rejected. I didn’t assign it much importance as the time because I assumed it was caused by capacity limits and I had applied relatively late.
How does having a waitlist make sense if every applicant is considered by a uniform bar independent of capacity?
The rejection email did say I could update my application, but I didn’t understand it at the time and only noticed it after reading this thread. I think maybe the communication around this could be improved, although I’m only one data point. The main point is that it only appears after a bunch of other text and can be easily ignored when you already know that the main message is “you got rejected”.
Hi Guy — thanks for the feedback. I’m not entirely sure what happened re your London application, as I wasn’t on the team then. However we didn’t really use the waitlist for SF and I don’t expect us to use it for the foreseeable future. We’ve since updated a lot of our email templates, so I’m hoping the issue you mentioned is at least partially resolved.
Thanks, glad to hear that.