@alijuttaj:

علی حسن ❤️
علی حسن ❤️
Open In TikTok:
Region: PK
Thursday 06 August 2026 16:39:06 GMT
238046
6591
177
1528

Music

Download

Comments

haidershah5495
Haider Shah.. 😎 :
pory documents har cheez hony k.bad b ap ka chalan kar diya jata he...🤦‍♂️
2026-08-07 05:11:58
283
user9556078153679
Syed Qamar Shah :
E Chalan front number plate say hota ha 😂😂 pic Kay Sath face ki
2026-08-08 07:35:47
17
moonprince3
🤟Moon Prince 🇵🇰 :
ye Pakistan ha hamara Dubai ky qanon follow krty hn per Dubai me fazol ky Chalan ni krty
2026-08-07 15:17:22
1
niazimd2
नियाज़ी-एमडी🖇️⃤ :
the problem
2026-08-08 11:55:47
6
khanzada___10
₮๑ຮཛཛf﹏κɧαղ✈🎀👑 :
e challan hota e front number plate sy hai
2026-08-08 03:02:24
10
shympi_gaming
SHYMPI GAMING 🇵🇰 :
2026-08-07 20:53:28
67
yasirilyas63
Yasir Ilyas :
fear of e challan
2026-08-07 11:47:36
2
itz_faiz_94
Faiz Ul Hassan :
chk kidr sy krty hein challan
2026-08-07 11:05:52
29
ahmed.bilal104
(EFC) Elahi food corner :
E challan
2026-08-07 10:06:06
1
aslammahessar32
🇹🇷سرائڪي🇹🇷 :
وطن کی نظروں سے بچتے ہوئے😂
2026-08-08 09:41:50
10
intsamhafeez2
@intsam hafeez3 :
online chlan 😅
2026-08-07 14:56:44
21
abdullahrajpoot95
Abdullah :
2026-08-08 05:41:13
5
miankhayam1
Mian Gee :
safe City Challan
2026-08-07 14:35:54
12
zosma7
zosma :
They are doing great job in injustice Society.. Why all rules applies on poor?
2026-08-07 17:01:37
8
rizwan_rajpoot46
𐒄𐤠ƝƖ 🫯 :
Only pakistani samj sakta han ya dukh😂
2026-08-07 09:42:56
7
faizan_wahcantt512
F🪐 :
abee aik sawal to batao log bolte han agar sab documents license sab Kuch ho to phir bhi challan ho jata ha iski waja Kya ha
2026-08-08 11:54:45
0
asadalirazamaher00
Asadaliraza Maher00 :
ya lanat h hukmarano pr jinho NY asa krny per majbor kia hoa h sab ko
2026-08-07 12:39:40
5
abbasjutt6333
ÎÑÑØÇÉÑT JÛTT🙃❤️‍🩹 :
E challan ka chakar he😂
2026-08-07 14:56:36
2
jabbarawan286
Jabbar Awan333 :
sai h 👍
2026-08-07 12:03:53
1
zainidrees00
ᴢᴀɪɴ ɪᴅʀᴇᴇs🪽 :
qasm sy Pakistan jisa Azad mulk kahi bi nahi
2026-08-07 16:27:53
1
sheikhahmadja
Jani bhai :
chalan sae bachny k lye
2026-08-07 02:23:56
4
rehmaaaaaannn
Sheikh Abdul Rehman :
yay k rakh dia awam ko is watan k hukmarano ny
2026-08-08 16:47:50
0
sohaib_chohan00
ℍΛررY💸ᴿᵃʲᵖᵘᵗ :
Gurbet
2026-08-08 14:45:50
0
basharbutt77
KĄشHMÎŘĮ💀❎ :
E Chalan sy bachny k liy😂
2026-08-08 14:18:18
0
To see more videos from user @alijuttaj, please go to the Tikwm homepage.

Other Videos

Replying to @a  n I've attached my CV — read it first and pull my background, timeline, differentiators and skills from it instead of asking me to retype them. Only ask about what it doesn't cover: target region, constraints, and academic record framing. Build me a personal job-search dashboard on autopilot: Target: [role type(s), e.g. consulting/PM/finance] roles in [region] only. Do not limit tracking to a fixed list of firms — the whole point is to surface roles I wouldn't find by checking a shortlist myself. Cast wide across every company in scope for this role type and region, discovered fresh each run, not just re-verified from a starting list. (Optional: name a few priority firms to always include, but scope must extend well beyond them.) Out of scope: [disqualifiers]. Constraints: [visa, notice period, internship-eligibility rules, etc]. 1. roles.json — source of truth. Per role: id, company, title, tier, type, location, opens/deadline dates, status (Open/Opens soon/Verify/Watch/Closed), fit score 1-5 vs my profile, eligibility, tactical notes, source, first_seen, region-confirmed flag, date-confidence flag. Store my profile at the top. 2. build_dashboard.py — reads roles.json, writes one self-contained HTML file (data inlined, no server): summary cards (closing soon, open, opening soon, total, unconfirmed), urgent banner (<14 days), category/status filters, search, sortable table, expandable rows for eligibility/notes/source. Dark theme, no dependencies. 3. Daily scheduled task — discovery is the primary job, not a side task: each run, run broad searches across job boards/aggregators and company career pages for the target role type and region, actively hunting for companies and roles not yet tracked, not just re-checking the existing list. Then re-check every Open/Opens soon/Verify role. Update roles.json, rebuild HTML. Draft an email via Gmail (draft only, never send) only when something changed: new role, role went live, deadline moved earlier, or <14 days left on an open role. Under 200 words. Stay silent if nothing qualifies. Sourcing rules (critical): Only track roles that recruit into my target region — leave off if unclear, don't guess. Only record a date from a region-specific source (firm's own regional page or the actual regional posting). A global page listing my city among many isn't enough. Tag each date: confirmed (regional page states it this cycle), indicative (regional but rolling/prior-cycle/no year), or unconfirmed (no regional source — leave date fields empty). Never alert on unconfirmed dates. Note foreign-market dates explicitly as not applicable rather than recording them. Some roles are rolling with no deadline by design — mark Open, no date, say so in notes; don't invent one. Known failure mode: JS-rendered portals return an empty page on a plain fetch, which looks like
Replying to @a n I've attached my CV — read it first and pull my background, timeline, differentiators and skills from it instead of asking me to retype them. Only ask about what it doesn't cover: target region, constraints, and academic record framing. Build me a personal job-search dashboard on autopilot: Target: [role type(s), e.g. consulting/PM/finance] roles in [region] only. Do not limit tracking to a fixed list of firms — the whole point is to surface roles I wouldn't find by checking a shortlist myself. Cast wide across every company in scope for this role type and region, discovered fresh each run, not just re-verified from a starting list. (Optional: name a few priority firms to always include, but scope must extend well beyond them.) Out of scope: [disqualifiers]. Constraints: [visa, notice period, internship-eligibility rules, etc]. 1. roles.json — source of truth. Per role: id, company, title, tier, type, location, opens/deadline dates, status (Open/Opens soon/Verify/Watch/Closed), fit score 1-5 vs my profile, eligibility, tactical notes, source, first_seen, region-confirmed flag, date-confidence flag. Store my profile at the top. 2. build_dashboard.py — reads roles.json, writes one self-contained HTML file (data inlined, no server): summary cards (closing soon, open, opening soon, total, unconfirmed), urgent banner (<14 days), category/status filters, search, sortable table, expandable rows for eligibility/notes/source. Dark theme, no dependencies. 3. Daily scheduled task — discovery is the primary job, not a side task: each run, run broad searches across job boards/aggregators and company career pages for the target role type and region, actively hunting for companies and roles not yet tracked, not just re-checking the existing list. Then re-check every Open/Opens soon/Verify role. Update roles.json, rebuild HTML. Draft an email via Gmail (draft only, never send) only when something changed: new role, role went live, deadline moved earlier, or <14 days left on an open role. Under 200 words. Stay silent if nothing qualifies. Sourcing rules (critical): Only track roles that recruit into my target region — leave off if unclear, don't guess. Only record a date from a region-specific source (firm's own regional page or the actual regional posting). A global page listing my city among many isn't enough. Tag each date: confirmed (regional page states it this cycle), indicative (regional but rolling/prior-cycle/no year), or unconfirmed (no regional source — leave date fields empty). Never alert on unconfirmed dates. Note foreign-market dates explicitly as not applicable rather than recording them. Some roles are rolling with no deadline by design — mark Open, no date, say so in notes; don't invent one. Known failure mode: JS-rendered portals return an empty page on a plain fetch, which looks like "no roles" but means "couldn't see it." Use Claude in Chrome (navigate + read rendered page) for those. If unavailable, say the portal couldn't be read rather than concluding anything from a blank result. Connectors to enable first (connect as many as apply — breadth of search sources is the point): Gmail (required, for the alert draft) Indeed, plus ZipRecruiter and/or Dice if relevant to the field — aggregators are the main discovery engine here, not just a backup. Discovery tools only, never the source for a date. Claude in Chrome browser extension (catches JS-heavy portals a plain fetch misses — the single biggest cause of missed roles) No reliable LinkedIn Jobs connector exists — check LinkedIn manually for alumni/referral leads. Ask me anything you need before building, then build all three pieces and set up the schedule. #gradjobs #jobhunting

About