Achieve more in life.
Interviews
10 Questions to Ask in an Interview for Developers
Oct 12th
Editors note: This article assumes that you have some knowledge of software development.
The wonderful world of software development. I have now been a “professional” programmer for about 6 months now and have learned much more in that time than I did during most of my entire education at college.
Thanks college.
But, there are a few things that I have learned about the company that I work for, the people that I work with, and about programming in general that I wish I would have known when considering employment with any company. This isn’t because I don’t like my job (in fact, I Love my job); it’s because there are some things every developer should know before entering a new job in a new company.
I’ve compiled a list of 10 questions to ask in an interview for developers. If I missed something , add your questions in the comments below.
1. What tools does the team / company use?
We never learned about good testing frameworks or testing frameworks in general in school. Never learned what a good text/code editor was. And sure as hell didn’t hear what to use for source control.
These are some some good things to know about the company that you are applying to. What coding environment do you use? What type of source control tools? Are there any other specific tools I need to know before you join the team?
2. Are there some sort of coding standards?
What are big “no-nos” when it comes to coding style? Is there some sort of coding standard and style? If not, it doesn’t mean that they don’t know what they are doing, but it could mean that source code ends up being “spaghetti code” and tough to wrap your head around.
3. What type of storage technologies are used?
What ways do developers and the company store information? Is it a specific type of database technology or is it open ended? For example, do you have to use a standard, company-issued type of database technology like SQL Server or MySQL to get things done? Or can you use MongoDB on a whim?
4. What operating systems are used?
This should be somewhat apparent before your interview, but it’s always something good to ask. Plus it doesn’t hurt to passionately talk about your favorite OS, you geek. I can imagine that many companies use a wide-range of operating systems. Of course the most popular being Linux, Windows, and Mac OS X.
5. Is the team an Agile team? Do they follow Waterfall methodology (yikes!)?
What type of development style does the company / team subscribe to? Are they an Agile team? Waterfall? How closely do they follow the methodology?
Also, different teams within one company may have different types of methodologies they use. learning this allows you to see how you will work and what other teams use.
6. How much room do developers have to “take charge”?
Are customer software requirements locked and stringent or do developers have wiggle room to try and create things that customers would like better?
Do developers have the opportunity to create tools and systems during their day to help the team that they work on without having to create an entire formal project? Some companies encourage developers to take charge and make things on the side while others simply want you to do what you are told.
7. Are there any tool / software restrictions?
Is there any software that the company has “banned” from use? This is more along the lines of open source software or software that has weird licensing restrictions for commercial use.
Even after your interview, it’s probably a good idea not to install and use software that isn’t directly “approved” by the company, unless you are given free reign to do so.
8. Is telecommuting an option?
What type of working condition does the company have when it comes to working remotely? This can be a huge benefit to a future employee – the ability to work from home. If the company allows for remote working arrangements, It’s important to know what expectations are.
9. Does the team have code reviews? If so what are they like?
Ahh, code reviews. The one place that can make you feel like a genius or show you aren’t the hotshot that you thought you were. Does the company and team give code reviews on a regular basis? If so, what are they like? Hell on earth or generally helpful in learning what you are doing wrong and how to make it better?
I haven’t had the opportunity to sit through a killer code review, but I have heard horror stories. It’s good to know what you are getting into.
10. What type of experience is on the team that I will join?
How seasoned are the developers that you are about to join up with? What type of experiences and code have they been to exposed to? What are the weaknesses of the team and what can they improve on?
It’s a great thing to know when joining a new team; who can I ask for help if (and when) I need it?
Of course there are other important questions that you may want to ask in a developer interview, but these 10 will quickly give you an idea of what the team and company is like that you are interviewing for.
Like I said, I haven’t been in the software development field for too long, but feel that I now have a better understanding of what I would ask in my next interview. Are there any other questions that developers should ask during an interview? Post them below.
Nerdiest Interview Ever: MPU Workflows Part II
Mar 27th
MPU 046: Workflows with Merlin Mann II « Mac Power Users
I have the life that I have because I've made a lot of weird decisions, and they've worked out well.
Not gonna lie to you. I'm a huge nerd. Surprised?
Yep. I can recite big chunks of The Big Lebowski from memory. I can argue for an hour on the merits of Dick York over Dick Sargent. And, I can—and frequently do—catch myself thinking Catwoman, Batgirl, Princess Leia, and Emma Peel should have a light-hearted pillow fight that ends with an hour of genial french-kissing.
Pretty much like you, probably. I dunno, maybe your version includes Kitty Pryde. Po-tay-to/Po-taht-o, right?
Perhaps most saliently, by virtue of having spent a solid 2,399 days as a Fake Productivity Guru, I have been provided with an unquestionably Janusian monkey's paw of a gift; I now know a lot about workflows. Nerdy, nerdy workflows.
I can tell you a few things that almost always work, I can tell you a handful of things that almost never work, and—best or worst of all—I can tell you thousands of things that might work. Sometimes. Maybe. Kinda. For some people. For now.
And, at the risk of gay-marrying my arrogance to my hypocrisy, I can tell you that I also know enough about the unholy diarrhea of potential options for Theoretical Productivity to share two big patterns:
- Getting your workflow right matters.
- Getting your workflow right to the exclusion of the actual work is a fool's game.
But. Managing to get the most useful and most elegant and least fiddly mix of 1 and 2 right is super-hard. Especially for nerds. Especially for me.
So, as I type this today, I believe there can be no greater testament to these claims—or, at least, no greater place to test the veracity of these claims for yourself—than in this TWO AND A HALF HOUR-long interview for Mac Power Users.
It is reeeeeeeeally nerdy. Almost intolerably nerdy. Just…overwhelmingly nerdy.
But, man, is it ever really good, and really fat with the most insanely granular details of How I Work.
Lo, even these 928.5 days after officially retiring from productivity pr0n, my desire to not "vend stroke material for your joyless addiction to puns about procrastination and systems for generating more taxonomically satisfying meta-work" is tempered by a (widely under-reported) practical streak.
Yes: I continue to despise empty advice about rearranging deck chairs on The Titanic. But, yes: I do also still very much enjoy talking about how all the tips and tricks can or can't work in the context of work you care about. That matters. It really does.
So. Here goes. A one hundred and forty six minute-long, Joyce-ian amble through the Big Stuff and the Little Stuff. David and Katie were very patient.
How I name text files. Why I break iOS apps. Why I love the letter "x." Why I won't row out to islands any more. How a 115,000 word book manuscript is "like a house full of confederate money." How "The Cloud" broke in New Zealand. How I use MultiMarkdown, Scrivener, TextExpander, OmniFocus, TextMate, Notational Velocity, Dropbox, and an explosive combination of Elements, Notesy, Nebulous, Simplenote, CF Outliner, iThoughts, Instacast, Good Reader, and wow wow wow.
How I try not to fiddle—how I sometimes succeed and often don't. But, how I try.
Anyhow. There you go. A perfectly nerdy bookend to last year's first Magnum Opus MPU interview on these same topics, Mac Power Users Episode 46 is just insanely nerdy. And, what have you.
I hope you like it. I hope it's useful. I hope you don't use it to replace real work.
And, as ever, I really hope Batgirl starts having more sexy pillow fights.
Enjoy. And, God save you.
MPU 046: Workflows with Merlin Mann II « Mac Power Users
”Nerdiest Interview Ever: MPU Workflows Part II” was written by Merlin Mann for 43Folders.com and was originally posted on March 27, 2011. Except as noted, it's ©2010 Merlin Mann and licensed for reuse under CC BY-NC-ND 3.0. "Why a footer?"
Catching Up: 3 Interviews from a Cooling Crucible
Mar 17th
After almost a year of hand-wringing, fretting, and occasionally even writing the odd string of English words, I've finally started turning into the home stretch with the first draft of my Inbox Zero book.
If it hasn't been obvious, or you couldn't just guess, this book project's been a big rock for me. Given the effort it's taken (read: most every hour I'm not sleeping, working, or pushing my daughter in a swing), it's also the primary reason why updates to 43 Folders have been so scarce over the last few months. The spirit was willing, but the brain--insanely sick of thinking about these very topics--was weak.
Yes, as it turns out, writing a book does require an extraordinary expenditure of both attention and time. And, in my own case, I'll confess that this often meant working even more than four hours a week. But, who knows? Maybe that's just a consequence of my slow typing and abject lack of lifetrepreneurship.
Thing is, this has also been a fantastic and exhilarating time for me. Despite the pressure, the stress, and the alternating tickity-tock of both clock and keyboard, in the end, performing the architecture and masonry required to build such a large project demanded that I gather a lot of seemingly unrelated material, choose the most promising ingredients, and then heat it all up in a deadline-fueled crucible. Sure, it's been mostly good pressure (who the hell complains about having a book deal?), but it's still been real pressure.
Fortunately, with much relief and abundant gratitude, I can say that I'm really satisfied with the emerging artifact. And, of course, I really hope you guys feel the same way when the book comes out. Probably some time in the fall of 2049.
Coming Up for Air
I mention all this here because, if you follow any of the stuff I do and say elsewhere, you'll have noticed a recent uptick in the number of appearances I've been making around the web. That's the happy confluence of my (finally) coming up for air, combined with my determination to (finally) make good on endless months of snoozed and punted and re-re-re-scheduled interview requests from some very cool people, publications, and podcasts. (Thanks to everyone who's asked and, if I missed you, please ask again.)
So, today, I beg your indulgence to share three recent interviews with me that I like quite a lot.
While all three are profiles of me and what I've been doing and thinking about as I work on this infernal book business, they also each bear directly on the topics that I know mean a lot to you guys, too. Especially, if you're one of the band of brothers who've stuck with me and courageously kept this XML-enabled null space in your feed reader since my much-discussed shift away from productivity pr0n.
Thus, by way of inarguably self-involved catch-up--and as an informal reintroduction to how I truly believe you can "find the time and attention to do your best creative work"--here's three recent interviews:
- on the values of voice, openness, and making mindful creative work;
- on a very detailed exegesis of my tactical workflow;
- on the benefits of diving into the projects that terrify you
I really hope you'll like them.
The Pipeline, ep. 7; with Dan Benjamin
The Pipeline 7: Merlin Mann | 5 by 5
Download MP3 of "The Pipeline, ep. 7" | Huffduff This
My longtime hero, Hivelogic's Dan Benjamin, recently invited me onto 5 by 5's flagship podcast, "The Pipeline." While it was intimidating to know I'd be standing alongside such august (and superior) talent as Zeldman, Haughey, Coudal, and Inman, I was honored to be asked, and I'm extremely happy with the results.
We cover a lot of territory in less than 40 minutes, but we basically hit on almost every major topic that means a lot to me right now, including, the power of voice, the challenges of knowledge work, the perils of the Lizard Brain, the primacy of action, the seeming unavoidability of Buddhism, and the hidden dangers of following herds, chasing dumb traffic, and aping the "success" of others.
Thanks much for this opportunity, Dan. You're a real pro.
Mac Power Users, ep. 23; with David Sparks and Katie Floyd
Mac Power Users» Blog Archive » MPU 023: Workflows with Merlin Mann
Download MP3 of "Mac Power Users, ep. 23" | Huffduff This
Averse as I am to promoting productivity pr0n for its own sake, this tour de force podcast should be a lot of fun to anyone who's interested in Mac and iPhone workflows.
Because, believe it or not, I am besieged with daily requests for details on how I actually work. And, if you have even the vaguest passing interest in how I currently sew together OmniFocus, Notational Velocity, TextExpander, Pastebot, Pinboard, Instapaper, Simplenote, Scrivener, MultiMarkdown, Quicksilver, and more, more, more, prepare for your head to explode multiple times. There's a lot here, so don't miss Katie's exhaustive show notes for a full run-down.
But, like I said, please do take all this in doses. This is something I've evolved over years, so you certainly don't need to stop what you're doing to try to implement all of this.
Still, I have to say, this podcast lays out an empirically nerdtastic workflow which even the dorkiest Mac fanboy will find something new and awesome in. And, yes, there's loads of non-tool-fetish advice on how to do the actual work. I promise.
Thanks so much to David and Katie for putting up with 90 minutes of me talking very quickly about the most embarrassing details of my encompassing Mac dorkery.
MaxFunCon Podcast, ep. 12; "Keep Moving"; with Jesse Thorn
iTunes: MaxFunCon Podcast Episode 12, Merlin Mann
Download MP3 of "MaxFunCon Podcast, ep. 12" | Huffduff This
I'm an unapologetic fan of everything Jesse Thorn does, including The Sound of Young America, Jordan Jesse GO!, and, of course, his annual conference celebrating all things awesome, MaxFunCon. In fact, you may remember the talk on "Getting Started" that I presented at MFC last year.
In this admittedly rambling (but hopefully charming) interview, Jesse and I talk about what makes MaxFunCon so special, as well as how a person who's as--to use Jesse's parlance--"ADD-addled" as I am can actually put a 50,000-word book together. Along the way I profess my love for Maria Bamford, Jonathan Coulton, and Chris Hardwick, as well as extol the virtues of drinking vodka from a glass skull with John Hodgman.
Silliness aside, we talk frankly about the pants-be-crapping fear of performing (and the more profound terror of sucking at performing) that dogs anyone who's ever decided to get up in front of a bunch of strangers and try to be entertaining. It's hard. So hard. Which is kind of why I love it.
Alas, MaxFunCon 2010 is now way sold out, but you can claim your spot on the waiting list by writing to maxfuncon at gmail. It is, as I've repeatedly said, easily the best conference I've ever attended. Ever. Even more than DB/Expo '97.
Thanks for your patience with this one, and sorry in advance if this seems all me-me-me.
But, if anything, 43 Folders is a site that started and still exists for me to share what has and hasn't worked for me along the road to trying to make great stuff.
I hope all three of these interviews will be of interest to anyone who walks that same road, stumbles onto those same shoulders, and shares my cardinal interest in always dusting yourself off, stepping back on the path, and plodding toward whatever comes next.
Onward, friends.
”Catching Up: 3 Interviews from a Cooling Crucible” was written by Merlin Mann for 43Folders.com and was originally posted on March 18, 2010. Except as noted, it's ©2010 Merlin Mann and licensed for reuse under CC BY-NC-ND 3.0. "Why a footer?"