⪼ Made with 💜 by realpolyglot.com
There are so many better ways to interview a candidate for a software programming job than the status quo. What is the status quo? Interviewers showing up late, little to no foreplay, just jumps right into shot gunning a bunch of technical questions. Whiteboarding, take home assignments, algorithms and data structures, low level bits & bytes? This would be fine except, you are interviewing for a job where you'll be making front-end CSS changes and building backend APIs with an ORM.
There are better ways. What about checking out the candidate's github and stackoverflow profiles? What about checking the candidate's development environment? How well do they navigate their tools? Do they seem like a power user of their machine?
Do they write tests? Do they know what a good test is? Can they use version control? Do they know how to open and close a PR/MR? Can they merge a PR from the command-line? Have they published any open-source code packages (i.e. npm, crates, gems, phar, etc?)
Do they know their ways around cloud platforms? Do they understand identity and access management? Do they understand the ins and outs of authentication and authorization? Do they understand primary keys, foreign keys, & materialized views in SQL/relational ACID compliant databases?
- Skillshare Course Creation
- How to Make Money Coding - 5 Ways Developers Make Money WITHOUT a Job @ Tutoring
- User Space Processes
- Shell
- OS Kernel
- Hardware
- Graph Data Structure Intro (inc. adjacency list, adjacency matrix, incidence matrix)
- Graph Algorithms for Technical Interviews - Full Course
- tr
- sed
- awk
- curl
- grep
- rm
- test
- sh
- ls
- ln
- cp
- kill
- hostname
- echo
- df
- date
- cat
- chmod
- id
- alias
- at
- atq
- banner
- base64
- basename
- bc
- chflags
- chgrp
- chpass
- chsh
- command
- ctags
- cut
- diff
- dirname
- du
- printenv
- file
- getopt
- getopts
- git
- gunzip
- head
- install
- make
- jobs
- killall
- nc
- read
- readlink
- rsync
- ssh
- tar
- tee
- top
- true
- ulimit
- umask
- uname
- wc
- which
- xargs
Lost In Tech :: How Not To Panic When You've Lost or Quit Your Software Engineering Job and Start Getting Interviews
- The Tech Resume Inside Out Complimentary Copy
- Key Values
- Stackoverflow Jobs
- Prelo
- Ask HN: Who is hiring? (September 2021)
- I want to make technical recruiters better at their job.
How to talk to non-technical women about tech without drying up the well.
- No take-home code assignments unless we are getting paid well and the excercise is something fun
- No whiteboarding excercises (check github, stackoverflow, if you want samples of our coding)
- published open-source software
- code blog & portfolio website
- conference talks
- CFPLand
- Open-source and crowd-sourced list of conferences around software development
- Wiki CFP
- 10 Times
- Lachie’s 7 step guide to writing a winning tech conference CFP
- list salary range for positions
- emphasize tech stack
- emphasize number of rounds
- NodeJS intrinsic HTTP/HTTPS