img

Would you feel any different getting rejected by a senior person vs a junior person?

So, recently, I interviewed for an Ed-tech firm. The questions asked were standard & i answered them pretty well. The instant feedback I received was good as well. But i got a rejection mail 2 days later. The guy who took the interview was a 2024 grad, an APM with only 3 months of full-time experience & 7 months of internship experience at the same company. Now, I am used to rejections without feedback but this one felt a bit different. Somehow, I felt weird about being judged by someone who has much less experience than me. I thought to myself "was this a fair assessment?", "would a senior interviewer analyze my skillsets differently?" Just wondering, has anyone ever felt the same? If so, have you dealt with it any differently other than just moving on? Would love to know your perspectives

img

Tigercow

Startup

8 days ago

Sign in to a Grapevine account for the full experience.

Discover More

Curated from across

img

Software Engineers on

by NotYourDhinchakPooja

Razorpay

Razorpay Frontend - More like a copy paste ninja job

Off late, the frontend engineering at Razorpay has become more of a data entry job. The design system (god knows how many years it will take to be completely ready) is restricting both the devs and the designers a LOT. Designers are literally fed up with being dictated to design things only in a particular way (limiting even animations, font-size, choice of italics v/s bold). There was even a long 2 month discussion to get font size for a component to support higher value, if you honestly want to know. The so called core team has been developing blade since God knows when. Agree that they've done a great work with tokens and other stuff, but it seems that by the time it's ready, it'll already be outdated design wise (suxs). So, any other devs, all they have to do is follows. 1. Open Figma 2. See if the component in Figma is supported by Blade. 3. If yes, then see if our designer has by mistake used any font-size, color, margin or spacing not supported by Blade. 4. If yes, start a thread between everyone and give them a month to come to a resolution (Blade team always retaliates like it's a personal attack) 5. Eventually end up using your own component to save time and move fast. 6. Explain to your manager's manager's manager why you can't use Blade. (they've funded it for 2 years and no dev likes it, so they push it from top) If your company has some interesting approach to this, please add in the comments.