As the first step in the decommissioning of sasCommunity.org the site has been converted to read-only mode.
Here are some tips for How to share your SAS knowledge with your professional network.
Solutions in the Round -- Professional Development: Interviewing Tips and Techniques
From the WUSS abstract for this topic
In this group discussion, we will address interviewing tips and techniques. Solutions in the Round is an exciting new section [at WUSS 2014]. The format is simple: we sit in a circle and discuss the many ways to approach and address a programming problem, and we'll identify situations where one approach might be more useful than another. We will keep notes, and those notes will be posted on sasCommunity.org where we can continue the discussion and allow other to join in after the conference. We hope to engage users from all different perspectives and experience levels to participate in these discussions.
Discussion at WUSS
- know who you're interviewing with
- slow down, elaborate
- STAR (situation, task, action, & response)
- write down the questions that you're being asked (and answers)
- always overdress, never underdress
- research the company (shows your interest)
- be flexible
- don't ever say "I don't like my boss" when asked why you're looking for a new job
- reread your resume before and interview
- send a thank you letter, but not a crappyone
- Toast Masters
- write down your 4 bullet points about things you want to get across
- be confident and don't apologize
- allow yourself time before an interview (find parking, review resume, look over notes, etc...)
- sell yourself!
- 0 screening interview by HR (communication, listening skills(
- 1 team experience
- 2 technical skills
- make sure your responses are geared toward the job you're interviewing for
what color is your parachute?
Further Discussion -- Open to All
Please join the conversation! Also, if you were one of the live participants, please feel free to correct any mistakes or omissions from our original discussion.
- First of all, my apologies for the delay in posting this to the site -- several months after the conference. It was a lot of fun to host this section and to collaborate in such a free-formatted section, and I hope that we can continue the discussion here. As the section chair, and in hopes of breaking the ice, I challenged myself to propose the worst solution to every problem. I think that it is important to identify the full spectrum of solutions to a problem, so that we can also identify the things that we are trying to avoid. Also, we can all agree that there is usually not just one solution that fits every single problem. In most cases, we would like a solution that avoids processing through every record on the dataset. However, in cases where there is very little data, this is not always necessary. I look forward to hearing others' thoughts. Cheers, --Otterm1 (talk) 10:58, 30 December 2014 (CST)