{"title":"Coffee Chats","description":null,"content":"Getting someone to agree to a short call is a good start, but the call still needs a little preparation. If you show up with vague questions and no clear purpose, the conversation may be pleasant but not very useful.\n\nA good coffee chat is simple: respect the person's time, ask thoughtful questions, learn something real about the team, and close with a sensible next step. Sometimes that next step is a referral. Sometimes it is another person to talk to. Sometimes it is just better information. All three can help your search.\n\n---\n\n# The Three Purposes of an Informational Interview\n\nAn informational interview has three practical purposes.\n\nFirst, you want to understand the team better than a job description can tell you. Second, you want the other person to see that you are serious and prepared. Third, if there is a real fit, you may want to ask about the best way to be considered.\n\nDo not treat the call as a hidden way to get a referral. People can feel that. At the same time, do not pretend there is no job-search purpose at all. The honest middle is best: you are exploring the company, you value their perspective, and you would like guidance on the right next step if the conversation goes well.\n\nPreparation is what makes the call useful. Ten minutes of research before the conversation helps you ask better questions and avoid spending the call on things you could have found yourself.\n\nHere is the full arc of an informational interview, from prep to next step.\n\n\n```mermaid\nflowchart LR\n A[Prep 10 min
profile, blog, role]:::start --> B[Open by respecting
their time]:::step\n B --> C[Ask prepared
questions]:::step\n C --> D[Close with a
clear next step]:::closing\n D --> E[Thank-you note
within a day]:::done\n\n classDef start fill:#00ceff,stroke:#000,color:#000\n classDef step fill:#ffa94d,stroke:#000,color:#000\n classDef closing fill:#38d9a9,stroke:#000,color:#000\n classDef done fill:#69db7c,stroke:#000,color:#000\n```\n\n\nThe middle of the call is where you learn about the team, but the two ends carry most of the value: arriving prepared earns the person's attention, and closing with a clear next step turns a pleasant chat into progress on your search.\n\n---\n\n# Running the Call\n\n### Prepare for ten minutes before the call\n\nRead the person's LinkedIn profile, skim the company's engineering blog if they have one, and review the role or team you are interested in. Look for two or three specific things to ask about, such as a project their team shipped, a technology they use, or how the team is structured.\n\n### Show up on time and ready\n\nTest your audio, have your questions written down, and keep your resume nearby in case they ask about your background. You do not need to sound rehearsed, but you should be ready.\n\n### Open by respecting their time\n\nThank them for making time and confirm the length of the call. A simple opening works: \"Thanks for taking the time. I know we planned for 15 minutes, so I'll be mindful of that.\"\n\n### Ask your prepared questions\n\nStart with specific questions that show you did basic research. Then listen. This should feel like a conversation, not an interview script.\n\n### Give a short version of your background when it fits\n\nThey may ask what you are working on or what kind of role you want. Have a two-sentence answer ready so they understand your background without getting a long career history.\n\n### End with a clear next step\n\nIn the last couple of minutes, ask a next-step question that fits the conversation. You might ask whether the team is hiring, who else you should speak with, or whether they would be comfortable referring you for a specific role.\n\n### Send a thank-you within a day\n\nSend a short note within a day. Mention one specific thing from the conversation and thank them for their time. If they offered to refer you, include the role link, your resume, and a short summary.\n\n---\n\n# The Questions Worth Asking\n\nGood questions help you understand the role and show that you came prepared. Vague questions make the other person do too much work.\n\n**Five questions worth asking:**\n\n- \"What does a typical week look like on your team right now?\" This gets closer to the real work than the job description.\n- \"What is the hardest technical problem the team is working on?\" This shows interest in the engineering and gives you useful context.\n- \"How did you decide to join, and has it matched what you expected?\" This can surface honest information about the team and company.\n- \"What would make someone successful on this team in their first six months?\" This tells you what the team actually values.\n- \"Is the team hiring, and if so, what is the best way for someone with my background to be considered?\" Ask this near the end, after you have had a real conversation.\n\n**Five questions that waste the call:**\n\n- \"What does your company do?\" You should know the basics before the call.\n- \"What is the salary range?\" This usually belongs with a recruiter or hiring manager, not an engineer on an informal call.\n- \"Can you refer me?\" as your opening. It is too abrupt before any real conversation has happened.\n- \"What is it like working in tech?\" This is too broad to answer well.\n- \"Do you have any tips for my job search?\" This is too broad. Ask a specific question instead.\n\n---\n\n# Ending the Call Well\n\nThe last two minutes matter. Do not let the call end with only \"this was great, thanks.\" Ask for a specific next step that matches how the conversation went.\n\nIf the call went well and the team is hiring, ask directly but politely:\n\n\n```javascript\nThis was really helpful. The team sounds close to what I'm looking for. Would\nyou be comfortable referring me for the open backend role, or pointing me to\nthe right person if someone else handles that?\n```\n\n\nIf the team is not hiring, or you are not sure a referral ask fits, choose a softer next step:\n\n\n```javascript\nIs there someone else on the team you think would be useful for me to speak\nwith?\n```\n\n\n\n```javascript\nWould it be alright if I reached back out if a relevant role opens up?\n```\n\n\nBoth options keep the door open without pushing too hard.\n\nThen send a thank-you within a day and make it specific.\n\n**Post-call thank-you template:**\n\n\n```javascript\nHi Wei, thanks for taking the time today. The point about how your team handles\non-call helped me understand what the work is like. I've applied to the backend\nrole we discussed (job ID 4821), and I appreciate you offering to refer me. I've\nattached my resume and a short summary in case it is useful for the referral\nform. Thanks again for your time.\n```\n\n\n**Why this works:** It references a specific moment from the call, confirms the next step, and gives them what they need if they offered to refer you. It is specific without being pushy.\n\n---\n\n# Common Coffee Chat Mistakes\n\nA coffee chat can end pleasant and still leave you with nothing useful, usually because of one of these six errors.\n\n- **Showing up without preparation.** Generic questions lead to generic answers. Ten minutes of research makes the call better.\n- **Treating it as only small talk.** It can be friendly and still have a purpose. Bring questions and close with a next step.\n- **Opening with the referral ask.** Ask for context first. If a referral makes sense, bring it up near the end.\n- **Asking questions you could have looked up yourself.** \"What does the company do?\" signals that you did not prepare.\n- **Running long.** If you asked for 15 minutes, respect that. Ask before going over.\n- **Skipping the thank-you.** A specific thank-you note is professional and helps the next step happen.","pageType":"job-search"}

Get Premium