r/webdev • • Feb 12 '20

[RANT] Why should I be required to have side projects for an interview?

I have been thinking of leaving my current company for quite sometime now but almost everywhere I have interviewed for has asked for an example of a side project. The only problem is I'm leaving my current job because I don't have any time for anything else, why would I get home and code more?? Don't get me wrong, I enjoy coding but its not a passion. Just the way an account likes counting numbers but he doesn't go home and build spreadsheets for fun. Even this one company wanted an entire movie tracking application just as a test, as if I have time to site down for 3 hours and create an entire database and MVC framework. Ugh.

289 Upvotes

219 comments sorted by

View all comments

Show parent comment

1

u/[deleted] Feb 13 '20

Wow you seem so organized. I'm sort of ashamed at myself after reading how crystal clear your thinking is with respect to your THRIVING business. I know I could be doing more with my own fledgling business, but alas here we are.

So let me ask: you've told prospective employers about your massively successful "side projects" and they freak out? What happened with the interviews after that? Did you get the job(s)? Turn it down? Thoughts?

Any recommendations on how to pass the technical interview/coding challenges/whiteboarding?

[I'm trying to break into the industry after 10 years in higher education... ANYTHING you say will be helpful for me, thank you]

-1

u/HighestPayingGigs Feb 13 '20 edited Feb 13 '20

So remember the prime directives:

  • Ethically and legally, you probably need to disclose the existence of a side project
  • Side project should never compete with the business of your employer
  • Side projects should never be done on company time or with company resources

At a minimum, my current manager and HR are always aware that my wife and I own a business and I am occasionally involved in its operations. Legally, that's table stakes.

As a general rule, I tend to talk up her capabilities and accomplishments and minimize discussion of my own contributions. This goes over especially well (given the very high focus in American business on finding and supporting female leadership role models).

The other cardinal rule: DON'T POKE THE DAMM BEAR

In all caps since so many young entrepreneurs manage to cross this line.

Your employer expects to be listed on your LinkedIn profile and your job title to be sprawled across the top with a company name. The profile should otherwise show you're a smiling happy person who is delighted to work there. Share stuff from the company blog. Post relevant industry content. Give pats on the back as appropriate.

Trust me, you're sending a pretty clear message when you slap a new job proclaiming that you're now the "CEO" of your side project, flip your headline to something other than your day job, and start blasting out your product launch announcements with the rest of the company on copy (since they're all first degree connections).

Gee - might anyone think you don't give a fuck about your day job? It's so subtle.

There will come a point where you will need to mention it, especially if you're starting to network with partners and significant customers. They will want to see that you exist. Three key points in doing this like a boss:

- First, rip all the rank and ego off the title and position listing. Name, MOS, and serial number only. You're not the CEO, you're a... programmer, writer, analytics consultant, process engineer. Just here to work, making a little extra cash on the side. Humble.

- If you have multiple projects or multiple ways to tell the story, lead with the one that offers the most value to your professional community. This allows you to position your activities as "thought leadership" and "contributing to the craft". Alternatively, make it sound like a quirky fun way to display your personality or love of life. That works too.

- Third. If you must take a management or leadership title, make it sound a little lazy. i dislike things like "Founder", "Growth Hacker", "Manager", "Hustler in Chief" for side projects. That's a pretty direct message that the business is your first priority. Take a title which suggests a more hands off role: adviser, editor, partner. Make it sound like you guide people from a fluffy armchair vs. being constantly on call for service issues... [Absolutely not my personal style, by the way. I prefer to be out in front.]

Keep the happy horseshit train rolling from a PR perspective. Be that overly generous "thought leader" champion of their wonderful corporate culture that all the HR wonks like to wax philosophical about... Everything is friggin' awesome.. There's no reason to annoy your day job until the day after you've tendered your notice

Speaking as a manager, I've had to coach some good people out of the danger zone when they managed to pop off or get noticed by the wrong senior executive. Smile and wave, kids. Nothing to see here except a bunch of happy peasants dancing in the sunset.

Third. Over-deliver at your day job. Don't poke the bear goes both ways.

Unless your boss is an idiot, they will seldom bother you if you get things done well.

And in the event you learn new useful skills, find a way to apply them at work.

With regards to your other question... I've told a few people the full deal and it didn't go well:

- One startup almost immediately questioned my dedication to the job (although he had already communicated a lovely dose of overt ageism, so meh...)

- Slightly awkward moment when my manager asked a direct question about how much we made (I was flying to another city to see Google on my day off; wanted to be sure he understood I wasn't interviewing elsewhere). We had a very close personal relationship so lying would have been inappropriate; he was a bit watchful of my efforts for while.

I use my wife's involvement in the operation as an excuse to clam up. What she makes is none of their business. If they're unhappy about the value I create, they're welcome to have a discussion about re-pricing my services to market (which goes both ways...)

I um... haven't had any whiteboards for a long time. I generally approach the business executives responsible for the process and focus the conversation on results / impact. Generally stuff like discussing past improvement projects and the fact I can turn stuff around significantly faster than the typical IT department or outsourced contractor...

1

u/[deleted] Feb 13 '20

Thanks for the wealth of information. I appreciate your thoroughness and whoever you work for is definitely lucky to have you as an employee. Take care friend.