Category Archives: Interviewing

Interviewing

Sample DBA Resumes

Nobody knows who I am.

Yes, I know, you think I waltz into restaurants without a reservation, get the best table in the house, and Rick Bayless brings the food out himself.

In reality, sooner or later, everybody asks for a resume.  (Except Rick Bayless.  He just asks for money.)  Managers don’t read blogs, so they don’t care how many times you’ve seen us do webcasts, how many presentations you’ve attended, or how often you retweet us.  They want a simple printout that explains whether we’re skilled.

We get a lot of emails asking how to create a DBA resume or looking for sample templates, so we thought you might get a kick out of viewing how each of us approached the resume thing.

Brent’s Resume: “I wanted to tell two stories for each position on my resume: how I ended up in that job, and what I did in a typical week.  I wanted the resume to fit on a couple of pages, but if people wanted more details on a particular job, I wanted to give ‘em more.  I used the jQuery Collapse-o-Matic plugin to add Read More sections.  Finally, managers have told me that they hired me because of my confident interactions in person, so I recorded a 15-minute virtual interview and embedded it.  I’d like to have a more professional one done later, but this is a good start.”

Jeremiah’s Resume: “I spent many years as a consultant at a number of mid-sized firms; I must have re-written my resume thirty or forty times and I’ve reviewed hundreds of resumes for job candidates. Unfortunately, resumes and bullet points don’t always tell the full story. I wanted people looking at my resume to know that I love my job and that I love sharing my knowledge. I don’t have the traditional DBA skill set and I wanted to emphasize my unique skills. The second half of the resume is a more traditional Title, Time, Tell Me What You Did format. It points out some of the interesting things I’ve done over the course of my career and some of the things that I’m proud of.”

Kendra’s Resume (PDF): “My big problem with resumes: I want to talk about the exciting things I’ve done right away. I don’t want what I’m proud of to get lost between dates, times, and employers. Since I love to draw, I also want my resume to be graphic. I wrote a two-page resume in a document format. On the first page I talk about the top three questions customers ask me and map in the related projects I get excited about. On the second page I walk through more of the traditional what, where, and when to contextualize my work history. I included the drawing I made of the team at the bottom of the pages– I love that I can swap this out to keep things fresh over time.”

Tim’s Resume (PDF): “I’ve a great number of things going on in my life and that wages a fierce war with my formal business education which preached the cardinal rule of “fit all of yourself onto a single 8.5″ x 11″ page with an ample number of bullet points”.  In the spirit of compromise I embraced the idea of still including the “ample number of bullet points” with the concept of a cover sheet of accomplishments and embedded links to provide even more information than I could fit on the page.  I’m relying on bits stored and served from other sites to tell the story of Me; plus it recycles leftover bullet points I’ve thrown out of my technical presentations.  I’m all about recycling wherever possible.”

So there you have it – four totally different ways of building a DBA resume.

Brent Ozar

Brent specializes in performance tuning for SQL Server, VMware, and storage. He's one of the very few Microsoft Certified Masters of SQL Server, a published author, and a Microsoft MVP. He likes travel, Jeeps, Apple gear, jokes, and writing about himself in the third person. Read more and contact Brent.

Website - Twitter - Facebook - More Posts

Land a Dream DBA or Developer Job: Seven Questions to Ask

Looking back over all my years of interviewing and being interviewed, I realize that there are simple secrets to getting a great job offer.

The big secret is just this: ask great questions.

Interviewing Goes Both Ways

Asking thoughtful questions in your interview process, from screening to salary negotiations, makes you more powerful. It shows you’re engaged, informed, and in control of your career.It's easy to remember a great engineer.

A candidate who asks good questions automatically demonstrates that they’re selective, and they have choices.

But what do you ask? Here’s a checklist to go through before each interview to develop questions and remind yourself what to emphasize by your questions. By all means, write down your questions and take them with you.

1. Be the Candidate Who Loves to Learn

Ask at least one question about technology you’re unfamiliar with. Find out what technologies are in place at your potential job before an in-person interview and do an hour of research on those you don’t specialize in. When it comes up in the interview make it clear that you were inspired by the interview process to start learning.

Don’t pretend to be an expert in fields you don’t know about. Do be honest about your interests and show you have initiative. Ask questions about challenges they’ve hit and what informed their design and implementation decisions.

Before your interview, make notes on times when you faced a difficult task, learned something new, and were able to improve something. You’ll likely be asked questions about your experiences when you can tell your stories.

2. Ask At Least Two Smart Technology Questions

Most candidates just ask basic questions about what versions of software are running. This is a great chance to set yourself apart.

  • What are their pain points? This is something we care a lot about at Brent Ozar PLF, but we don’t mind sharing our mojo with you for your interview. This is the most interesting question you can ask: tell me where it hurts in your technology. You’ll want to get lots of detail on this. Make notes and follow up on different points they cover. Ask this question of different people throughout a day of interviews and compare the responses. I promise it’ll be interesting.
  • Are they leveraging their strengths? When you’re familiar with the products they’re using, think about the strengths of that product. Ask a question in a way that shows your knowledge. If you know that the JurgenPlufen can provide high availability when clustered, then ask if they’re doing that. If they aren’t, ask why– the reason will let you know a lot about their business. Keep your tone curious, not judgmental.
  • What major changes have they made? Over the history of the company, are there any revolutions in technology they can tell you about? How did they handle that change, and what would they do differently now?
  • Are they open to other technologies? This matters more to some people than others, but it’s an important thing to know. Is this a company that looks for the right tool to solve an individual problem, or do they prefer to standardize to narrow the scope of support? There are pros and cons to both ways, but you need to know which way they go in order to see how you fit in.
  • Have they tried the New Hotness? This is something you want to be a little careful with, unless you’re always about the new hotness and it’s important to work for someone who’ll support that. But if they describe a problem and you think there’s a fairly obvious newer product they could by or upgrade they could make to support that, ask about it. You want to find out why they haven’t gone there– are they slow to adopt? Short on people? Short on budget for new technologies?
Good questions show you’re not only a skilled technician. You’re an engineer who takes the initiative to find out how to improve an environment.

3. Ask A Question About Process

You want to know what processes are in place at a prospective employer. You also want to show that you’re responsible.

As a candidate for DBA positions I made it a habit to ask during phone screens, “Can you tell me a bit about your change management processes?” More often than not, IT hiring managers were thrilled that I’d asked. When I asked follow up questions it was clearly hard for them to sit still.

Focus on exploratory questions– don’t be critical. For a later interview, you should think about scenarios you might be in and create a hypothetical question. “What if we decided to change the Yak so that it had air conditioning? Can you walk me through what the process of making that change would be like here?”

Be ready in case the question is turned back around to ask what YOU would recommend— that should be a home run.

4. Ask About the Business

Before you ever talk to the company look for technical blogs, or any blogs written by employees. These are a great source for information about how things work at the company, and also a great source for questions.

It's good to ask about what's important. But not just about tuna.

This is what the competition is asking.

Always check out recent news articles for the company as well. Care about the industry. Make sure you have a few good questions about that market and where the company is going– if you make it to higher level interviews with executives, these will be particularly useful. If you don’t have much experience in that industry, it’s perfectly fine to ask questions like, “I haven’t worked for a dairy but I’ve read there are three major players. As a smaller company, how do you position yourselves in the milking industry?”

Your overall goal is to show you’re not just a technologist, you’re a potential invested employee.

5. Ask A Question that Shows You Listen

On a full day of interviews, you will be able to take information you get in one interview and use it to ask questions of other people. This is one of the great reasons to take notes in your interviews.

Be careful that your questions don’t seem to pit people against each other, or slight the previous person you talked to. You want to ask questions more like, “Harriet described the asynchronous processing she designed for the Femisphere system. Can you tell me how that works from an operational perspective?”

This shows you listened to Harriet and absorbed some of the concepts she discussed. Not everyone can do that! If you have follow up questions ready because you understand some of the operational challenges in the area, you’re in the catbird seat.

6. Ask A Question That Shows Your Strengths

Sometimes people ask what your greatest strengths are, sometimes they don’t. Figure out what your greatest strengths will be for that position, but do it so you can ask the right questions.

Let me get one thing straight: this isn’t BS. You want to pick a few real things that set you apart and make you satisfied about work.

Here’s some example questions:

“I like to identify big changes and drive them to completion in an active production environment. Is this a place where that’s encouraged? What are the barriers to large changes? What support is available?” Big changes work much better in some companies than others, and you want to know if you’ll always be holding your horses, or if you can make things happen. (If you ask this question, have two stories of how you’ve done this in the past ready.)

“I really enjoy specializing in certain areas of NERDERY and diving deep. This means I like to take four hours a week to do research. I can document what I learn and present it to the team. Would people be interested in that?”

“I am a generalist and I really enjoy reaching out to other teams and working out how components integrate. For example, would I have access to the configuration of the Gigabiggers and is their team open to having me sit with them once a week to learn about what they do?”

A question like this shows self-awareness, and it will tell you a lot about whether you’re going to sink, swim, or run for shore in that environment.

Practice, Practice, Practice

Interviewing is a bit like swimming. At first you have no idea how to do it, but you get thrown in the water and you learn it to survive. If you never practice then your technique suffers.

If you haven’t interviewed in a while or if you are changing industries and are not sure how you’ll do, ask for help. Get connected with bloggers or people in the industry on Twitter. Go to a user group. Ask people if they would be willing to do a 45 minute practice interview with you as the candidate. Listen to their feedback. When you practice, make sure you’re asking them questions as well as responding to questions.

Don’t be afraid to go on multiple job interviews. The downside is that interviewing is hard work, and it’s unpaid. The upside is that you can learn a ton, make great connections, and also find that you’re better at a lot of things than you ever realized.

Did You Land That Dream Job? What did You Ask?

I’d love to hear about your experiences as candidates and about the questions you asked. Did these make a big difference in your interviews? Do you feel that your questions set you apart from the competition?

Kendra Little

Kendra specializes in high availability and performance tuning. She is a Microsoft Certified Master in SQL Server-- the highest technical SQL Server Certification available. Kendra loves databases and software development more than long walks on the beach. Those cartoons in her blog posts? She draws 'em all. Read more and contact Kendra.

Website - Twitter - Facebook - More Posts

Knowledge in ____ is a plus

Got this email from a recruiter this morning and just had to share it:

But it's not required

But it's not required

That’s right, it actually says “Knowledge in ____ is a plus.”

No, they didn’t bother finishing the above sentence that starts with, “However the expectation is that this” but I’ll fill it out for you.  “However, the expectation is that this position will never be filled because the recruiter isn’t trying all that hard to begin with.”

And recruiters wonder why I let all unknown calls go straight to voicemail on my phone….

Brent Ozar

Brent specializes in performance tuning for SQL Server, VMware, and storage. He's one of the very few Microsoft Certified Masters of SQL Server, a published author, and a Microsoft MVP. He likes travel, Jeeps, Apple gear, jokes, and writing about himself in the third person. Read more and contact Brent.

Website - Twitter - Facebook - More Posts

Working With Recruiters

You’re mad as hell, and you’re not gonna take it anymore, so you decided to start looking for another job.  You put your resume on HotMonster, and within a matter of minutes, the calls from recruiters started pouring in.  Here’s what they’re going to ask, and how you should answer.

“Can you send me your resume?”

Your answer: “Yes.  What’s your email address?”

Have a nicely formatted Word doc with your resume ready to go at all times.  Right now, during the call, open a new email, type their email address in, attach the doc, and put your name in the subject.  Hit send.  Do not answer another question from the recruiter until you’ve hit send.  Don’t put anything fancy in the email body, don’t thank them for their time, just get your resume in their hands immediately.  You want them to read through it right away so that they can ask you any related questions while they’ve still got you on the line.

Don’t worry about what they’re going to do with the resume.  They’re going to stick it into their database and try to match you up with potential job opportunities.  If you match, they’ll call you up and ask for your approval to submit you for the job.

“What’s your current salary?”

Your answer: “I’m looking for a position in the $XX’s.  If the job has spectacular benefits – or none – we can adjust that number.”

Recruiters will follow up with, “Yes, but what are you making now?”  I can be a jerk sometimes, and I’ve been known to answer, “I’m getting paid really crappy wages, getting really crappy benefits, and doing way too much work, and that’s why I’m looking for a job.  If you wanna hook me up with another really crappy job, let’s just end this call now.  If you’d like to find me a job that I’d love to take, I’m looking for a position in the $XX’s.”

Tailor that answer to fit your (much more upbeat) personality.  If they keep asking for your current salary, there’s your sign.  I talked about this in my post about Salary Negotiations During the Interview.

“Can you make this change to your resume to match the job?”

Your answer: “Yes, as long as it’s honest.”

As a DBA, I did a lot of things in my day-to-day work.  When going after a particular job, a recruiter asked me to include my experience with using SQL Server Management Studio and installing SQL Server on local drives.  I hadn’t bothered to include that on my resume, because I figured every DBA does that – it comes with the territory.  The recruiter didn’t see it on my resume, and she wanted me to have the best shot possible at making a good first impression.  Good recruiter.

When going after another job, a recruiter asked me to say I had replication experience.  I didn’t.  She said, “Go fire up SQL Server, get the book out, set up replication once, and that’s all you need.  Trust me, you’ll learn on the job.”  If she was willing to lie to the company like that, then she’d be just as willing to lie to me.  Bad recruiter.

There’s a whole lot of gray area in between, and I can’t coach you on that.  Your mileage may vary.

“Can you come in for an interview?”

Your answer here depends on how bad you need another job.  If you need another job pretty badly, then yes, you need to go in to meet them, and you should bring a dozen roses.  On the other hand, if you’re happily employed and they’re trying to lure you into another gig, it’s up to you.  The recruiter might indeed have an amazing job for you, but that’s the exception rather than the norm.

Recruiters do want to meet you before they send you off to their trusted clients.  They don’t want to look bad for sending in a sloppily dressed mess who can’t string a sentence together without staring off into space.  I understand where they’re coming from, but at the same time, they don’t need to meet me if they don’t have a position available right now.  There’s one headhunter company that aggressively asks for face-to-face interviews without actually having any positions – they imply that they might have something, but they want to see you first.  They’re slimeballs, and they don’t respect your time.  It’s fair for you to protect yourself from those kinds of requests.

When I’m happily employed, my response is, “I’m not really looking right now, and I wouldn’t want to alienate my employer by sneaking off during work hours to meet with recruiters.  That would send my boss a really bad sign.  If you have something that sounds like a really good fit for me, go ahead and tell me about it now.  If it sounds really attractive, I’d be happy to meet you for lunch near my office, but let’s get the details out of the way first.”

“Are you working with any other recruiters?”

Your answer: “Yes, but I understand how the recruiting process works, and I commit to you that I will let you know whenever any recruiter tries to submit me at any company, no matter who it is.”

When Recruiters Meet

When Recruiters Meet

Recruiters make money – a lot of money – when they submit a candidate for a job, the candidate takes a job, and the candidate stays on the job for X months.  They make so much money that they will fight desperately for their fees.  If two recruiters submit the same person’s resume for a job at a company, the company may throw out the candidate altogether rather than deal with these cat-fighting recruiters.

Recruiters want you to work exclusively with them.  They’ll promise to work really hard for you, but they say you have to trust them and only work with them so that everybody’s protected.  But if you’re like me, you don’t know whether a recruiter has lots of connections or none.  I didn’t want to exclusively hook up with some junior recruiter who’d never placed anybody before. That’s why I wouldn’t stick with any one recruiter no matter how many beautiful promises they made me.  I talked more about this in my post, Recruiters are Not Your Friends or Your Enemies.

“Have you seen any positions out there that interest you?  I can get you in the door.”

Your answer: “I’ve just started looking, so I don’t know yet.  Have you seen any positions that are a fit for me?”

Recruiters have their own list of companies that they work with regularly.  When these companies need a person, they call their favorite headhunter first.  The bigger companies even have contracts directly with one specific recruiting company. Whenever a recruiter calls you, they know exactly what positions are available at their own clients, but they also want to submit you anywhere else that you might be interested.  They want to represent you everywhere, because they’ll make money off you no matter where they submit you.

If you get your foot in the door at a company, you can sometimes negotiate a signing bonus or a better salary if there’s not a recruiter involved.  This doesn’t always work – heck, it doesn’t even USUALLY work – but if you’ve got in-demand skills and a good business head, you can pull it off.  That’s one reason why you might want to submit yourself directly to companies that post jobs rather than asking your recruiter to submit your resume.

The recruiter will say they’ve got contacts inside the company – and they might.  They’ll say they’ll be able to push your resume to the top of the pile.  Even better, though, would be if you had your own contacts inside the company who can vouch for you personally.  This is why it’s so important for you to network, and I talked about that in my post on How to Get a Better Job.

“Can you send this job ad to your friends?”

Your answer: “Yes, as long as it includes a job description and a salary.”

If a recruiter’s desperate enough to ask for help from strangers, that means they’ve already exhausted their network.  Nobody in their network is interested in this particular job.  Maybe the demands are too high, maybe the salary is too low, or maybe the recruiter just flat out doesn’t have any friends.  All of those are danger signs.

Don’t simply forward bad jobs along to your friends.  Rather than having 10 people deal with a bad job, filter it out right away by asking for the job requirements and salary.  Most recruiters will balk, and that’s fine.  I talk more about this in my post about How to Reply to a Recruiter Email.

“If you pay me, I’ll work harder for you. Whaddya say?”

Your answer: “That sounds interesting. Can you give me some references from other people in my profession?”

There are good executive talent agencies out there at the C*O level.  You, my friend, are not at that level.  The techniques and contacts that executive agencies use to place their C*O friends won’t work to place their SQL friends.

If you’re still tempted, take the cost for this recruiter, think about how much time it would take you to make that money, and ask yourself what else you could do in that same time.  If it would take you 40 hours to make that money, why not take those same 40 hours and:

  • Give a presentation at your local user group
  • Write an article for a SQL Server web site like MSSQLTips or SQLServerCentral
  • Write a guest post for someone’s blog or do a podcast with them

All of those things will get you more exposure to the SQL Server community than hiring a talent agency, which brings me to my final point.

If you’re looking for a job, tell your trusted friends.

The SQL Server community members know what it’s like to look for a job, and they know other people who might be hiring.  They are your fastest route to a good job.  They’ll put your resume on the top of the pile, or better yet, you’ll be the only resume in the pile.  When you’re good, and when your peers know you’re good, they’ll create positions for you or they’ll sneak you right in without going through a whole public process.

Brent Ozar

Brent specializes in performance tuning for SQL Server, VMware, and storage. He's one of the very few Microsoft Certified Masters of SQL Server, a published author, and a Microsoft MVP. He likes travel, Jeeps, Apple gear, jokes, and writing about himself in the third person. Read more and contact Brent.

Website - Twitter - Facebook - More Posts

Salary Negotations During the Interview

On Twitter, Pat Wright posed a question:

Dangerous Interview Question

Dangerous Interview Question

My answer: it depends.  (Hey, I’m a DBA, right? Isn’t that always the answer?)  My favorite salary negotiation book recommends postponing the salary question as late as possible during the hiring process, but I don’t think that’s realistic.  I don’t go house shopping without looking at prices.

How to Give Your Salary During the Interview

When you’re desperate to get out of a bad job, you have to play ball.  They’ve got something you want.  You shouldn’t lie, but you shouldn’t give them an exact dollar amount, either:

“My current salary is in the seventies, but that’s part of the reason why I’m looking for other opportunities.  My current company doesn’t offer a competitive salary, doesn’t pay for training, and doesn’t share on-call rotations.  It’s a great place to get started and prove yourself under fire, but they haven’t been rewarding hard work.  I’m looking for a company where I can work hard, keep my skills sharp, and get rewarded for keeping their most valuable data safe.”

With that answer, they’re going to be hesitant to offer you a salary similar to what you’re making now, and they’re going to think about the training package.  During conversations like this, you have to make sure to point out that you’re willing to bust your hump.  Even better, build them a 30-90 day plan of what you’d like to accomplish as you take over responsibilities.

When Not to Reveal Your Salary

If you’re happy with your current job, and someone is trying to sweet-talk you into changing companies, then you’ve got the upper hand.  You have something they want.  In that case, I approach it with:

“Right now, I’m really happy with my salary, but it’s only a part of the picture.  I’m also happy with my manager, my coworkers, my training benefits, and the work we’re doing.  If I just wanted money, I’d be a hired gun consultant by now.  Let’s make sure the rest of our needs fit before we talk money.”

Segue into a discussion about how you’d like to go to industry conferences and why it pays for them to send you.  If they’re interested in having the discussion, then they’re interested in your well-being as an employee.  If they don’t even want to talk about things like that, well – you just learned a little something about them.

If they keep pressing for your salary, don’t give them your current number – give them the number it would take to get you to switch.  They’re going to balk.  They’re going to say the number’s too high.  It doesn’t matter what number you quote – they’re going to haggle.  If they’re a good company, they never overpay for anything.  They’re going to say you’re crazy and that you’re out of touch.  You can respond with:

“I know you’re used to paying a lot less – but are you happy with what you’ve been getting at those rates?”

I guarantee you that works, because they’re the ones who sought you out.

If you’re happy at your current position, stand your ground.  Several times in my career, I’ve had companies tell me my “switch” salary range was ludicrous, but they came back to me weeks or months later with a close offer.  If you’re good – and if you’re reading blogs like this, you’re good – then companies will hire idiots cheaper, get their databases shrunk, and come crying to you for help later.  Be confident in yourself, never stop learning, and never stop networking.

When to Lie About Your Salary

Never.  You’re an IT professional, and they’re a businessperson.  Guess which one of the two is closer to con artist.  You can’t lie anywhere near as well as they can, and they’ll sniff you out miles away.  The instant they know you’re lying, they’ll lose respect for you, and that’s the end of your happy employment before it even starts.

Brent Ozar

Brent specializes in performance tuning for SQL Server, VMware, and storage. He's one of the very few Microsoft Certified Masters of SQL Server, a published author, and a Microsoft MVP. He likes travel, Jeeps, Apple gear, jokes, and writing about himself in the third person. Read more and contact Brent.

Website - Twitter - Facebook - More Posts

What is Your Biggest Weakness?

David Stein (BlogTwitter) started a new game of blog tag by asking the classic interview question, “What is your biggest weakness?” I got a chuckle out of David’s answer – he loves to jump straight into code as soon as he hears the problem.  I’m right there with him on that one.

Me?  Only one – if I had any humility, I’d be perfect.

Okay, no, seriously, my biggest weakness is a mental hangup.  I only want to do things I can do better than anybody else very quickly.

I’m not giving you a sales pitch here.  I’m not trying to say, “I like to make sure I’m successful when I take on a project.”  That’s not it at all.  And I’m not saying I’m lazy, so you should hire me because I like to find the solution with the least amount of work involved.  I’m saying if I don’t think I can win often, I don’t want to bother playing.

In high school, I tried out for the tennis team.  I went to the first practice, left early, and never went back.  While I liked playing around with tennis, I didn’t like the thought of mindlessly training over and over and over in order to be the best.  I wouldn’t play if I was going to be a half-ass player, and I didn’t have the patience to train to be the one of the best players.  Piano, basketball, soccer, volleyball field hockey, you name it, I tried it and I wasn’t really interested.

The Only Player to Defeat Me

The Only Player to Defeat Me

Chess, on the other hand – I loved chess.  As long as I could think extremely fast, I could outplay the vast majority of my opponents.  Since I could beat most of the people around me, that made me more interested in playing stronger and stronger opponents, which ended up sharpening my skills.

I still take this same approach when I look at new technologies.  I’m not interested in learning SSAS, SSIS, or SSRS because without a whole lot of training and dedication, I’d just be one of the thousands of people who get the job done.  Nothing more, nothing less.  The skills I’ve accumulated over the years don’t really translate into making me an SSIS rocket surgeon like Andy Leonard.  On the other hand, when I had the chance to jump into SAN administration, I was all over it because it would make me a better DBA.  I didn’t know any other DBAs who’d also done SAN administration, so it would move me up a notch.

I’ve been lucky to find a career that works well for my strengths and weaknesses, but I don’t think the “production DBA” job will be around forever.  In the back of my mind, I’m already looking for my next career.  To give an extreme example, “social media expert” is the kind of job I could probably nail down easily with zero effort, but I can’t say that with a straight face, so it’s out of the question.

Time to tag a few other people: hey Andy Leonard, Jeremiah Peschka, Tim Ford, and Tom LaRock, what’s your biggest weakness?

Brent Ozar

Brent specializes in performance tuning for SQL Server, VMware, and storage. He's one of the very few Microsoft Certified Masters of SQL Server, a published author, and a Microsoft MVP. He likes travel, Jeeps, Apple gear, jokes, and writing about himself in the third person. Read more and contact Brent.

Website - Twitter - Facebook - More Posts

How to Get a Better Job

One of the most common questions I get goes something like this:

I’ve been working as an (insertJobHere) for a few years, and I’d like to start looking for another job as an (insertBetterJobHere).  How can I get started?

It depends on the phase of your career.

Phase 1: The Kindness of Strangers

When you’re just getting started – whether you’re fresh out of college or currently enrolled – you’re not going to know anybody.  You’re going to be cold-calling strangers, sending your resume to people you’ve never met, and hoping that you can knock ‘em dead in the interview.

Headhunter Company Car

Headhunter Company Car

Examples of hiring methods for Phase 1 are:

  • Newspaper and online ads
  • Recruiters
  • Consulting companies

There’s two problems with Phase 1.  First, you’re going up against complete strangers.  People in Phase 1 are desperate, and they’ll do some crazy stuff to beat you out in the job hunt.  They’ll work for less money, they’ll lie about their resume, they’ll use their mom as a reference, you name it.  Getting a better job when you’re going up against strangers can be a nightmare.

Second, you’re going to work for complete strangers, which can be a living hell.  You won’t find out that they’re raving lunatics until after you’ve already quit your current job and gone to work for them.  Every time I’ve gone to work for strangers – every single time – I’ve regretted it within a matter of months.

Strangers hire other strangers when they run out of friends willing to work for them.

Phase 2: The Buddy System

After you’ve been working for a few years, going to local user group meetings, and survived a few reorgs, you’re going to know a lot of other people working in your same field.  You’ll even know people in unrelated fields.  DBAs meet project managers, end users, report writers, developers, and so on.

Everybody Loves the Buddy System

Everybody Loves the Buddy System

When it’s time for you to start looking for another job, you can put out the word among your contacts.  Because they’ve worked with you before and they know what a kick-ass worker you are, they’re likely to vouch for you.  They’re likely to tell you about jobs before they go into Phase 1 recruitment, because they’d rather hire you than a stranger.  You’re a sure bet, because you’re doing such good work.

The only way to get from Phase 1 to Phase 2 is staying in touch with people.

I can’t emphasize this enough – if you don’t learn to network, you’re going to be permanently stuck in Phase 1.

Networking sounds so slimy, but it just boils down to this: meet people, and keep in touch with the ones you genuinely like.  I used to think networking meant rubbing shoulders with greaseballs who were trying to sell each other stuff, but that’s not true at all.  Just keep in touch with people you like, and go to the places where they hang out to meet more people like them.  For database professionals, that’s the upcoming PASS Summit.

Befriend Buddies, Not Just Bosses

One fast way up the corporate ladder is to hitch your wagon to a rising star.  If you do great work for a great boss, you can both go places quickly.  I’ve taken that approach a few times in my career, and it’s served me really well.  I remember getting a call from one boss as soon as he’d changed companies, and he said, “I know what you’re making now.  I’ll give you an extra $X to come work for me at the new shop, and you know I’ll be good to you.”  Sold.  However, that’s not the only way up.

The programmer next to you today might be the CIO at another company tomorrow.  A few years ago, Matt Mullenweg was just another guy I ran into at Houston Wireless meetings.  I had no idea he was building something cool in his spare time, and since then, that little blogging platform has raised tens of millions of dollars in funding.

Look around you right now.  Your coworkers and customers are the only ones who will take your career to the next level, regardless of how unskilled and antisocial they seem.  Even if they’re really, really bad at what they do, it’s your job to make them look better and leave a permanent positive impression on them.  They might be your key to a better job down the road.

If you wait to network until you need a job, it’s too late – and you’ll be stuck in Phase 1.

Brent Ozar

Brent specializes in performance tuning for SQL Server, VMware, and storage. He's one of the very few Microsoft Certified Masters of SQL Server, a published author, and a Microsoft MVP. He likes travel, Jeeps, Apple gear, jokes, and writing about himself in the third person. Read more and contact Brent.

Website - Twitter - Facebook - More Posts

What I Want Versus What I Can Afford

I got an interesting comment on my article about the Top 10 Interview Questions for Senior DBAs.  AngryDBA said:

“Man, I don’t mean to sound harsh but..you’re an expert DBA? I’m guessing you wouldn’t survive one of my interviews. I only expect the candidates to get 50%. I’ve had them all too. PhDs, Masters in blah-blah-blah, Captain of the Patterns Team at Yale majoring in C#, writing joins since she was in Pampers. Uh huh.”

Answering this requires more than just a comment.

My Dream House Checklist

My Kind of Yard

My Kind of Yard

I use RememberTheMilk to store a lot of stuff, including my list of things that I’m looking for in my dream house. I’m planning long term, baby! It includes things like:

  • No ground-level windows – we don’t like people looking in or breaking in.  We like high windows on the ground floor (like 7′ up).  The other floors can have floor to ceiling windows, though.
  • On the water, but no nearby vegetation – we hate bugs.  Ideally, there wouldn’t be a plant on the property.  I’m not kidding.
  • Within walking distance of at least 2 restaurants – Erika and I really enjoy eating at restaurants.  It’s nice to have other people take care of everything once in a while.  Okay, often.
  • Gadget nook in the entryway – I like having my electronic gear near the door so that I can grab it on the way out.  Ideally, I’d have an inset nook in the wall with electric outlets, and the whole thing would be concealed so that wires weren’t dangling all over the place.
  • Lots of AC ventilation in the kitchen – we love a really cold house.  I’m talkin’ 65 degrees.  Erika loves to cook, but the kitchen always gets hot, because no house’s AC is ever designed to pump that much cold air into the kitchen while keeping the rest of the house tolerable.  Speaking of which….
  • Very powerful but very quiet AC – I don’t want to hear the air conditioning kick on and off, but I want the house at 65, and no, the answer isn’t leaving the air running full blast 24/7.
  • Silent garage door openers – I get up early in the morning and I like taking drives.  I hate it when the garage door opener vibrates in a way that you can hear it in the bedroom.  (Yes, there’s a lot of silent items on this list.)

I could go on and on – the checklist has over 20 items on it at the moment.  That doesn’t include my set of tear sheets with all of the interior design features and furnishings we’ve liked over the years, too, or my Delicious bookmarks tagged dreamhouse.

My Current Housing Checklist

My Kind of Price

My Kind of Price

Back in the real world, since I’m not making seven figures (yet), my housing search checklist is decidedly more utilitarian:

  • Washer/dryer connections – I don’t want to go to a community laundry facility.
  • Good phone/cable wiring – I need high speed internet access and old building wiring presents problems with that.
  • Two parking spots – we’re looking at downtown one-bedroom lofts, and those don’t always come with two spots.
  • Low crime rate – I don’t want to have to carry a gun when I walk the dog.

Notice the difference?  Champagne tastes, beer budget.  I can’t go asking about waterfront property with what I’m payin’.  Asking about waterfront property when I can’t afford it doesn’t make me look good – and in fact, my real estate agent is pretty quickly going to start rolling her eyes when I call.  “Here comes this bozo again, asking about waterfront property for fifty large.  What a jerk.”

How This Relates to Database Administrators

If money wasn’t an object, my interview question list would simply be:

  • Is your name Paul Randal?

However, money is always an object.  Even when you think money isn’t an object, you have to ask yourself if you would hire one super-expert-senior DBA, or hire two solid but not super-expert DBAs.  My DBA interview questions aren’t designed to separate Paul Randal from the rest – they’re designed for companies who need to find somebody reliable without spending a fortune.

One of my favorite sayings is that there’s two kinds of questions: the ones designed to find out how much the other person knows, and the ones designed to show off how much you know.  Showing off in interviews doesn’t impress the candidate – and in fact, it does the exact opposite.  Humiliating a candidate makes them bitter about your company before you even make them an offer.  If your candidates rarely achieve 50%, then you’ve got a disconnect between your tastes and your budget.

Start asking questions that your candidates might be able to answer.

Otherwise, you’re just showing them you’ve got a lot of DBA-ness.

Brent Ozar

Brent specializes in performance tuning for SQL Server, VMware, and storage. He's one of the very few Microsoft Certified Masters of SQL Server, a published author, and a Microsoft MVP. He likes travel, Jeeps, Apple gear, jokes, and writing about himself in the third person. Read more and contact Brent.

Website - Twitter - Facebook - More Posts

How to Get a Junior DBA Job – Part 2

Yesterday I talked about why companies aren’t hiring junior DBAs, and today I’ll talk about how you can get in the door anyway.

Companies are Cheap, and DBAs are Expensive

Even in a healthy economy, companies want to get a bargain.  They want to hire an experienced senior database administrator for junior DBA wages.  They think they’ve got something special – a great work environment, flexible working hours, nice plants in the lobby – and that it offsets the lower wages.  It doesn’t: good senior DBAs get good money, and have their pick of companies.

Some companies take the approach of hiring remote DBAs who telecommute.  I have a blog series coming up about getting & keeping a job as a telecommuting DBA, but that doesn’t work for junior DBAs.  Juniors need mentoring and training that’s difficult to get in a home office environment.  For your first DBA job, don’t be tempted to apply for a remote job, because you’re setting yourself up for failure.

Instead, throw your hat in the ring for local senior DBA jobs.  It’s not career suicide: it’s a case of the company asking for something unrealistic.  They may not get the candidates they want for the price they want to pay, and that’s your chance to get your foot in the door.  Don’t exaggerate your reputation, of course – be honest about your skill level and your experience, but at the same time, don’t sell yourself short.

You’re Working with SQL Server, Right?

I got my start as a developer and as a network admin (here’s the story).  When I went to look for my first pure SQL Server job, I didn’t have much on my resume and I didn’t really think I was all that qualified.  If anything, I underestimated the bejeezus out of what I put on the resume.

When I started hiring other DBAs, though, I remembered my own experience.  As a result, when I interviewed DBA candidates, I had a checklist of skills that I’d ask them, like:

  • Have you ever had to restore a single table’s contents?
  • Have you set up log shipping, or done troubleshooting on it?
  • Have you ever built a server connected to a SAN?

Go pick up a SQL Server administration book, look at the table of contents, and check off everything that you’ve actually done.  Even if you’ve only done it a few times, put it on your resume and explain that you’ve dabbled in it, because it’ll give you a big edge over the other candidates.  Don’t say that you’re an expert on the topic, by any means, but the fact that you’ve done it is a plus.

More often than not, I’d hear candidates answer, “Well, yeah, but hasn’t everybody done that?”  Actually, no – some candidates haven’t.  Every single skill that you performed in production – not in theory – is another reason why you might get the job.  Even if you’ve only done it once a quarter for a year, that means something.

Senior DBA

Senior DBA

How Long Have You Been Doing It?

Did your boss ask you to start backing up a SQL Server a year ago?  Last year, did you start restoring the production database onto your desktop for development testing?  Did you start working on making stored procedures a year ago?

Presto, you have a year of experience.

I can almost hear the angry emails coming in now from really senior DBAs who do this stuff full time, nonstop, for a living, but they’ve forgotten how junior-level experience works.  People don’t get handed the keys to the enterprise on Day 1 and start some kind of master clock.  Experience happens gradually, almost imperceptibly.  There’s no knighting ceremony where the CIO taps you on both shoulders with a laser pointer.

This is why so many junior-level DBA positions ask for a year or two of experience: they’re expecting to hear from developers and sysadmins who’ve been dabbling with database tasks over time, getting their feet wet.  I don’t want to hire somebody who’s never seen SQL Server Management Studio: I want to hire a developer who installed SSMS a year ago and has been dabbling with it ever since.  He may not like going in there – it may scare the pants off him – but as long as he’s been going in there grudgingly and tapping his terrified fingers on the keyboard to get his job done, then that’s a plus in my book, because I’ll train him the rest of the way.  DBA training never ends.

Training and mentoring is the way junior DBAs become senior DBAs.  In the last post of the series tomorrow, I’ll talk about what you should – and shouldn’t – expect in the way of training from a new employer, and how that affects your asking price.

Part 3: Getting DBA Training On the Job

Brent Ozar

Brent specializes in performance tuning for SQL Server, VMware, and storage. He's one of the very few Microsoft Certified Masters of SQL Server, a published author, and a Microsoft MVP. He likes travel, Jeeps, Apple gear, jokes, and writing about himself in the third person. Read more and contact Brent.

Website - Twitter - Facebook - More Posts

How to Get a Junior DBA Job – Part 1

So you’re hearing all the fun that DBAs are having on Twitter and around the intertubez, and you’re wondering how to get in on the fun.  Maybe you’re a developer or a network admin, and you’ve been learning about SQL Server from books and from peers, and you’re starting to look around for your first Junior DBA job.

Where Are the Junior DBA Job Ads?

Search for the terms “junior dba” or “senior dba” on national job sites, and the results are dramatically different:

To make matters worse, drill into the requirements for some of the so-called junior positions and they ask for:

  • “2+ years of hands-on experience administering customer-facing databases”
  • “Minimum 2 years of information technology experience is required”
  • “2 years of database administrations experience including installation and configuration”

These ads make me chuckle because a DBA with two years of hands-on experience isn’t looking for his next junior DBA job – he’s aiming for his first senior DBA job.  People don’t aspire to make lateral moves – they aspire to move up the ladder.

So we’ve started to establish that it’s not just you: there aren’t junior DBA ads sitting around waiting for takers.

Why Aren’t More Companies Hiring Junior DBAs?

Databases are among a company’s most valuable assets.  They hold sales data, payroll data, information about customers and competitors, and all kinds of proprietary data.  Companies guard this data closely, and they don’t want just anybody stepping up to the server to handle backups, restores, and security configuration.

Companies may be willing to hire junior developers instead – for some reason, they don’t have a problem giving a fresh-out-of-college person access to all the data.  But when it comes time to actually managing the data, they want someone experienced.

As a result, even when a small company with a handful of SQL Server instances goes shopping for a DBA, they want someone experienced.  They want to hear from the candidate, “Yes, I can do what you need – I’ve already done this for a much larger shop, and I’ve got experience handling this sort of thing.”  They sleep better at night knowing their DBA is not stressed out trying to figure out how to automate backups for the first time.

Every now and then, big companies will actually hire junior DBAs.  This mostly happens when they’ve already got a crew of senior DBAs, but here’s the odd part: they don’t have anyone internally that wants to get promoted into the DBA team.  That’s very peculiar, because in companies large enough to have DBAs already, they often have people in other teams who want to become DBAs.

Know Your Competition: Other Junior DBA Candidates

The few available junior DBA positions attract a few kinds of candidates:

  • Developers with a year or more of SQL Server programming experience who’ve decided they want to focus on SQL Server instead of development.  They’ve written code that stores data in SQL Server, so they know the basics of T-SQL or LINQ, understand the basics of data models, and maybe they’ve even done a little SQL Server administration on their dev boxes.
  • Windows administrators with a year or more of Windows experience who also want to switch their focus.  These people know hardware, know the basics of performance tuning, have backup/restore experience, and maybe they’ve even built a cluster or two.  They might have even built SQL Servers, but they haven’t been working on SQL Server full time.
  • SQL Server DBAs who’ve been let go, and they’re desperate.  They might have worked for a company in financial trouble, they might have been drinking on the job, who knows.  These are your most dangerous competitors, because at first glance, their resumes kick sand on your resume.
  • College grads or training grads with no experience.

If you’re in that last category, I gotta be honest: you’re screwed.  Go get a job as a junior developer or a junior Windows admin first, and then work your way into database administration.  There is no classroom training that’s going to convince a company to hand over the keys to their data on your first day in the office.  You may see ads for certification programs that promise to make you DBA-ready within a week for a few thousand dollars.  It won’t get you the job – at least, not when you compare yourself to the competition.  After you’ve gotten started in a development or sysadmin position working around SQL Server, come back here and continue reading about how to take it to the next level.

Getting Promoted is Easier than Getting Hired

If you’re a developer or Windows admin, try to get promoted internally rather than switching companies.  You’ve already built up a level of trust with your coworkers.  Make yourself the natural candidate by actively going after the position before the position even exists: volunteer to spend time with the DBAs, help them during scheduled outages, or just ask if you can sit around and watch during the weekend maintenance windows.  Bring coffee, donuts and bacon, and be the most pleasant (but not over-the-top) person in the room.

If you’ve already got a job in close proximity to SQL Server, this is one of the times where getting certified in SQL Server without getting the job first does make sense.  I’ve blogged about how certification is the icing on the cake: don’t get certified without at least some vague experience in SQL.  Developers and Windows admins will gain knowledge from the certification training process, and it’ll buy them a little bit of credibility in the eyes of the DBA team.  Not a lot – but some.

If you dislike the DBA team at your company, I’ve got bad news: you’re probably going to dislike most DBA teams, and switching companies isn’t going to make things better.  However, if you’re absolutely determined to jump ship, there’s a few things you can do to make the hiring process easier, and I’ll explain those in my next post.

Part 2: You CAN Get DBA Experience Without a DBA Job

Brent Ozar

Brent specializes in performance tuning for SQL Server, VMware, and storage. He's one of the very few Microsoft Certified Masters of SQL Server, a published author, and a Microsoft MVP. He likes travel, Jeeps, Apple gear, jokes, and writing about himself in the third person. Read more and contact Brent.

Website - Twitter - Facebook - More Posts