I Don’t Interview Well (Part 2)

Last week I interviewed for a new position in the office.  As I’ve mentioned before, I’m not very good in interviews.  As of writing, I have not heard back whether I’m moving to the next round of interviews (successful candidates will have a further interview with the manager and an interview with the College President), however I’m not overly optimistic that I’ll be selected.

When I say that I don’t do well in interviews, I have to own the fact that not doing well in interviews is wholly my fault.  For last week’s interview, I spent time studying for the position and about engineering educational accreditation processes, and constructing a presentation about the key domains of the accreditation process, but I spent next to no time preparing my answers to the interview questions themselves.  My preparation was largely to watch two mini-courses on Lynda.com on interview prep, and to take notes on some case examples I could bring up for achievement or behaviour questions.  Only  the night before, for about twenty minutes, did I have my wife run some sample questions past me.  My lack of preparation and practice on answering questions is entirely on me.

I did have one insight, though, that gives me some solace.  In thinking about how poorly I thought my interview went, I reflected on how many interviews I’ve done in my career to date.  This was my 5th interview, and only my third interview for a non-entry level position.  I  realized that one of the reasons why I was so unprepared, and why I didn’t spend more time prepping my answers is that I don’t know how to prepare for a mid-career interview.  The phrase “what got me here won’t get me there,” comes to mind in this scenario.  I don’t yet have a clear picture of what I should be aiming at in interview questions.

I know the mechanics of the interviews – I should be demonstrating value to the employer and painting a picture of what I can do for them.  I should consider what their questions are trying to elicit from me and tailor the response accordingly.  When giving a behavioural- or achievement-based answer, make sure to ground the example using the STAR method (situation, task, action, results).  Link strengths back to the job competencies, and identify weaknesses from the job competencies that I’m actively addressing.  I know these facts, but because I lack confidence in myself I have a hard time selling it to others because I don’t believe it for myself.  No amount of resentment towards the dog-and-pony show process will elevate me above other candidates.

If I want to succeed, I need to get better at playing their game.

Stay Awesome,

Ryan

Advertisements

The Value of a Myers-Briggs Test

There seems to be a publishing cycle, where every year a new slew of articles are released to damn personality tests, such as the Myers-Briggs.  Lifehacker published one recently, and a book was released at the end of summer about the mother-daughter duo who created the assessment tool, which can be paired with a book released a decade ago discussing personality tests more broadly.

A few years back, I was thinking about my career, and I happened to take the test.  According to it, I’m a INTP, the Logician, an introverted big-thinker who is logical but adaptive.  A year later, I took the test again and I drifted into ENTJ territory; apparently in that time I became more extroverted and more rigid in my planning.

This, of course, is the biggest issue with these personality tests.  They tend to overly rely on generalizations of fluid behaviours and attitudes.  People rarely have stable traits over time, and the test tends to loosely clump these together in attempt to create a meaningful picture.  In this, the Myers-Briggs is nether reliable nor valid from a scientific point of view.  As the Lifehacker article points out, along with many others, it’s dangerous when you base decisions on the conclusions drawn from these tests for things like dealing with others or hiring employees.  The best thing you can do, the article claims, is to use it as a fun conversation starter and nothing more.

But I find value in the tests for another reason.

Humans are drawn to stories.  We like crafting narratives to explain events and give meaning to our lives.  While we would want our stories to align with true accounts of history or phenomena (a book I recently bought argues that it’s not possible), we can still find value in stories that are not, strictly speaking, true (I’m appealing to a coherence-model of truth, rather than a correspondence-model of truth; I never thought I’d drag that grad course back up in conversation again…).  We can find value in a story even if we are agnostic towards it being literally true or corresponding to a fact “out there” in the world.

When it comes to my career, one problem I have is that I have a hard time knowing how to sell myself.  When you are crafting your resume or CV, or when you are interviewing for a position, you are trying to create an appealing story of yourself.  You are painting a picture of the kind of person you are that aligns with the demands of the job or the needs of the employer.  Sometimes, it’s hard to create a compelling story for yourself.  You don’t know what to include, what to leave out, and what needs some mild spin.  You have to decide how to play-up key points and downplay unsavory details.  How you choose to connect the dots can make a large impact on what others will think of you as a candidate.  You don’t want to be dishonest, but sometimes the “truth” is very compelling.

One critical area that the Myers-Briggs can offer value is providing inspiration for how to tell that story.  It creates neat little packages that arranges details in interesting ways.  It allows you to take the generalizations and apply them to your own experiences.  It’s the same trick astrology uses – if you make a statement sufficiently ambiguous, you can find confirming evidence to support it.  Using this to your advantage, you can create a compelling backstory for yourself while also prompting you to fill in the details with good stories.

And if something does fit?  Leave it out and move on.

As long as you don’t pigeonhole yourself, you can tell a story about you that shows how valuable, interesting, and desirable you are to others.  The Myers-Briggs can offer some themes and typologies to help sell the best version of you.  Just don’t believe everything you read.

Stay Awesome,

Ryan

Post-Script: After I drafted this post last week, Seth Godin posted some thoughts about changing your story.  If I’m randomly coming up with ideas that coheres with advice from Seth, I count myself in good company.

~R

Policy vs. Guidance Pedagogy

During an ethics board meeting recently, we discussed ways of providing direction to faculty members who have student-based research in their courses.  For faculty who have research elements built into their courses, it can be a challenge to determine what counts as research, and whether said research is subject to the rules governing conducting research at an institution (specifically in our case, whether an ethics application would need to be submitted to the board).  Not every scholarly activity necessarily counts as research, and not every kind of research requires an approval from the institutional research ethics board.  Since this can be a bit of a murky area, we have been considering ways of providing direction.

The conversation abstracted away from the specifics of this case, and we discussed some of the issues concerning policy and guidance, which applies to education and pedagogy more generally.

The benefit of policy is that it spells out clear expectations of what is expected, what the division of responsibility looks like, and what consequences might be considered in the event of a policy breach.  Policy is designed to protect the institution through due diligence, and it focuses on expressing what rules need to be followed in order to not get into trouble.  Loopholes arise when the policies are not sufficiently rigorous the cover contingency cases and when policies are not harmonized laterally or vertically with other policies.  Policy documents focus on the “ends.”

On the other hand, guidance documents focus on the “means” by providing suggestions and best practices that could be followed.  Guidance documents typically do not include comprehensive rules unless it’s appropriate.  Instead, the purpose of the guidance document is to provide clarity in ambiguity without necessarily spelling things out.  They are deliberately left open because guidance documents are meant to supplement and add to ongoing conversations within a field or system.  While guidance documents also do not provide comprehensive options to contingent situations, the strength of the guidance document is that it’s educational in intent – it provides reasoning that helps the reader understand the position it takes, and paints a vision of what success looks like.

I realized in the meeting that this has a lot of crossover into considerations for teaching.  It’s is better, in my opinion, to teach students frameworks for thinking, rather than rules for success.  In the case of ethics, I would avoid teaching students what rules they need to follow, and what they need to do to avoid getting into trouble.  Instead, I would seek to build good practices and habits into the material I’m teaching so that I can model what success looks like and help them understand why.  This way of conceiving the material is forward-thinking.  It gets the students to envision what the end-step looks like, and allows them to work backwards to figure out how they want to arrive there.  By focusing on the principles you want the students to uphold (as opposed to rules to follow), the students learn to think for themselves and are able to justify the decisions they make.  This also has the benefit of avoiding the problem with prescriptive policies – students are prepared to reason through novel situations based on principles.

 

Stay Awesome,

Ryan

 

Thoughts on Providing Feedback

I had a heartwarming moment this past week where a student provided some positive feedback about my teaching.  I “teach” an online course through the college and have been one of the instructors for the past year.  I find online courses a difficult medium to engage with students because you never get face to face interaction with them, so you need to find other ways to reach out and build a rapport.

One of the methods I choose, and use when I teach in-class as well, is to take time to provide comments and feedback on assignments.  I think of assignments as ways for me to provide real, concrete feedback on student performance (rather than just a grade).  In addition to the marking rubric, I will give three kinds of feedback:

  • comments on how well a student engaged with material according to a certain criteria;
  • areas where the student did not measure up to the criteria and why;
  • (most importantly) guidance on how the student could improve in the future.

That last bullet point is important to me because when I reflect back on my own learning in school, I realize that grades are often a poor way of gauging how well you understand the material.  Instead, the numeric grade stands as a proxy for how many “answers” you got right.  For the purposes of education, I’m concerned of the other side of the grade – the marks that you didn’t get; why you didn’t get 100%.  If I, as an instructor, can fill in the details of what the student missed, I can guide them towards improving in the future.

It takes me a while to grade assignments because I spend the extra time giving constructive feedback to the students.  If I simply told them what they  got wrong, the student won’t have a sense of what steps they could take to do better next time.  I don’t want the students to use trial and error to figure out how to improve skills.  Instead, I will give them explicit feedback on what I want them to do differently in the future.

Perhaps you are thinking that I’m coddling the students too much.  Maybe you are right, but I assume the students are here to learn, that I’m positioned as the expert, and that teaching is more about molding and guiding students, not expecting them to stumble across the correct answers.  I want the students to be mindful of what I expect of them (and it forces me to reflect on what I want to see in the student’s progress, which is significantly harder than a capricious grade you slap on after reading through a paper).

If done right, you should see a general improvement in the quality of the assignments you receive over the semester.  Students who are looking to improve will pay attention to your feedback and will get better over time.

I’ll close off with an excerpt from the student who emailed me:

I struggle with philosophy but I wanted to try out this elective. Your feedback has really helped me to know where I have gone wrong and what to work on for the future assignments. I have never got so much feedback from teacher, so thank you.

Stay Awesome,

Ryan

100th Post!

EXPEDITION

This post marks my 100th entry on this site!

My first post went live on April 21st, 2016 and, if memory serves, I have managed to post at least once every week since then.

The original motivation to start this site was three-fold.  First, I vainly wanted to snag up the domain name in the off-chance that I wanted to use it in the future.  Second, I wanted an excuse to force myself to write regularly.  It had been a few years since I finished my master’s degree, and I found that my writing skills had softened over time, so I wanted a reason to regularly practice those skills to keep them sharp.

The third, and primary reason, was to chronicle and reinforce my path towards becoming a paramedic.  I had intended to document the application process of returning to school, the time spent as a student, and eventually the transition into a career.  I also wanted to use the website to discuss and teach the concepts I was learning because I believe it is a good mode of reinforcing the material I would have learned in class (an effective way of learning is being forced to teach it to others).

While the first two reasons have been honoured, I have since shelved the idea of becoming a paramedic.

The unfortunate result is that I’ve been maintaining this site up to 100 posts without a clear purpose or direction of where I want to go.  This is amusingly also the case with what I want to do career-wise.

I had my performance appraisal at work last week, and my boss said she was “super happy” with my work and contribution (there are a few areas of growth we identified, but otherwise it was a great appraisal).  When we discussed my future avenues of growth, I was hard-pressed to come up with the next steps of where to go next beyond wanting to take on more responsibility in general.  I have a few concrete skill sets that I want to work on, but nothing that lends itself to an obvious career choice.

I suppose this blog is an accurate reflection of my career trajectory.  On the one hand, the status quo looks good, clean, and polished.  On the other hand, it lacks direction and purpose.  However, the blog also affords me the space to stop, reflect, and document things as I go.

I don’t have an answer as to where I’m intending on going next, but at least I can share my muses along the way.

He’s to another 100 posts!

Stay Awesome,

Ryan

 

Skills Worth Developing – Resisting “That’s Not My Problem”

The job I have at the college is my first full time job after I finished university.  Prior to the position I’m in, I have worked only full-time hours on contracts and a smattering of part time jobs.  I thought, like many others, coming out of university that I knew what it would mean to have a job, be an employee, and work responsibly.  I wouldn’t say I was unprepared to enter the workforce, but it would be charitable to say that I had a lot to learn, and many beliefs to update.

This is, in part, why I decided to occasionally write thoughts in a series of posts loosely connected with the theme “Skills Worth Developing.”  There are many hard skills that employees should pick up over time to help them do their jobs better and advance in their careers.  Organizations like Coursera, Udemy, Lynda, etc. are excellent resources to help one pick up those kinds of skills.  But many other skills (usually dubbed “soft skills”) are usually picked up through experience and self reflection.  This blog serves both to force me to write, but also to force me to make permanent any self-reflections I’ve had, and these reflections might be valuable to others.

The last time I discussed Skills Worth Developing, I discussed the merits of storytelling as a communication tool.  This time, I want to reflect on a phrase I heard a lot when I first started working – “That’s not my problem” or “That’s not my job.”

You might be wondering why I lump this in with the notion of skills, instead of some other attribute, such as attitude.  True, something like this will overlap with one’s “attitude” while on the job, but I view this as a skill because it’s a habit and ability that can be modified over time, practiced, and strategies can be employed to use it in the workplace.  Therefore, I loosely connect it under the skills area that should be developed and practiced over time.

One other observation I want to make is that this skill – avoiding falling into the “That’s not my problem” mentality – is something I exercised as a beginner.  I think this is a fantastic skill to develop early in your career, but I’m not entirely sure of it’s value when you are well-established in your role.  The value of this skill is that it increases your value to the company when you are still differentiating yourself.  The same can not be said for someone who is either well-established in their company or field, where their value is tied directly to their ability to focus on problems that they can uniquely solve.  In those instances, it’s probably a better strategy to limit distractions from your primary role and duties.

And so, we come to the problem of “That’s not my problem.”  I found early on that many employees in a work environment can take on the “not my problem” mentality for a variety of reasons.  Perhaps they were burned in the past and now refuse to extend themselves.  Some feel overworked and overstretched.  Some are lazy.  For whatever reason, they resist helping others in their duties.

I find two issues with this kind of mentality.  First, it goes against the spirit of cooperation, collaboration, and teamwork.  The workplace is a team of employees who are working towards common goals to advance the interests of the organization (while hopefully advancing their own personal interests in parallel).  Any time someone says to a coworker “that’s not my problem,” what they are in fact saying is “your problems aren’t important enough for me to take an interest.”  They end up placing themselves above the interests of their coworkers and the organization.  I’m not saying that this is wrong per se – I am sympathetic to the ideas that this mentality is easy for organizations to exploit, and that there is no moral imperative to place the company’s interests above your own, so you should guard against it taking advantage of you.  What I am saying is that taking this as a default position undermines the team.  Everyone is supposed to work together to solve problems and strive to the company’s mission.  If you don’t want to do that, what’s the point of working at that company?  I would hardly think that it’s just in service of the paycheque.

The second issue I have with this attitude is it closes you off to development.  I directly attribute my success so far to my willingness to learn outside of my prescribed job.  By helping others with their tasks (so long as it does not prevent me from taking care of my own job area), I am able to develop new hard skills and learn about areas laterally and vertically from my position.  I am better able to see how my role fits within the larger context of our department, which continuously exposes you to new opportunities for growth and development.  You become more valuable to the team and you strengthen your ties with your coworkers.  When you are just starting out, this is a valuable way of integrating yourself and setting yourself up for advancement.

When you ignore the impulse to say “that’s not my problem,” you acknowledge that your coworkers are people with their own problems, concerns, hangups and worries, while also setting yourself up as a person of value for the team.  It is a perfect opportunity to step up and be noticed in your workplace.

That is why I think resisting the impulse to say “that’s not my problem” is a skill worth developing.

Stay Awesome,

Ryan

The Arts of Learning & Teaching

I’ve been in the apprenticeship phase of teaching for the last year, so I’ve largely been gaining experience in how information is conveyed and how to give feedback to students.  While I have given some consideration to course design and what kinds of courses I’d be interested in teaching, my primary focus has been on ensuring the students receive good content and (more importantly) good feedback on performance. Good performance management involves timely and specific feedback to either reinforce good behavioural outcomes, or quickly identifying and redirecting bad performance outcomes. It’s a challenge to ensure that feedback is both timely and useful, but it’s an important step of the process. 

I’m currently working my way through the Art of Learning by Josh Waitzkin, and I’ve started thinking about the process of learning.  While learning and teaching are separate domains, they are interconnected since they share similar goals.  However, being able to translate learning (whether being taught by a teacher or through self-teaching) into teaching to others is something that I have a lot of gaps in my knowledge about.

The first time I taught in-class in the college setting, I quickly became aware that my experiences with formal education (the university style lecture) was not a good mode of delivery to copy. While I am comfortable in the lecture setting, I saw that my students did not excel in that environment. I wish I could say that I had fixed my delivery before the end of the semester, but the reality is that I didn’t fully appreciate the situation until after the course was over and I reflected on the term. An environment where I stood at the front and spoke at length for two-hours was not one which the students could effectively absorb the material.

The problem I found is that how I think and absorb content is different from my students. Rather than teaching them to my style, I need to be more mindful of their talents and experiences. Waitzkin discusses this in his book, where he contrasts two kinds of teachers he’s had. One is the kind that teaches his own strengths and relies on rote memorization of strategies and techniques. In chess, this teacher has you studying opening moves to take early advantage of the board.  The other kind of teacher allows the student to play to their inner style, and teaches by building up concepts atomistically. In chess, this kind of teacher strip the board of all the pieces and focuses on the relationships between pieces at the end of the game. By showing how individual pieces play off each other, the student becomes comfortable across the game and learns not only how pieces fit together, but how to set yourself up for control at the end of the game.

I think my teaching style should embrace this second kind of teacher. Instead of dictating knowledge, I should focus on breaking the knowledge down and building up understanding in ways that make sense to the student. I can’t assume my students will have the prerequisite knowledge to compile the facts together on their own. It’s also the case that if I can’t break ideas down simply, the students might not get it, nor may I truly know what I’m talking about.  Afterall, Einstein and Feynman believed that if you couldn’t explain something simply, you probably don’t understand it very well yourself.

Stay awesome, 

Ryan