Ask a Mentor.

1. How they use AI tools.
2. How they analyze the doc requirements.
3. Where they draw the line between AI and human intervention.
4. At which point they get involved with the stakeholders.
5. Networking skills.

In today's world, a technical writer plays a multi-dimensional role. In many organizations, apart from merely writing end-user documents, I've been actively doing QA (writing and performing test cases), UX-UI content drafting and review, UAT, and other project-management activities. No organization values a tech writer who only writes documents — they literally ask what else you do apart from tech writing.

The more senior you become, the more versatile your role becomes.

A candidate who writes well can produce grammatically correct content, but a good technical writer reduces user effort and increases user success. They understand the user's goal and design content that helps users complete tasks successfully — thinking beyond individual documents to create an information experience that's structured, discoverable, consistent, and aligned with the product experience.

What differentiates them is ownership and judgment. They ask the right questions, challenge ambiguity, and influence product decisions. With AI generating content, the value of a good technical writer lies less in producing text and more in applying judgment, solving problems, and ensuring content enables users to succeed.

Chisel your questioning approach in a manner that treats the product and its documentation like a Rubik's cube — or sudoku, whatever cooks your spaghetti. Language is just a means to communicate your findings. If you keep digging and dusting to make the cube align and fall into place, your expanding product knowledge will make you a subject-matter expert who writes well. That's where you want to go.

A great technical writer isn't just someone who knows where to put a comma; they are a strategic communicator who bridges the gap between complex systems and human understanding. While strong communication is the baseline, the true distinction lies in how a candidate treats information structure and how they master the technical ecosystem.

[Hardware Architecture] ──> [Data Path & Protocols] ──> [Data Protection]
   (NVMe, SSD arrays)         (Fibre Channel, iSCSI)        (RAID, Snapshots)

Given the current market situation, organizations need people immediately (at least those that are still hiring). If they believe you're the right fit, they may be willing to wait for a month, but waiting for two months can already be risky, as business priorities may change. A three-month notice period will almost certainly require negotiation, and it’s important to handle those discussions without burning any bridges.

Here are some possible options:

• Resign first and then search/apply for jobs during your notice period. The risk is that if your job search extends beyond three months, you could end up without an income. The payoff is that you'll have access to a much wider range of opportunities, as many employers prefer candidates who can join sooner.
• Maintain the status quo. In this case, nothing changes—there’s no additional risk, but there’s also no significant upside beyond continuing with your current situation.
• Find an organization that is willing to wait for your full three-month notice period. The risk here is that there’s no guarantee the role will still be available three months later. The payoff is that you secure the opportunity you want without having to resign before receiving an offer.
• Explore other alternatives, such as moving to a different role or team within your current organization.

These options could provide a path forward with potentially lower risk.