Reading a job posting
Reading a job or internship posting: its sections, required and desirable, the matching grid, the signs of a fake offer and forbidden criteria.
- 25 cards
- 5 topics
- Free
The outline, topic by topic
Each topic is weighted the way the exam weighs it.
- Concepts
- Questions
- Sort and link
- Scenarios
- Understand
A few cards from the deck
Job posting: what is it?
Show the answer
An advertisement by which an employer describes a post: title, tasks, profile sought, contract, place and conditions.
It is read section by section: the tasks describe the real work, the profile what the employer wants, the terms how to apply.
Before any interview, a posting asks for bank details and an ID copy "to reserve the post". What do you do?
- I send nothing and report the posting to the site that publishes it
- I send only the ID, which is less sensitive than bank details, to show my goodwill
- I send both: a serious recruiter must be able to prepare the contract before even meeting me
- I first ask for a signed contract, then send the documents once I have received it by mail
Show the answer
I send nothing and report the posting to the site that publishes it
Such documents are used to steal an identity or empty an account. Even a contract received by mail proves nothing. Reporting protects other candidates.
In a posting, the … describe what you will do; the … describes what the employer expects of you.
Show the answer
In a posting, the tasks describe what you will do; the profile describes what the employer expects of you.
The tasks show the real work: if they do not match the title, that is a first signal to note.
Required and desirable: what is it?
Show the answer
The first covers what the employer deems indispensable; the second, what would be an advantage without being a bar.
Words such as "a plus" or "appreciated" mark the desirable. A candidate who covers most of the required can apply without ticking everything.
A work-study posting asks for Python, Git and "ideally Docker". You know Python and Git, never Docker. What do you do?
- I do not apply: a posting naming a tool I have not mastered is necessarily out of my reach
- I write Docker in my skills to be shortlisted, counting on learning the tool if I am asked
- I apply, put Python and Git forward and say that I am learning Docker
- I apply without naming any tool, so that nobody notices that I am missing one
Show the answer
I apply, put Python and Git forward and say that I am learning Docker
"Ideally" marks a desirable. A lie about a skill is found out in the technical interview. Saying what you are learning shows initiative.