Before pushing any branch to production, I treat AI as a strict, localized peer reviewer. I pass it my diffs specifically prompting it to look for security vulnerabilities, unhandled exceptions, or inefficiencies in database queries (like N+1 problems in Prisma or PostgreSQL)—effectively acting as a pre-CI quality gate.
Interview questions [1]
Question 1
Before pushing any branch to production, I treat AI as a strict, localized peer reviewer. I pass it my diffs specifically prompting it to look for security vulnerabilities, unhandled exceptions, or inefficiencies in database queries (like N+1 problems in Prisma or PostgreSQL)—effectively acting as a pre-CI quality gate.
I applied online. The process took 1 week. I interviewed at Twice (San Francisco, CA) in Mar 2014
Interview
Submitted application on line along with questionair. Waited 2 weeks to hear back, then proceeded to interview. After a brief interview I was invited to do 2 trial shifts. After passing I was highered.
I applied through an employee referral. The process took 1 week. I interviewed at Twice (San Francisco, CA) in Jan 2015
Interview
Extremely easy, interview was during the afternoon at the warehouse. Asked basic questions. If the interview goes well, you get chosen for a trial shift. This is when they make sure you're a good fit.