After two decades in human capital and years of placing IT talent across Malaysia, I can tell you this with confidence: most “recruitment problems” are job description problems in disguise.
A hiring manager sends us a ten-page internal spec. Someone pastes it onto a job board. Applications arrive — or they don’t. The shortlist looks random. Interviews feel inconsistent. Everyone blames the market, the agency, or Gen Z. Very few people look at the document that started the mess.
Here is the truth we live with every day at Tech Talent: you do not need one Job Description. You need two artefacts for the same role — an attraction JD for posting, and a screening scorecard for evaluation. Same role. Same honesty. Different jobs to do.
Why people ignore the JD (and pay for it later)
Busy managers treat the JD as admin. They recycle last year’s copy, add three more “nice to haves,” and hit publish. Recruiters inherit the ambiguity. Candidates read a wall of requirements and self-select out — or apply anyway because they have learned that JDs are fiction.
When the brief is vague, screening becomes vibes. Two recruiters shortlist differently. Two interviewers score differently. You lose good people who never applied, and you waste panels on people who never should have been booked.
In Malaysia’s IT market — software, data, cloud, cybersecurity, product — that cost shows up fast: stretched time-to-hire, soft interview-to-offer conversion, and hiring managers who stop trusting the shortlist.
Part 1 — The attraction JD (what you post)
The attraction JD is a marketing document with integrity. Its only job is to make the right people want to talk to you — and to help the wrong people opt out early.
Write it for a tired candidate scrolling on their phone after work. Lead with the problem they will own, the stack that matters, the level of ownership, location or hybrid reality, and why this role is worth leaving their current job for. Cut the corporate fluff. Cut the 18-tool laundry list. Put the real must-haves above the fold.
What belongs in an attraction JD:
- Role title that matches the market (not only your internal grade name)
- One clear paragraph on mission and impact — what success looks like in 6–12 months
- Must-have skills only — the ones you will actually reject on
- Nice-to-haves clearly labelled as nice-to-haves
- Team context, reporting line, and how work is done (agile, on-call, client-facing, etc.)
- Location, hybrid/remote policy, and any hard constraints (shift, travel, language)
- Honest signals on seniority — build vs lead vs architect — without title inflation
- A reason to apply: product, learning, impact, stability, or growth — pick what is true
What to leave out of the public post
Do not dump your full interview scorecard onto JobStreet or LinkedIn. Do not publish every internal tool, every political stakeholder preference, or a “10 years of experience” line when you will happily hire a strong five-year profile.
Inflated requirements shrink your pool and train candidates to ignore you. In IT hiring in Malaysia, the best people have options. If your ad reads like a wish list written by committee, they will not apply — they will wait for a clearer brief from someone else.
Attraction JD rule: if you will not reject someone for lacking it, do not list it as a requirement.
Part 2 — The screening scorecard (what you hire against)
The screening scorecard is not a prettier JD. It is the evaluation instrument. This is what recruiters, AI screening tools, and interview panels should use so every CV and every interview is judged the same way.
At Tech Talent, when a brief is sharp, our shortlists get sharper — including when we use structured screening such as OPAL against a role rubric. When the brief is soft, no tool and no recruiter can invent clarity you refused to write down.
What belongs in a screening scorecard:
- Knockouts — absolute deal-breakers (e.g. right to work, core language/stack depth, shift readiness)
- Weighted competencies — skills and behaviours that matter most for this role, with clear definitions of “good”
- Evidence to look for on the CV — owned delivery, scale, production vs academic exposure
- Interview probes — 3–5 questions per critical competency so panels compare fairly
- Seniority signals — what “mid” vs “senior” means in scope, not only years
- Salary band reality — so you do not shortlist people you will never close (use Free Salary Research if the band is unclear)
- Culture / working-style notes — how this team actually operates, without discrimination or illegal criteria
A simple Malaysia IT example
Suppose you need a mid-level backend engineer in the Klang Valley.
Attraction JD might say: join a product team shipping APIs used by Malaysian banking clients; own services in .NET / Azure; hybrid PJ; must have solid C# and SQL in production; bonus for messaging or observability.
Screening scorecard might weight: production ownership of APIs (high), Azure depth (medium-high), SQL performance awareness (medium), communication with BA/QA (medium), Kafka (nice-to-have). Knockout: no professional C# delivery. Interview probe: “Walk me through an API you owned end to end — failure modes, monitoring, and what you changed after an incident.”
Same hire. Two documents. Suddenly the job board copy is readable, and the shortlist is defendable.
How the two documents work together
The attraction JD and the screening scorecard must tell the same truth. If the ad says “mid-level” and the scorecard rejects anyone without lead experience, you will frustrate candidates and distrust your own process.
Use this operating rhythm:
- Write the scorecard first with the hiring manager — force the must/want conversation
- Derive the public JD from the scorecard — only publish what you will screen on
- Share the scorecard with every interviewer before panel day
- After each failed interview, update the scorecard — not your memory
- Brief your agency on both: what to advertise and what to score
What I tell hiring managers at Tech Talent
If you only have time for one improvement this quarter, make it this: stop pasting internal specs into job ads, and stop screening from gut feel. Give your TA team and your agency two clean artefacts.
We will still do the human work — market mapping, outreach, judgement, and client partnership. Tools help with consistency. They do not replace a clear brief. A vague job description still produces a vague shortlist. That has not changed since I founded this firm, and it will not change because AI got faster.
Get the JD right, and everything downstream gets cheaper: fewer wasted interviews, stronger offers, better retention of people who actually match the work.
A closing note from me
Talent is not scarce because Malaysia has no good engineers. Talent feels scarce when we advertise confusion and screen without a scorecard. Write to attract. Score to hire. Keep both honest.
If you want a second pair of eyes on a live IT brief — or a free salary band against your JD — my team is ready to help.
Datin Malliga Subramaniam
Founder & Managing Partner, Agensi Perkerjaan Tech Talent (JTKSM 1304)
Ready to hire?
Need help hiring IT talent in Malaysia?
Tech Talent supports permanent recruitment, contract hiring, RPO, and EOR across Malaysia. Speak with our team to plan the right approach for your next role.