{
  "$type": "site.standard.document",
  "content": {
    "$type": "site.standard.content.markdown",
    "text": "import JobSearchSankeyChart from '../../components/JobSearchSankeyChart/index.astro'\n\nAt the end of 2021, [I left my job at Talent Inc.](https://eligundry.com/blog/what-i-learned-working-at-my-first-startup) and conducted an extremely thorough job search.\nI really prefer to job search without a day job so that I can give it my full focus. Today, I am happy to announce that\nafter a little over a month of interviewing, I found the perfect job for me. But, before I get to that, I really want to\ntalk about how I conducted my job search as it's been something I've been planning for a bit.\n\n# [Numbers On The Board](https://www.youtube.com/watch?v=DawrlSwHUiM)\n\n<JobSearchSankeyChart year={2022} />\n\nThis job market is wild! I can't tell if companies are hiring harder this cycle or if the fact that my last role was\n\"senior software engineer\" at a startup or what. This cycle could not have gone any more different than my last job\nsearch in 2017.\n\nLet's take a quick at conversion rates compared to 2017:\n\n- Application β†’ callback rate was 75% in 2022 vs 35% in 2017\n- Application β†’ code test rate was 40% in 2022 vs 9% in 2017\n- Application β†’ on site rate was 27% in 2022 vs 6% in 2017\n- Application β†’ offer rate was 19% in 2022 vs 1% in 2017\n\nThe numbers don't tell the full story here either! The later stage numbers here are weighed down by the fact that I was\nable to drop out of processes later on if I wasn't getting good vibes from the company. That freedom alone allowed me to\nhave a little more swagger in walking into interviews.\n\n# \"Technology Enabled Job Search\"\n\nWith working at a job focused on job seekers, I had four years to think about how I would approach my own job search.\nA big one that I thought about was how to effectively track open rates of emails and my website. So, I went about wiring\nmy resume and email signature to append `utm` parameters to all the links to my website. My thought here was that\na click through to my site would lead to a more positive outcome on initial submission.\n\n**This turned out to not work at all! I only got 3 visitors to the site from clicks in my email signature or resume\nlinks.** Making unique copies of my resume and updating my signature on all my emails was seriously annoying, so this\ndefinitely is not worth the effort. In fact, it may have subtly played against me as the checksum of my resume changed\non each job submission, which can throw off ATSs, like those used in Greenhouse. Finally, most of my processes went\nthrough external recruiters so even if the user clicked through, I would have no idea which of the three companies they\nsubmitted me to even clicked.\n\nI did get elevated traffic to my website during my job search, though. It seems that I can attribute this increase from\nthe fact that I did post my last blog post on Linkedin right as my job search started. This post was brought up a few\ntimes during interviews, which felt really good and gave the interviewer confidence in my writing skills. As they always\nsay, **content is king πŸ‘‘**.\n\n# What Would I Do Differently?\n\n**I spent too much time prepping for interview programming questions and not enough time asking what I actually want in my\nnext job.** This lead me to go deeper in processes that I knew that I was not going to take. I feel that, in all my\nprevious job searches, I was lucky to get what I get and not throw a fit. This search, people were thirsty for me and\nI had to make hard decisions based upon feelings that I should have already talked out.\n\nAnother problem is that **I'm a people pleaser that's uncomfortable saying no**. This lead to me working with some… inept\nrecruiters this cycle that caused more headaches than what they were worth. In talking to some friends that are also\ninterviewing, I realized that their bullshit tolerance was much lower than mine and cut processes off if things felt\nwrong or they were disrespected.\n\nFinally, the last problem is that **I applied to way too many jobs**. I keep track of my progress during my job search in\na spreadsheet. I sent that spreadsheet to some of my friends and they were shocked by the number of places I started\nprocesses with. In my defense, in past job searches, I have noticed that a lot of my applications go nowhere, which\nI attribute to not having a degree and/or super interesting past positions. With that said, I had just too many\ninterviews back to back to back that I'm certain my performance in some of them was degraded by my lack of energy.\n\n# Interviewers Say The Funniest Things\n\n> We love chaos here. We want just enough chaos to scare us to ship things fast, but not so much it paralyzes us.\n>\n> We like to say that do things right the second time. We want that first time to ship fast.\n\nOh lord, I ran away from that company so fast. They had a wild code test that was closer to drive by than learning about\nhow I can benefit them.\n\n> So, your process of learning is just detective work?\n\nThis was an interviewer's reply after I described, in detail, how I work in an unfamiliar and terrible codebase. It's\nnot super funny, but I had never heard it put that way before and I'm stealing it.\n\n> Our lead investor is [Scooter Braun](https://en.wikipedia.org/wiki/Taylor_Swift_masters_controversy).\n\n\\#TeamTaylor until I die, ran away from that super fast.\n\n> The only downside is that product likes to live in the moment\n\nNever heard it put that way before, but product does be like that sometimes.\n\n# Enough about the search! Where are you working!?\n\n![Chord Commerce Logo](https://eligundry.com/../../assets/img/job-search-2k22/chord-logo.jpg)\n\n**I will be joining [Chord](https://chord.co) as a Staff Engineer in early February!**\n\nI got seven offers and picking one was really hard, but also not hard at all. Out of all the places I interviewed, Chord\nhas the friendliest team that just \"got me\", if that makes any sense? There were no red flags that came up during the\ninterview, no one complained about how much the code needed to be fixed and everyone just seemed happy and competent.\n\nMost importantly, what I'm going to be working on excites the heck out of me! Chord's vision is to bring ecommerce\ntooling to statically generated sites. I love [static sites](https://eligundry.com/blog/2021-website-redesign) and selling things to\ncustomers! I've never worked on libraries that other developers use, so this will be an exciting challenge on top of all\nthe feature work that needs to be done at a startup!\n\nIn closing, this has been a hectic job search and I'm so happy to finally be done with it. Now, I am going to take two\nweeks off to be a human being. I'm probably going to go upstate for a long weekend. Definitely going to play some\ntennis. Maybe I'll get lost in Central Park a few times or get another dumb tattoo.",
    "version": "1.0"
  },
  "description": "This was the most wild job search I've ever done",
  "path": "/blog/job-search-2k22/",
  "publishedAt": "2022-01-28T05:00:00.000Z",
  "site": "https://eligundry.com",
  "tags": [
    "code"
  ],
  "textContent": "import JobSearchSankeyChart from '../../components/JobSearchSankeyChart/index.astro'\n\nAt the end of 2021, I left my job at Talent Inc. and conducted an extremely thorough job search.\nI really prefer to job search without a day job so that I can give it my full focus. Today, I am happy to announce that\nafter a little over a month of interviewing, I found the perfect job for me. But, before I get to that, I really want to\ntalk about how I conducted my job search as it's been something I've been planning for a bit.\n\nNumbers On The Board\n\nThis job market is wild! I can't tell if companies are hiring harder this cycle or if the fact that my last role was\n\"senior software engineer\" at a startup or what. This cycle could not have gone any more different than my last job\nsearch in 2017.\n\nLet's take a quick at conversion rates compared to 2017:\nApplication β†’ callback rate was 75% in 2022 vs 35% in 2017\nApplication β†’ code test rate was 40% in 2022 vs 9% in 2017\nApplication β†’ on site rate was 27% in 2022 vs 6% in 2017\nApplication β†’ offer rate was 19% in 2022 vs 1% in 2017\n\nThe numbers don't tell the full story here either! The later stage numbers here are weighed down by the fact that I was\nable to drop out of processes later on if I wasn't getting good vibes from the company. That freedom alone allowed me to\nhave a little more swagger in walking into interviews.\n\n\"Technology Enabled Job Search\"\n\nWith working at a job focused on job seekers, I had four years to think about how I would approach my own job search.\nA big one that I thought about was how to effectively track open rates of emails and my website. So, I went about wiring\nmy resume and email signature to append  parameters to all the links to my website. My thought here was that\na click through to my site would lead to a more positive outcome on initial submission.\n\nThis turned out to not work at all! I only got 3 visitors to the site from clicks in my email signature or resume\nlinks. Making unique copies of my resume and updating my signature on all my emails was seriously annoying, so this\ndefinitely is not worth the effort. In fact, it may have subtly played against me as the checksum of my resume changed\non each job submission, which can throw off ATSs, like those used in Greenhouse. Finally, most of my processes went\nthrough external recruiters so even if the user clicked through, I would have no idea which of the three companies they\nsubmitted me to even clicked.\n\nI did get elevated traffic to my website during my job search, though. It seems that I can attribute this increase from\nthe fact that I did post my last blog post on Linkedin right as my job search started. This post was brought up a few\ntimes during interviews, which felt really good and gave the interviewer confidence in my writing skills. As they always\nsay, content is king πŸ‘‘.\n\nWhat Would I Do Differently?\n\nI spent too much time prepping for interview programming questions and not enough time asking what I actually want in my\nnext job. This lead me to go deeper in processes that I knew that I was not going to take. I feel that, in all my\nprevious job searches, I was lucky to get what I get and not throw a fit. This search, people were thirsty for me and\nI had to make hard decisions based upon feelings that I should have already talked out.\n\nAnother problem is that I'm a people pleaser that's uncomfortable saying no. This lead to me working with some… inept\nrecruiters this cycle that caused more headaches than what they were worth. In talking to some friends that are also\ninterviewing, I realized that their bullshit tolerance was much lower than mine and cut processes off if things felt\nwrong or they were disrespected.\n\nFinally, the last problem is that I applied to way too many jobs. I keep track of my progress during my job search in\na spreadsheet. I sent that spreadsheet to some of my friends and they were shocked by the number of places I started\nprocesses with. In my defense, in past job searches, I have noticed that a lot of my applications go nowhere, which\nI attribute to not having a degree and/or super interesting past positions. With that said, I had just too many\ninterviews back to back to back that I'm certain my performance in some of them was degraded by my lack of energy.\n\nInterviewers Say The Funniest Things\n\nWe love chaos here. We want just enough chaos to scare us to ship things fast, but not so much it paralyzes us.\nWe like to say that do things right the second time. We want that first time to ship fast.\n\nOh lord, I ran away from that company so fast. They had a wild code test that was closer to drive by than learning about\nhow I can benefit them.\n\nSo, your process of learning is just detective work?\n\nThis was an interviewer's reply after I described, in detail, how I work in an unfamiliar and terrible codebase. It's\nnot super funny, but I had never heard it put that way before and I'm stealing it.\n\nOur lead investor is Scooter Braun.\n\n\\#TeamTaylor until I die, ran away from that super fast.\n\nThe only downside is that product likes to live in the moment\n\nNever heard it put that way before, but product does be like that sometimes.\n\nEnough about the search! Where are you working!?\n\nI will be joining Chord as a Staff Engineer in early February!\n\nI got seven offers and picking one was really hard, but also not hard at all. Out of all the places I interviewed, Chord\nhas the friendliest team that just \"got me\", if that makes any sense? There were no red flags that came up during the\ninterview, no one complained about how much the code needed to be fixed and everyone just seemed happy and competent.\n\nMost importantly, what I'm going to be working on excites the heck out of me! Chord's vision is to bring ecommerce\ntooling to statically generated sites. I love static sites and selling things to\ncustomers! I've never worked on libraries that other developers use, so this will be an exciting challenge on top of all\nthe feature work that needs to be done at a startup!\n\nIn closing, this has been a hectic job search and I'm so happy to finally be done with it. Now, I am going to take two\nweeks off to be a human being. I'm probably going to go upstate for a long weekend. Definitely going to play some\ntennis. Maybe I'll get lost in Central Park a few times or get another dumb tattoo.",
  "title": "Job Search 2k22",
  "updatedAt": "2025-02-12T02:34:47.000Z"
}