...
> It was AJ, a candidate that Zouhair Belkoura, KeepSafe’s cofounder and CEO, readily admits he would have overlooked, had he come in through traditional channels.
This was the story of my job search three years ago. It still kinda is.
...
> It was AJ, a candidate that Zouhair Belkoura, KeepSafe’s cofounder and CEO, readily admits he would have overlooked, had he come in through traditional channels.
This was the story of my job search three years ago. It still kinda is.
I ended up reluctantly taking a job working for the State of California, mostly because the schedule was flexible and it was a 5 minute commute. In the last 18 months I've gotten two promotions, including one four months after I started which is unheard of in state service (and which my bosses had to fight HR to get). I spearheaded the acquisition and implemented of a version control system, which no one hear had ever used (they were just FTPing files all the time, risking overwriting of others' work etc), and got buy-in from all the developers who now say they couldn't imagine working without it. I also now wear a variety of hats besides programming including sysadmin work, dba work, architecture design, etc. My bosses rely on me more and more everyday just for my opinions and advice, let alone the work I do.
Yet now, when I send out my resume, it's almost always crickets. A year and a half ago, when the first item on my work experience list was "failed entrepreneurship", the response rate to my resume was about 80% (not even talking about interviews, just getting a response at all). Now it's more like 20%, all because the first item in my work experience section is my current job working in public service.
I admit, many of my coworkers probably deserve the reputation that public sector work has. A significant number of them are clock-watchers that the bosses don't even try to assign anything important to, because they know they don't give a shit and can't easily be fired (union), they are just filling a chair waiting for their public pension to accumulate over 20-30 years. Nevertheless, I also list on my resume all of the above, including the pioneering (for us) work I've accomplished here implementing version control etc. I never intended to stay here more than a couple of years, but I also never intended for this job to have such a negative impact on my job prospects.
I think I am probably going to revise my resume to leave this job off completely, and just say I've been working for myself for 9 years instead of 7. I predict sadly that this will return the response rate back to what it was before I had this job.
The fact that you can and did push change in public sector is huge, HUGE to anyone with half a brain. It's all in how you tell your story.
That doesn't sound too far off from a lot of corporate america as well.
My cv makes reference to some experiments I worked on at my first job which are described in very generic terms to avoid any problems with the official secrets act.
eg "complex problems involving digitizing data, from both still and high-speed film cameras."
I do like the idea of a straight up pitch using the more interesting jobs I have done
In that sense he had an advantage over me. The sec people know the deal with the engineers who work for the government on this stuff. I did radar signal processing code; without details I can't share it becomes very hard for me to explain how my background is relevant even though I could prove it in a practical task.