Who We Are

Spectro Cloud aims to make cloud infrastructure boundaryless for the enterprise. We provide solutions that help enterprises deploy Kubernetes their way, anywhere. We were founded by multi-cloud management experts and a founding team that has built products and companies successfully before and is doing it again. Talented team members and industry-leading investors back us up so that we can focus on making an impact that our customers value and that you can be proud to be involved with. We are a fully remote organization.

What’s The Job?

As a Lead Technical Writer, you will help lead the technical writing team, improve writing practices, and champion technical documentation. In your day-to-day, you will manage the backlog engineering tracks and create reference material, diagrams, and how-tos for our practitioners to help them better understand the product. We have a technical product, so we require individuals who are comfortable with developer workflows and using the same tools as developers, such as git, Kubernetes, virtual machines, command line interfaces, GitHub, containers, Docker, cloud providers, and Terraform. A solid technical background is required for this position.

Internal efforts to improve the writing architecture and quality of the writing are underway. You will play a key role in improving the existing documentation and shaping the future of the Docs platform, including its content.

This is a full-time position and a remote-first role. The role is open to all Canada/U.S.

Salary Range: $120k - 170k.

About The Team

The team is made up of highly technical individuals who work well together, enjoy each other's company, and are all high performers. We strive to automate as much as possible, and we, the team, maintain our own documentation site built on top of Docusaurs. That means the team's technical writers and education engineers write code (JavaScript, CSS, GitHub Actions, and some bash) to facilitate new documentation features. Please take a peek at our GitHub code base for a better understanding of what we do.

Qualifications and Experience

We don’t expect the ideal candidate to check every box, but the items below are things we look for when reviewing candidates. Do not let this discourage you from applying.

• At least six years of experience as a technical writer.

• Experienced with creating, improving, and implementing processes.

• At least one year of experience in a lead role that requires mentoring other writers and providing guidance.

• Capable of managing and aiding in distributing work among the team (project management).

• Excellent communication skills, both written and orally

• A self-starter with the ability to dive into technical features by themselves and create documentation

• Experience in analyzing information architecture and restructuring content

• Able to coach and mentor other technical writers

• Comfortable writing in markdown and operating in a Docs as Code workflow. 

• Comfortable using developer tools such as git, CLIs, Docker, and GitHub

• Familiar with containers and virtual machines.

• Comfortable working in a remote setting and with a remote-first culture

• Experience with public cloud providers (AWS, Azure, GCP, Oracle)

• Comfortable creating diagrams and visual resources to help the learning process

• Displays a passion for learning and exploring new technologies

• A self-starter with a strong sense of ownership

• Experience with CSS, JavaScript, and HTML.

The Hiring Process

Your time is valuable, so we want to ensure we respect your time and the effort you put into the hiring process. The interview process is divided into four sections: a screening interview, a technical interview, a writing and information architecture discussion, and a culture and team fit interview.

• Screening Interview—This is a thirty-minute interview during which we verify whether we are a good fit for each other. We’ll ask questions to learn more about your career experience and technical writing skills.

• Technical Interview - a sixty-minute interview where we verify your technical teaching capability, writing skills, and technical knowledge. We use a writing assignment to validate your teaching and writing capabilities. The writing assignment is not a pass or fail but instead utilized as an indicator to help us understand your current abilities.

• Writing & Information Architecture - a thirty-minute interview where we review your understanding of composing, writing, and structuring information.

• Culture/Team Interview—This is another thirty-minute interview. The questions here focus on your experience working in a team setting. Other questions check for organizational core values and culture fit.