Now that I have a couple of confirmed speaking engagements, I figured that this was a good time to update my upcoming speaking schedule!
These engagements are confirmed. I don’t have exact dates or times for either of these (and I might not for a little while); all I know is that these events are confirmed, and I am definitely speaking at them!
Note: these are both virtual events. To the best of my knowledge, they are both free to attend (well, I know PASS Data Summit is, anyway), so check the links for more information and to register.
All my presentations (so far) are professional development sessions, so feel free to register for these, regardless of whether you’re a techie or not. Don’t let the “technology” conferences scare you!
For those who’ve been following along, PASS Data Community Summit is the successor to PASS Summit, the worldwide conference for data professionals! It has been described as “the Super Bowl of SQL/Data Saturday” (I, personally, have described it as being “the All-Star Game of SQL Saturday“)! This is the third straight year that I will be speaking at this conference. Being selected just once is an honor. Being selected twice is amazing! Being selected three times? I suppose that makes me a star!
I will be doing my presentation about joblessness and unemployment, titled: “I lost my job! Now what?!?” This talk is geared toward people who are out of work and seeking employment; however, if you’re a student trying to break into the professional ranks, or even if you’re looking to make a change, you can get something out of this presentation as well!
Yesterday, a good friend of mine texted me, asking me to send him my resume. This particular friend works for a major nationwide consulting firm. I won’t say which firm, but I will say that it’s a household name. In his position, he is often in a position to hire, and he is well-connected.
After reviewing my resume, he texted me back again, saying “let’s talk. I have some ideas that might make your resume even better, and I want to make sure those changes are implemented before I pass your resume along. Do you have time to talk tomorrow?”
I got off the phone with him a little while ago, and what he had to say was eye-opening — and in our conversation, I managed to improve my resume even more.
His advice (and I’m paraphrasing here): “what projects are you the most proud of? As a hiring manager, that’s something that stands out to me. Your work experience looks good, but everything you mention is general day-to-day activities. You don’t really list much in terms of a specific project you worked on. For example, something like ‘I designed such-and-such app that helped people do their work more efficiently by whatever-it-did-to-help-them, saving the company millions of dollars’ is something that would stand out to me. What are you the most proud of? Make sure you highlight that in your resume.”
I did raise a concern. I told him, yes, there is a project that immediately pops into my head, but it goes back many years; in fact, it’s a project I worked on for a company that goes outside of the past ten years. He told me, “that doesn’t matter” (he also relayed to me a project that he was proud of that took place over twenty years ago). “I’m proud of that, and I still include that in my profile.”
I had my resume file open in front of me during our conversation. While we were talking, editing ideas started forming in the back of my head.
His suggestion was to include these projects in my work experience, but I decided to leave that section alone. Instead, I decided to rewrite the Career Summary section of my resume. I wanted to do it this way for a couple of reasons: one, this appears at the top of my resume and would be the first thing that prospective employers read, and two, rewriting the Work Experience listings would have been a lot of work, and could have potentially resulted in document restructuring issues.
In terms of projects in which I take pride, I immediately wanted to mention a server inventory database that I built years ago; whenever anyone asks me about a professional project of which I am the most proud, this is the one that I always think of immediately. I also wanted to mention my involvement with recovery efforts after 9/11 (my Disaster Documents presentation is based on this experience), so I included that on the list as well. I also wanted to include a project that was much more recent, so I included a user guide that I wrote from scratch, including developing the Word template for it (additionally, I wanted to highlight that it was for a SaaS application). Finally, I also wanted to make mention of a project in which I learned about MVC concepts (unlike the other projects, this one does appear in my Work Experience section).
There were also a few other things I wanted to do with my Career Summary section. A while back, I came up with my own personal tagline, but it did not appear in my resume. I wanted to make sure it was included. Additionally, whenever I submitted my resume, I was finding that I was experiencing confusion on the part of prospective employers. I was (and still am) targeting primarily technical writer positions, and I was often questioned, “with all this technical experience, why are you targeting tech writing jobs?” I wanted to restructure it in such a way to explain that I was drawing upon tech writing as a strength, without sacrificing the fact that I had a technical background.
Before I made my edits, the Career Summary section of my resume looked like this.
When all was said and done, this is how it came out.
Additionally, I had to make changes to other sections of my resume, entirely for formatting purposes. I wanted to ensure that it would fit on two pages. I consolidated a few sections of information that, while helpful, I didn’t think would be as important.
I made the changes, updated my resume files (Word and PDF), and resent it to my friend. As of this article, I’m still waiting to get his feedback (he texted me to say he was busy, but would look when he had the chance), but personally, I like the way these changes came out.
(Edit: I heard back from my friend; his advice was to keep the accomplishments to one line each. In his words, “make it punchier.”)
You don’t necessarily have to do this within your Career Summary section; this was how I decided to approach it. If you can incorporate these highlights into your work experience listings, then by all means, do so.
I want to mention one thing when adding “proud accomplishments” to your resume. There is a fine line between talking about accomplishments you’re proud of and bragging about things to stroke your ego. Keep in mind that the purpose of a resume is to get you a job interview. Talking about projects you did that made a difference can help with that effort. Bragging about things you did (or didn’t do) will not. Nobody cares about your ego; they care about what value you can bring to their organization.
So what are your thoughts on these changes? Feel free to comment on them, especially if you’re a recruiter or a hiring manager.
I’ve spoken to a number of friends about my frustration regarding the job hunt (going nine [!!!] months — and counting). I’ve wondered, at times, whether one of the reasons why I’ve been constantly rejected is my age.
Ageism — a.k.a. age discrimination — is, of course, illegal. But when it comes to the job hunt, it’s nearly impossible to prove. I’ve spoken with a number of my friends and colleagues who believe that it not only exists, but is prevalent. (Before anyone decries me for this statement, no, I don’t have any facts to back this up; this is merely what has come up in conversation. Maybe someone who knows more about human resources can explain this better than I can.)
In any case, one piece of advice I’ve received is to only include the last ten years of experience on my resume. That’s well and good, except that I have a lot of relevant experience that goes back a lot more than ten years. As a technical writer, I want to keep all my listings consistent. How do I go about keeping these experience listing on my resume without listing dates?
The solution: I divided the work experience on my resume into two sections. Under my Work Experience heading, I listed my experience going back to 2009 (slightly more than ten years, but for my own purposes, it works). The second section uses a heading labeled “Previous Work Experience (before 2009),” under which I list my positions — without dates — that I held before then.
It seems like a good solution for obfuscating older experience dates that might reveal your age. However, also be wary of other parts of your resume that might also indicate how old you might be. For me, personally, that section was my education. Before I revamped my resume, my bachelors and masters degree listings included my years of graduation. Those years were also removed as well. Prospective employers just need to know that I have those degrees; they don’t have to know when I got them.
So, if you’re a job hunter who’s older than, say, 35, hopefully this tip will help you with your job search and combat any ageism that might exist.
A vast number of people, myself included, are looking for work. I will do my presentation titled “I lost my job! Now what?!?” this Saturday. I will discuss topics that include, among other things, dealing with the emotional impact, resumes, interviewing, and things you can do to hold yourself over during this period of uncertainty.
I had a conversation today with a recruiter — technically, it was an interview, but the way we spoke, it was more of a conversation between an agent (her) and a client (me) — who gave me some advice regarding my resume. I came away from the conversation with a few insights, and I’d like to share those insights here. This is not the first time I’ve written about resumes. I continually learn something new about them.
We left the conversation with her giving me a homework assignment: revamp my resume to incorporate what we had discussed.
Probably the biggest takeaway was to rethink how I was presenting my resume. I shouldn’t have the mindset of a job seeker telling prospective employers to hire me. Rather, I needed to approach it as a marketer. I’m marketing a product. The product I’m marketing is me.
This mindset is important. When you’re trying to present yourself to an employer, you feel a need to impress them with your extensive experience, everything you’ve done, and the many reasons why the employer should hire you. But if you’re marketing yourself, the thought process shifts. Instead, you’re advertising yourself and your skills. “Hire me! Here’s why!” She told me that it’s okay to not put everything on your resume — not lie, mind you, but rather, not throw in the kitchen sink when putting your resume together. Just highlight the important selling points. If they want to know more, they can refer to your LinkedIn profile — and maybe even call you in for an interview (which, of course, is the purpose of a resume).
I found this to be profound, because this is a point that I espouse as a technical writer, and yet I don’t practice what I preach when it comes to my resume. I am a believer in not necessarily including everything on a document. And yet it never occurred to me to apply my own technical writing skills to my own resume. Don’t try to provide every little detail. If they’re interested, they’ll ask for more (and if they want more, they can look at my LinkedIn profile).
I mentioned ageism as a concern, and a possible reason as to why I haven’t had a job nibble in seven months. (I believe ageism exists in the job hunt; it is illegal, but is nearly impossible to prove.) In the same vein of not needing to include everything, one of the takeaways was to only list positions for the past ten or so years. One of my concerns was that my experience before 2009 would likely reveal my age, but at the same time, it was all professionally relevant, and I didn’t want to leave it off. She suggested an idea that had never occurred to me: list the jobs (employer and title), but leave off the dates. Just say “here’s where I worked before 2009.” Again, if an employer wants to know more about those positions, check out my LinkedIn.
As an afterthought, after I’d removed the dates from the older positions, I still had a potential age identifier on my resume: my educational experience included my dates of graduation. Sure enough, in my latest resume revamp, my graduation dates will be removed. Employers just need to know I have a Masters degree; they don’t have to know when I got it.
The recruiter also asked me another question: what accomplishment at each position are you proudest of? I have to admit that that was a good question. She said that it was a question that should be asked for every listed position, and the answer for each was something that should be included on the resume.
I was told, be your own client. Market yourself. When it comes to marketing yourself, you’re your own blind spot. Only when it was pointed out to me did I know that the blind spot was even there.
After this weekend, Christine wrote this ‘blog article. I haven’t yet had a chance to fully process it (as I’m writing this, I haven’t had my coffee yet, and my brain is still in a fog), but what little I did process, I found interesting.
I intend to scrutinize this more when I’m a little more awake. And I suspect I’ll be making some adjustments to my presentation.
INTRO: Recently I attended a presentation where a commonly held belief was repeated and I feel the need de-bunk this. The speaker stated “75% of applications are rejected by an ATS (applicant tracking system) and a human never sees them…”
First, I want to point out that recruiters will tell you this is false. As the main users of ATSs, recruiters have extensive experience and years in talent acquisition, and will tell you they hear this all the time and they cringe upon it’s utterance. But if you want to know my opinion on why this “myth” has infiltrated the job seeking world, scroll past all the research and jump to the end.
MY RESEARCH: Secondly, let’s track down the origin of this false statistic. The speaker I heard it from cited topresume.com. So I did some digging:
This upcoming Saturday, October 3, I will be speaking at SQL Saturday #1003, Memphis. Of course, because of pandemic restrictions, I will not actually be traveling to Memphis; SQL Saturday #1003 is virtual, and I will be presenting from my home office in Troy, NY.
(In a way, it’s too bad I won’t be in Memphis. I’ve heard good things about Memphis barbecue!)
A lot of people (myself included) have lost their jobs during the pandemic, so it’s especially apropos that I will be presenting my session titled, “I lost my job! Now what?!?“
If you want to check out my (and other great) sessions this Saturday, use the SQL Saturday #1003 link to register.
This morning, one of my LinkedIn contacts (a recruiter for a consulting firm) contacted me about a potential job opportunity. She sent me the description. The position in question is for a senior programmer analyst for a local firm. They’re seeking someone knowledgeable about .NET, XML, and SQL. I gave her a call, and we had a very good conversation about the opportunity. She asked me to tailor my resume to more closely match what the client sought, and that she would do whatever she could to get me in to speak with the client. I also told her to let the client know that if this position was not a good fit, I would also consider other opportunities with the client, if any were available.
These skills do appear on my resume, and I do have experience with these technologies. At the same time, however, I also make no secret that my career seems to be moving away from hardcore technical development and more toward soft-skill professional development that involves communication, writing, and visual design. It’s been at least a couple of years since I did much in the way of serious application development work, so any technical skills that I’ve accumulated over the years are likely to be rusty.
I did mention this as a concern to my recruiter associate, and she told me that she appreciated my honesty and openness. I wanted to make clear that while I do have that experience and background, the client, if by some chance they do hire me, will not be getting a technical guru or expert, and they shouldn’t expect one. What they would get is someone who has the diverse technical skill set who, while not necessarily being an expert in them, knows enough to mostly get by and at be able to sound like he knows what he’s talking about, not to mention someone who’d do his best to make sure things got done.
I mention this because in my current job search, this is the type of position to which I likely would not have applied, had my associate not contacted me. I’ve been applying primarily for technical writer and business analyst positions. That said, I am also open to programmer analyst positions should the right opportunity come along.
I did mention to my contact that I had nothing to lose by applying to this position. If the client decides to talk to me, it’s another potential opportunity to pursue. If not, at least I gave it a shot.
The moral of the story: even if a position doesn’t appear to be what you’re pursuing, if you believe you’re capable of doing it, go ahead and apply for it. You never know. Nothing ventured, nothing gained.