[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-hiring-criteria-en":3,"blog-related-hiring-criteria-en":30,"blog-adjacent-hiring-criteria-en":62},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":12,"readingMinutes":13,"featured":14,"tags":15,"category":19,"seoSettings":29},95,"hiring-criteria","How We Hire","Not puzzle counts, not buzzwords on a CV. Three things matter.","\u003Cp>In a small team a bad hire is expensive; it takes half a year to absorb. After interviewing over a hundred people, we narrowed our criteria to three and simplified the process accordingly.\u003C\u002Fp>\n\u003Ch2>Three criteria\u003C\u002Fh2>\n\u003Cp>They have actually built things. Pick one feature they owned end to end; the details must survive probing. Builders describe detours and trade-offs; others only conclusions.\u003C\u002Fp>\n\u003Cp>They want to understand the problem. They ask about unclear requirements instead of coding first, and rework after launch is visibly lower.\u003C\u002Fp>\n\u003Cp>They collaborate. A strong engineer who makes the team miserable damages a small team more than they contribute.\u003C\u002Fp>\n\u003Ch2>The interview process\u003C\u002Fh2>\n\u003Cp>Round one covers project history, listening for detail and decisions, with no algorithm puzzles.\u003C\u002Fp>\n\u003Cp>Round two is a small take-home: a realistic mini feature over two days, with full freedom to search and ask.\u003C\u002Fp>\n\u003Cp>Round three is a conversation with future teammates. Once skills clear the bar, this step weighs heavily.\u003C\u002Fp>\n\u003Cp>Fewer criteria mean more consistent execution. Hold these three lines and the team's floor is guaranteed.\u003C\u002Fp>","","cyan","佳益方圆团队","2026-07-31T15:18:00+08:00",1,false,[16,17,18],"Team Culture","Hiring","Interviews",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},4,0,"team-culture","Team and Culture","Company events, tech sharing, team building and hiring culture that show the daily life of the Jiayifangyuan team.","users","blue","article",30,{},[31,41,51],{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":40},89,"thirty-minute-weekly","The Thirty-Minute Weekly Share","No new technology, no industry trends. Just the pitfalls of the week and how they were solved.","2026-10-11T09:00:00+08:00",[16,38,39],"Knowledge Sharing","Growth",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":42,"slug":43,"title":44,"excerpt":45,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":46,"updatedAt":46,"readingMinutes":13,"featured":14,"tags":47,"category":50},90,"what-code-review-is-for","What Code Review Is Really For","Review is not fault-finding. It is letting another mind walk through your code.","2026-09-29T10:13:00+08:00",[16,48,49],"Code Review","Engineering Practice",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":52,"slug":53,"title":54,"excerpt":55,"content":9,"cover":9,"tone":56,"author":11,"publishedAt":57,"updatedAt":57,"readingMinutes":13,"featured":14,"tags":58,"category":61},91,"docs-start-with-templates","Documents Start With Templates","People avoid writing docs mostly because they do not know where to start. A template solves most of it.","teal","2026-09-17T11:26:00+08:00",[16,59,60],"Documentation","Knowledge Management",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"previous":63,"next":80},{"id":64,"slug":65,"title":66,"excerpt":67,"content":9,"cover":9,"tone":68,"author":11,"publishedAt":69,"updatedAt":70,"readingMinutes":13,"featured":14,"tags":71,"category":73},8,"project-retrospective-practice","How to Run a Retrospective That Works: A Real Session from Our Team","A retrospective is not a blame meeting and should not be a process performance. It only needs to solve one problem: how to do a little better next time.","slate","2026-08-01T17:00:00+08:00","2026-10-18T15:58:14.744+08:00",[72,16],"Retrospectives",{"id":74,"parentId":21,"slug":75,"name":76,"description":77,"icon":78,"cover":9,"tone":26,"kind":27,"sortOrder":79,"count":21},3,"project-retrospective","Project Retrospectives","Real project records from zero to one, covering problems, solutions, lessons learned and final outcomes.","clipboard-check",40,{"id":81,"slug":82,"title":83,"excerpt":84,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":85,"updatedAt":85,"readingMinutes":13,"featured":14,"tags":86,"category":90},114,"data-compliance-for-smb","Where SMBs Should Start With Data Compliance","Compliance is not only for large firms. Small ones need a starting point they can actually execute.","2026-07-29T15:18:00+08:00",[87,88,89],"Industry Watch","Data Compliance","SMB",{"id":91,"parentId":21,"slug":92,"name":87,"description":93,"icon":94,"cover":9,"tone":26,"kind":27,"sortOrder":95,"count":21},5,"industry-watch","In-depth analysis of internet, software and digital industry trends with our own point of view.","globe",20]