@ruianxp:

iris
iris
Open In TikTok:
Region: PH
Monday 30 March 2026 10:20:36 GMT
1411
66
9
6

Music

Download

Comments

terryyd.25
YD25ETSBOOST :
pretty
2026-03-30 10:32:52
1
kaloyens_z
kaloyens_z :
congrats🎊🎊
2026-03-30 18:11:02
1
aeeronq
I'll Be :
congratss te
2026-04-01 12:35:27
1
red.morales69
Reddd :
🫠
2026-04-04 00:46:28
1
woo_nzy
ady :
GANDAAAAA
2026-03-30 14:27:21
1
_yourslexiii
yourslexiee.vii_ig :
GANDAAAAA 🔥🔥🔥🔥
2026-03-30 11:40:43
1
To see more videos from user @ruianxp, 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