馬上要準(zhǔn)備TW面試的小伙伴們，為你們奉上滿滿干貨：

• 面試考核點(diǎn)
• 英文TW面試題集錦
• 中文TW面試題集錦

面試考核點(diǎn)

1. 首先，作為TW初斑，基本功一定得扎實(shí)辛润。中英文寫作理論與基礎(chǔ)知識(shí)扎實(shí)膨处，要講得出平臺(tái)遵照的寫作原則與規(guī)范 （English Technical Writing Guidelines）见秤。面試時(shí)要能講得出來；筆試時(shí)真椿，要充分運(yùn)用鹃答。
2. 其次，對各類文檔的寫作與評審流程有一個(gè)清晰的認(rèn)識(shí)突硝，能有條理地講述出來测摔。對平時(shí)工作中的痛點(diǎn)及個(gè)人思考心得，也要講得出解恰。

   在《技術(shù)文檔工程師6大必殺技》一文中锋八，我根據(jù)自己的經(jīng)驗(yàn)，給出了如何培養(yǎng)這些技能护盈，可供大家參考借鑒挟纱。

3. 對于以往工作中寫過的產(chǎn)品，要至少能有條理地講出它的功能與特點(diǎn)腐宋、面向的讀者群紊服、最好還能講出你對產(chǎn)品技術(shù)的理解。
4. 作為TW胸竞，與人溝通欺嗤，團(tuán)隊(duì)合作意識(shí)，做事的主動(dòng)性都很重要卫枝。準(zhǔn)備一兩個(gè)能體現(xiàn)你個(gè)人品質(zhì)的案例煎饼。
5. 最后，面試官會(huì)問你有沒有問題--“你還想了解職位或是公司的什么信息校赤？”腺占。我個(gè)人覺得這一點(diǎn)能反映出應(yīng)聘者思維活的躍度與深度。假使你不太善于現(xiàn)場提問痒谴，那不妨提前準(zhǔn)備2個(gè)衰伯。

前幾天，有位學(xué)文的TW進(jìn)入二面技術(shù)面試积蔚，在網(wǎng)上問我：有點(diǎn)怵技術(shù)面試意鲸，該怎么準(zhǔn)備？
我覺得這個(gè)問題提的很有代表性尽爆。的確怎顾，在技術(shù)面試環(huán)節(jié)，會(huì)有開發(fā)人員參與面試漱贱，目的是了解你對行業(yè)槐雾、技術(shù)的了解與熟悉程度。我想幅狮，即便是學(xué)理科的同學(xué)募强，也不一定專業(yè)對口株灸，也一樣會(huì)有忐忑。
我的建議：面試前擎值，不用盲目地到網(wǎng)上去學(xué)基礎(chǔ)知識(shí)慌烧，你要做的是到該公司的網(wǎng)站，充分了解該公司的產(chǎn)品鸠儿，行業(yè)領(lǐng)域屹蚊，在學(xué)習(xí)過程中，有些疑問进每，有時(shí)間的話汹粤，可以去追蹤與學(xué)習(xí)。沒有時(shí)間的話田晚，就把這些問題記在心里玄括，在面試時(shí)，也可能有機(jī)會(huì)與面試官就此進(jìn)行交流肉瓦。
不懂不可怕遭京，怕的是不懂不愛學(xué)習(xí)。TW是一個(gè)要求不斷學(xué)習(xí)的職位泞莉，學(xué)習(xí)能力/好奇心/探究能力是TW非常重要的素質(zhì)--這是我作為面試官時(shí)很看中的品質(zhì)哪雕。

English TW面試題集錦

先拋點(diǎn)干貨。我不是個(gè)愛跳的人鲫趁，所以前兩家公司斯嚎，一家九年，一家7年挨厚。其間也沒有出去試試水堡僻。我在今年失業(yè)后，面試過幾家公司疫剃，其中有兩家文檔外包公司是招English TW钉疫。我大致回憶一下，招聘需求以及試題巢价。此外牲阁，我也會(huì)講講上家公司（Moody's Analytics (MA) 的面試試題）以及作為APAC TechComm組的深圳招聘官，我在招TW時(shí)會(huì)關(guān)注些什么壤躲。

* 某國外外包公司為瑞典電信設(shè)備商招外包TW

• JD：英文撰寫深圳研發(fā)中心產(chǎn)品手冊（網(wǎng)絡(luò)通信中用到的軟件加密認(rèn)證軟件城菊，如果我沒記錯(cuò)的話）。
• 電話面試：公司國內(nèi)總經(jīng)理英文面試碉克，主要是介紹個(gè)人工作經(jīng)歷凌唬，由此發(fā)散隨機(jī)問些問題，記得不清楚了漏麦，了解人的基本素質(zhì)吧客税。
• 第1輪：外包公司總經(jīng)理電話面試况褪，英文聊經(jīng)歷、薪資要求霎挟，隨機(jī)擴(kuò)散發(fā)問。
• 筆試試題：
  • 寫一份打印機(jī)操作使用說明麻掸。（沒有給出更多的提示）酥夭。-- 考查基本操作類手冊的寫作手法，寫作規(guī)范功底脊奋。
  • 給出一個(gè)房間3D布局圖熬北，要求給出房間布局描述。-- 考查作者的條理性诚隙，與語言文字的表達(dá)能力讶隐。
  • 給出一份現(xiàn)在文檔的前幾章，要求你提出改進(jìn)建議久又。-- 考查你的寫作與編輯經(jīng)驗(yàn)巫延。
• 技術(shù)面試：
  測試、項(xiàng)目經(jīng)理地消、產(chǎn)口經(jīng)理分別面試
  • 聊以往的工作經(jīng)歷炉峰。
  • 最大的挑戰(zhàn)是什么？
  • 講講你以前所寫產(chǎn)品的原理與工作流程脉执。

* 港交所離岸開發(fā)中心招外包TW

• JD: 英文撰寫研發(fā)文檔（港交所內(nèi)部為英文工作環(huán)境）疼阔、中譯英、英譯中半夷，寫英文宣傳文稿.
• 線下筆試--給出一遍18頁的中文稿（講Block Chain原理)婆廊，翻譯至少3頁。這個(gè)我準(zhǔn)備了一周交稿巫橄，因?yàn)樘粤冢艺J(rèn)為要翻譯得 準(zhǔn)確到位，一定要對這個(gè)領(lǐng)域有一定認(rèn)識(shí)湘换，技術(shù)術(shù)語也要專業(yè)列荔、準(zhǔn)確。所以工作日的晚上枚尼，我在上網(wǎng)學(xué)習(xí)英文相關(guān)知識(shí)贴浙，并沒有做翻譯。周六日抽空翻譯了大約5頁署恍，翻到一個(gè)概念完結(jié)處打住崎溃。
• 面試--只有一個(gè)開發(fā)總監(jiān)面試，聊對職位及該公司的看法盯质，過往工作經(jīng)歷袁串，聊對股市的認(rèn)識(shí)概而。
• 現(xiàn)場筆試--還是翻譯，翻譯一份Block Chain技術(shù)實(shí)現(xiàn)的個(gè)人心得囱修∈旯澹基于我前一周的學(xué)習(xí)以及自己的網(wǎng)絡(luò)通信基礎(chǔ)，做得不錯(cuò)破镰，還指出了里面的描述性錯(cuò)誤（或者是原作者的筆誤吧）餐曼。

* 英國軟件startup公司的郵件面試

A fictional scenario for a technical writing exercise

• It's up to you to decide how long it needs to be, but conciseness is in general a virtue.
• Present some notes on how you went about the writing task:
  • • what your process was
  • • why you made any decisions you did
  • • any assumptions you made
  • • anything else you think we should know

* 某軟件公司面試問卷

• An explanation outlining how you feel you meet the requirements of this role.
• A 250 - 500 word essay explaining what you feel are the biggest challenges in being a technical writer and the strategies you have developed to overcome them. Please provide specific examples from previous jobs. Focus on 3-5 challenges in your answer.
  My answer for your reference:
  As a technical writer, what are the pain points you ever get? The following I list a few I ever encountered in different writing phases and share how I handle them.
  Planning -- > Writing -- > Review --> Publishing
  • Planning
    How to draft an outline for a guide?
    Solutions: Gain an overview on the product by reading feature proposals and attending feature-related meetings.
    How to have a clear understanding of my audience?
    Study user persona, and put myself into users' place, and talk with product managers.
  • Writing
    How to present the document in a clear, concise and professional language?
    When I entered Moodys Analytics in 2011, I stepped into the Financial Technology domain from the previous Telecom domain. One of my work is to co-author RiskOrigins User Guide for staff in financial institutions. I did the following to get myself up to the speed, and completed my first document in this company with very positive feedback from my manager:
    Get familiar with the company's writing style. I read Moodys Style Guide in details. Plus, I asked my manager to recommend a similar User Guide from other product lines and saw how these writing rules are applied. I discussed constantly with my manager and colleagues to get to know the reasons behind these rules.
    Getting familiar with the product. I read through feature proposals, specifications, user stories for the product. Attended daily scrum, feature proposal review meetings, and show-and-tell meetings to get myself submerged into this product. I talked to product managers about features to dig out why users need a feature and how important it is to users.
    Gather terminology used in this industry. I asked my manager for our competitors' names and famous industry journals and wiki links. In this way, I was getting familiar with the terminology used this industry.
  • Review
    How to have the review parties review my documents in time and with quality?
    This is really a headache for writers. It time permits, I can write a long article to talk about the ways that I have ever used and its effectiveness.
    The following I'd like to share two stories:
    Thumb of rules is to gain support from the upper manager.
    For guides targeted at technical audience, review comments from QAs and sometimes Developers are valuable. But at the project planning stage, project managers often neglect the review efforts in QAs and Developers' workload. What I (my team) did is to come up with a documentation development plan at the project planning phase where we list all guides to be released for this release, required review parties, input that we need, and the timeframe for the review. We have this plan reviewed and approved at the project planning meeting, and have the product owner authorize the project management to assign review efforts (manpower) to each user story in the Rally system. This really helps improve the review efficiency.
    To give a workable review schedule to book reviewers' time
    RiskOrigins customers complained about the usability about the User Guide. They wanted to see more real-life examples for operation tasks not the step-by-step procedures. Based on this request, what we need is to have the SMEs to review each chapter in the guide and provide samples where there is a need.
    SMEs are based in London and normally not reviewers of user documents. As the lead writer of this guide, I need to work out a new way. SME manager is also the owner of this product and I talked to her when she was in Shenzhen on business trip, and she was very supportive to this idea and gave me the name list for each module. I came up with a detailed review schedule for each chapter (module) including when the chapter will be ready for review and when we expect the review comments and examples to be back. Then I sent this schedule to SMEs for confirmation respectively and made adjustment based on their feedback.
    Meanwhile, I created a wiki page on our Confluence platform for the cooperation. I put the confirmed schedule there and created a table to track the writing progress and review status.
• More information on the more significant technical documentation that you have written – for each, please include size of the document, total effort, your specific responsibility (for example: author, reviewer, editor, and so on), complexity of the document, your approach to planning the content, and how you ensured quality of the final result.

* MA當(dāng)年在深圳招TW:

• JD：為基于workflow的風(fēng)控軟件產(chǎn)品招TW舰褪，用英文撰寫各類產(chǎn)品用戶手冊锄俄。英文、計(jì)算機(jī)壹置、經(jīng)濟(jì)類專業(yè)皆可孕似。
• 第1輪英文電話面試--SG與SF TechComm Director與Manager分別英文面試踩娘，決定是否move onto現(xiàn)場面試環(huán)節(jié)。
• 第2輪現(xiàn)場面試與筆試
  • 現(xiàn)場面試--APAC TW組英文群面喉祭。介紹職位需求养渴，公司，開始提問泛烙，考核點(diǎn)：了解你對英文寫作規(guī)范的認(rèn)識(shí)與經(jīng)驗(yàn)厚脉，你以往的文檔寫作流程，團(tuán)隊(duì)合作能力胶惰，文檔工作中的難點(diǎn)及你的解決辦法傻工。聊得開心的話，會(huì)找到不少共鳴點(diǎn)孵滞。
  • 現(xiàn)場筆試--1. 給出了一節(jié)操作說明（半頁）中捆，進(jìn)行優(yōu)化。2. 給出一段描述類產(chǎn)品描述坊饶，進(jìn)行優(yōu)化泄伪。3. 給出一份現(xiàn)有其它產(chǎn)品線的用戶手冊，讓你給出修改建議匿级。

* Philips Healthcare ECR products在深圳招TW （非本人親歷蟋滴，朋友轉(zhuǎn)述）

• JD: Researching, interpreting, analyzing and writing, by interpreting technical source information and determining approporateness for inclusion into documentation and other content development. Collaborating with cross-functional teams, including Localization, Product Management, Engineering, Quality and Regulartory, to produce high quality and accurate customer documentation that ensures compliance with regulatory requirements. ... requirements: 技術(shù)寫作或相關(guān)專業(yè)。 5年以上產(chǎn)品技術(shù)文檔寫作經(jīng)驗(yàn)..
• 1. HR二輪面試 2. 美國TWs電話群面 3. 美國TW Manager面試 4. 筆試
• 筆試題為：寫一段英文文檔痘绎，介紹如何在Outlook中用Calendar發(fā)起會(huì)議邀請

中文TW面試題集錦

異地某金融云平臺(tái)中文TW面試 (TW圈內(nèi)部推薦）

• JD： 推薦人給的JD與HR的JD有些出入津函，HR的版本：各種產(chǎn)品的文檔、教程孤页、最佳實(shí)踐 等形式的完整內(nèi)容體系尔苦，為用戶快速上手使用產(chǎn)品提供完整的支撐。要求：信息類畢業(yè)（計(jì)算機(jī)，信息工程允坚，軟件魂那，自動(dòng)化，電子工程稠项，通信涯雅，數(shù)學(xué)等）或者有IT從業(yè)經(jīng)驗(yàn)3年以上
• 第1輪電話面試--由TC組文檔工程師面試，簡述工作經(jīng)歷展运，了解日常文檔寫作版本管理活逆、TW寫作與人員管理心得。聊得很投機(jī)乐疆，從一開始的小緊張中放松下來划乖，侃侃而談贬养。在這樣一個(gè)小眾行業(yè)挤土，有人能懂你，認(rèn)同你的做法误算，頓時(shí)有惺惺相惜之感仰美。
• 第2輪晚間郵件筆試--收到郵件筆試試題，晚上收到花了近3小時(shí)做完（要求2小時(shí)儿礼，可是TW的職業(yè)習(xí)慣和這個(gè)崗位的高匹配度咖杂，讓我認(rèn)真應(yīng)對）。試題分幾大部分：
  • 選擇題：考查基本英文文法
  • 改錯(cuò)題：考查英文技術(shù)寫作與編輯技能
  • 中譯英翻譯題--英文翻譯技能
  • 中文編輯試題
    考題出得挺不錯(cuò)蚊夫，方方面面都有诉字，難度于我不大。唯一覺得做得不太理想之處是：英文翻譯知纷。我歷來閱讀比翻譯做得多壤圃，所以，在翻譯上琅轧，我通常要花較長時(shí)間去推敲才出得了精品伍绳。
• 第3輪下午電話面試--我覺得是TC組Manager角色吧。簡述工作經(jīng)歷乍桂，聊文檔寫作流程冲杀，文檔組角色設(shè)置、概述目前所做產(chǎn)品睹酌，TW職業(yè)發(fā)展經(jīng)歷與考慮权谁、如何面對年青我二十歲的開發(fā)相處。展開聊了一個(gè)半小時(shí)憋沿。結(jié)合第1與3輪面試闯传，兩位TW同行都很nice。回過頭來看甥绿，我可能在某些問題的回答上字币，沒有換位站在面試官的角度體會(huì)出問題的用意，一聊high就一股腦什么都倒 切記：面試的目的是找工共缕，要謹(jǐn)記這是找工談話呢洗出！但也要時(shí)刻保持穩(wěn)重與謙和，Don't jump the gun图谷，盡最大能力展現(xiàn)自己對這份工作的熱忱與投入 翩活。
• 面試結(jié)果：HR發(fā)來郵件拒了我。評語是：您的學(xué)識(shí)和資歷給我們留下了良好的印象便贵。 遺憾的是菠镇，您所應(yīng)聘職位的要求與您的實(shí)際情況不太符合，因此暫時(shí)沒有機(jī)會(huì)與您合作承璃。我們已經(jīng)將您的資料列入人才儲(chǔ)備檔案利耍，希望我們今后有共事的機(jī)會(huì)。
• 自我分析：能進(jìn)入第三輪盔粹，起碼說明我的寫作基礎(chǔ)得到了認(rèn)同隘梨，增加一次筆、面試體驗(yàn)舷嗡，個(gè)人信心與應(yīng)試能力都得到了提高轴猎，又多了一份體驗(yàn)收獲，雖說是以失利結(jié)尾进萄，不過捻脖，也算是一次很有意義的體驗(yàn)!
  對于失利，我覺得：優(yōu)質(zhì)公司職位候選人一定不會(huì)少中鼠，從HR角度考量可婶，如果是一個(gè)較為junior的職位+異地就職+中年女性，我是沒有優(yōu)勢的兜蠕。高處不勝寒扰肌，起舞弄清影，何似在人間

某云平臺(tái)中間件中文TW筆試

• JD： 云平臺(tái)中間件產(chǎn)品的文檔熊杨。要求：信息類畢業(yè)（計(jì)算機(jī)曙旭，信息工程，軟件晶府，自動(dòng)化桂躏，電子工程，通信川陆，數(shù)學(xué)等）或者有IT從業(yè)經(jīng)驗(yàn)3年以上
• 郵件筆試：約定時(shí)間收到郵件筆試試題剂习，要求在2小時(shí)內(nèi)提交。試題分以下三大部分：

  • 文檔優(yōu)化改寫 （如果沒有相關(guān)產(chǎn)品背景，做起來會(huì)找不到北鳞绕。）

  • 撰寫指定平面幾何圖形的繪制步驟

  • 翻譯幾段平臺(tái)相關(guān)的Marketing資料

    本來憧憬滿滿失仁，筆試自我感覺也很好。但國內(nèi)互聯(lián)網(wǎng)公司對年齡設(shè)的這道坎们何，讓我心塞萄焦，本以為TW崗位更看重經(jīng)驗(yàn)。退而思之冤竹，也只能說明自己還不夠優(yōu)秀拂封，不足以讓雇主動(dòng)心放棄年齡的顧慮。那就繼續(xù)努力完善自我吧ｐ腥洹冒签！

每次面試都是一次修行!都是自己了解自己缺點(diǎn),發(fā)現(xiàn)不足,重新認(rèn)識(shí)自己,改善提高的機(jī)會(huì)!每一次面試又是一次緣分,我們可以靜靜的聽對方的故事和建議,思考對比自己的人生,不斷修正,學(xué)習(xí)借鑒!自我鞭策! --摘自微信文章《43歲，2017我的第15次面試-1中年海歸的下崗再就業(yè)自救寶典》钟病，說出我的心理話!

相關(guān)話題
深圳文檔工程師-市場需求與薪資分析
各大招聘網(wǎng)站 (APP) 適用性評測
技術(shù)文檔工程師六大必殺技