IT-Tech Writer

Preface

We are looking for talents to help us building knowledge as an organization brain while serving millions of customers. We love to learn from mistake, teach each other and grow together. We respect every single knowledge from people. We collect, study, refine and share everything.
You are looking for an environment where you can learn and share your knowledge? Or you love to analyze and solve problem? Let’s come and join ACB!

Find your job here

Learning is your hobby:

• You don’t hesitate to ask about what you don't know.
• You are curious about how things works.
• You have an End-To-End mindset.
• Understand your organization culture.
• Understand how people communicate to each other.
• Technology is your passion.

You know how to transfer knowledge on documentation:

• Sharing a story both in visual and text.
• Writing walkthroughs to guide readers from being Novice to being Expert.
• Understand the edge between Reality and Imagination.
• Understand that you are a storyteller, not just only a writer.
• Being disciplined to clarify and verify what you have learned before writing any documentation.
• Understand how to write a live document which takes constant communication.

You might already have a lot of templates but you should know how to create new templates:

• Able to classify content type (MoSCoW): Must Have, Should Have, Could Have, Won't Have.
• Able to define template purpose.
• Able to make a template as Audience-Focused.
• Able to know who will use the template as a writer and you will be their coach (in documentation).
• Able to define a template life cycle.

You are a master of neatness:

• You cannot stand chaos but aim for orderly, step by step processes.
• You are able to organize and structure complex concepts.
• You are able to re-arrange a structure when new things come.
• You centralize and share everything but understand information security as well.

You have "Documentation as A Product" mindset:

• Able to research audience/customer needs.
• Understand you cannot be perfect at the first time: Make a MVP (Minimum Viable Product) then work with your audience to refine it.
• Able to plan for publish date and announce everyone to use.
• Understand that documentation publishing is not the end. You get audience feedback and constantly improve.