"Employers hiring technical writers want candidates with the technical knowledge and written communication skills to simplify complex concepts. In an interview, be prepared to discuss your writing experience and provide an example of a time you explained a difficult idea to a group or classroom. Your interviewer may also quiz you on technical concepts or ask you to engage in a written exercise."
How do you prioritize topics that need to be written?
I try to get a sense of the need for the topics by asking subject matter experts and other interested parties; then I prioritize based on whether this is a new topic, a revision, a requirement to address changed circumstances, or a "nice to have." Emergency topics take first priority; then topics that can be completed quickly; then topics that are needed, but which will require more time to investigate.
You would have to draw up an outline that included variables with respect to deadline and value. Once that was accomplished, you should develop an analysis of each item with respect to profit, qty available, vs realistic completion of the project deadline expectation. Say we have 100 widgets that are slow sellers, with a low margin and time consuming to write, and 1000 widgets with the same amount of work, yet are far more profitable, you would outline them in a multi-fold hierarchical format. Equal work and deadline, unequal values. If the next four items were also fast sellers with high quantities and significant profit margins, and took as much work as the 100 widgets, decisions would need to be made. Rush jobs are better served by making compromises. It's better to exclude weaker profit items, in order to ensure all high profit items are included and the quality of the finished product does not read as slap-dash, and that pesky deadline is met. Over-reaching is the hobgoblin of lost accounts.