DARK HEART LABS systems thinking with a pulse
[CV]

[cv]

Jennifer Picado

Technical Writer · Accessible Frontend · IT Support

504.510.1878 · jv@darkheartlabs.technology · linkedin.com/in/darkheartlabs · Remote · async · global

Professional Summary

Async remote hire who writes the how-to, ships the accessible page, and documents the DNS, mail, or endpoint failure so a tired first-time user can finish without a call. Comfortable in technical writing, front-end delivery, and IT analysis / desktop-support work — applying as an individual contributor, not a staff engineering seat.

Async-first · written handoffs · Slack · GitHub · Markdown · timezone-flexible with teams worldwide

Availability

Remote · global

Seeking an async remote IC role worldwide in technical writing, accessible frontend, or IT support. AEWV-accredited employers in New Zealand are welcome; they are not required.

Role match
Technical Writer · Accessible Frontend · IT Support
Relocation
On the ground in Auckland Dec 2026–Feb 2027 for in-person meetings · full NZ relocation in 2027 if an offer funds it
Mobility
NZ eTA approved · Australian business visitor visa approved · overlapping hours with US, Oceania, and EU teams

Formal dated CV, references, and writing samples available on request for employer due diligence and the immigration process.

Employer due-diligence pack
  • Formal dated CV and employment chronology
  • Selected how-tos, READMEs, and shipped public work
  • Public writing at darkheartlabs.technology/writing
  • Identity, qualification, and immigration documents on request

A formal evidence pack is available for employer due diligence and the immigration process.

Official Immigration New Zealand AEWV process ↗

Selected work

  • NeuroShell

    User docs and README for an ADHD-friendly macOS tool: task-oriented how-tos, keyboard shortcuts, accessibility notes.

  • mystic-bytes

    Jekyll / GitHub Pages site for darkheartlabs.technology: HTML/CSS, writing section, CV, search.

  • ask

    Interactive front-end microsites (date-proposal flow) on a static stack.

  • accessibility-rails-components

    WCAG 2.1 AA Rails ViewComponents with usage docs and keyboard-path how-tos.

  • focus-guard

    Operator-facing README and policy notes for an Envoy focus-mode module.

  • dark-heart-themes

    High-contrast editor themes (Cursor / Zed) for long sessions.

Experience

Independent contractor

Documentation, front end, and IT support

2015–Present Remote

How-tos, accessible pages, and written fixes for DNS, mail, and endpoints — individual contributor, not a staff engineering seat.

  • Wrote how-tos, READMEs, and help text from engineer notes, Slack threads, live systems, and sessions with clients and implementers — what the user actually needed to do, in a form a first-time user can finish.
  • Turned client questions and first-week chaos into revised how-tos, setup checklists, and onboarding guides so the same confusion did not become another ticket.
  • Built and maintained accessible HTML/CSS/JS and Jekyll sites (darkheartlabs.technology, Ask microsites); documented CMS workflows so clients could publish without a developer on the call.
  • Evaluated tools for client setups and recommended what to keep, drop, or replace — in writing.
  • Wrote step-by-step DNS, mail authentication (SPF, DKIM, DMARC), hosting, and Docker setup so a non-specialist could finish without a call.
  • Supported remote macOS and Windows endpoints and wrote the fix down so the next similar ticket did not start from zero.

365 Connect LLC

Web Developer

2007–2015 On-site / remote

Front-end and help text for a property-management platform, plus internal notes so recurring fixes did not have to be re-explained.

  • Front-end and help text for a property-management platform (WordPress, Drupal).
  • Implemented responsive CSS and JavaScript so the platform held up across devices.
  • Worked with design on accessibility for the property-management UI.
  • Used what users actually did in the product to fix help text and interface bottlenecks.
  • Documented publishing workflows for teammates and clients.
  • Turned recurring support tickets into internal notes — IT analysis so the same outage was not explained from scratch.