I always see canonical postings on the stack overflow job board. I thought "hey maybe toss out my line, how bad could it be?"
Well I got past the initial glance at the resume and I received the most insane recruiting email I've ever seen.
After the initial screening, the next step is a written test, an aptitude(iq) test, and a personality test. The written test is anonymized to avoid bias. I'm just going to copy and paste these questions.
"The current stage is your written interview. Please take some time to answer the questions below. We’re looking to get a sense of who you are, what’s important to you, and how you communicate. If you’ve already completed this when applying for another role, please feel free to copy/paste from your previous submission.
Education
At high school, how did you fare in mathematics and physical sciences? Which were your strongest subjects in the hard sciences, and how did you rank in your class?
At high school, what leadership roles did you take on?
What course and university did you choose, and why?
How did you rank competitively in university? Which were your strongest courses, and which did you enjoy the most?
At high school and university, describe your achievements that were considered exceptional by colleagues and staff.
Career development
How would you describe your level of experience as a professional software engineer?
Describe your skill in your preferred development language, and how you attained it.
What are your strengths as a software engineer?
Experience
Describe your level of experience in Golang, and how you have attained it.
Describe your level of experience in Python, and how you have attained it.
When did you start working on Linux? Describe your level of experience as a user & developer on Linux.
Which SoC / platforms have you worked on?
Describe the embedded Linux products you worked on (purpose, market, etc.)
Describe your contributions to those projects (bootloader, kernel, userspace apps, etc.)
Describe your experience with systemd and init, boot and initramfs
Describe your experience with embedded Linux graphics
Describe your experience working with bluetooth and networking
How do you debug very low-level issues in boot, the kernel, and firmware?
How do you address software performance, systematically, in your products and in your software engineering practices?
How do you prefer to drive documentation for your products?
How do you think about quality in your products?
Describe a case where it was very difficult to test code you were writing, but you found a reliable way to do it.
If available, provide your public github/gitlab repository links
If available, provide your personal blog/website links
If available, provide your professional Youtube channel
What would you like to achieve in career development and skills development?
Context
How are you involved in open source software?
Describe any significant contributions to open source (with links where possible)
What do you think are the key ingredients of a successful open source project?
Why you most want to work for Canonical?
Which other companies are building the sort of products you would like to work on?
Describe pros/cons of Ubuntu Core
Describe areas for improvement in Ubuntu Core
What do you think Canonical needs to improve in its engineering and products?
What do you think is the biggest opportunity for Canonical in this arena?
Who do you think are key competitors to Canonical? How do you think Canonical should plan to win that race?
"
The most bizarre thing is they're asking about my grades/ranking in high school. Dude I'm applying for a job, not babby's first internship.
Its no surprise that a company that isn't that big has constant and numerous postings online. They're obviously actively hostile to their applicants and set on wasting as much time as possible.
Yeah, big same. I like having a couple different interviews for technical roles cause it lets different people assess the candidate and lets us get different kinds of signals, so we can filter out the "good programmer, huge asshole" people or the "great at pitching their past work, can't write fizzbuzz" people
We give the same basic programming exercise to engineers of all levels (interns through seniors/leads) and it's amazing the number of people with 15+ years experience who can't write a script to make a request to an api and parse/munge the result