txarli/txarli.dev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add alllll the old blog posts from college

Browse Source
This commit is contained in:
Cassidy Williams
2024-01-03 02:40:59 -06:00
parent cac0bb8232
commit e38268b56a
43 changed files with 836 additions and 140 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
src/posts/how-ace-an-interview.md
View File

@@ -2,7 +2,7 @@
layout: "../layouts/BlogPost.astro"
title: "How to Ace an Interview"
slug: ace-interview
description: "Interviews are scary, but they don't have to be. When you're on the spot, it's best to be prepared. Let's prepare you."
description: "Interviews are scary, but they don't have to be. When you're on the spot, it's best to be prepared. Let's prepare you."
added: "Mar 04 2014"
tags: [advice]
---
@@ -13,8 +13,9 @@ So, I thought I'd give you some advice based on what I've learned.
Right now.
## Study the usual interview questions, and fit in your own experiences.
All you have to do here is go on the internet and search, “common interview questions.”
Everything from “describe a time when you worked on a team” to “what was the most fun presentation you’ve ever had to plan?” is asked to everyone, engineers and business majors alike.
All you have to do here is go on the internet and search, "common interview questions."
Everything from "describe a time when you worked on a team" to "what was the most fun presentation you've ever had to plan?" is asked to everyone, engineers and business majors alike.
Make sure you follow STAR: _Situation_ (what was the situation you were in), _Task_ (what was your job, or task, to tackle the situation), _Action_ (what were the actions to ultimately took), and _Results_ (what were the responses you received and the results you achieved)!
Now, if you're thinking about technical questions (which I'm a computer science chick too, I get it), my only advice here is to talk a LOT.
Too many engineers just go up to the white board and start coding then and there without explaining what they're doing.
@@ -25,23 +26,27 @@ The _thought process_ is what these companies are looking for, not just correct
It's better to have a good thought process and bad code than good code and a bad thought process.
## Know your story well.
Instead of reflecting all the time on interview questions and rehearsing answers, try reflecting on your school and career chronology until now!
Think about how you got started in your field, struggles you overcame, what you’ve learned over the years, where and how you developed certain skills, what you’re most proud of, etc.
Think about how you got started in your field, struggles you overcame, what you've learned over the years, where and how you developed certain skills, what you're most proud of, etc.
When you know your story, you can answer almost any question about anything because of your personal experiences and what you know already about yourself.
## Follow the PIE.
I mean this in both senses of the word. Pie is delicious.
BUT, what I really mean is, the best interviewees are the ones who are _Positive, Interested, and Engaged_ in the interview conversations.
If you keep worrying about the next question and saying things perfectly, you might forget to have your positive game face showing.
Just remember to smile! If you look like you’re happy to be there, they’ll be more happy to interview you.
Just remember to smile! If you look like you're happy to be there, they'll be more happy to interview you.
## Consider what the company (or organization or school, whatever) wants.
When you’re at the career fair, ask companies what they look for, and what their culture is like.
You don’t want to think, “oh yeah I’ll just keep practicing, if I know what I’m talking about and can show it, they’ll hire me.”
Yes and no. You do want to show them that you know what you’re talking about. But, they also want to feel that you are likable, and that you’ll fit in at the company!
When you're at the career fair, ask companies what they look for, and what their culture is like.
You don't want to think, "oh yeah I'll just keep practicing, if I know what I'm talking about and can show it, they'll hire me."
Yes and no. You do want to show them that you know what you're talking about. But, they also want to feel that you are likable, and that you'll fit in at the company!
Focus more on demonstrating aptitude while being likable rather than just spitting out perfectly crafted answers.
Laugh with them, relax a bit, and let them see your personality! I mean, I like you, so why wouldn’t they?
You personality is one of your skill sets that people often don’t count. Believe me, it counts for a lot.
Laugh with them, relax a bit, and let them see your personality! I mean, I like you, so why wouldn't they?
You personality is one of your skill sets that people often don't count. Believe me, it counts for a lot.
## Breathe.
You’re going to rock this! Just know that if it doesn't work out, it's not the end of the world, and if it does, that's even better. Have FUN and good luck!
You're going to rock this! Just know that if it doesn't work out, it's not the end of the world, and if it does, that's even better. Have FUN and good luck!