What is it about books? They still hold a place of magic in our society and to me.
I have had a few opportunities to write a book or two now, at least the offer to begin writing one or talk about writing one. I have passed on all of them so far. Not because I don’t want to. I actually would quite enjoy it. However, talking to all the people I know who have written (technical) books have told me two things:
It’s really really really hard
It’s really worth it.
How am I supposed to process that? I suppose it’s much like asking someone whether their time in the military was worthwhile. They became a stronger person because of it and opportunities may have emerged because of their new credentials. But it probably wasn’t fun every single day and it wasn’t a quick process. I suppose when you really step back and look at it, the same is true for anything worth having.
The last time I met with someone to discuss a possible book, I couldn’t help laugh and think about the fact that it’s 2014 and “everything” is digital and we were talking about a book. A set of ideas captured statically and printed on paper not to be updated for a few months or whenever the information was needed to be updated. Hell, this blog gets updated more often than that sometimes (and that’s not saying much).
Still. Can’t say I haven’t thought about it a bunch. It got me to post again.
I have corresponded with a international student for a few years now. I honestly can’t even remember how we met online and it doesn’t matter. He showed interest in my work and we started talking and have continued as he has graduated from US university and found a job locally. Recently he asked me:
I don’t like my current job. How can I get a job at Google?
I asked him why he wanted to move to Google. High pay? Exciting work? Big challenges? A recognizable name on a resume? All of these things can be had at other companies, many that are easier to get to than Google. Without having someone on the inside of Google that knows his work, I told him that he will be forced to go through the same process that every other interviewee does when applying to jobs posted online…and that’s a lot of competition. Not that competition is bad, just that there are so many better ways to find interesting, rewarding, high paid work.
So here’s the advice I give him and to all of you and any other recent graduates or young people looking for work:
I recommend you pick an open source project you think that Google would work on (or any other target company you’d like to work with). Maybe it’s a robot. Or a new API. Or a delivery service for soggy cereal milk (really?!?).
Next, start working on that project. If you can’t find an existing project, start your own (I started the BenchBudEE as part of Contextual Electronics because I didn’t see anything else in the marketplace). If you can’t do it alone, find some others that might be interested in the same topic. Find discussion boards or subreddits around the topic to find like minded people (hopefully with complementary skill sets)
Finally, spend all of your waking moments not at your job or school working on this project. You won’t be paid at all and likely never will be for this project. Work really really hard on it. At the end, you’ll either have one of two things
A job offer from Google (or whichever company you were targeting)
A great project and great experience.
If you don’t want to do the hard work when you’re not already working for Google, they likely won’t want to hire you in the first place.
I’ve looked at a lot of resumes for electronics positions, so I thought I’d share some of my opinions on what should or shouldn’t be on there. Nothing formatting specific, so much as how to get across your interest and passion in electronics. I used examples that are resumes meant for engineering internships, but a lot of the info can be generalized to anyone. Hope you enjoy the video!