Weekly Notes 2026/39

  • I went to Western Ghats near Ettina Bhuja: an overnight stay in a homestay, and easy hike early in the morning. It was a long weekend so a few friends also joined. Kaalu enjoyed hiking in the mountains.
  • My on-boarding has started at Progress.

Reading list

Weekly Notes 2026/38

  • Yesterday (Sep 25, 2026) was my last day at Toyota Connected India (🚗️TCIN, Bengaluru). I’ll be starting a new position (Principal Engineer, tech-stack: Rust) at Progress Software (Bengaluru) from Oct 1. I’ve mostly positive things to say about my 7 months long stint at TCIN. I recommend them for Rust and C++ roles.
  • Over last few months, I turned a C firmware to Rust/embassy. The first iteration was done using Claude. After couple of days, I had a non-blocking firmware which worked without any bug!! This is very rare in other languages where things just work if they compile (Haskell also comes pretty close but it doesn’t work on embedded systems).
    • Claude did a decent job i.e. we had non-blocking firmware that has similar behavior. The code is also better than I’d have gotten if people wrote it. I am cleaning it up now especially around error handling. I’d say it was overall positive. On the other hand, the firmware I was working at TCIN, requires keen eyes if you are using Claude/Copilot.
    • When multiple people are working on a codebase, the trouble with LLM generated code is same as LLM generated text. Its hard to know what is important in the wall of text. When people write decent text or code, the important bit is usually obvious and review process starts from there. This is not to say that people don’t write vacuous or disjointed prose and code.
  • Ookie had annual sports day at her daycare this week. It was a fun gathering though clouds didn’t offer help. It was a sunny morning and kids got tired soon. Parents were as usual more tired!
  • SIR has been going on in my neighborhood where I’ve been voting for last ten years. Yesterday, the ECI appointed contact person called and asked for 2000 bribe to “take care of SIR notice”! I’ve blocked his number and will take care of notice by myself.

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.

What Kind of Work I Want (in 2026)

  • I like spending time building systems! I build (software) systems because I enjoy it. I enjoy working at places where that is the vibe.
  • I almost always prefer to work remote unless your office is in my neighborhood. I hate commuting: 10 to 20 mins of walking, cycling or train commutes are fantastic. But I don’t see any city where cycling to work is feasible. Quarterly in-person off-sites or similar are OK. Occasional in office sync for white-boarding are fun. I rather work extra couple of hours for free than spend an hour commuting.
  • I prefer feeling average in a very talented team over feeling like a big fish in a small pond, imposter syndrome not withstanding. Stupider I feel talking to your senior engineers about systems, better are the chances I’ll lean towards you. And no, inverting binary tree on whiteboard is not a measure of that.
  • I want to work on something central to the company. I enjoy “pressure” of ownership, it brings the best out of me.
  • I don’t mind extending legacy systems but I don’t like maintaining them.
  • I do not care much about doing greenfield or fancy work or building the most interesting part of the product. I will happily build CI pipelines or a boring API, write documents, and do performance improvements if that’s what needs doing.
  • These days, I am learning how to use AI. I like what it has to offer but I am also very concerned about both organizational and individual skill-rot. If you have a culture of toxen-maxxing, I am out.
  • I want a low-process management style that trusts me to do my job. I act like a grown-up (as far as my work is concerned) and would like to be treated as responsible adult. A company that takes Agile software development very seriously or has no process at all is unlikely to be a good fit for me.
  • I like teams that articulate its engineering values clearly e.g. do we value stability over speed? In other words, how do you make hard decisions.