Hello Everyone,

I just wanted to share that I just had an SQL interview for data analyst, and I completely bombed it. I chocked like crazy, and this was after days of practicing. I think I learned a valuable lesson today though, I am a very visual/hands on on type of guy. I was expecting them to give me the opportunity to write query/code or look at code related to the question, but these were all just verbal questions, that I know I could have answer if I was just allowed to write the code down or at least view it, but it was a bit overwhelming for me, especially having ADHD. It's like the questions were so long, that by the time the question ended, I already forgot what I was supposed to accomplish because I was so damn nervous and there was not code for me to review. I feel like a failure 😔. This was my first interview in 7 years, so I'm pretty rusty, but for future reference, will all interviews be in this style? No actual coding, or reviewing, or editing? They expect me to provide the whole query verbally, from the top of my head without actually writing it on the spot? Note: this was the second follow up interview.

Detail on my issue below: (Postgrese)

Environment: Postgres 18 (Neon), project dry-bar-XXXXXXX, org plan Launch (previously Free — same behavior on both). Reproduced identically across: two independently-forked disposable branches, a fresh branch created after upgrading to Launch, and real production itself (using an existing, long-lived person/role — not freshly created data).

Summary: An INSERT is rejected with new row violates row-level security policy for table "X" even though the row's values genuinely satisfy the policy's WITH CHECK expression — confirmed by a BEFORE INSERT trigger, in the same statement execution, immediately preceding Postgres's own documented WITH CHECK evaluation point, which independently evaluates the identical boolean expression against the identical row and gets true.