Technical Writer

As a Technical Writer at Prophecy, your primary responsibility will be to develop and refine documentation that enhances the user experience for our data transformation platform. This includes creating user guides, product manuals, quick start guides, and tutorials that are clear and engaging. You'll collaborate closely with product managers and engineers to ensure that the documentation reflects accurate technicalities while democratizing complex concepts for a varied audience. Additionally, you’ll need to stay up-to-date with industry trends, fostering innovation through continuous learning and communication.

To qualify for the Technical Writer position at Prophecy, you should have a Bachelor's degree in Computer Science, Engineering, Communication, or a related field. Ideally, you’ll bring 2-3 years of experience in technical writing within B2B SaaS companies, along with familiarity in ETL, data engineering, or analytics. Proficiency in markdown, GitHub, and visual tools like LucidChart and Figma is essential. Moreover, having basic coding skills and the ability to articulate complex information into digestible content is a huge plus!

Prophecy is committed to the professional growth of its team members, including Technical Writers. We offer an annual reimbursement of $500 for professional development, which can be used for training, courses, or events that enhance your skills. We believe that continuous learning not only benefits you as an individual but also enhances the quality of documentation produced at Prophecy, ultimately driving innovation in our approach to data engineering.

At Prophecy, Technical Writers utilize a variety of tools to create and manage documentation effectively. You'll work primarily with markdown in GitHub for version control and collaboration, alongside design tools like LucidChart and Figma for visuals. Proficiency in using SDKs, APIs, and CLIs will also be beneficial, allowing you to better understand product functionalities as you craft your materials.

The work environment for a Technical Writer at Prophecy is dynamic and collaborative. You will work remotely but will have the opportunity to closely engage with product managers, software engineers, and subject matter experts. The culture at Prophecy is inclusive and values merit, providing the kind of supportive atmosphere that encourages creativity and innovation in technical documentation processes.

In answering this question, emphasize specific projects you've worked on in your previous roles that highlight your technical writing expertise, especially those related to B2B SaaS. Discuss the types of documentation you created and the audience they served, showcasing how you adapted your writing style to meet the needs of both technical and non-technical users. Don’t forget to mention any tools or methodologies you employed.

To answer this question effectively, explain your process for verifying technical accuracy. This could involve collaborating with engineers, reviewing code, conducting interviews with subject matter experts, or testing software functionalities yourself. Highlight your attention to detail and processes you follow to keep your documentation up-to-date with product changes.

Discuss your strategies for effective simplification, such as breaking down information into manageable sections, using analogies, or leveraging visual aids like diagrams. Provide an example of a technical concept you simplified in the past, illustrating your storytelling ability and creativity in reaching a broader audience.

In answering this question, talk about your experience with GitHub or similar version control systems. Mention specific tasks you’ve performed, such as managing changes, collaborating with others, or documenting processes in Git. If you're less familiar, express your eagerness to learn and adapt to such tools.

Share the resources you utilize to stay informed, such as industry blogs, webinars, online courses, or networking with professionals in the field. You could also talk about specific communities or professional organizations you engage with, showing your commitment to continuous learning and industry relevance.

Use the STAR method (Situation, Task, Action, Result) to narrate a specific situation where you received feedback. Focus on how you approached the feedback professionally, made necessary adjustments, and the positive outcome that resulted from acting on constructive criticism. This will highlight your ability to improve and adapt.

Discuss the importance of collaboration in your writing process, emphasizing how working with engineers, product managers, and other stakeholders enriches the quality and accuracy of your documentation. Share specific examples of projects where collaboration led to enhanced documentation outcomes.

In your response, identify what you see as essential—clarity, accessibility, accuracy, or user engagement—backed with examples of how you've prioritized each aspect in your work. Illustrate how these elements collectively contribute to a positive user experience.

Share specific situations where you complemented your written content with visuals, such as flowcharts or diagrams, to clarify complex topics. Describe the feedback you received from users and how the visuals improved understanding and engagement.

Discuss your aspirations, whether that involves growing into leadership within technical writing, specializing further in data engineering, or even transitioning to product management. Ensure your goals align with Prophecy's mission and ethos, illustrating your excitement for contributing to the company's success.