I had planned to get back into tech blogging this January with the Code Newbie “blog more” challenge — but then everyone in my house got sick and would you believe I am still sick today — this is the bronchitis that keeps giving, I tell you.
I had also planned to start prepping for tech interviews to launch a job search sometime later this year. I have been happy working at ExpertVoice (formerly Experticity, formerly ReadyPulse) — where for two years I’ve been doing full-stack software development with a fantastic team. My hours and work location are flexible, I get to work on interesting projects, the snacks are plentiful, and the time off “unlimited.”
Job perks aside, I’ve always known that it wasn’t my forever job. My commute isn’t ideal, and the company is heavily skewed towards the outdoor industry, which meant that a large segment of clients are gun manufacturers (hunting and whatnot). They don’t sell guns directly, but they definitely help gun manufacturers sell guns and shooting accessories to military and law enforcement officers. This has never aligned with my values, and sometime after the mass shooting in Vegas, I remember thinking, crap, I have to find a new job.
You know… sometime.
Anyway, an unexpected round of layoffs (30% of the company) has turned “sometime” into “right dang now” and I find myself facing down my nemesis, the tech interview. Just like finding a job out of boot camp, finding a(nother) job now requires dedicated and specific preparation. I took some baby steps at the end of last year and did a few interviews with little to no prep — and failed spectacularly. Apparently the fact that I have a few years of actual job experience, have built real software that people use, and can provide great references means nada if I can’t solve a specific technical challenge on a whiteboard or on a shared screen, while my interviewer watches, within the time allotted, which SPOILERS: