<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Communication on Jim's Notes</title><link>https://shizhi3620.github.io/en/tags/communication/</link><description>Recent content in Communication on Jim's Notes</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://shizhi3620.github.io/en/tags/communication/index.xml" rel="self" type="application/rss+xml"/><item><title>Job-Search Notes: Making the Work Visible</title><link>https://shizhi3620.github.io/en/posts/job-search-notes-on-making-the-work-visible/</link><pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate><guid>https://shizhi3620.github.io/en/posts/job-search-notes-on-making-the-work-visible/</guid><description>&lt;p&gt;Job-search preparation often begins with a resume, but a harder question remains beyond it: how can someone understand how I work without reducing complex experience to a few vague verbs?&lt;/p&gt;&#10;&lt;p&gt;I prefer to begin with a specific problem. Describe the constraints at the time, the role I held, the actions taken, and which parts of the result can be verified. Where there is no data or public material to support a claim, preserving uncertainty matters more than adding an attractive story. It respects the facts and makes the conversation more efficient.&lt;/p&gt;&#10;&lt;p&gt;Public work, short retrospectives, and ongoing learning notes can extend the limited space of a resume. But being public is not the same as revealing everything. Information about former employers, clients, colleagues, or internal systems should be de-identified, and sometimes omitted entirely. The point of professional communication is the approach to solving a problem, not details that are not mine to share.&lt;/p&gt;</description></item></channel></rss>