Freelancers using React in BekasiFreelancers using React in Bekasi
Developing High-Class & Scalable Framer Sites Super Fast⚡
$25k+
Earned
11x
Hired
4.9
Rating
35
Followers
Developing High-Class & Scalable Framer Sites Super Fast⚡
Figma · Framer · Next.js
$10k+
Earned
11x
Hired
4.9
Rating
19
Followers
Figma · Framer · Next.js
Mind of an engineer and the heart of an entrepreneur.
$50k+
Earned
1x
Hired
10
Followers
Mind of an engineer and the heart of an entrepreneur.
Cover image for Optimize Remote Job Applications for Indonesian Developers w...
Built a RAG job-hunting agent for Indonesian developers applying to remote USD jobs. 28 days of real usage. Here's what I learned. The problem: applying to 50+ remote jobs manually is exhausting. Wrong roles, no resume tailoring, hours wasted per application. The workflow now: One message → agent retrieves relevant jobs → ranks them → generates tailored resume + cover letter → user approves or skips. Stack (still running $0 free tier): · Embeddings: Cloudflare Workers AI qwen3-embedding-0.6b · Vector search: Cloudflare Vectorize, cosine similarity · Database: Cloudflare D1 / SQLite, one batched query · Semantic cache: Cloudflare KV, cosine ≥0.92 threshold · LLM: JSON-mode slot extraction + reply Only variable cost: ~$0.002/turn LLM usage 28-day numbers: · 235 sessions · 329 return visits · 743 agent turns · 357 job cards surfaced → 46 approved applications ~20 approvals per 100 sessions (target was 10–15) Total LLM cost: ~$1–4 Example matches from one natural-language query: Linear — 96/100 · DatAds — 95/100 · Spotify — 100/100 Two decisions I'd make again: · The scorer is deterministic — pure function, 7 weighted components, 0–100. No model drift. Users see exactly why a job scored highly. I didn't trust LLM ranking for something this consequential. · There's a regex fallback behind every LLM extraction. If the model fails or times out, the conversation continues. Users never hit a dead end. What's next: · Tracking downstream outcomes — recruiter replies, interviews Detecting expired/duplicate posts more aggressively Calibrating scoring weights from real approval behavior · The pipeline runs cheaply and generates real approvals. The next challenge is proving it improves actual job outcomes — not just application volume. This is the kind of system I enjoy building: AI-native product on constrained infra, with real users and measurable north-star metrics. If you're working on something similar — hiring pipelines, talent matching, AI agents for job seekers — I'd enjoy comparing notes. And if you're an Indonesian dev hunting remote USD roles, the product is live at lokerdollar.com (http://lokerdollar.com). What would you build differently? 👇 #RAG (https://www.linkedin.com/search/results/all/?keywords=%23rag&origin=HASH_TAG_FROM_FEED) #CloudflareWorkers (https://www.linkedin.com/search/results/all/?keywords=%23cloudflareworkers&origin=HASH_TAG_FROM_FEED) #BuildInPublic (https://www.linkedin.com/search/results/all/?keywords=%23buildinpublic&origin=HASH_TAG_FROM_FEED) #AIEngineering (https://www.linkedin.com/search/results/all/?keywords=%23aiengineering&origin=HASH_TAG_FROM_FEED) #RemoteJobs (https://www.linkedin.com/search/results/all/?keywords=%23remotejobs&origin=HASH_TAG_FROM_FEED) #IndonesianDevelopers (https://www.linkedin.com/search/results/all/?keywords=%23indonesiandevelopers&origin=HASH_TAG_FROM_FEED)
3
71
Web Design & Frontend Developer for SaaS and startups
Web Design & Frontend Developer for SaaS and startups
7+ years building optimized web products
$5k+
Earned
2x
Hired
2
Followers
7+ years building optimized web products