English yang bikin kamu di-hire

Skenario: Job posting: "Junior QA Engineer — Remote. 1+ tahun experience. Must be detail-oriented. Apply with CV and 3 sentences why you fit."

Tugas: Tulis 3 kalimat "why you fit" dalam bahasa Inggris untuk posisi ini.

Jelek: I am very interested in this position. I am detail-oriented and hardworking. I believe I can contribute to your team.

Bagus: I've completed 30 test cases for a checkout flow as a practice project, catching 5 critical edge cases the original tester missed — I can share the documentation. I'm comfortable working async and always document findings clearly so developers don't need to ask follow-up questions. I'm looking for my first remote role to apply this directly.

• Kalimat 1: bukti konkret dari task yang sudah dikerjakan
• Kalimat 2: tunjukkan async skill dan documentation habit
• Kalimat 3: honesty tentang level + intent yang jelas

Self-check: Ada satu angka atau konkret proof? · Ada connection ke remote work skill? · Tidak ada kata "hardworking", "passionate", atau "team player"? · Di bawah 5 kalimat?

Skenario: Kamu lihat recruiter dari perusahaan yang hiring QA Engineer. Mereka belum posting di job board tapi company-nya terlihat bagus di LinkedIn.

Tugas: Tulis LinkedIn connection request message (max 300 karakter) dan follow-up message pertama (max 5 kalimat).

Jelek: Hi, I want to connect with you for future opportunities in your organization. I am looking for a remote job and I think your company is great.

Bagus: Connection: "Hi Sarah, I noticed [Company] is expanding the QA team — I'm a QA specialist with a focus on API testing and would love to connect." Follow-up: "Thanks for connecting! I've been following [Company]'s engineering blog — particularly the post on your testing pipeline. I have 2 years of manual + API testing experience and recently built a 30-test-case suite for a checkout flow. If you're open to a 15-minute chat about the team, I'd love to learn more. No worries if the timing isn't right."

• Connection: tunjukkan kamu tahu mereka lagi grow, jangan generic
• Follow-up: reference sesuatu yang spesifik dari company mereka
• Satu proof point yang konkret
• "No worries if..." menunjukkan respect for their time

Self-check: Ada referensi spesifik tentang company atau role mereka? · Ada satu proof point kamu? · Ada satu clear ask? · Ada acknowledgment bahwa mereka mungkin sibuk? · Tidak ada "I am very interested" atau basa-basi?

Skenario: Job posting di Upwork: "Need data analyst to analyze our 3-month sales data (CSV, ~20K rows). Want to know: top products, best-selling regions, and monthly trend. Budget: $150-250. Needed in 3 days."

Tugas: Tulis proposal Upwork (max 150 kata) untuk job ini.

Jelek: Hello, I am a professional data analyst with 3 years of experience. I have worked on many projects and I am very skilled in Excel and Python. I can complete your project in 3 days. My rate is $200. Please consider me for this project.

Bagus: Your sales data has three questions I can answer clearly: top products, best regions, and monthly trends — let me show you how. My plan: 1. Clean and audit the CSV (Day 1) 2. Build summary tables + 3 charts (top products, regions, trend line) in Google Sheets (Day 2) 3. Write a 1-page insight memo with key findings (Day 3) I did similar work for an e-commerce client — delivered 5 charts + memo in 2 days: [link] Deliverables: cleaned CSV + Google Sheets dashboard + insight memo. Timeline: 3 days. Rate: $200 flat. One question: do you have any benchmark targets you're measuring against?

• Buka dengan summary problem mereka, bukan perkenalan diri
• Plan langkah per hari = reassuring untuk client
• Portfolio link = trust signal
• Deliverables eksplisit = no scope creep
• Pertanyaan = buka dialog dan tunjukkan kamu strategic thinker

Self-check: Dimulai dengan problem client, bukan tentang diri sendiri? · Ada timeline per hari? · Ada link atau referensi portfolio? · Deliverables ditulis eksplisit? · Ada satu pertanyaan di akhir? · Di bawah 200 kata?

Skenario: Kamu interview 5 hari lalu untuk remote data analyst role. Hiring manager bilang "kami akan kasih tahu dalam 3-4 hari". Belum ada kabar.

Tugas: Tulis follow-up email (max 80 kata) yang profesional dan tidak terkesan desperate.

Jelek: Hi, I am following up again on my application. I have been waiting for your response. Please let me know the status. I am very interested and available to start immediately.

Bagus: Hi [Name], I wanted to follow up on our interview last [day] for the Data Analyst role. I've been thinking about the data pipeline challenge you mentioned — I actually have a relevant SQL approach I'd be happy to share. Could you give me a quick update on the timeline? Happy to provide any additional information that would help. Best, [Name]

• Reference spesifik interview — bukan generic "my application"
• Value-add: tunjukkan kamu masih berpikir tentang problem mereka
• Request: single clear ask tentang timeline
• Offer: terbuka untuk provide more info tanpa terkesan memaksa

Self-check: Ada nama posisi yang spesifik? · Tidak ada kata "desperate", "still waiting", atau pressure words? · Ada satu value-add atau insight? · Di bawah 100 kata?

Skenario: Client offer kamu $15/jam untuk QA work. Kamu biasanya charge $25/jam dan rate pasar untuk QA remote di global market adalah $20-40/jam untuk level kamu.

Tugas: Tulis email negosiasi (max 120 kata) yang sopan, confident, dan berbasis data.

Jelek: Hi, thank you for the offer but $15/hr is too low. I need at least $25/hr. Please reconsider.

Bagus: Hi [Name], Thank you for the offer — I'm excited about the project scope. Based on current market rates for remote QA with API testing experience ($20-35/hr) and my track record of reducing escape bugs by 40% in similar projects, I'd like to propose $22/hr as a starting point. I'm happy to discuss the scope in more detail to find a number that works for both sides. Would a 15-minute call work this week? Best, [Name]

• Acknowledge terlebih dahulu — jangan terkesan transactional
• Market data reference = tidak personal, ini bisnis
• Specific proof point = justify kenapa kamu worth more
• Counter dengan range tengah, bukan rate tertinggi
• Offer call = menunjukkan kamu serius dan flexible

Self-check: Ada acknowledgment positif dari offer mereka? · Ada market data reference? · Ada proof point yang spesifik? · Counter dengan range, bukan fixed angka? · Ada invitation to discuss lebih lanjut?

Skenario: Kamu remote ops specialist. Tim kamu ada di US, UK, dan Australia. Kamu perlu post weekly update di Notion tentang progress system documentation project yang sedang kamu kerjakan.

Tugas: Tulis weekly async project update (max 150 kata) untuk tim lintas timezone ini.

Jelek: Hi team, update for this week. I am working on the documentation. It is going well. Will continue next week. Let me know if you have questions.

Bagus: Weekly Update — System Documentation | Sep 22-28 Status: On Track **Done this week:** - Completed onboarding doc (v1) — reviewed by US team ✓ [Notion link] - Drafted SOP for tool access requests (80% complete) **Next week:** - Finalize SOP + AU team review by Wed - Start incident response template **Blockers:** - Need sign-off from Sarah on access policy section — pinged her Tue, following up Thu **Questions?** Comment on the Notion doc or async-message me — I check messages 2x daily (9am + 3pm WIB).

• Status indicator di awal = quick scan untuk busy teammates
• Done list konkret dengan completion markers
• Next dengan deadline dan owner
• Blocker dengan action yang sudah diambil
• Availability info = mengurangi unnecessary ping

Self-check: Ada status indicator yang jelas? · Done list ada minimal satu angka atau konkret marker? · Next actions ada due date? · Blocker ada tindakan yang sudah diambil? · Ada link ke dokumen terkait?

Skenario: JD: "Must: Playwright + TypeScript 3+ yrs. Bonus: CI/CD. Kirim CV + 2 kalimat kenapa kamu + link bukti." Kamu punya 2 tahun Playwright + CI/CD kuat.

Tugas: Tulis 2 kalimat pitch + 1 baris link bukti untuk JD ini.

Jelek: I have 2 years experience and I am a fast learner. I am confident I can do this job well.

Bagus: "2 years focused on Playwright + TS — built a 120-case suite that cut regression from 3 hours to 25 minutes on CI. Bonus: I own our GitHub Actions pipeline (parallel shards + Slack alerts). Proof: test run video + repo [link]."

• Kalimat 1: spesialisasi + angka before/after
• Kalimat 2: bonus requirement (CI/CD) langsung dijawab
• Link: deep link ke bukti, bukan homepage

Self-check: Ada angka before/after? · Bonus requirement dijawab eksplisit? · Link ke bukti spesifik, bukan homepage?

Skenario: Intro call 15 menit. Interviewer: "Tell me about yourself." Kamu punya 60 detik sebelum mereka bosan.

Tugas: Tulis (lalu baca keras) jawaban 60 detik: now → before → proof → ask.

Jelek: I graduated in 2020 and I have worked in several companies doing various tasks. I am hardworking and looking for new challenges.

Bagus: "I'm a QA focused on checkout flows — last project I built a 30-case suite that cut escape bugs 40%. Before that I did manual + API testing for 2 years. I saw you're scaling payments — is flaky test suite the main pain right now?"

• Now-proof langsung di 10 detik pertama
• Tidak ada riwayat hidup kronologis
• Tutup dengan pertanyaan = dialog, bukan monolog

Self-check: Di bawah 60 detik saat dibaca keras? · Ada 1 angka bukti? · Diakhiri pertanyaan, bukan "thank you"?

Skenario: Klien mau retainer 40 jam/bulan untuk SEO content. Kamu biasa $25/hr project-based. Mereka tawar $18/hr "karena stabil".

Tugas: Tulis balasan 120 kata: anchor, counter $22-24/hr retainer, scope guardrail, trial.

Jelek: I cannot accept $18/hr. My rate is $25/hr fixed. Let me know if you agree.

Bagus: "Thanks — I like retainers too. My project rate is $25/hr; for a 40h retainer I can do $22/hr ($880/mo) with scope: 8 articles/mo, 2 revisions each, 5-day turnaround. Anything beyond that billed at $25/hr. Happy to trial 1 month then review. Does a 15-min call Thu work to lock scope?"

• Kasih diskon retainer yang masuk akal, bukan jebol
• Scope ditulis = anti scope creep
• Trial + call = tetap jalan, tidak deadlock

Self-check: Ada angka retainer bulanan eksplisit? · Ada scope guardrail (jumlah + revisi)? · Ada trial + review clause?

Skenario: Sudah follow-up day-3 tanpa balas. Sekarang day-7. Satu email terakhir sebelum move on.

Tugas: Tulis breakup email 70 kata: value-add + permission to close + pintu tetap buka.

Jelek: I am still waiting for your response. Please reply ASAP as I need to know.

Bagus: "Hi [Name], closing the loop on the Data Analyst role — no worries if timing shifted. Sharing a quick teardown I did of a similar funnel issue [link], in case useful for the team. If priorities change, happy to reconnect. Wishing you a smooth hire. — [Name]"

• "Closing the loop" = kamu yang tutup, bukan memohon
• Resource gratis = diingat sebagai giver
• Nada lulus = reputasi jangka panjang

Self-check: Tidak ada kata menekan? · Ada satu value-add link? · Nada closure, bukan begging?

Skenario: Job: "Need ID LQA for mobile RPG, 10K words, in-context review + bug log. Budget $400. 5 days."

Tugas: Tulis proposal 150 kata: tool + process + sample bug format + timeline.

Jelek: I am a translator and gamer. I can translate your game well and fast.

Bagus: "ID gamer + 3 RPG titles shipped. Process: 1) Glossary lock Day 1 2) In-context pass on Android device (Redmi Note) Day 2-3 3) Bug log + severity Day 4 4) Final QA Day 5. Sample log: [BTN_045] TRUNCATION — ID text overflows 20% → suggest 'Masuk' not 'Masuk Sekarang'. Rate $400 flat, 2 revision rounds. Question: build provided via TestFlight or APK?"

• Device + genre disebut = trust gamer
• Sample log 1 baris = bukti format kerja
• Pertanyaan build = paham workflow game

Self-check: Ada device + genre? · Ada sample bug format? · Ada timeline per hari?

Skenario: Klien: "Bikin dashboard dong." Tidak ada data sample, tidak ada user, tidak ada deadline. Kamu punya 15 menit untuk gali.

Tugas: Tulis 7 pertanyaan discovery berurutan (goal → user → data → decision → timeline → budget → next step).

Jelek: What tools do you use? When do you need it? What is your budget?

Bagus: "1) What decision will this dashboard change weekly? 2) Who opens it daily vs monthly? 3) Where does data live now — Sheets/CSV/API? 4) How messy is it (dupes/missing)? 5) What does good look like in numbers? 6) Deadline driver apa? 7) If I send a 1-page scope + fixed price by Friday, who approves?"

• Q1-Q2: value + user = anti dashboard zombie
• Q3-Q4: data check = estimasi realistis
• Q7: kunci approval + tanggal = deal maju

Self-check: Ada pertanyaan decision, bukan cuma tool? · Ada pertanyaan data source + quality? · Ditutup next step + approver?