Agenda:
9.00 – 11.00
1. Overview of work of a programmer. We discuss “three layer” architecture, map layers to job profiles and go through different “types” of programmer profiles.
You will be able to answer the questions:
  1. What happens when you type something into Google?
  2. How is work of frontend developers different from that of backend engineers?
  3. How is project-based programming work different to product-based programming work? Which single one question to ask to WOW coders and find out what the candidate prefers?
11.00 – 11. 30 Q&A
11.30 – 12.30 Lunch break
12.30 – 14.30
2. Understanding the difference between stacks, Java/Spring,  Javascript/Angular/React/Node, exotic languages like Haskell and proprietary tech like C/C++.
Learning Goals: Understand how stacks, skills and personalities of programmers differ (e.g., Python vs Java vs Haskell). You will be able to answer the questions:
  1. What is the difference between a programming language and a framework?
  2. If someone has 10 different programming languages and frameworks on the CV, which single most important question should you ask?
  3. What is the difference between statically typed languages (such as Java) and dynamically typed languages (such as Javascript) from the viewpoint of programmers (education, experience)?
14.30 – 15.00 Q&A
3. Optional deep dives:
a. Javascript/Node/Frontend: How Javascript/frontend job profiles evolved and why it is so hard to recruit for them?
OR
b. Big data/cloud/data analytics: Beyond the hype. What are ”Big data” job profiles and relevant skill sets?
OR
c. Scrum/agile/management (recommended for bbv): What is agile? Why is software engineering nowadays differently managed than, say, construction?
15.00 – 17.00
4. Learn how to setup your own to read someone else’s Github / Stackoverflow profile and craft a written approach based on it.
Learning Goals: Given an online profile of a developer you will be able to quickly get valuable information and “WOW” the potential jobseeker in a cold email or in a phone interview.
You will be able to answer the questions:
  1. What is most important on a Github/Stackoverflow profile?
  2. How to see how much effort someone put into a Github project or if it is “just a fork”?
  3. Should you and how to source on Github?
17.00 – 17.30 Q&A, closing
Achieved goals after the course: You understand what different “IT-people” do on a daily basis and you share their self-understanding of the profession. This helps you craft cold outreach that stands out and hold an engaging work conversations with any “IT-person”.
About the trainer: Iwan Gulenko experienced tech hiring from every angle. He worked as a software engineer and recruited developers both as an internal and as an external consultant. Now, he helps both agencies and hiring firms to recruit more efficiently.