SaaS: The recruiter does not think you’re hot.

This is part of the SaaS series. Any connection to reality will be strictly denied.
I've only had one truly unbearable job.  It was awful - The code base sucked, the boss had pointed hair, and to top it off I got a terrible review. 
Let’s rewind. Four months prior I’d just aced a job interview with HappySoft.  I nailed the questions, and the job was a nice fit for my career. But, I wasn't ready to sign on the dotted line until I evaluated all my options, namely my next interview with EbolaSoft.
My EbolaSoft interview was at 9am and it started off on the wrong foot. The interviewer didn't know the answers to his own questions, and couldn't tell me what I’d be working on. With 15 minutes left in the interview I’d given up on EbolaSoft. At that point the interviewer excused himself and Rene entered the room. Rene was the recruiter for EbolaSoft, and my heart skipped a beat when she smiled at me. As she discussed the company, she twisted a long strand of brown hair around her fingers and I forgot how the interview began.
That night, with a job offers from EbolaSoft and HappySoft in my left hand, an IPA in my right hand, and Biff, my college roommate, sitting across from me, I worked through the details.   “Sure the job might suck, but Rene is hot, and man her smile...  Look if the job sucks, I’ll work less and spend all my time seeing the city with my favorite recruiter”.  Biff, knowing better than to argue after I’d made up my mind, just paid for our beers and left. 
The next morning, I signed the job offer with Rene’s company. 
I started work for EbolaSoft in September, in the middle of a long death march. Too busy trying to get his feature out the door, my new boss hadn't spent any time thinking about what I’d be working, and he certainly didn't have the time to talk to me about what I should be working on.  Worst of all, even though I was always hanging around recruiting I never saw Rene’s smile again.
Moral of the story 1: Do not take a job because your recruiter is hot, I don’t care how much she smiles at you.
Moral of the story 2: Rene – if you’re reading this – You made the biggest mistake of your life.

Comments

Unknown said…
This comment has been removed by the author.
3/05/2018 8:48 AM
Post a Comment

Popular posts from this blog

Finding CLR exceptions without visual studio

(If you want to understand what exception code 0xe0434352 is, read this post ) Often exceptions are thrown and caught and you don't see them. You probably know how to debug this in Visual Studio, so let me show you how to do it in cdb. Sample Code: class Program { static void Main(string[] args) { foreach (var x in Enumerable.Range(0,2000)) { Thread.Sleep(TimeSpan.FromSeconds(1)); Console.WriteLine("Hello World"); ThrowAndCatchException(); } } private static void ThrowAndCatchException() { try { throw new NotImplementedException(); } catch(Exception) { } } } Output of the application: Hello World Hello World Hello World Nothing about an exception, but you're sure it's happening behind the covers -- fire up cdb: C:\Program Files\Debugging Tools for Windows (x64)>cdb -pn consoleapplication3.exe <SNIP> ModLoad: 000007fe`f7e90000 000007fe`f7eb4000 C:\Windows\Mi...
Read more

Why do I keep getting exception code e0434352?

If you want to know how to debug CLR exceptions using cdb then read this post . Exception code e0434352 is the exception code used internally by the CLR to represent most exceptions(*). Regardless of if you throw a System.NullReferenceException or a System.ArgumentException in C#, you'll throw a SEH exception e0434352 under the covers. A fun way to validate this theory is to watch what happens to the CLR exceptions settings in cdb. Fire up cdb, and see the state of clr exceptions: 0:000> .shell -ci "sx" findstr clr clr - CLR exception - second-chance break - not handled clrn - CLR notification exception - break - handled .shell: Process exited Now, set the exception handler for exception number e0434352 and recheck the value of the clr exception handler: 0:000> sxe e0434352 0:000> .shell -ci "sx" findstr clr clr - CLR exception - break - not handled clrn - CLR notification exception - break - handled .shell: Process exited Armed with ...
Read more

Powershell script to enable windows to capture localhost traffic in wireshark

If you want to understand why the following scripts work read this post . Otherwise just paste the following into an elevated powershell window: Setup windows networking to allow localhost capturing in wireshark: # Find the network configuration that has the default gateway. $defaultAdapter = Get-WMIObject Win32_NetworkAdapterConfiguration | ? {$_.DefaultIPGateway} if (@($defaultAdapter).Length -ne 1) {throw "You don't have 1 default gateway, your network configuration is not supported" } # Route local IP address via the default gateway route add $defaultAdapter.IPAddress[0] $defaultAdapter.DefaultIPGateway Write-Host "Start capturing on localhost by connecting to $($defaultAdapter.IPAddress[0])" Return windows networking to normal configuration: # Find the network configuration that has the default gateway. $defaultAdapter = Get-WMIObject Win32_NetworkAdapterConfiguration | ? {$_.DefaultIPGateway} if (@($defaultAdapter).Length -ne 1) {throw "Y...
Read more