So update for anyone following the journey. I finished the hiring task submissions and sent them through yesterday at 3am. Today, I got the email for the final review scheduled meeting. 6pm CET tomorrow. This is what the entire hiring pipeline boiled down to, this final review.
I'd be lying if I said I wasnt stressed, or anxious, but I think I got this. After all, I did build the systems they're gunna be asking questions about, not like it's a blackbox file out of context again.
So fingers crossed and lets see how it goes! I'll write an update once the review is done on how it went and when it's all said and done, I'll write an overarching post, detailing the hiring process, so people who dont know what to expect when going into the hiring pipeline have a reference point and know what are the things that I tripped up on and what are the things that really impressed them, so you know where to spend your time and what skills to refresh on.
Top comments (6)
Finished the whole pipeline at 3am, then got the email for the final review, and now you're sitting with that stress before 6pm CET. So real. That is not you being dramatic. Your subconscious decides how safe you are in a room through a filter called the RAS. Someone about to judge whether you belong reads as a threat, so it clamps even when you already built the systems they are going to ask about.
You cannot logic that open with another night of prep. Your brain is a neural network trained on every evaluation room you have been in. If a lot of those felt like a test you might fail, that is the data it is running on. Knowing the code cold does not unlock it. New experiences do.
Get a few reps before you walk into that call that have nothing to do with hiring. Genuine compliment to a stranger. Cool shoes, nice jacket, whatever you actually notice. When that is easy, add how's your day going. Does not matter how it lands. The action is the win, not how polished the review goes. Stack enough of those and that 6pm room stops owning your nervous system.
Why is everything taking this long?
Guess that's hiring? Dunno, but yeah over a month to go from 'lets schedule an interview' to the final review and offer, is a bit long for me. Though I imagine it's done this way so they avoid the whole probation flaking. Especially cuz with a companies like Wasmer, where you'd need to build rust from source, they tend to have a 'home office stipend' that gives you a budget to kit yourself out to do the job to the fullest and idk bout you, but I'd want a candidate to prove themselves, before I'd just 'give' them $3000 (as an example) to buy the equipment they need to do the job?
So, it's a remote job? That may be why they are overly cautious.
Go get some rest. Youβre just overthinking and getting anxious, hahaha π
Yeah, they wanted to have the review today, but my brain is still cooked, so I postponed to tomorrow, so I can refresh myself again on the implementations and rest up. Cuz in between, I've made massive changes to IDE and I finally got Notepad++ working properly in my SASOS!!! 42mb of ram used for the entire QEMU instance, running the OS and windows's Notepad++! It only took half a mil LOC worth of windows API shims, but it works! So I gotta get my brain back on the pgrust port and the AFS, before I strike blank again π I switch projects so often that I just context swap entirely, so they dont bleed over (maybe I am an AI? my fiance seems to think so?). So genuinely need to shut down from all the other projects to keep a clear mind for tomorrow.