Virtual Assistant (Technical Content – Developer Infrastructure)

**Remote (NYC Hours Required)**
**Full-Time (8 hrs/day)**
**5+ Years Professional Experience Required**

We’re hiring a high-caliber operator who can function as both:

1. A precision-focused Virtual Assistant
2. A strong technical content writer for a developer infrastructure product

If you are primarily a general admin VA, this role is not for you.

If you’ve written real documentation for APIs, deployment platforms, Kubernetes-based systems, or cloud infrastructure — keep reading.

---

## About Us

We’re a US-based startup building a developer-first deployment platform — similar to Vercel or Render — but designed for teams that want to deploy into their own cloud (AWS, GCP, Azure) or on-prem infrastructure.

Our users are engineers and platform teams. They care about correctness, security, performance, and infrastructure control.

We operate with high standards and low bureaucracy.

---

## What This Role Actually Is

You will:

* Bring structure and clarity to startup operations
* Turn raw engineering notes into production-grade documentation
* Help improve our internal systems across GitHub, Linear, Notion, and Slack
* Act as a force multiplier for founders and engineers

You will not:

* Just manage calendars
* Write fluffy marketing content
* Wait for detailed step-by-step instructions

We’re looking for someone who sees ambiguity and creates structure.

---

## Responsibilities

### Execution & Operational Rigor

* Own inbox and calendar coordination with precision
* Track issues and deliverables in Linear and GitHub
* Follow up consistently and close loops
* Create clean internal documentation in Notion
* Conduct structured research and produce concise summaries
* Identify process gaps and proactively improve them

### Technical Documentation (Developer-Facing)

* Write and maintain:

* API documentation
* Deployment workflows
* Cloud setup guides (AWS/GCP/Azure)
* Kubernetes-based deployment documentation
* Self-hosting and infrastructure configuration guides
* Translate engineering discussions into clear, structured documentation
* Create realistic developer examples and workflows
* Improve clarity and usability of existing docs
* Use ChatGPT and Claude Code effectively — without relying on them for correctness

---

## Requirements (Non-Negotiable)

* 5+ years of professional experience
* Proven experience writing technical documentation for developer tools or infrastructure platforms
* Strong understanding of:

* AWS, GCP, or Azure
* CI/CD concepts
* Containers (Docker fundamentals)
* Infrastructure basics (networking, auth, environments)
* Ability to read and understand code (JavaScript, Python, or similar)
* Strong GitHub literacy (issues, PRs, repo structure)
* Excellent written English
* Highly organized and detail-oriented
* Must work NYC business hours

---

## Strong Advantage (Highly Valued)

* Practical familiarity with Kubernetes:

* Understanding of pods, services, ingress, deployments
* Helm or YAML-based configuration
* K8s-based deployment patterns
* Experience documenting Kubernetes or cloud-native systems
* Experience in early-stage startups
* Experience supporting founders or senior operators
* Ability to test APIs and run CLI tools independently

Kubernetes familiarity is a major plus, especially given the nature of our platform.

---

## What “Great” Looks Like (90 Days)

* Our docs read like they were written by someone who understands infrastructure
* Engineers spend less time explaining basic cloud concepts
* Kubernetes and deployment flows are clearly documented
* Internal operations feel structured and predictable
* You operate with minimal oversight and high judgment

---

## Compensation

Competitive, based on experience.
Long-term role with meaningful ownership and leverage.

---

## Application Requirements

To be considered, include:

1. 2–3 examples of technical documentation you’ve written for developer tools or infrastructure products
2. A short explanation of your experience with cloud platforms (AWS/GCP/Azure)
3. Any experience working with Kubernetes (if applicable)
4. Your timezone and confirmation you can work NYC hours
5. A brief note explaining why you thrive in high-ownership environments

Applications without documentation samples will not be reviewed.