<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: PrismResume</title>
    <description>The latest articles on DEV Community by PrismResume (@prismresume).</description>
    <link>https://dev.to/prismresume</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3966702%2F0875b334-9755-46cb-837a-e84f887e4317.png</url>
      <title>DEV Community: PrismResume</title>
      <link>https://dev.to/prismresume</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/prismresume"/>
    <language>en</language>
    <item>
      <title>Resume After Coding Bootcamp Without a CS Degree</title>
      <dc:creator>PrismResume</dc:creator>
      <pubDate>Tue, 15 Sep 2026 15:41:30 +0000</pubDate>
      <link>https://dev.to/prismresume/resume-after-coding-bootcamp-without-a-cs-degree-1do0</link>
      <guid>https://dev.to/prismresume/resume-after-coding-bootcamp-without-a-cs-degree-1do0</guid>
      <description>&lt;h2&gt;
  
  
  Why Your Degree Status Is Not the Real Problem
&lt;/h2&gt;

&lt;p&gt;Hiring managers do not reject bootcamp grads for missing a CS degree. They reject resumes that &lt;em&gt;feel incomplete&lt;/em&gt; — lists of language names without proof, job gaps explained by education, or a skills section that repeats the bootcamp syllabus. The real problem is vagueness, not the missing credential.&lt;/p&gt;

&lt;p&gt;Every bullet on your resume should close the gap between "I took a bootcamp" and "I can contribute on day one." If a sentence could appear on the syllabus, it must be rewritten as an accomplishment. "Learned React" becomes "Built a three-component checkout flow that reduced form validation errors by 40%." That single change makes the degree irrelevant.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Skills-First Format: How to Structure a Bootcamp Resume
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Replace the Education Section with a Results Section
&lt;/h3&gt;

&lt;p&gt;Most bootcamp grads open with an Education section and list the bootcamp name, date, and a bullet about "12-week immersive program." That tells the reader nothing useful. Instead, lead with a &lt;strong&gt;Professional Summary&lt;/strong&gt; of two lines that names your strongest skill and a concrete result you can deliver:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Full-stack developer who builds accessible React applications. Deployed a customer portal that reduced support tickets by 30% in the first quarter."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Follow that with a &lt;strong&gt;Technical Projects&lt;/strong&gt; section before any job experience or education. This is where you prove competence. List 2-3 projects with links to live demos or GitHub repos. Each entry must include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;One sentence of context (what did the project solve?)&lt;/li&gt;
&lt;li&gt;The tech stack (React, Node, MongoDB — be specific)&lt;/li&gt;
&lt;li&gt;A measurable result ("cut page load time from 3s to 0.8s")&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The One Rule: Never Let the Reader Guess Your Skills
&lt;/h3&gt;

&lt;p&gt;If a recruiter scans your resume and cannot immediately tell what you &lt;em&gt;did&lt;/em&gt; with each tool, the resume fails. Replace generic phrases like "Proficient in React" with a bullet that shows proficiency:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Before:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Proficient in React, Node.js, and MongoDB&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;After:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Built a multi-user dashboard with React and Redux, reducing API calls by 60% through client-side caching.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The second bullet tells the recruiter exactly how you work, not just what you studied.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to Do About a Non-Technical Work History
&lt;/h2&gt;

&lt;p&gt;Your previous jobs may have zero code in them. That is fine — but do not list a retail or food-service job as four bullets about "handled cash" and "assisted customers." Instead, mine that experience for transferable skills and rewrite every bullet to sound like engineering behavior:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Original (retail associate):&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Handled customer returns and processed exchanges&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Rewritten:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Resolved 40+ escalated customer issues per week by diagnosing root causes and implementing a follow-up checklist — a process later adopted by three other stores.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Diagnosing root causes, implementing repeatable processes, and having work adopted by others are the exact signals hiring managers look for in a developer. Do not leave those signals buried.&lt;/p&gt;

&lt;p&gt;If you have no job experience at all — recent graduate with no work history — skip the work section entirely and add a fourth project. An all-projects resume is better than a thin employment section.&lt;/p&gt;

&lt;h2&gt;
  
  
  ATS Formatting Rule Bootcamp Grads Get Wrong
&lt;/h2&gt;

&lt;p&gt;Applicant tracking systems (ATS) parse your resume for keywords, but they also flag formatting that hides information. The biggest mistake bootcamp grads make? Using columns, tables, or infographic progress bars for skill levels.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Correct approach:&lt;/strong&gt; List programming languages, frameworks, and tools in plain comma-separated lines under a single "Technical Skills" heading. Never use:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Skill bars ("React ██████◻◻◻◻")&lt;/li&gt;
&lt;li&gt;Star ratings&lt;/li&gt;
&lt;li&gt;Tables or multi-column layouts&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Why? An ATS reads left-to-right, top-to-bottom. A two-column layout often reads as one long, wrapped line of gibberish, causing the parser to drop entire sections. Stay single-column, 1-inch margins, and use a standard sans-serif font (Calibri, Arial, or Helvetica).&lt;/p&gt;

&lt;h2&gt;
  
  
  The One Project That Should Be on Every Bootcamp Resume
&lt;/h2&gt;

&lt;p&gt;If you build only one thing outside the bootcamp curriculum, make it a &lt;strong&gt;form-to-API pipeline&lt;/strong&gt; with error handling, loading states, and a database write. Here is what that looks like on a resume:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Customer Feedback Dashboard&lt;/strong&gt; – A full-stack app capturing user feedback and visualizing trends.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;React frontend with controlled form inputs, validation, and optimistic UI updates.&lt;/li&gt;
&lt;li&gt;Node/Express REST API with rate limiting and PostgreSQL persistence.&lt;/li&gt;
&lt;li&gt;Deployed on Render with a CI/CD pipeline running Mocha tests on each push.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;A single project that touches the full stack — frontend, backend, database, deployment, testing — communicates more than a list of ten half-finished tutorial apps. Every hiring manager wants to know you can move code from your local machine to the internet. Prove that once, and the degree question disappears.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Should I list my bootcamp on the resume or leave it off?
&lt;/h3&gt;

&lt;p&gt;List it, but only after your Technical Projects section and only as a single line: "[Bootcamp Name], Full-Stack Web Development, [Month Year]." Do not explain the curriculum in bullets — the reader already knows bootcamps teach X, Y, and Z. Show what you built instead.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I explain a gap after bootcamp if I haven't found a job yet?
&lt;/h3&gt;

&lt;p&gt;Do not explain it on the resume. Use the gap to build one more project, then add that project to your resume under a "Projects" heading. The only thing a hiring manager cares about is whether you can code today — not when you last studied.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I get a software engineering job without a CS degree?
&lt;/h3&gt;

&lt;p&gt;Yes — thousands of developers do it every year. The key is to emphasize results and projects over credentials. Companies like Google, Apple, and IBM have dropped degree requirements for many roles. Focus on demonstrable skills, and the degree becomes irrelevant.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should I add "CS50" or "Codecademy" certificates to my resume?
&lt;/h3&gt;

&lt;p&gt;No. Certificates from self-paced platforms carry no weight compared to a live demo or a GitHub repository. One deployable project outperforms ten certificates. If you must include a certificate, place it under a small "Additional Training" line at the very bottom — never in the main education section.&lt;/p&gt;

&lt;p&gt;Your resume is stronger than you think. The missing degree is invisible once your bullet points show real work. If you want a free, clean resume template built for ATS parsing — designed specifically for skills-forward applicants — start with a free download at PrismResume.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://prismresume.com/blog/resume-after-coding-bootcamp-without-a-cs-degree" rel="noopener noreferrer"&gt;prismresume.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>programming</category>
      <category>career</category>
    </item>
    <item>
      <title>From 996 to US Resume Bullets: Rewriting Scope and Hours</title>
      <dc:creator>PrismResume</dc:creator>
      <pubDate>Wed, 09 Sep 2026 16:22:54 +0000</pubDate>
      <link>https://dev.to/prismresume/from-996-to-us-resume-bullets-rewriting-scope-and-hours-b85</link>
      <guid>https://dev.to/prismresume/from-996-to-us-resume-bullets-rewriting-scope-and-hours-b85</guid>
      <description>&lt;h2&gt;
  
  
  Why 996 Details Hurt Your Resume, Not Help It
&lt;/h2&gt;

&lt;p&gt;Mentioning "996 culture" or writing bullets like "worked 12 hours daily for months" signals a norm that US hiring managers interpret as operational chaos, not dedication. American recruiters value efficiency and results over seat time, so listing hours can make you seem like a cost center, not a driver of value.&lt;/p&gt;

&lt;p&gt;Instead, every bullet should answer: &lt;em&gt;What changed because of your work?&lt;/em&gt; Focus on lead time, defect rate, team throughput, or revenue protected. If you crashed a server at 2 AM, write "restored production in 47 minutes, preventing $12K/min revenue loss" — not "stayed until 3 AM."&lt;/p&gt;

&lt;h3&gt;
  
  
  The One Phrase to Delete From Every Bullet
&lt;/h3&gt;

&lt;p&gt;Delete every variation of "worked long hours," "overtime," "996 schedule," or "extended shifts." These words are anti-patterns in US resumes. Even if the hiring manager is sympathetic to your work ethic, your resume will be screened by keywords — and those keywords flag burnout, not brilliance.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before and After: A Real Rewrite
&lt;/h2&gt;

&lt;p&gt;Take this original bullet from a Chinese internet company developer:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Before (996-era phrasing):&lt;/strong&gt; &lt;em&gt;"Worked 996 schedule for 3 months to complete backend migration; often stayed until 2 AM to meet aggressive deadlines."&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After (US-impact style):&lt;/strong&gt; &lt;em&gt;"Led backend migration covering 12 microservices with zero production downtime; completed 2 weeks ahead of revised schedule by automating regression tests."&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Notice what changed:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Deleted the hours and schedule mention.&lt;/li&gt;
&lt;li&gt;Added concrete scope: 12 microservices.&lt;/li&gt;
&lt;li&gt;Measured quality: zero downtime.&lt;/li&gt;
&lt;li&gt;Quantified speed: 2 weeks ahead.&lt;/li&gt;
&lt;li&gt;Identified the method: automated regression tests.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Translating Role Scope: From Team Size to Span of Control
&lt;/h2&gt;

&lt;p&gt;Chinese 996-culture roles often have wide scope but loose reporting structures. A "tech lead" in a 996 environment might manage 8 developers without an official title, while handling DevOps, QA, and production support. On a US resume, combine these responsibilities: &lt;em&gt;"Supervised 8 engineers (2 senior, 5 mid, 1 junior); reduced incident response time 40% by building an on-call rotation."&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Use these substitution rules:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"996/997 schedule" → "On-call for critical system 24/7, resolved 15+ monthly incidents"&lt;/li&gt;
&lt;li&gt;"Worked overtime to fix bugs" → "Reduced outstanding bugs 70% in 90 days"&lt;/li&gt;
&lt;li&gt;"Volunteered for extra shifts" → "Increased team output 25% by cross-training 3 new hires"&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The Three-Bullet Cleanup Checklist
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Delete&lt;/strong&gt; every time reference (hours, weeks, months, years). Replace with a result: "migration completed," "code deployed," "incident resolved."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Insert&lt;/strong&gt; a number: percentage reduced, units shipped, dollars saved, minutes improved. If you don't have the exact number, estimate conservatively (e.g., "reduced by ~30%" — honest and still concrete).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rewrite out loud&lt;/strong&gt; as if you're telling a friend at a coffee shop. If you sound miserable, cut. If you sound impressive, keep.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Formatting for ATS: What Really Matters
&lt;/h2&gt;

&lt;p&gt;ATS systems parse your bullet text, not the headers you create. So a section called "996 Project" is fine if the bullet text follows impact rules. But avoid graphics, tables, or time bars with hours per week. Use a standard chronological format: company, title, dates (month/year to month/year). ATS reads month/year best; writing "2018-2021" can confuse parsers that expect month-specific dates. Use "Mar 2018 – Jun 2021" or just list years if that's all you have.&lt;/p&gt;

&lt;p&gt;One factual point: most ATS software cannot interpret implied context from a single bullet that says "996 work." It only sees words. So if your bullet says "Resolved production issues within 30 minutes — typical 996 environment," the parser sees the word "996" and might reject you for anything a recruiter manually flagged as "high turnover culture." Keep your resume clean of cultural qualifiers.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Should I ever name "996" on my resume?
&lt;/h3&gt;

&lt;p&gt;No. Never list the phrase "996" anywhere on your US resume, even inside a bullet. It has no positive connotation and may trigger unconscious bias about burnout or poor management. If asked in an interview, explain it matter-of-factly: "The team had aggressive delivery timelines; I handled the pressure by improving automation."&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I explain gaps in tenure if 996 made me leave jobs quickly?
&lt;/h3&gt;

&lt;p&gt;Don't frame the gap around 996. On your resume, just list the dates honestly — short tenures are common for early-career tech roles. In your cover letter or interview, say "The pace was unsustainable, so I sought a healthier environment where I could do my best work." Keep the resume focused on results, not reasons.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I list a promotion that happened because I worked extra hours?
&lt;/h3&gt;

&lt;p&gt;Yes, but phrase it around performance: "Promoted to Senior Engineer after delivering 3 major features in 8 months — each ahead of schedule." The hours are implicit; the outcome is the star. You lose nothing by omitting the overtime detail.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should I translate Chinese company names and role titles?
&lt;/h3&gt;

&lt;p&gt;Absolutely. Use the standard English title for your role level (Software Engineer II, not "R&amp;amp;D Engineer"). If the company is well-known globally (Alibaba, Baidu, Tencent), keep the name. If it's lesser-known, add a one-line industry description, e.g., "Top-5 Chinese fintech company, $2B revenue." That gives context without mentioning hours.&lt;/p&gt;




&lt;p&gt;If you want a free tool to check your bullet language before sending, try the PrismResume checker. It flags vague phrasing and suggests impact-focused rewrites — no sign-up required to start.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://prismresume.com/blog/from-996-to-us-resume-bullets-rewriting-scope-and-hours" rel="noopener noreferrer"&gt;prismresume.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>programming</category>
      <category>career</category>
    </item>
    <item>
      <title>Indian IT Services to US Product Company Resume Rewrite</title>
      <dc:creator>PrismResume</dc:creator>
      <pubDate>Tue, 08 Sep 2026 16:17:02 +0000</pubDate>
      <link>https://dev.to/prismresume/indian-it-services-to-us-product-company-resume-rewrite-1a74</link>
      <guid>https://dev.to/prismresume/indian-it-services-to-us-product-company-resume-rewrite-1a74</guid>
      <description>&lt;h2&gt;
  
  
  Why your TCS resume looks like a services brochure (and how to fix it)
&lt;/h2&gt;

&lt;p&gt;Product recruiters scan for ownership, not hand-holding. When you write "Managed a team of 5 developing a payroll module for a UK telecom client," they see a cog in a vendor machine, not a product builder. The fix is simple: drop the client, drop the team size, and lead with the result. "Reduced payroll processing time by 30% by architecting a batch scheduler that cut manual intervention" — now you sound like a product engineer, not a services invoice.&lt;/p&gt;

&lt;p&gt;Your resume already contains the raw material; you just need to translate it. The rules below turn "maintained" into "improved" and "coordinated" into "led."&lt;/p&gt;

&lt;h2&gt;
  
  
  The one-sentence strike rule: Always lead with the business metric
&lt;/h2&gt;

&lt;p&gt;Every bullet must answer one question from the recruiter: &lt;em&gt;So what?&lt;/em&gt; If the first five words don't name a quantifiable result, delete them.&lt;/p&gt;

&lt;h3&gt;
  
  
  Before (services-style):
&lt;/h3&gt;

&lt;p&gt;"Developed REST APIs for a client-facing order management system using Spring Boot and deployed on AWS ECS."&lt;/p&gt;

&lt;h3&gt;
  
  
  After (product-style):
&lt;/h3&gt;

&lt;p&gt;"Increased order throughput by 25% by designing REST APIs that eliminated a polling bottleneck and cut response times from 4 seconds to 900 ms."&lt;/p&gt;

&lt;p&gt;The after version forces the reader to care. The before version is a checklist item anyone could write.&lt;/p&gt;

&lt;h2&gt;
  
  
  Drop the client, keep the problem
&lt;/h2&gt;

&lt;p&gt;Product companies hire you for your judgment, not your previous client's budget. Never start a bullet with "For Client X" or "As part of a team of N." Instead, describe a business problem you solved.&lt;/p&gt;

&lt;h3&gt;
  
  
  Concrete checklist: replace these 9 phrases
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;"Managed" → "Reduced manual effort by X%"&lt;/li&gt;
&lt;li&gt;"Coordinated with team" → "Drove cross-functional alignment to deliver Y"&lt;/li&gt;
&lt;li&gt;"Maintained" → "Overhauled" or "Refactored for 40% faster load"&lt;/li&gt;
&lt;li&gt;"Implemented" → "Designed and deployed"&lt;/li&gt;
&lt;li&gt;"Assisted" → "Led" (if you truly influenced outcome)&lt;/li&gt;
&lt;li&gt;"Supported" → "Developed from ground up"&lt;/li&gt;
&lt;li&gt;"Monitored" → "Automated monitoring, cutting alert noise by 70%"&lt;/li&gt;
&lt;li&gt;"Participated in" → "Contributed to" (but only if you had a vote in decision)&lt;/li&gt;
&lt;li&gt;"Created documentation" → "Built runbooks that reduced onboarding time for 3 new engineers"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Copy-paste the checklist into a sticky note. Work through every bullet until none use the left column.&lt;/p&gt;

&lt;h2&gt;
  
  
  Restructure your experience: Project lens, not tenure lens
&lt;/h2&gt;

&lt;p&gt;US product recruiters scan by relevance, not chronology. If you have 8 years at TCS spanning four different client projects, don't list them under one employer entry with a single date range.&lt;/p&gt;

&lt;h3&gt;
  
  
  What to do instead:
&lt;/h3&gt;

&lt;p&gt;List each project as a separate line under the same company header. Date each one with month-year spans. The format looks like:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;TCS&lt;/strong&gt; | Senior Systems Engineer | Bangalore, India | June 2018 – Present&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Project: Retail Order Platform for Nike (October 2021 – March 2023)&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Reduced abandoned carts by 22% by building a real-time inventory lookup that updated stock within 150 ms.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Project: Claims Processing Engine for Aetna (April 2019 – September 2021)&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Cut average claims adjudication time from 2.5 days to 4 hours by redesigning a legacy batch system into an event-driven pipeline.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Now the recruiter sees ownership of discrete outcomes, not a generic tenure. Each project is a mini resume that shows decision-making.&lt;/p&gt;

&lt;h2&gt;
  
  
  ATS formatting fact that actually helps
&lt;/h2&gt;

&lt;p&gt;A standard US resume uses a two-column layout &lt;em&gt;only&lt;/em&gt; if the left column is a thin sidebar (contact info + technologies) and the main column is text. Do not use a table-based layout or text boxes—ATS parsers (e.g., Kula, Talemetry) strip them. Use simple left-aligned headers with bold section names. No graphics, no icons. The safest font is 10–12 pt Calibri or Arial; margins no smaller than 0.5 inch. If your resume contains a chart or graphic, delete it—ATS cannot read embedded images, and your bullet text will be invisible.&lt;/p&gt;

&lt;h2&gt;
  
  
  The skill section trap: never list a technology you cannot defend in an interview
&lt;/h2&gt;

&lt;p&gt;Product engineers expect you to explain trade-offs. If your skill section lists "Docker, Kubernetes, Jenkins, Ansible, Terraform, AWS Lambda, DynamoDB, Kafka," be ready to discuss &lt;em&gt;why&lt;/em&gt; you chose DynamoDB over Cassandra for a specific query pattern. If you cannot give a reasoned trade-off, remove the skill. A resume with 10 well-understood tools beats a resume with 30 buzzwords.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick match for a real difference
&lt;/h2&gt;

&lt;p&gt;Run your current resume through PrismResume's free checker (no sign-up) to spot which bullets still sound services-y. It highlights passive phrasing and missing metrics, so you can fix before sending.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  How do I handle a client project under NDA?
&lt;/h3&gt;

&lt;p&gt;Don't name the client; name the vertical and the problem. "For a Fortune 500 retail client" is fine. Focus on the technical decisions and outcomes, not the client name.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should I include the team size for each project?
&lt;/h3&gt;

&lt;p&gt;No—it signals you were a member of a vendor team, not a product owner. Product resumes rarely mention team size. If you led a team, say "Led a team that" but omit the number.&lt;/p&gt;

&lt;h3&gt;
  
  
  What about certifications like AWS Certified Developer or PMP?
&lt;/h3&gt;

&lt;p&gt;List them in a separate Certification section at the bottom, but only if they are active and relevant. PMP is borderline—product companies prefer evidence of actual technical delivery over project management theory.&lt;/p&gt;

&lt;h3&gt;
  
  
  My resume currently has a summary that says "X years of experience." Should I keep it?
&lt;/h3&gt;

&lt;p&gt;Replace it with a 2-line value proposition targeting the specific role. Example: "Backend engineer who built distributed systems that processed 10M+ transactions daily at sub-100ms latency." Avoid generic lines like "professionally trained."&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://prismresume.com/blog/indian-it-services-to-us-product-company-resume-rewrite" rel="noopener noreferrer"&gt;prismresume.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>programming</category>
      <category>career</category>
    </item>
    <item>
      <title>Social Credit System to Resume: Ethical Data Privacy Wins</title>
      <dc:creator>PrismResume</dc:creator>
      <pubDate>Sun, 06 Sep 2026 16:00:43 +0000</pubDate>
      <link>https://dev.to/prismresume/social-credit-system-to-resume-ethical-data-privacy-wins-27k5</link>
      <guid>https://dev.to/prismresume/social-credit-system-to-resume-ethical-data-privacy-wins-27k5</guid>
      <description>&lt;h2&gt;
  
  
  Why Your Social Credit Experience Is a Privacy Asset—Not a Stigma
&lt;/h2&gt;

&lt;p&gt;US hiring managers in data privacy, cybersecurity, and compliance fear one thing above all: candidates who treat personal data as a surveillance tool. Your Chinese social credit system project sounds like the exact opposite of ethical data handling. But here is the twist: China's Personal Information Protection Law (PIPL) is structurally very close to GDPR, and any project that handled real Chinese citizen data had to comply with PIPL's consent, minimization, and right-to-deletion requirements. That makes you more qualified than most US applicants who have never touched a real privacy framework.&lt;/p&gt;

&lt;p&gt;The key is to reframe the system's purpose. Never describe it as "tracking citizen behavior" or "scoring compliance." Instead, describe the technical challenge: building a data platform that balanced multiple data-subject rights (consent, access, rectification, erasure) while processing high-volume personal data under strict regulatory oversight. That is exactly what a US privacy engineer or data governance analyst does.&lt;/p&gt;

&lt;h2&gt;
  
  
  The One Ethical Frame That Makes Every Bullet Safe
&lt;/h2&gt;

&lt;p&gt;Use this frame for every bullet: "Designed/implemented [technical action] to comply with [regulation] while [positive ethical outcome for the data subject]." This converts surveillance-tinged work into a privacy-advancing narrative. For example:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Before:&lt;/strong&gt; "Built social credit scoring algorithm that evaluated citizen trustworthiness based on 200+ data points."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;After:&lt;/strong&gt; "Designed data-processing pipeline for 200+ personal-data attributes under PIPL consent-and-minimization rules, reducing unnecessary data collection by 35% and ensuring each data subject retained right to access and correct their own record."&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The second version never uses the word "scoring" or "trustworthiness." It emphasizes the privacy controls you implemented, not the judgment the system made.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to Translate the System's Purpose (Without Lying)
&lt;/h2&gt;

&lt;p&gt;US recruiters are not naive—they know what social credit systems do. You cannot pretend the project was a charity data platform. But you can honestly describe your role's compliance layer. Use these substitution rules when writing your bullet points:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Instead of:&lt;/strong&gt; "evaluated citizens" → "managed personal data records"&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Instead of:&lt;/strong&gt; "scoring" → "data aggregation with privacy controls"&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Instead of:&lt;/strong&gt; "behavioral tracking" → "consent-based data collection"&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Instead of:&lt;/strong&gt; "punishment system" → "regulatory compliance framework"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Then add the specific regulation you followed. Even if the project was not audited by a privacy authority, if your team documented consent or data minimization, you can say "under PIPL data-minimization principles" or "following internal compliance policies aligned with PIPL."&lt;/p&gt;

&lt;h2&gt;
  
  
  Before/After Bullet Rewrite Example (Real, Specific, Copy-Paste Ready)
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Before (as most Chinese engineers write it):
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Developed citizen social credit database for 10 million users, assigned scores based on financial and social behaviors.&lt;/li&gt;
&lt;li&gt;Optimized SQL queries to reduce score calculation time by 40%.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  After (US-ethics-ready, ATS-friendly):
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Architected a 10-million-record personal data platform with role-based access controls (RBAC), data-anonymization layers, and automated consent-revocation workflows compliant with PIPL Article 15-19.&lt;/li&gt;
&lt;li&gt;Built batch-processing pipeline for aggregated personal-data attributes (no individual scoring output), reducing ETL latency by 40% while logging every data access for audit trails.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The second version uses standard US data-engineering keywords (RBAC, anonymization, consent-revocation, ETL, audit trails). It never mentions "scoring" or "behavior." It also shows you understand data-subject rights (consent revocation) and auditability—two core US privacy expectations.&lt;/p&gt;

&lt;h2&gt;
  
  
  ATS-Formatting Fact That Actually Matters
&lt;/h2&gt;

&lt;p&gt;ATS systems parse the "Work Experience" section by looking for standard job titles and dates. If your title was "Data Engineer — Social Credit Project," keep it exactly like that—do not rename it to "Privacy Engineer." ATS will reject a fake title match. Instead, under that honest title, write bullets that clearly describe privacy work. The ATS cares about keywords in bullets far more than the title itself. Also, use the month-year format ("May 2021 – Aug 2023") and never embed dates in paragraph text—ATS parsers scan for date ranges on separate lines.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Can I mention the Chinese government as my client?
&lt;/h3&gt;

&lt;p&gt;Yes, but do not say "government surveillance project." Say "government-contracted data infrastructure project under regulatory compliance requirements." The US recruiter knows what it means, but the phrasing signals you understand how to work with regulated data, not surveillance.&lt;/p&gt;

&lt;h3&gt;
  
  
  What if I had no formal PIPL compliance documentation?
&lt;/h3&gt;

&lt;p&gt;If your project followed any data-handling rules at all (consent checkboxes, data minimization, deletion requests), you can say "applied PIPL-informed data governance practices." You do not need a certification. The frame is honest if your team actually handled personal data with those principles.&lt;/p&gt;

&lt;h3&gt;
  
  
  Will a US recruiter reject my resume outright for a social credit project?
&lt;/h3&gt;

&lt;p&gt;Not if you frame it ethically. A 2024 LinkedIn survey of privacy hiring managers found that candidates with real-world experience in any strict data-regulation environment (including PIPL) were preferred over those with only theoretical GDPR knowledge. The stigma vanishes when you lead with compliance, not surveillance.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should I omit the project entirely if I feel uncomfortable?
&lt;/h3&gt;

&lt;p&gt;If you feel the project was genuinely unethical and you cannot reframe it honestly, omit it. A resume gap explained by "relocated to the US" or "pursued further education" is safer than a bullet that feels dishonest to you. But if you built technical privacy controls that protected individual rights, that work is legitimate and valuable—write it.&lt;/p&gt;




&lt;p&gt;Get a free, instant check on how your Chinese experience reads to US eyes. No sign-up, no uploads stored—just paste your bullets at PrismResume's checker.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://prismresume.com/blog/social-credit-system-to-resume-ethical-data-privacy-wins" rel="noopener noreferrer"&gt;prismresume.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>datascience</category>
      <category>career</category>
    </item>
    <item>
      <title>List a Chinese Patent Application on a FAANG Resume: One Rule</title>
      <dc:creator>PrismResume</dc:creator>
      <pubDate>Thu, 03 Sep 2026 15:35:25 +0000</pubDate>
      <link>https://dev.to/prismresume/list-a-chinese-patent-application-on-a-faang-resume-one-rule-1nm</link>
      <guid>https://dev.to/prismresume/list-a-chinese-patent-application-on-a-faang-resume-one-rule-1nm</guid>
      <description>&lt;h1&gt;
  
  
  Why a Chinese Patent Application Belongs on a FAANG Resume
&lt;/h1&gt;

&lt;p&gt;A published Chinese patent application is a verifiable technical document that demonstrates original problem-solving, system design, and implementation skills—the exact traits FAANG hiring managers look for in senior or staff engineers. Unlike a granted patent, an application is still under examination, but it already carries a publication number (e.g., CN114123456A) that an ATS or recruiter can cross-check. Listing it correctly signals that you understand US intellectual property norms and are confident in your work.&lt;/p&gt;

&lt;p&gt;Chinese applicants often worry that a pending application will be seen as less valuable. In practice, FAANG technical screeners treat published applications as strong evidence of your ability to architect, document, and defend a technical idea—especially for roles in cloud infrastructure, distributed systems, ML platforms, or security.&lt;/p&gt;

&lt;h1&gt;
  
  
  The One Rule: Always Mark the Status
&lt;/h1&gt;

&lt;p&gt;The single most common mistake is omitting the status entirely. A line like "Chinese Patent: Multi-Tenant Data Pipeline" looks like a granted patent, and an interviewer who searches the number may find only the application—and assume you misrepresented it. Instead, use this exact format:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Title&lt;/strong&gt; – Filing/Publication Number (Application), Date&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Example (correct):&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Chinese Patent Application: Scalable Stream Processing for Multi-Tenant Log Analytics – CN114123456A (Application), filed March 2023&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;If the application has already been granted, use "Patent" and include the grant date. If it is still under examination, always write "(Application)" after the number. Do not use "patent pending"—that phrase is vague and not a substitute for the real number.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before / After Bullet Rewrite
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Before (weak):&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Filed a Chinese patent on data pipeline optimization.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;After (strong, FAANG-ready):&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Co-invented a stream-processing method (Chinese Patent Application CN114123456A) that reduced end-to-end latency by 38% across 200+ production nodes, saving $1.2M/year in compute cost.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The rewritten version includes the application number, a quantified impact, and the co-inventor role—exactly what a FAANG technical resume reviewer expects.&lt;/p&gt;

&lt;h1&gt;
  
  
  Where to Place It on the Resume
&lt;/h1&gt;

&lt;p&gt;Put the patent application in a dedicated "Patents and Publications" section, not buried under "Projects" or "Work Experience." If you have only one application, it can sit at the bottom of the resume after Education and Skills. For senior roles with multiple patents, create a standalone section immediately after Experience but before Education.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sample section header:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;PATENTS&lt;/p&gt;

&lt;p&gt;Chinese Patent Application: Dynamic Resource Allocation for GPU Clusters – CN114654321A (Application), filed June 2024&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;If you co-invented the application with colleagues, add your role: "Second inventor (of four)." Do not list your percentage of contribution—that is unusual on a US resume.&lt;/p&gt;

&lt;h1&gt;
  
  
  What a FAANG Recruiter Actually Checks
&lt;/h1&gt;

&lt;p&gt;FAANG recruiters and hiring managers are familiar with Chinese patent applications because many candidates from Tencent, Alibaba, and Baidu list them. They will verify the publication number on the Chinese National Intellectual Property Administration (CNIPA) database or through a quick Google search. A fake or unverifiable number is a red flag that can disqualify you immediately.&lt;/p&gt;

&lt;p&gt;They care about three things: (1) Does the application exist and match the title? (2) Is the candidate a named inventor? (3) Does the technical description align with the claimed impact? If your resume says the application reduced latency by 40%, be prepared to explain how—not just in the interview, but in the bullet itself.&lt;/p&gt;

&lt;h1&gt;
  
  
  ATS-Formatting Fact for Chinese Patent Numbers
&lt;/h1&gt;

&lt;p&gt;Most ATS systems parse patent numbers as free text—they do not auto-detect a Chinese patent number the way they might a US patent (US20210000000A1). To avoid parsing errors, write the number in a single string with no spaces: CN114123456A. Do not use hyphens, slashes, or characters like “CN.114.123456.A.” If the ATS splits the number on punctuation, your application becomes unverifiable. Keep it to one unbroken token.&lt;/p&gt;

&lt;p&gt;Also, include the application date (month and year is sufficient) so a recruiter can quickly gauge recency without clicking out of the resume.&lt;/p&gt;

&lt;h1&gt;
  
  
  What If the Application Was Rejected?
&lt;/h1&gt;

&lt;p&gt;A rejected Chinese patent application is still a valid technical achievement if you can describe the invention clearly. Write:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Chinese Patent Application (rejected): Title – CN114123456A, filed March 2023&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The word "rejected" is honest and avoids surprise in an interview. FAANG engineers know that many strong applications are rejected for procedural or prior-art reasons. If you cannot explain why it was rejected, do not list it. If you can, it shows maturity and self-awareness.&lt;/p&gt;

&lt;h1&gt;
  
  
  When to Leave It Off
&lt;/h1&gt;

&lt;p&gt;Do not list a patent application if you cannot remember the filing number, the title, or your specific contribution. A vague line like "Chinese patent on AI algorithms" hurts more than it helps—it looks like name-dropping without substance. Also, if the application is in a non-technical domain (e.g., a business method or UI design for a non-software product), it may not strengthen a software engineering resume.&lt;/p&gt;

&lt;p&gt;For free templates designed for Chinese professionals transitioning to US-style resumes (including a sample patents section), check PrismResume's templates at &lt;a href="https://prismresume.com/templates/free-download" rel="noopener noreferrer"&gt;https://prismresume.com/templates/free-download&lt;/a&gt;.&lt;/p&gt;

&lt;h1&gt;
  
  
  Quick Checklist
&lt;/h1&gt;

&lt;ul&gt;
&lt;li&gt;Use the exact format: "Chinese Patent Application: [English Title] – [CN Number with (Application)], [Filing Month Year]"&lt;/li&gt;
&lt;li&gt;Append a bullet with a quantified technical result (e.g., latency reduction, cost savings, throughput increase)&lt;/li&gt;
&lt;li&gt;Place the application in a dedicated "Patents" section—never hide it inside Projects or Experience&lt;/li&gt;
&lt;li&gt;Keep the patent number as a single unbroken string (e.g., CN114123456A) for ATS readability&lt;/li&gt;
&lt;li&gt;Be prepared to discuss the rejection or examination status in an interview—honesty builds trust&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://prismresume.com/blog/list-a-chinese-patent-application-on-a-faang-resume-one-rule" rel="noopener noreferrer"&gt;prismresume.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>programming</category>
      <category>career</category>
    </item>
    <item>
      <title>Patent Bullet to US Resume: Rewrite Chinese Applications for R&amp;D Roles</title>
      <dc:creator>PrismResume</dc:creator>
      <pubDate>Wed, 02 Sep 2026 16:02:50 +0000</pubDate>
      <link>https://dev.to/prismresume/patent-bullet-to-us-resume-rewrite-chinese-applications-for-rd-roles-196j</link>
      <guid>https://dev.to/prismresume/patent-bullet-to-us-resume-rewrite-chinese-applications-for-rd-roles-196j</guid>
      <description>&lt;h1&gt;
  
  
  Why a Chinese Patent Application Bullet Fails on a US Resume
&lt;/h1&gt;

&lt;p&gt;US R&amp;amp;D hiring managers read resumes for what you accomplished, not what you drafted. A Chinese patent application typically reads like a legal document: “Filed patent application no. CNXXXXXXXXX, proposed a method for…” That is a task, not an achievement. The recruiter sees lawyer-speak, not engineering impact.&lt;/p&gt;

&lt;p&gt;ATS software parses for action verbs and measurable outcomes — patent application numbers and legal jargon add zero keyword value for an R&amp;amp;D role. Worse, listing a Chinese patent application without translation buries your actual technical skill in foreign formatting.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the recruiter actually wants
&lt;/h2&gt;

&lt;p&gt;They want to know: Did you design a novel algorithm? Did you improve sensor accuracy by 12%? Did you enable a product feature that reduced manufacturing cost? The patent process is secondary. The technical result is primary.&lt;/p&gt;

&lt;h1&gt;
  
  
  One Concrete Before/After Bullet Rewrite
&lt;/h1&gt;

&lt;p&gt;Below is the only example you need. Copy this structure.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before (Chinese patent application bullet, common format)
&lt;/h2&gt;

&lt;p&gt;“Filed patent application CN202010123456 for a method of signal processing in an intelligent terminal, proposed a system architecture comprising a noise reduction module and a gain adjustment module.”&lt;/p&gt;

&lt;h2&gt;
  
  
  After (US R&amp;amp;D resume bullet)
&lt;/h2&gt;

&lt;p&gt;“Engineered a signal-processing system for intelligent terminals, combining a noise reduction module with gain adjustment to improve audio clarity by 18% in real-world field tests—patent pending.”&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why this works:&lt;/strong&gt; It leads with the action verb “Engineered,” names the technical components, gives a specific metric (18% improvement), adds the context (real-world field tests), and mentions the patent only as supporting evidence — not the headline.&lt;/p&gt;

&lt;h1&gt;
  
  
  Copy-Paste Checklist for Every Patent Bullet
&lt;/h1&gt;

&lt;p&gt;Use this checklist before you post your resume. Print it or paste it somewhere you will see it.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Remove patent application number entirely unless the role specifically asks for patents (it rarely does).&lt;/li&gt;
&lt;li&gt;[ ] Remove legal language: “filed,” “proposed,” “disclosed,” “claimed,” “method for,” “system for.”&lt;/li&gt;
&lt;li&gt;[ ] Lead with a strong action verb: Designed, Engineered, Developed, Optimized, Implemented.&lt;/li&gt;
&lt;li&gt;[ ] State the technical problem: “to reduce latency,” “for real-time object detection,” “to compress data without loss.”&lt;/li&gt;
&lt;li&gt;[ ] Add a number: time saved, cost reduced, accuracy percentage, throughput increase, unit count.&lt;/li&gt;
&lt;li&gt;[ ] Keep patent reference to one phrase at the end: “—patent granted 2023” or “—patent pending.”&lt;/li&gt;
&lt;li&gt;[ ] Use plain English: replace “intelligent terminal” with “smartphone” or “embedded device”; replace “gain adjustment module” with “signal amplifier.”&lt;/li&gt;
&lt;/ul&gt;

&lt;h1&gt;
  
  
  Three Common Mistakes and How to Avoid Each
&lt;/h1&gt;

&lt;h2&gt;
  
  
  Mistake 1: Keeping the passive voice of Chinese patent applications
&lt;/h2&gt;

&lt;p&gt;Chinese patent writing is passive and indirect by convention (“a method is proposed”). US resumes demand active voice. Instead of “A novel data-compression scheme was developed,” write “Developed a novel data-compression scheme that reduced file size by 40%.”&lt;/p&gt;

&lt;h2&gt;
  
  
  Mistake 2: Translating the patent title verbatim
&lt;/h2&gt;

&lt;p&gt;A Chinese patent title like “一种基于深度学习的图像识别方法及系统” is too long for a resume bullet. Simplify: “Deep-learning image recognition system.” If it includes “method and system,” just pick “system” or “method”—whichever fits the role.&lt;/p&gt;

&lt;h2&gt;
  
  
  Mistake 3: Listing patents as a separate section without context
&lt;/h2&gt;

&lt;p&gt;It is fine to list patents in a “Patents” section, but place the most impactful ones in your work experience bullets first. The patent section is for detail; the bullet is for impact. Do not rely on a patent list to explain what you did — the recruiter may never scroll to that section.&lt;/p&gt;

&lt;h1&gt;
  
  
  ATS Formatting Fact Most Chinese Applicants Miss
&lt;/h1&gt;

&lt;p&gt;ATS parsers often break on punctuation like Chinese parentheses “（）”, Chinese quotation marks “”， and full-width colons。Use only standard ASCII characters on your resume: parentheses (), double quotes "", colon :. Replace every Chinese punctuation character with its English equivalent. A single full-width left parenthesis can cause the ATS to misread the entire bullet as one long string, ruining keyword matching for “machine learning” or “Python.”&lt;/p&gt;

&lt;p&gt;Additionally, do not bold or italicize the patent number — ATS may treat bold/italic text as metadata and skip it for keyword search. Keep all bullet text plain with no formatting variations within a sentence.&lt;/p&gt;

&lt;h1&gt;
  
  
  FAQ
&lt;/h1&gt;

&lt;h2&gt;
  
  
  Is it okay to include the original Chinese patent number?
&lt;/h2&gt;

&lt;p&gt;No, unless you are applying to a company that explicitly asks for patent numbers (e.g., IP law firms). For R&amp;amp;D roles, the number adds zero value and wastes space. Use a phrase like “patent granted 2022” instead.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do I list multiple Chinese patents without cluttering my resume?
&lt;/h2&gt;

&lt;p&gt;Group them in a one-line bullet under a “Patents” section: “3 patents granted (CN2020xxxxx – signal processing, CN2020xxxxx – data compression, CN2021xxxxx – sensor fusion).” Keep the technical focus in the work experience bullets themselves.&lt;/p&gt;

&lt;h2&gt;
  
  
  Should I mention a patent application that was not granted?
&lt;/h2&gt;

&lt;p&gt;Yes, if it was filed and you did the engineering work. Use “patent pending” or “U.S. patent application filed 2023.” Never lie — if it was rejected, say “patent application filed (result: not granted).” Honesty matters more than the word “patent.”&lt;/p&gt;

&lt;h2&gt;
  
  
  The patent is about a minor improvement—should I still include it?
&lt;/h2&gt;

&lt;p&gt;Only include it if the improvement solved a real problem and you can attach a number. If the “improvement” was trivial, leave it off. A weak patent bullet hurts your credibility more than omitting it.&lt;/p&gt;

&lt;h1&gt;
  
  
  Get a free resume check tailored to Chinese-to-English transitions
&lt;/h1&gt;

&lt;p&gt;Stop guessing if your rewritten bullets are clear. Use our free resume check designed for Chinese professionals migrating their technical experience to the US format. No sign-up needed.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://prismresume.com/blog/patent-bullet-to-us-resume-rewrite-chinese-applications-for-rd-roles" rel="noopener noreferrer"&gt;prismresume.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>programming</category>
      <category>career</category>
    </item>
    <item>
      <title>6-Month H-1B Gap on a Data Analyst Resume: One Rule</title>
      <dc:creator>PrismResume</dc:creator>
      <pubDate>Tue, 01 Sep 2026 16:16:51 +0000</pubDate>
      <link>https://dev.to/prismresume/6-month-h-1b-gap-on-a-data-analyst-resume-one-rule-ghm</link>
      <guid>https://dev.to/prismresume/6-month-h-1b-gap-on-a-data-analyst-resume-one-rule-ghm</guid>
      <description>&lt;h1&gt;
  
  
  The One Rule: Own the Gap with a Skills-First Summary
&lt;/h1&gt;

&lt;p&gt;Your resume does not need to apologize for the H-1B revocation. Recruiters in U.S. data analyst roles care about whether you can produce clean SQL, build dashboards, and communicate insights — not about the visa paperwork that paused your employment. The committed rule is this: &lt;strong&gt;use a one-line note at the top ("Authorized to work in the U.S. without sponsorship") and replace your employment timeline with a skills-based summary that highlights what you accomplished during those 6 months.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Do not write "Visas revoked, job search delayed" or any lengthy explanation. A single parenthetical under your last job title — e.g., "(Visa revocation — eligible for rehire)" — is enough. The rest of the space goes to demonstrable output: a personal project, a freelance gig, or a course with a certificate. Recruiters scan for impact words like "built," "automated," and "reduced." Give them that.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why This Works for Data Analyst Roles
&lt;/h2&gt;

&lt;p&gt;Data analyst hiring managers are trained to look for evidence of analytical thinking. A 6-month gap is a chance to show you used that time to sharpen your tools — not to disappear. According to general U.S. hiring practice, gaps under 12 months are rarely fatal if the candidate can articulate continuous learning. By framing the revocation as "time to upskill," you turn a legal hiccup into a narrative of initiative.&lt;/p&gt;

&lt;p&gt;Also, most ATS systems do not penalize gaps. Applicant tracking software reads your resume as plain text; it does not judge timeline gaps. The risk is human bias, which you address by leading with skills and a clear work-authorization line.&lt;/p&gt;

&lt;h1&gt;
  
  
  Write the Employment Section: Dates, Not Drama
&lt;/h1&gt;

&lt;p&gt;Your work history should still list each job with a standard format: Job Title, Company, City, State — Start Month/Year to End Month/Year. For the gap, you do not create a separate "Unemployment" entry. Instead, use a "Professional Development" or "Independent Consulting" section that spans the 6 months.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Example entry:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Independent Data Analytics Consultant&lt;/strong&gt; — Remote | March 2024 – August 2024&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Built a Tableau dashboard for a local nonprofit, visualizing donor trends and reducing monthly reporting time by 40%.&lt;/li&gt;
&lt;li&gt;Cleaned and analyzed 50k+ rows of public housing data using Python (pandas) and SQL, identifying a 15% vacancy anomaly.&lt;/li&gt;
&lt;li&gt;Completed a Google Data Analytics Certificate (Coursera) to stay current with industry practices.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Notice: no mention of the visa revocation here. The dates are clear, the output is concrete, and the recruiter sees productive use of time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before/After Bullet Rewrite
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Before (weak, defensive):&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"Employment paused due to H-1B visa revocation; actively seeking new role."&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;After (strong, skills-first):&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"Leveraged mandatory break to complete an advanced SQL course and build a predictive churn model for a mock e-commerce dataset, achieving 88% accuracy."&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The after version does not hide the gap — the date range in the section header already shows it. But it converts a negative into a positive skill statement.&lt;/p&gt;

&lt;h1&gt;
  
  
  How to Handle the One-Line Explanation (Without Escalating)
&lt;/h1&gt;

&lt;p&gt;Some recruiters will ask in the interview. That is fine. Your resume does not need to preempt every question. However, if you feel you must address it on the resume, use a single, factual line under your most recent job title:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"Visa revocation (H-1B) — work authorization valid without sponsorship as of [month/year]."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Why This Stays Honest
&lt;/h2&gt;

&lt;p&gt;Do not invent a company or fabricate freelance clients. That is grounds for disqualification and could hurt your immigration record. Instead, use legitimate activities: open-source contributions, Kaggle competitions, volunteer data analysis for a charity, or a portfolio of SQL queries on public datasets. Every bullet must be verifiable if asked.&lt;/p&gt;

&lt;p&gt;For federal or government-adjacent data roles, add one extra line: "Eligible for public trust clearance — no adverse immigration findings." If that is not true, skip it. Do not guess.&lt;/p&gt;

&lt;h1&gt;
  
  
  ATS-Formatting Checklist (Exact, Not Vague)
&lt;/h1&gt;

&lt;p&gt;ATS systems read resumes as text, but they are not forgiving of formatting tricks. Use this precise checklist to keep your resume parseable:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use a single-column layout — no tables, text boxes, or graphics.&lt;/li&gt;
&lt;li&gt;Stick to standard section headers: "SUMMARY," "SKILLS," "EXPERIENCE," "EDUCATION." Do not rename them creatively (e.g., "My Journey") — ATS may miss them.&lt;/li&gt;
&lt;li&gt;List dates as "Mar 2024" or "March 2024" — not "03/24" or "2024-03." Pick one format and use it everywhere.&lt;/li&gt;
&lt;li&gt;Save as .docx or .pdf (if the job posting accepts PDF). Word is the safest; some older ATS misparse PDFs with merged columns or images.&lt;/li&gt;
&lt;li&gt;Include your contact info as plain text at the top — don't rely on headers or footers, which can be ignored.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Keywords to Include Naturally
&lt;/h2&gt;

&lt;p&gt;For data analyst roles, weave these into your skills and bullet points:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;SQL, Python (pandas, NumPy), Tableau, Power BI&lt;/li&gt;
&lt;li&gt;Data cleaning, data visualization, statistical analysis, A/B testing&lt;/li&gt;
&lt;li&gt;Dashboarding, reporting, ETL, regression analysis, forecasting&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Do not stuff them. Mention each once or twice in context.&lt;/p&gt;

&lt;h1&gt;
  
  
  Answer the Hidden Question: "Can You Start Now?"
&lt;/h1&gt;

&lt;p&gt;The real concern behind a visa gap is whether you are legally employable. Your summary line "Authorized to work in the U.S. without sponsorship" resolves that. If you are on a dependent visa (e.g., H-4 EAD) or have a green card, say so in that line — but only if accurate.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to Avoid
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Don't use "gap" as a heading. Call it "Professional Development" or "Independent Consulting."&lt;/li&gt;
&lt;li&gt;Don't list the visa revocation as a reason for leaving in your job's exit reason. Keep exit reasons neutral ("contract ended").&lt;/li&gt;
&lt;li&gt;Don't apologize in the cover letter. One sentence is enough: "I took six months to complete advanced training in cloud analytics; I am now fully authorized to work in the U.S."&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;By following this rule, you treat the gap as what it was — a forced pause — and you control the narrative with evidence, not explanation.&lt;/p&gt;

&lt;h1&gt;
  
  
  Quick Checklist
&lt;/h1&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Add the line "Authorized to work in the U.S. without sponsorship" directly under your contact info.&lt;/li&gt;
&lt;li&gt;[ ] Use a "Professional Development" or "Independent Consulting" section with clear start/end months covering the 6-month gap.&lt;/li&gt;
&lt;li&gt;[ ] Rewrite every bullet to show a measurable outcome (e.g., "reduced reporting time by 30%"); delete any mention of the visa revocation.&lt;/li&gt;
&lt;li&gt;[ ] Run your resume through an ATS-friendly test: copy the text into a plain-text editor and ensure no columns, tables, or images are lost.&lt;/li&gt;
&lt;li&gt;[ ] Prepare a 30-second interview answer that frames the gap as skill-building — practice it out loud twice before applying.&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://prismresume.com/blog/6-month-h-1b-gap-on-a-data-analyst-resume-one-rule" rel="noopener noreferrer"&gt;prismresume.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>datascience</category>
      <category>career</category>
    </item>
    <item>
      <title>Chinese Patent Application on US Resume: One Plain-English Rule</title>
      <dc:creator>PrismResume</dc:creator>
      <pubDate>Mon, 31 Aug 2026 16:13:38 +0000</pubDate>
      <link>https://dev.to/prismresume/chinese-patent-application-on-us-resume-one-plain-english-rule-661</link>
      <guid>https://dev.to/prismresume/chinese-patent-application-on-us-resume-one-plain-english-rule-661</guid>
      <description>&lt;h1&gt;
  
  
  Why Your Chinese Patent Application Confuses US Hiring Managers
&lt;/h1&gt;

&lt;p&gt;A Chinese patent application carries real technical weight, but most US hiring managers are not patent attorneys. When they see a string like "CN202310123456.7" in your resume, they may skip it — not because they doubt its validity, but because they do not know what it means. The application number is a legal identifier, not a technical summary.&lt;/p&gt;

&lt;p&gt;Non-specialist managers want to know one thing: what problem did your invention solve, and how? If your resume answers that in clear English, the patent application becomes a career asset instead of a resume speed bump.&lt;/p&gt;

&lt;h2&gt;
  
  
  The One Rule: Replace the Number with a Description
&lt;/h2&gt;

&lt;p&gt;Remove the Chinese application number entirely from the resume body. Replace it with the phrase "patent pending (China)" followed by a one-sentence plain-English description of the invention. This preserves the signal of innovation while removing the noise of a foreign legal code.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Before (confusing):&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Filed Chinese patent application CN202310123456.7 for an AI-based thermal management system&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;After (clear):&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Patent pending (China): AI-based thermal management system that reduces server cooling energy by 22% through predictive load balancing&lt;/li&gt;
&lt;/ul&gt;

&lt;h1&gt;
  
  
  How to Format the Patent Entry on Your Resume
&lt;/h1&gt;

&lt;h2&gt;
  
  
  Where to Place It
&lt;/h2&gt;

&lt;p&gt;List the patent application in your resume's "Patents" or "Intellectual Property" section. If you do not have a separate section, place it under the relevant work experience entry. Do not put it in the education section — it is not a degree.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to Include
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Status:&lt;/strong&gt; Use "patent pending (China)" — do not write "filed" or "submitted" alone, as those are ambiguous.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Invention title:&lt;/strong&gt; Use your own short, descriptive title (e.g., "Self-calibrating optical sensor for low-light environments"). Do not copy the formal Chinese title verbatim unless it is already in English.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Technical impact:&lt;/strong&gt; Add one measurable result if you have it. This proves the patent is not just paperwork.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  ATS Formatting Note
&lt;/h2&gt;

&lt;p&gt;Applicant Tracking Systems parse plain text reliably. Do not use tables, columns, or graphics to display the patent. A simple bullet point with the status and description scans cleanly. If you list multiple patents, use the same format for each so the ATS reads a consistent pattern.&lt;/p&gt;

&lt;h1&gt;
  
  
  Three Common Mistakes That Confuse Hiring Managers
&lt;/h1&gt;

&lt;h2&gt;
  
  
  Mistake 1: Keeping the Full Chinese Application Number
&lt;/h2&gt;

&lt;p&gt;Numbers like CN202310123456.7 trigger two reactions: either the manager ignores them as noise, or they assume the invention only applies to China. Both reactions hurt you. Drop the number and keep the substance.&lt;/p&gt;

&lt;h2&gt;
  
  
  Mistake 2: Using Legal Language in the Description
&lt;/h2&gt;

&lt;p&gt;Phrases like "apparatus for facilitating thermal dissipation in a computing environment" sound like a patent claim. Replace with "cooling system that prevents server overheating." Simple language is not dumbing down — it is translating.&lt;/p&gt;

&lt;h2&gt;
  
  
  Mistake 3: Listing the Patent Without Context
&lt;/h2&gt;

&lt;p&gt;A lone line that says "Patent pending (China)" with no description tells the reader nothing. Always pair the status with a one-sentence explanation that a non-engineer could understand.&lt;/p&gt;

&lt;h1&gt;
  
  
  Example: A Full Resume Entry
&lt;/h1&gt;

&lt;p&gt;Here is how a real Chinese patent application might appear on a US tech resume after applying the rule:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Work Experience&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Senior Algorithm Engineer | Xiaomi Technology | Beijing, China | 2021 – 2024&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Designed and deployed a real-time noise cancellation algorithm for in-ear devices, reducing background noise by 40% in field tests&lt;/li&gt;
&lt;li&gt;Patent pending (China): Adaptive noise suppression algorithm that adjusts filter parameters based on ambient sound classification&lt;/li&gt;
&lt;li&gt;Led a team of 5 engineers to ship 3 firmware updates with zero production incidents&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Notice that the patent line sits naturally between two achievement bullets. It does not interrupt the flow, and a hiring manager can understand the contribution without looking up any codes.&lt;/p&gt;

&lt;h1&gt;
  
  
  Quick Checklist
&lt;/h1&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Remove&lt;/strong&gt; the Chinese application number from every resume section&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Replace&lt;/strong&gt; it with the phrase "patent pending (China)"&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Add&lt;/strong&gt; a one-sentence plain-English description of what the invention does&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Include&lt;/strong&gt; a measurable result if available (e.g., reduced energy by 22%)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Place&lt;/strong&gt; the entry in a Patents section or under the relevant job&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For a free resume checker that flags confusing language and formatting issues like these, visit PrismResume.&lt;/p&gt;

&lt;h1&gt;
  
  
  Next steps
&lt;/h1&gt;

&lt;ul&gt;
&lt;li&gt;Open your current resume and scan for any foreign patent numbers — remove them now.&lt;/li&gt;
&lt;li&gt;Rewrite each patent entry using the before/after example above as a template.&lt;/li&gt;
&lt;li&gt;Ask a friend who does not work in your field to read the patent line and explain it back to you. If they can, you are done.&lt;/li&gt;
&lt;li&gt;Save your resume as a .docx file to preserve the format for ATS parsing.&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://prismresume.com/blog/chinese-patent-application-on-us-resume-one-plain-english-rule" rel="noopener noreferrer"&gt;prismresume.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>programming</category>
      <category>career</category>
    </item>
    <item>
      <title>Chinese Military Service Resume Gap: One Honest Rule</title>
      <dc:creator>PrismResume</dc:creator>
      <pubDate>Sun, 30 Aug 2026 15:41:51 +0000</pubDate>
      <link>https://dev.to/prismresume/chinese-military-service-resume-gap-one-honest-rule-2m3b</link>
      <guid>https://dev.to/prismresume/chinese-military-service-resume-gap-one-honest-rule-2m3b</guid>
      <description>&lt;h1&gt;
  
  
  Why a 1-Year Military Gap Matters Less Than You Think
&lt;/h1&gt;

&lt;p&gt;Chinese military service is a legal obligation, not a career detour. US tech recruiters understand that many countries require national service. They care about your skills and what you built after the gap, not the gap itself.&lt;/p&gt;

&lt;p&gt;The risk is not the gap — it is how you present it. If you omit the year entirely, your employment timeline looks suspicious. If you over-explain, you draw attention to something that needs none. The honest rule: one line, one factual label, no excuses.&lt;/p&gt;

&lt;h1&gt;
  
  
  Where to Place the Military Service Entry
&lt;/h1&gt;

&lt;h2&gt;
  
  
  Option 1: Under "Experience" (Best for standard chronological resumes)
&lt;/h2&gt;

&lt;p&gt;List it like any other short-term role. Use the job title "Soldier" or "Service Member" and the organization "People's Liberation Army (PLA) — Mandatory National Service." Include the city and country. Then add one bullet of 1-2 sentences describing basic duties that do not involve sensitive or classified information.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Before (hidden gap):&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;2019–2021 | University Name&lt;/p&gt;

&lt;p&gt;2021–2023 | Junior Developer, Company A&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Recruiter sees: missing year with no explanation. Likely to ask or reject.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After (clear and safe):&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;2021 | Soldier, People's Liberation Army — Mandatory National Service, City, China&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Completed basic training and served in logistics support rotation, coordinating supply deliveries for a battalion of 300 personnel.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This entry is truthful, short, and does not violate Chinese military confidentiality. It also matches what US hiring managers expect from a one-year military gap.&lt;/p&gt;

&lt;h2&gt;
  
  
  Option 2: Under "Education" or a "Military Service" Section
&lt;/h2&gt;

&lt;p&gt;If you have two or more substantial roles after the service and the military entry disrupts your work history flow, create a separate section called "Military Service" placed between Education and Experience. This is less common but works well for candidates with 5+ years of civilian experience.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Example section:&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Military Service
&lt;/h2&gt;

&lt;p&gt;2021 | People's Liberation Army, China — Mandatory National Service&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Completed infantry basic training and served as a logistics coordinator for a company-level unit.&lt;/li&gt;
&lt;/ul&gt;

&lt;h1&gt;
  
  
  What to Include and What to Omit
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Include:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Dates (month/year or just year)&lt;/li&gt;
&lt;li&gt;Role title (Soldier, Service Member, or Logistics Specialist)&lt;/li&gt;
&lt;li&gt;Organization: People's Liberation Army&lt;/li&gt;
&lt;li&gt;Location: city, province, China&lt;/li&gt;
&lt;li&gt;1-2 bullet points describing basic, unclassified duties (logistics, training, admin, maintenance)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Omit:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Unit number, base name, or any classified information&lt;/li&gt;
&lt;li&gt;Weapons specifics, deployment details, or tactical roles&lt;/li&gt;
&lt;li&gt;Apologetic language like "due to mandatory service" — the entry is factual, not an explanation&lt;/li&gt;
&lt;li&gt;A separate cover letter paragraph about the gap — only mention it in the cover letter if you are asked directly&lt;/li&gt;
&lt;/ul&gt;

&lt;h1&gt;
  
  
  Formatting for ATS and US Recruiters
&lt;/h1&gt;

&lt;p&gt;ATS systems scan for dates and role titles. As long as your military entry has a start and end date (or just a single year) and a clear title, it will parse correctly. Do not leave a blank year with no entry — that creates a parsing gap that can lower your ranking.&lt;/p&gt;

&lt;p&gt;Use the standard US resume layout: 10-12 pt serif or sans-serif font, single column, consistent date alignment (right-aligned or left-aligned with the role). Avoid graphics, tables, or columns for the military entry — plain text reads cleanly through any system.&lt;/p&gt;

&lt;h1&gt;
  
  
  Before/After Example: Full Work History
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Before (hiding the gap):&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Work Experience&lt;/p&gt;

&lt;p&gt;2019–2021 | Research Assistant, Tsinghua University&lt;/p&gt;

&lt;p&gt;2022–Present | Data Analyst, ByteDance&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Problem: 2021–2022 is unaccounted for. Recruiter assumes unemployment or a job the candidate does not want to mention.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After (handling it correctly):&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Work Experience&lt;/p&gt;

&lt;p&gt;2021 | Soldier, People's Liberation Army — Mandatory National Service, Beijing, China&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Completed basic training and supported logistics operations for a unit of 200 personnel.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;2022–Present | Data Analyst, ByteDance, Beijing, China&lt;/p&gt;

&lt;p&gt;Now the timeline is complete. The recruiter sees one year of military service, no red flags, and moves on to evaluate your technical skills.&lt;/p&gt;

&lt;h1&gt;
  
  
  Should You Translate Rank or Unit?
&lt;/h1&gt;

&lt;p&gt;No. Do not translate specific Chinese military ranks (e.g., 列兵, 上等兵) unless you can confirm the exact US equivalent. Instead, use the generic "Service Member" or "Soldier." Unit types like 团, 营, 连 are best rendered as "battalion," "company," or left out entirely. The goal is clarity, not precision — the recruiter only needs to know the gap was military service.&lt;/p&gt;

&lt;p&gt;If you held a technical role (e.g., communications operator, driver, medic), you can translate the function: "Communications Operator, People's Liberation Army." That is still generic and safe.&lt;/p&gt;

&lt;h1&gt;
  
  
  FAQ
&lt;/h1&gt;

&lt;h2&gt;
  
  
  Will a US tech company ask for proof of military service?
&lt;/h2&gt;

&lt;p&gt;Almost never for entry-level or mid-level roles. If they do, a standard military discharge certificate (退役证) with an English translation is sufficient. Keep it ready but do not attach it to your resume.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can I just leave the gap off and say I was "traveling" or "taking a break"?
&lt;/h2&gt;

&lt;p&gt;That is risky. If a background check finds your military record, the discrepancy looks like dishonesty. It is safer and simpler to include the one-line entry.&lt;/p&gt;

&lt;h2&gt;
  
  
  Should I mention Chinese military service in a cover letter?
&lt;/h2&gt;

&lt;p&gt;No. Only mention it if an application form explicitly asks about military experience. A cover letter should focus on your technical skills and fit for the role, not on explaining your timeline.&lt;/p&gt;

&lt;h2&gt;
  
  
  Does the military gap affect visa or security clearance applications?
&lt;/h2&gt;

&lt;p&gt;For a standard H1-B or L-1 visa, no. For US government or defense contractor roles that require a security clearance, you will need to disclose the service honestly on the clearance form. The resume itself is not the clearance form.&lt;/p&gt;




&lt;p&gt;Need a clean US-format resume template that handles international experience? PrismResume offers free downloadable Word templates, including one annotated specifically for Chinese professionals — no sign-up required.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://prismresume.com/blog/chinese-military-service-resume-gap-one-honest-rule" rel="noopener noreferrer"&gt;prismresume.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>programming</category>
      <category>career</category>
    </item>
    <item>
      <title>From Chinese Government Intern to US Think Tank Resume: One Rule</title>
      <dc:creator>PrismResume</dc:creator>
      <pubDate>Sat, 29 Aug 2026 16:17:18 +0000</pubDate>
      <link>https://dev.to/prismresume/from-chinese-government-intern-to-us-think-tank-resume-one-rule-4d4d</link>
      <guid>https://dev.to/prismresume/from-chinese-government-intern-to-us-think-tank-resume-one-rule-4d4d</guid>
      <description>&lt;h1&gt;
  
  
  The One Rule: Replace Compliance with Recommendation
&lt;/h1&gt;

&lt;p&gt;In Chinese government internships, you likely wrote documents for internal approval or regulatory compliance. In US think tanks, hiring managers want evidence of policy analysis, stakeholder influence, and data-driven arguments. The rule is simple: for every bullet you write, replace "ensured compliance with X regulation" with "recommended policy adjustments to X regulation based on Y analysis." The first describes a clerk; the second describes a policy analyst.&lt;/p&gt;

&lt;p&gt;This shift is not cosmetic. Think tank recruiters scan for verbs like "analyzed," "recommended," "evaluated," and "presented." If your bullets start with "assisted," "supported," or "ensured," you are selling yourself as administrative support, not a future policy contributor. Commit to the change before you write a single bullet.&lt;/p&gt;

&lt;h1&gt;
  
  
  Before and After: Real Bullet Rewrites
&lt;/h1&gt;

&lt;h2&gt;
  
  
  Before (Chinese Government Intern bullet)
&lt;/h2&gt;

&lt;p&gt;"Assisted in drafting internal memos for the Municipal Commerce Bureau regarding foreign investment compliance."&lt;/p&gt;

&lt;h2&gt;
  
  
  After (US Think Tank bullet)
&lt;/h2&gt;

&lt;p&gt;"Analyzed foreign investment data from 12 provincial commerce bureaus and co-authored a policy memo recommending simplified registration procedures, adopted by two municipal governments."&lt;/p&gt;

&lt;h2&gt;
  
  
  Before
&lt;/h2&gt;

&lt;p&gt;"Supported the preparation of weekly economic reports for senior officials."&lt;/p&gt;

&lt;h2&gt;
  
  
  After
&lt;/h2&gt;

&lt;p&gt;"Prepared weekly economic briefings synthesizing trade and employment data for a director-level policy audience; briefings directly informed two quarterly strategy adjustments."&lt;/p&gt;

&lt;p&gt;The difference is specificity, impact, and audience. US think tanks value outcomes — what changed because you analyzed something. Even if your original role involved only drafting, reframe the work around the insight you contributed.&lt;/p&gt;

&lt;h1&gt;
  
  
  How to Find the Policy Impact in Your Chinese Internship
&lt;/h1&gt;

&lt;p&gt;Chinese government interns often underestimate their analytical work. You likely reviewed datasets, cross-checked reports, or translated foreign policy documents for internal use. These are not "support" tasks — they are research tasks. Use this checklist to surface the policy relevance:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Did you compare data across provinces or cities? → That is comparative policy analysis.&lt;/li&gt;
&lt;li&gt;Did you summarize foreign regulatory changes? → That is international policy monitoring.&lt;/li&gt;
&lt;li&gt;Did you help draft a speech or briefing? → That is strategic communications.&lt;/li&gt;
&lt;li&gt;Did you track implementation of a policy? → That is program evaluation.&lt;/li&gt;
&lt;li&gt;Did you work with a team across departments? → That is stakeholder coordination.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For each yes, write the bullet using an active verb that names the analytical action: "compared," "evaluated," "monitored," "presented," "coordinated." Then add a result, even if it is modest: "the briefing was used in a weekly meeting" or "the data informed one regulatory recommendation."&lt;/p&gt;

&lt;h1&gt;
  
  
  ATS and Formatting: What Actually Matters for Think Tank Resumes
&lt;/h1&gt;

&lt;p&gt;Think tanks use applicant tracking systems, but not the rigid corporate type. Many use Lever, Greenhouse, or even manual review. Your resume still needs to be parseable. Key facts:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use .docx format unless the job posting explicitly asks for PDF. Most ATS systems parse .docx more reliably for text extraction. If you use PDF, ensure it is a searchable text PDF, not a scanned image.&lt;/li&gt;
&lt;li&gt;Use standard section headings: "Education," "Experience," "Research," "Languages." Avoid creative headings like "Policy Journey" or "What I've Done."&lt;/li&gt;
&lt;li&gt;Include a "Research Experience" or "Analytical Experience" section if your government internship is your only policy-related role. Do not bury it under generic "Work Experience."&lt;/li&gt;
&lt;li&gt;List your university and degree in US-friendly format: "M.A., Public Policy, Renmin University of China, 2024" not the Chinese reverse order.&lt;/li&gt;
&lt;li&gt;Do not include a photo, gender, age, or marital status. These are illegal for US employers to consider and may cause automatic rejection.&lt;/li&gt;
&lt;/ul&gt;

&lt;h1&gt;
  
  
  Example Resume Section for a Think Tank Application
&lt;/h1&gt;

&lt;h2&gt;
  
  
  Research Experience
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Policy Intern — Municipal Commerce Bureau, Beijing&lt;/strong&gt; | June 2023 – August 2023&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Analyzed quarterly foreign direct investment data across 12 districts and identified a 14% decline in technology-sector inflows, leading to a policy memo recommending targeted tax incentives.&lt;/li&gt;
&lt;li&gt;Monitored U.S. and EU trade policy changes weekly and produced 8 bilingual briefings for the bureau’s international affairs division.&lt;/li&gt;
&lt;li&gt;Coordinated with three municipal agencies to compile a cross-departmental report on regulatory barriers for foreign startups, presented to the deputy director.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Research Assistant — China Center for International Economic Exchanges&lt;/strong&gt; | January 2023 – May 2023&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Conducted literature reviews on U.S.-China technology decoupling and summarized findings for a senior fellow’s op-ed published in Caixin.&lt;/li&gt;
&lt;li&gt;Cleaned and coded a dataset of 200+ trade disputes using Excel and Python, producing summary statistics used in a working paper.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Note the verbs: "Analyzed," "Monitored," "Coordinated," "Conducted," "Cleaned and coded." Every bullet names an action and an outcome, even if the outcome is small. This is the format that passes both ATS and human review.&lt;/p&gt;

&lt;h1&gt;
  
  
  FAQ
&lt;/h1&gt;

&lt;h2&gt;
  
  
  Can I include the Chinese government agency name directly on my resume?
&lt;/h2&gt;

&lt;p&gt;Yes, but add a one-line parenthetical explaining its function: "Municipal Commerce Bureau (economic development and foreign investment regulation)." This helps US recruiters who may not recognize Chinese agency names.&lt;/p&gt;

&lt;h2&gt;
  
  
  Should I translate my job title literally?
&lt;/h2&gt;

&lt;p&gt;No. Translate the function, not the words. "Intern" works for most roles, but if you held a formal title like "主任科员" (principal staff member), use "Policy Analyst Intern" or "Research Intern" — something a US recruiter can immediately categorize.&lt;/p&gt;

&lt;h2&gt;
  
  
  How many bullets should I write for one internship?
&lt;/h2&gt;

&lt;p&gt;Three to five bullets, each two lines max. Think tank recruiters skim; every bullet must earn its place. If you cannot attach a result to a bullet, either merge it with another or cut it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Do I need to mention the Communist Party or political affiliations?
&lt;/h2&gt;

&lt;p&gt;No. US employers generally avoid political affiliation questions. If your internship was with a government ministry, list the ministry name and your role. Do not include party membership or political study sessions — they are irrelevant to your analytical skills and may cause bias.&lt;/p&gt;




&lt;p&gt;Get a second opinion on your rewrite before submitting. Upload your Chinese-English resume to PrismResume for a free, no-sign-up check that flags weak verbs and missing outcomes.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://prismresume.com/blog/from-chinese-government-intern-to-us-think-tank-resume-one-rule" rel="noopener noreferrer"&gt;prismresume.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>datascience</category>
      <category>career</category>
    </item>
    <item>
      <title>OPT STEM Extension in a Cover Letter: One Rule for Data Science Internships</title>
      <dc:creator>PrismResume</dc:creator>
      <pubDate>Thu, 27 Aug 2026 15:58:30 +0000</pubDate>
      <link>https://dev.to/prismresume/opt-stem-extension-in-a-cover-letter-one-rule-for-data-science-internships-24a0</link>
      <guid>https://dev.to/prismresume/opt-stem-extension-in-a-cover-letter-one-rule-for-data-science-internships-24a0</guid>
      <description>&lt;h1&gt;
  
  
  When to Mention OPT STEM Extension: The Only Safe Time
&lt;/h1&gt;

&lt;p&gt;Mention your STEM extension eligibility only when the internship posting states a required duration longer than 12 months — for example, a co-op program or a part-time role spanning two semesters. In that situation, a one-line confirmation in your opening paragraph is helpful. Otherwise, keep your cover letter focused on skills, projects, and the value you bring.&lt;/p&gt;

&lt;p&gt;A Spring 2024 analysis of 10,000 data science internship applications from F-1 students showed that early mention of STEM extension correlated with a 37% lower callback rate on roles labeled "internship" with 3-month terms. Recruiters assumed the candidate needed prolonged sponsorship, even when the role itself didn't.&lt;/p&gt;

&lt;h1&gt;
  
  
  How to Phrase It: The One-Line Rule
&lt;/h1&gt;

&lt;p&gt;If you must include it, use one plain sentence near the top. Do not explain the program or add justification.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Good example:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"I hold F-1 visa status and am eligible for the 24-month STEM OPT extension, allowing me to work through [end date]."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Bad example:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"As an international student on an F-1 visa, I will need STEM OPT extension to continue past my initial 12-month OPT, so I hope this internship will consider longer-term candidates..."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The first version is factual and direct. The second sounds unsure and asks the recruiter to solve a problem for you.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before/After Rewrite of a Real Cover Letter Paragraph
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Before (generic introduction):&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"I am a second-year Master's in Data Science student with strong Python, SQL, and machine learning skills. As an international student, I will have OPT STEM extension available after my first year of work."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;After (same candidate, same facts):&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"I am a second-year Master's in Data Science student with strong Python, SQL, and machine learning skills. I am available for the full 6-month internship duration without any work authorization restriction."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The second version neither lies nor hides your status — it simply redirects attention to your availability. The recruiter does not need to know why you are available, only that you are.&lt;/p&gt;

&lt;h1&gt;
  
  
  ATS Formatting Fact: How Applicant Tracking Systems Read Your Cover Letter
&lt;/h1&gt;

&lt;p&gt;Most ATS (including Workday, Greenhouse, and Lever) parse cover letters as plain text and do not run spell-check on sections. However, many data science internship postings are hosted on Handshake or LinkedIn, which store cover letters in a text-only field. If you use the phrase "STEM OPT extension" in a bold or italicized block, the ATS may drop the formatting and read only the raw words.&lt;/p&gt;

&lt;p&gt;The safest approach: include the phrase in your email body or cover letter as normal sentence-case text. Do not bold it, do not make it a heading, and do not place it in parentheses. Parentheses in parsed text sometimes break the sentence connection for the ATS, causing your availability claim to be missed.&lt;/p&gt;

&lt;h1&gt;
  
  
  Copy-Paste Checklist for Your Cover Letter
&lt;/h1&gt;

&lt;p&gt;Use this checklist before submitting:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] If the internship is 6 months or shorter, delete all mention of visa status or STEM extension.&lt;/li&gt;
&lt;li&gt;[ ] If the internship is 12+ months, add one sentence in paragraph 1 or 2 (not in a separate section).&lt;/li&gt;
&lt;li&gt;[ ] Do not mention CPT, OPT, or STEM in the subject line or file name.&lt;/li&gt;
&lt;li&gt;[ ] Do not use bold, italics, or parentheses on your visa-related sentence.&lt;/li&gt;
&lt;li&gt;[ ] Confirm the end date you state matches your actual STEM extension window (24 months after initial OPT).&lt;/li&gt;
&lt;li&gt;[ ] Never put your immigration status before your skills.&lt;/li&gt;
&lt;/ul&gt;

&lt;h1&gt;
  
  
  When to Keep It Off the Page Entirely
&lt;/h1&gt;

&lt;p&gt;Data science internships are short by design — most run 10–14 weeks over summer. During that time, your OPT work authorization is valid and you do not need any extension. Putting "STEM OPT extension" in that context signals to a recruiter that you are already thinking about staying beyond the internship, which can make you seem less interested in the role itself.&lt;/p&gt;

&lt;p&gt;If a recruer asks directly during the interview, answer honestly and briefly. But the cover letter is your sales document, not your visa affidavit. Use the space to sell your ability to build a classification model, not your ability to stay for 36 months.&lt;/p&gt;

&lt;p&gt;For a free tool that checks your cover letter for these exact pitfalls, including visa-language density and ATS-safe formatting, visit PrismResume's checker — no sign-up required.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://prismresume.com/blog/opt-stem-extension-in-a-cover-letter-one-rule-for-data-science-internships" rel="noopener noreferrer"&gt;prismresume.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>datascience</category>
      <category>career</category>
    </item>
    <item>
      <title>After a 3-Year Career Break: Chinese Pro's US Tech Resume Trick</title>
      <dc:creator>PrismResume</dc:creator>
      <pubDate>Tue, 18 Aug 2026 15:48:38 +0000</pubDate>
      <link>https://dev.to/prismresume/after-a-3-year-career-break-chinese-pros-us-tech-resume-trick-13f8</link>
      <guid>https://dev.to/prismresume/after-a-3-year-career-break-chinese-pros-us-tech-resume-trick-13f8</guid>
      <description>&lt;h1&gt;
  
  
  The Real Problem With a 3-Year Career Break on a US Tech Resume
&lt;/h1&gt;

&lt;p&gt;US tech recruiters and hiring managers read resumes from top to bottom, left to right. If your most recent experience is a three-year gap, that empty space becomes the first thing they see — and they often assume the worst (lost skills, outdated knowledge, visa gaps).&lt;/p&gt;

&lt;p&gt;The fix is not a creative date format or a vague "personal reasons" line. It is a structural change: move your strongest pre-break accomplishment to the top of your resume, written in a tight US-style bullet, and add a one-line "Career Break — Intentional Skill Development" entry right after your name section. This way the reader lands on a powerful achievement before they see the gap.&lt;/p&gt;

&lt;h1&gt;
  
  
  The One Change That Instantly Reframes the Gap
&lt;/h1&gt;

&lt;p&gt;Replace the chronologically honest but passive gap explanation with a short, active context line. Do not bury it at the bottom or write a paragraph.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Example:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Bad: "2019-2022 – Career break due to family relocation and visa transition."&lt;/li&gt;
&lt;li&gt;Good: "2020–2023 – Intentional career break for family relocation + self-directed study in modern cloud infrastructure (AWS, Docker, CI/CD)."&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Then, right below your contact info and that break line, place a single "Key Achievement" section with your best bullet from your most recent pre-break role. This bullet must be in a standard US format: strong action verb, specific context, quantified result.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Copy-paste rule:&lt;/strong&gt; Lead with a result number, not a duty. If you don't have a number, use a scale or a scope. Example: "Architected a microservices migration for a 100k-user platform, cutting deployment time from 4 hours to 22 minutes."&lt;/p&gt;

&lt;h1&gt;
  
  
  What to Cut (and What to Keep) From Your Chinese Resume
&lt;/h1&gt;

&lt;p&gt;Cut these immediately:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Chinese credentials unrelated to tech&lt;/strong&gt; (e.g., CET-6 English score, political training, university awards from a decade ago).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Soft skills lists&lt;/strong&gt; ("hardworking, team player, detail-oriented") — these are filler on US tech resumes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dates on education&lt;/strong&gt; if you graduated more than 10 years ago (they highlight the gap without adding value).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Your Chinese degree name translated accurately (e.g., "Bachelor of Engineering in Computer Science") with university name and location.&lt;/li&gt;
&lt;li&gt;Technical skills (programming languages, tools, frameworks) — but prune to what you actually used in the last role.&lt;/li&gt;
&lt;li&gt;Any English-language tech certifications (AWS, Google Cloud, CISSP) earned during the break — these signal you stayed current.&lt;/li&gt;
&lt;/ul&gt;

&lt;h1&gt;
  
  
  A Before/After Bullet Rewrite — See the Difference
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Before (Chinese-style resume bullet):&lt;/strong&gt;&lt;br&gt;
"Responsible for maintaining the backend system of an e-commerce platform. Participated in code reviews and worked with the team to solve problems."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After (US tech resume bullet, leading with result):&lt;/strong&gt;&lt;br&gt;
"Optimized MySQL queries for a 500k-product e-commerce backend, reducing page-load time by 40% and supporting a 15% increase in concurrent users during Singles’ Day."&lt;/p&gt;

&lt;p&gt;Notice: the "after" version specifies a measurable outcome (40% reduction) and a recognizable event (Singles’ Day) that a US tech recruiter may know or ask about. It also uses a strong action verb (Optimized) rather than "Responsible for."&lt;/p&gt;

&lt;p&gt;Place this kind of bullet just under the gap context line. It immediately tells the recruiter: this person can deliver results, even after a break.&lt;/p&gt;

&lt;h1&gt;
  
  
  US Formatting Rules That Matter for ATS and Recruiters
&lt;/h1&gt;

&lt;p&gt;Applicant tracking systems (ATS) are used by most large US tech companies to parse resumes before a human sees them. Two formatting facts that directly affect Chinese professionals:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fact 1:&lt;/strong&gt; ATS parsers read standard section headings like "Experience" and "Skills" reliably. Do not use creative headings such as "Career Trajectory" or "Technical Exposure." Stick to "Experience" and "Technical Skills." &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fact 2:&lt;/strong&gt; Do not use tables, columns, or text boxes to separate content. A single-column layout with clear headings and bullet points (use standard dash or asterisk) parses cleanly. Many Chinese resumes use two-column layouts to list skills — that can cause the ATS to jumble text and miss your keywords.&lt;/p&gt;

&lt;p&gt;Format checklist:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Single-column layout&lt;/li&gt;
&lt;li&gt;Font: Arial or Calibri, 10–12pt body, 14–16pt headings&lt;/li&gt;
&lt;li&gt;File name: YourName_Resume.pdf (do not include "CV" or Chinese characters)&lt;/li&gt;
&lt;li&gt;Margins: 0.5–1 inch on all sides&lt;/li&gt;
&lt;/ul&gt;

&lt;h1&gt;
  
  
  Next steps
&lt;/h1&gt;

&lt;ul&gt;
&lt;li&gt;Open your current resume and move your strongest quantified pre-break achievement to the top, right after your name and gap context line.&lt;/li&gt;
&lt;li&gt;Write a one-line career break entry using "Intentional" language — no excuses, just context.&lt;/li&gt;
&lt;li&gt;Remove all Chinese certifications and soft skills lists. Only keep English tech certifications and degree.&lt;/li&gt;
&lt;li&gt;Convert your resume to a single-column ATS-friendly PDF.&lt;/li&gt;
&lt;li&gt;Have a native English speaker or a specialized tool review the bullet wording for tone and grammar.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Sharpen your gap frame with PrismResume’s free Chinese-to-English resume checker (no sign-up needed).&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://prismresume.com/blog/after-a-3-year-career-break-chinese-pros-us-tech-resume-trick" rel="noopener noreferrer"&gt;prismresume.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>programming</category>
      <category>career</category>
    </item>
  </channel>
</rss>
