Job hunting for database professionals

Like most people, I’ve changed jobs a few times in my life. My path from teenage grocery store cashier to Database Architect was a complicated and multi-step journey. During that journey, I’ve made some good decisions, and some bad decisions. If you’re like most tech folks, you’ve probably had a similar experience.

I recently changed jobs, and I thought it was a good time to share some thoughts on the topic of job hunting.

 

Why is my advice worth listening to?

The job where I fit bestI’m not a recruiter. I’m not a Human Resources professional. I didn’t even stay at a Holiday Inn Express last night. I’m just a database professional. I’m not that different from you.

Finding a new job is hard. At every turn, it’s a lot of work: finding a job, interviewing, negotiating. I don’t know anyone who likes doing it. I do know lots of people who struggle with various parts of the process.

I want to share my experience, my thoughts, and my opinions. Hopefully, you can learn from my experience (good and bad). By sharing my experience, hopefully I can make life a little bit easier on you the next time you’re job hunting.

What’s my plan?

I don’t really have a plan. This isn’t a formal, well-planned series of blog posts. I’m going to tell a few success stories, and a few stories where I was <ahem> less successful. I’m going to share some advice from the internet, and talk about why it’s good or bad. As I post those stories, I’ll come back here, and update this post as an index, with links to the other posts. Go ahead and bookmark this post now, I’ll wait.

Got it bookmarked? Good.

Want to help?

Use the comments section if there’s something in particular that you’d like to hear my thoughts on. I have some topics I’m planning to address, but since this isn’t a pre-planned series, your input will help me plan future posts.

 

Further reading

2 Trackbacks & Pingbacks

  1. Job Hunting – Curated SQL
  2. The most important resume tip - Andy M Mallon - AM²

Leave a Reply