So, I've Started Doing Tech Interviews Again

Yo! Welcome to my dead blog. I created it for my time attempting to become and then being the Go developer advocate for JetBrains during 2023.

It’s been around 7 months, since I departed (as explained here) and well, as the title suggests, I’ve started doing tech interviews again. 

Why are you Interviewing Again?

Well, it’s a funny story! Thank you for asking. 

Now I could go into a lot of detail, but if you’re that interested just dm me and I will spin you a 3-hour tale of my odyssey.

Anyway, back in January, the original plan was simply to start applying for software engineering positions, but a part of me felt that before leaping back into it, maybe there’s something else I could play around with first. 

It’s tricky to say without feeling a bit silly, but I guess I just wanted to try and practice some video production, and all that entails such as, finding your niche, marketing, networking, presenting, organization, sticking to deadlines and fighting through the feelings that everything you make is terrible and no-one will ever care.

During my time at JetBrains I had the opportunity to play with these kinds of skills, but I knew in a traditional software role I likely couldn’t, so it just felt like a good opportunity to try.

And boy, it was tough. 

Putting yourself back into the suck zone where you’re essentially learning the basics of a completely different untrained skill set and navigating an unfamiliar and mentally hostile area is quite a wild experience.  

Still, I can't say I regret it. If money were no object I’d probably still be muddling along with it and honestly I learnt quite a bit about myself, what I believe I can do and I have a much deeper appreciation for those who chose to pursue something similar and were able to push their way through to making it their own. (Especially those who did it while full-time employed (Big Props!))

However, before embarking on that journey, I had to be realistic. In the field I chose to explore it can take multiple, multiple years to get anywhere and even then nothing is guaranteed at all. 

So, I set a timebox of six months, just so I could see what would happen in those six months and how I would feel about what I was doing. From there I would make a decision on what the next steps would be.

Hence, here we are.

You Giving Up?

Oof. That’s a very pointed question, the version of myself that wrote that heading. 

My heart… says no. Which honestly is a bit annoying. (It would save me soooo much work)

But as I said I have to be realistic, so this stuff I’ve been working on will need to essentially be what I do part-time and as a hobby. Which isn’t all that bad really.

There are many many people like me who pursue some of their passions in hobby form, which ultimately likely helps their relationships with their jobs, and perhaps even their lives. 

However, it’s a bit difficult to shake the feeling that we are essentially back where we started and all I have is one less t-shirt. 

You see, although it feels like I’ve grown quite a bit, these skills I’ve gained aren’t really that useful in a traditional software engineering role, so it’s gonna be a bit of an uphill climb to get back into a new role. 

Tech interviews are basically my kryptonite so I’m likely going to have to struggle through a number of them before I can regain my confidence a bit.

But eh, oh well, that’s the way she goes.  

So, That’s It From Me

See you on the mean streets of the interview process. If by any chance you may be looking for a referral bonus feel free to reach out or if you have any interesting opportunities for a mid/senior level Go engineer. 

As it says on my CV: Looking to work with newer technologies and provide an impactful voice to projects while bolstering the productivity and camaraderie of your team.

If that rocks your socks, then let’s chat and I can send you the rest of the CV. 

But yea, until next time. Ciao!