Level up Your Team with Better Technical Interviews

[SeanKilleen]

About You

Your Name: Sean Killeen

Twitter handle (optional): sjkilleen

The best way to reach out to you: E-mail (SeanKilleen@gmail.com)

A quick bio: Originally from the Philadelphia area, Sean has 15+ years of experience solving problems as an IT professional and developer for commercial, non-profit, and federal clients. He's currently the .NET Specialty Lead at Excella Consulting -- he highly recommends you check them out. He recently served on a modernization project that industry analysts called "more complex than the moon landing". He also servers as a co-trainer for Excella's Agile Testing & Automation and Agile Engineering courses. Aside from loving his work way too much, there's a good chance he's enjoying/stressing about being a new homeowner, sipping great beer, exploring the Arlington area, or singing somewhere. You can find him on Twitter at @sjkilleen or blogging not nearly often enough at SeanKilleen.com. He doesn't bite; say hi!

Your Talk

Title: Level up Your Team with Better Technical Interviews

What your talk is about: Have you ever been in a technical interview, stuck at a whiteboard or solving a brainteaser, and thought “there must be a better way”? Good news: there very much is. Agility and adaptability are crucial for a development team’s success, but how often do we target for agility when considering who to bring into our team? And how do we set expectations for agility from the first time this potential new hire begins evaluating our team? In this talk, I walk through my philosophy & provide practical tips for running technical interviews that are primed for success.

How long will your talk be?

• 5-15 minutes (lightning talk)
• 20-30 minutes
• 30-45 minutes
• 60 minutes or more

Meta

Do you need help crafting your talk?

• Yes
• No

[stale]

Hi there — thanks for submitting this talk! It’s been a year since the last activity — would you mind taking a look to see if you’re still interested in presenting about this topic, and if the talk’s content is still up-to-date?

If everything’s still good, just drop a comment here and I’ll pop back into hibernation like a good little robot.

If you’re no longer interested in giving this talk, or the talk is out-of-date, feel free to close this issue.

Should I not hear back in a week, I’ll close this issue so you needn’t feel guilty about it. ❤️

Thanks for your contribution to the tech community in DC!

[SeanKilleen]

Still good here! Thanks Stalebot. 👍

[stale]

Hi there — thanks for submitting this talk! It’s been a year since the last activity — would you mind taking a look to see if you’re still interested in presenting about this topic, and if the talk’s content is still up-to-date?

If everything’s still good, just drop a comment here and I’ll pop back into hibernation like a good little robot.

If you’re no longer interested in giving this talk, or the talk is out-of-date, feel free to close this issue.

Should I not hear back in a week, I’ll close this issue so you needn’t feel guilty about it. ❤️

Thanks for your contribution to the tech community in DC!

[SeanKilleen]

Still good here! Thanks Stalebot. 👍