Tag: knowledge management

  • CV, STARs, and (Personal) Sales Pitches

    CV, STARs, and (Personal) Sales Pitches

    It seems to be job hunting season for my friends and family. And I’ve been helping them write and polish their resumes and curriculum vitae (CV). I often find myself repeating the same information – how to approach a job search, how to write a cover letter and a resume so that it helps you find the job, how to keep a log of your accomplishments at your job – so I wrote up a few pointers that I send along and refer to as I walk people through the job search process.

    It is a process. And each step of the process should hopefully take you to the next one, with the goal of eventually getting you a job that you are excited to work at. Your cover letter should convince the reader to look at your resume or CV. In turn, that should make them want to bring you in for an interview, where they decide if they want to offer you the job, and you decide if you want to take it.

    First things first: CVs and resumes are different beasts, even though the terms are used somewhat interchangeably. A resume should be 1-2 pages. It should highlight your most significant achievements in each job. A CV is much more suitable for academia – it should encompass all your professional achievements – papers, presentations, jobs, et cetera.

    The flow of a resume is fairly straightforward. You want the reader to very quickly grasp that you are capable of doing the job, and how you’ve done your jobs in the past.1

    One of the smartest ways that I learned to highlight my achievements was the STAR method of bullet point-writing. The STAR method is a simple formula for your bullet points that I learned while doing my MBA at Bayes Business School2. Each bullet point should be a sentence built using the following guidelines:

    • (S) Describe the Situation,
    • (T) Define your Task,
    • (A) Say what Action you took, and
    • (R) What the Result of that action was.

    Situation, Task, Action, Result will give you a succinct sentence that fits a bullet point. Whenever possible, use concrete terms and numbers for the results, and use active language to describe it.

    As you start doing this, you’ll see things that you’ve done that are outside what your job description stated or what the job you’re applying for needs. That’s fine. Keep them in the vault for another application. Or to bring up when you’re asked in an interview to "describe a time when you…" showed conflict management skills, or collaboration skills, or client management skills. This becomes your story bank. You might remember some difficult patches or conflict – note them down too, and what you learned from them.

    Understand what a CV or resume is meant to do. It’s job is to get you an interview. Be clear in what you’re putting in the document. This is a sales pitch for you.

    And don’t just do this when you’re looking for a job. Once a week, or at worst, once a month, look back on your work and add relevant points to your STAR bank. It helps to have this information on hand when you’re discussing your performance or negotiating for a raise. If you keep at this, you’ll wind up with your own career management document. You’ll see how you’ve grown and never dread an annual review because you won’t have to wonder what you’ve accomplished in the last few months.


    1. Pasting your job description here is not the way to go. It shows nothing of what you have accomplished in the job, and in the worst case, can come off as lazy. If you’re not putting in the effort to remember and show off your accomplishments, why should anyone else? 

    2. Thanks, Bayes Career Team. 

  • The Collectors Fallacy: How I Hoard Shit And Don’t Produce

    The Collectors Fallacy: How I Hoard Shit And Don’t Produce

    I feel overwhelmed all the time. I know that a lot of people feel like that these days, so at least I’m not alone in this. I try to do a lot with UA Kathachitra and my personal life. And sometimes, I can fall into what some in the productivity porn1 circles call “the collector’s fallacy”. I came across this way back in 2015 (I think) on zettelkasten.de.

    Now, I know Zettelkasten are the rage these days. There’s Roam Research, Obsidian, Tinderbox, Devonthink, Drafts, Taio…to name just a few apps that I’ve seen. Not to mention Emacs, Orgmode, and all the wonderful tinkering that accompanies them2. All of them promise that you will be able to produce things faster and better. That you will become a creator.

    There’s just one problem: you still need to do the work. And be confident in the work that you are doing. Now, I have an ADHD fuelled brain that is sure that it will remember everything 3 combined with some perfectionist tendencies. So I want to hoard ALL THE INFORMATION.

    Let’s get a glimpse into how my collection (read: hoarding) problem works. It looks like this:

    • Hundreds of open tabs in multiple browsers4 (I’ve maxed out my phone’s maximum allowed on more than one occasion),
    • Nearly 4000 bookmarks in Raindrop.io (mostly unread, or read and unprocessed),
    • My RSS reader (The Old Reader & Reeder 4) regularly acting as a holding space for things I want to read,
    • Outside of Raindrop and Reeders, in several other places, I have saved to read/listen/watch:
      • tweets and twitter threads,
      • reddit post and comments,
      • YouTube videos, and
      • podcasts, and
    • A constantly growing backlog of media to explore between all the streaming services.

    You remember the list of apps I threw up before? I try to test ALL THE APPS. This drives a constant search for the next shiny object that will help me DO SOMETHING with all this input5. I’m pretty sure that I’ve paid a lot of money for apps and services for notetaking and productivity that I have never used.

    Really though, all of – the hoarding of information nuggets, the switching of apps, the quest for becoming more efficient – it’s procrastination. Procrastination driven by fear. Fear of forgetting. Fear of not knowing. Fear of getting it wrong when the work is out there. Fear of… who knows?

    The first thing that Christian and Sascha write is “Collectors don’t make progress.” That hit me hard. It hit me hard when I first read it, and it hits me hard today, when I’m writing it here. There are times when I don’t feel like I’ve made any progress on turning information into something that I can use for my entire life.

    Over the last few months, as Vaidehi and I have been finding better ways to work. We’ve been forced to. So, it’s time to simplify and let a lot of things go. I promise you, this isn’t because I’ve read Cal Newport’s new book (I haven’t, and I’m not adding it to the pile).

    But how do I simplify? And how did I cope this long? That’s for another post.


    1. Productivity porn (or food porn, home improvement porn, or travel porn) is like regular porn. You watch someone else do things instead of doing it yourself. I look at how other people do things efficiently and think about how to apply those tactics to my own life. But I don’t actually do that – because that is hard. It’s also hard to figure out if something is useful for me if I haven’t settled into a system. Spoiler: I never do. So it’s a hamster wheel of the next system, the next app, the new hotness. It’s exhausting

    2. The two reasons I haven’t fallen down the Emacs rabbit hole is that it isn’t available on iOS and it’s not good at working collaboratively. 

    3. Spoiler: it doesn’t. 

    4. I’m ashamed to say that there was a time when I lost my shit on a poor QA tester who borrowed my phone to test a webapp our company was working on. He cleared the cache as part of his process, and I went nuclear because I had lost a few hundred open tabs. The sad part is that I could reopen most of them from memory… 

    5. I vaguely considered writing tech reviews, but honestly, I don’t have the money, nor the energy to keep up with all the services that I want to explore. And if I did explore them, I would be dropping the ball on my life, and the company that we’re trying to build.zettelkastenzettelkasten method