Reflection On Interviews (last 9 months)

Since late December 2025, I participated in over 20 interviews. First, I tried maintaining a database of all success & failures but I gave up after a while. I only added entry to my Notion database when I went through at least one round successfully. I must have applied at over 100 places and heard back from 20 of them, gave interviews at 15 to 17 places, crossed half-way mark at 6 of them, and had offer from 3 of them. I was shooting for 5 to 10 YoE roles with larger scope if possible.

More importantly, I was looking for positions that were either fully remote or required at most one or two day in office with as little traveling as possible. This removed most of the usual suspect I’d have applied. I was pretty liberal in my applications. It is the best strategy when you have no other strategy.

It seems to me that the single most important factor in my success was whether someone read my resume carefully and liked something on it. At one place, they went through my GitHub and they liked what I saw. During interview, you can almost tell if someone has read your resume or just skimmed though it. When they read it, they jump quickly into the details of a project/work they liked. Since you are talking about things that you’ve done well in the past, you can easily set the tone of the interview. More importantly, you start your interview with a lot of headwinds in your favor.

Other important factor was a presence of a “friendly face” in the panel, especially if the interview is online (most of them were). You occasionally meet people who are unusually nice to strangers, and they try to help them you as much as possible. Perhaps they don’t like to see any kind of suffering in their midst. Bless their soul! Most people on interview panels are usually from schools where competition is a celebrated norm. Which means that they expect you to do handle anxiety and pressure well which I guess is fair if not ideal for me. Sadly, I am not one of those friendly face myself when I am in panel!

I had much better results when interviewers were senior engineer/manager and technically hands-on. These folks are usually more worried about maintaining and running a system than developing new features. The tone of the conversation is immediately set to an abstraction level where I articulate better. I am terrible when HR or non-tech person starts the conversation. I think I am getting better at it. The trick is to answer slowly and nothing more. You can’t have a conversation with a person you don’t share vocabulary/language.

I guess what I am saying that interviewing is a social process. And like every other social process, it is ridden with ambiguity. Things that are easier for other will be hard for you and vice versa. Quite a lot depends on figuring this part out that you can’t unless you had gone through enough interviews without feeling paralyzed. Like any other skill, you need to train for it. AI live interviews (audio mode) helped me a lot. The questions and feedback/response you get from the AI is not the point; the point is that you get to practice and get to notice occasional bullshit you say.


My recommendation is to start interviewing at places where you don’t have much interest in joining (though you’d never know) so rejection doesn’t take as much emotional toll. And you get to work your interview muscle before it matters. If you have friends who are going though interviews, team up.

If you are not getting good vibe from the team during interview, my recommendation is to not join them (if you have a choice, some job is better than no job). I know some people who are genuinely not very interested in interviewing even if they would be excellent co-workers but I don’t think it is worth the risk. “Vibes” reflect culture. Personally, I am against the practice where the team interviewing is different than team hiring you because this model is tilted in favor of large organization and can work against candidates who enjoy being part of a capable team.

For a principal/staff role, and perhaps even for a senior role, you’d do well not to show (or worse fake) interest in something that you’ve no decent experience which could be hard if you are a generalist. Sine they can genuinely find almost everything interesting. I see all of them as software problems, no matter how different is the domain. Whether you are like me or not, it’d help not to do this (perhaps except at early stage startups). Keep focus on things that you are interviewing for and link it to things that you have done before. Closer they match, better are the chances of success at senior role.

If you genuinely excited about the role without having too much experience (e.g. I’d give a shot at Oxide Computers despite not doing any hardware for last 9 years), you may need to clearly articulate why you are excited in football now even though you’ve played hockey, cricket etc. so far. Remember that money they ware willing to pay you correlated with what your are most skilled at and how well it aligns with the job at hand. If you are willing to take a pay-cut then by all means explore new (potentially nearby) territories. I don’t think playing cricket everyday makes you any better as hockey, just like solving puzzles everyday won’t make you any better at combinatorics, let alone at linear algebra. It just shows that you are a good athletes and have what it takes to become a good athlete but I am not paying a price of a good footballer to a no-matter-how-good hockey player. If you willing to come as a rookie football player, fine! I am not yet not convinced that a good generalist could be an excellent specialist with LLM.


Follow the classic advice: you can never over-prepare and work on your resume. I spent weekends preparing for interviews. A friend was going through interviews and helping them also helped me lot. I recommend going though videos that talks about interviews (e.g. Hello Interview channel) if you have not given interviews for a long time. It is good if someone keeps continuously remind you (CRY) what is important. The point behind these exercise to learn how to leave a better impression on people who are going to pay you. To do better, you need to practice. And you can always do better no matter how good you are. Besides, if you can’t put effort during interview, what signal you are sending to your interviewer that says the you gonna put effort in your job?

I’ve been pretty bad as resume, and I still think I am not great at it. I usually don’t find enough excitement working on it (except for occasional urge to use LaTeX). It is tricky to figure out what to add or remove from the resume and what to highlight. I have a resume of a generalist which works well at startup and small enterprises but not at large organizations. Large orgs look for a specific skill. This is a tradeoff I am yet to learn how to make properly.

February 01, 2026 – Weekly Notes

  • I spent last month (Jan 2026) interviewing and job hunting. I have one offer that feels good, and I may receive another by the end of this week. I also have one interview left that starts next week.
  • I really enjoyed Veeam’s interview process. The Toyota interview went great as well. I was a bit disappointed with Cloudflare’s process—I was expecting them to reschedule after I missed the second round.
  • Kaalu is now officially overweight. She weighs 25 kg; her ideal weight is 20 kg. Dieting doesn’t work since the whole neighbourhood feeds her, and she eats competitively outside.
  • I’m thinking of migrating from Notion to WordPress. Notion is great at what it does, but the publishing options are less than ideal. I’m also reluctant to pay $12 per month for it. They should bring back the $5 personal plan! It feels like they’re moving more toward enterprise users.

January 10, 2026: Weekly Notes 2026/02

  • I’m trying to set up an engineering workflow at Dognosis (my current employer). After brainstorming with ChatGPT, I ended up with a template: Engineering Workflow Rhythm for a 20–100 Person Startup.
  • I clearly spelled out what I was looking for in the prompt—and what I didn’t want:
    • The first thing in the week is a short meeting; everyone should know they’ll work independently for the rest of the week.
    • Every Friday, we review work, update status, and report to stakeholders.
    • During the week, no cat herding. Each engineer acts like a professional and is treated like one (I don’t ask for updates).
    • Write before talking. Every meeting must have a written agenda.
  • I did the same exercise with Gemini. The results were not to my liking. ChatGPT’s responses were short, pointed, and—most importantly—felt implementable. Gemini, on the other hand, used language I don’t usually hear from good engineers. It added phrases that would make a PHB from Dilbert proud.
  • You may also like this post:Small projects, clear scope | Swizec Teller, along with his other posts on related topics.
  • I used to think std::move was C++’s way of implementing Rust-like move semantics. Turns out it’s another confusing monstrosity created by the committee that doesn’t do what it sounds like (f**king RAII?). std::move doesn’t move anything: A deep dive into value categories. Academic-type people should never be in charge of a language—or anything used by many people. Get a few normal programmers onto the committee, you C++ 😡.
  • 💡 Suddenly there’s a lot of incoming interest in my resume. Either the job market is heating up, or my resume is finally making sense to people. I spent over three months tweaking it (revisiting once a week). Talking to AI about my resume helped a lot.
  • 💬 I gave a few interviews this week.
    🚗 Toyota Connected is almost done. It’s Rust + firmware + software-defined vehicle work, which I’m pretty excited about. The interview itself was very pleasant: the technical team asked relevant questions and were very friendly. I felt comfortable after the first five minutes and didn’t suffer from brain fog.
  • Another interview was with a seemingly good company working in the secure computation domain. Senior leadership described the role one way, while the interviewer described it differently. The interviewer was very focused on dotting i’s and crossing t’s on a LeetCode question—and asked me to write code in Google Docs! I’m not really sure what he wanted to see. You meet every kind.
  • I had a first round with Cloudflare. I applied for a zero-trust and data-protection–focused role. They have the network, they have the edge—I wouldn’t be surprised if they start offering secure enclaves and other services where “trust” is explicitly computed.
  • A few surprising moments in the first round: I wasn’t expecting a technical screening but rather a discussion about the role and engineering problems with a manager. It turned out I’m in their general hiring pipeline, which means a phone screen by a manager first. Perhaps I’ll talk to the relevant team later. Not great, but not a deal-breaker.
  • I went through the round and felt I did average. I said a few very dumb things and had some brain fog. We finished early, which I really liked. +1 to the manager for keeping the agenda tight and being professional. I wasn’t very surprised when I was moved to the next round.
  • After that, I did something embarrassing. I made an off-by-one error in real life and ended up missing my second round 😢. I scheduled it for early Saturday morning (00:00 hrs) but marked my desk calendar for Sunday morning. Strong DND settings on both my phone and desktop made it impossible to error-correct—there was no persistent notification. Very unprofessional on my part, though I’m not mad at DND at all.
  • I sent an apology to the interviewer and asked to reschedule, but I’m not sure if this error is recoverable. Let’s see.
  • Three more opportunities are in the pipeline—all incoming interest, and all pretty interesting: hardware/algorithm development for space satellites, Windows security kernel development, and a data backup and protection SaaS.

November 22, 2025: Weekly Notes 2025/23

  • I think I’ll be able to complete 1000 km of run this year without putting any special effort 🤞🏾.
  • Eating outside for food, like movies, is becoming a luxury. Thankfully the traditional South Indian restaurants are still standing strong.
    • Covid had a negative impact on restaurants and car hygiene. We have not recovered from it yet.
    • Weird how things become worse slowly and then get normalized — like garbage in Bengaluru?
  • I applied at a few places for my next startup. I don’t think I did an outstanding job at the application, but time was short.
    • I decided to go through them pretty late. I feel most alive in the driver seat.
    • It doesn’t have to be a startup. An open source project gives me the same feeling.
      You make decisions and you are responsible for everything! You only deal with your own BS 🙂!
  • I meant to write about what went wrong at the previous one. I don’t think I can still write about it, I’ll try soon though.
  • I like EF, Antler, and South Park Commons–like programs. They let you, even encourage you, to walk in from the front door. For someone like me, who never had social capital or connections, this is something to be supported and cherished.
  • I read a funny story on this thread RE: What’s so cool about Scheme?

The venerable master Qc Na was walking with his student, Anton. Hoping to prompt the master into a discussion,
Anton said, “Master, I have heard that objects are a very good thing – is this true?”
Qc Na looked pityingly at his student and replied, “Foolish pupil – objects are merely a poor man’s closures.”

Chastised, Anton took his leave from his master and returned to his cell, intent on studying closures.
He carefully read the entire “Lambda: The Ultimate…” series of papers and its cousins,
and implemented a small Scheme interpreter with a closure-based object system.
He learned much, and looked forward to informing his master of his progress.

On his next walk with Qc Na, Anton attempted to impress his master by saying,
“Master, I have diligently studied the matter, and now understand that objects are truly a poor man’s closures.”
Qc Na responded by hitting Anton with his stick, saying,
“When will you learn? Closures are a poor man’s object.”
At that moment, Anton became enlightened.

Interview at NCBS Bangalore

_This article was written in 2016 from my experiences in 2015. Things have changed quite a lot at NCBS._

Every year, during the last week of May, NCBS Bangalore conducts interviews for admission to our Ph.D. and Integrated Ph.D. programs. If you are invited to the interview, this post is for you.

You should report to the campus by 7:45 am (I know this is too early and cruel). To reach the campus, you can use an auto/cab. There is a shuttle service between IISc and NCBS, but it won’t be of any help in the early morning. Food is not a problem for you or your parents. If you can’t report to the campus by early morning, do contact the people given in your brochure/information sheet/email.

There will be volunteers to help you throughout the interview process. You’ll get to know them during your orientation. Catch any of them, ask anything; they will sort out most of your problems.

The interview process consists of two stages for both Ph.D. and Int. Ph.D. candidates. Results are usually announced post-dinner at the end of the last interview day. Try to be calm during the process; it helps your chances.

Interviews will be in your area of expertise. You really don’t have to prepare for it. People are interested in how you think about scientific problems and not how much you know (which is always useful). The interviewers will not have access to your mark sheets, etc. You won’t be judged according to grades or your performance in the written tests. They will start afresh; it is all based on interviews from now on.

If you are from different backgrounds such as physics, computer science, or engineering, they will ask you general questions which are easy to understand (why do plants have flowers/fruits?). For goodness’ sake, don’t just say random things if you don’t know the answer. Do not throw any jargon at them in the guise of an answer. Try to answer logically and in simple terms — from the first principle. Or ask them to ask another question if you feel clueless.