Urgent.News

What's breaking now, across thousands of outlets.

Tech

First Interview Exprience

25 May 2026, I appeared in API round of one of the best companies of college placement. I had always been nervous about my vibecoding skills, so i had practised past year's project, but what was asked this year was obviously different, with an additional layer of deployment this time. I had created local projects but never deployed any before, and i instantly panicked seeing the deadline off only…

On 25th May 2026, the author appeared for an API round at one of the best companies for college placement. Although they had been practicing past year's projects, they were caught off guard by the additional layer of deployment this year. The author had created local projects but never deployed any before, which caused them to panic under the tight deadline.

They were already demotivated, knowing it wasn't their cup of tea, and felt their preparation wasn't enough. The round ended, and the author managed to submit just before the deadline. Around evening, the author realized a significant blunder during deployment, leading to panic and self-doubt. The results were announced, but the author's name wasn't on the list, and they accepted their lack of preparation.

The next day, they were called for the Assessment round, which marked their first DSA and SQL assessment. The author had only recently started DSA practice, and the questions were quite tricky. Despite their nervousness, they managed to pass most test cases of the questions. When results were announced, they were shortlisted for an interview, but they panicked and made numerous mistakes during the interview.

The author spent the next three months reflecting on their performance and vowed to restart their journey, focusing on building consistency, sharing insights, and learning from their mistakes.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Critical Outage Alerts: Choose an SMS API by Polling Delivery Status

Short answer: choose the SMS API whose delivery evidence can be normalized into your own small state machine, retained under a documented policy, and tested independently of its dashboard.

  • Choose SMS API with integrable small state machine for critical alerts.
  • Prioritize normalized evidence of message delivery, not provider dashboard.
  • Document reportjobid, alertid, attempt number, provider message ID, and timestamps.

More from Tuesday 25 August →