Skip to content

Contributors


WikiWalls is written by a small editorial team. Every piece carries a named byline, a methodology disclosure, and a “Last reviewed by” line. The team page below is the canonical record of who writes what and how to reach them.

📝 How to read a WikiWalls byline
  • Named editor at the top of every piece, linked to this page.
  • Methodology link in the body for every tested-comparison piece. See /test-methodology/.
  • “Last reviewed by” line in the footer with the editor’s name. The month-year is operational metadata, not editorial copy.
  • Person schema on every article. Author entity is the editor named in the byline.
  • Editorial independence: recommendations are not paid placements. Sponsor relationships, when they exist, are disclosed at the top of the piece. See /editorial-standards/.

Daniel Park

Senior Editor, AI & Engineering

Daniel Park leads WikiWalls’s AI and engineering coverage. He writes the publication’s tested-comparison cornerstones in the AI vertical and oversees the methodology that anchors them: public pricing, published-benchmark cross-checks, and production-diary reporting. His pieces aim to be the version of an AI buying decision that you can hand to a senior engineer without footnotes.

Beats: AI APIs and model evaluation, AI coding tools, AI agent frameworks, RAG architecture, production AI engineering, developer-tooling reviews, the weekly research-paper translation.

Owns the methodology for: AI cluster. See how the AI desk tests and prices.

Reach Daniel: [email protected] (subject line: “For Daniel”). Pitches via /pitches/.


Hannah Whitfield

Services Editor — Hardware, Travel-Tech, Founder Operations

Hannah Whitfield runs the service-journalism arm of WikiWalls. She writes the tested-comparison cornerstones across hardware, travel-tech, and founder operations, with an emphasis on testbed discipline: photographed setups, named measurement tools, in-country test dates, and 30-day production windows. Her pieces are written for the reader who is about to spend money and wants to know whether the spec sheet survives contact with a desk, a country, or a P&L.

Beats: mini-PCs and homelab hardware, monitors, dev laptops, NAS and storage, eSIM provider tests, country-level travel-tech guides, travel routers, business banking (Mercury / Brex / Ramp), founder-ops stacks.

Owns the methodology for: hardware and travel-tech clusters. See how the hardware desk tests and how the travel-tech desk tests.

Reach Hannah: [email protected] (subject line: “For Hannah”). Pitches via /pitches/.


Editorial leadership and additional roles

The masthead is in the process of being built out. The roles below are open and will be filled in the coming months. When a hire lands, this page is updated with the named editor and their bio.

Open roles

  1. Editor in Chief. Sets editorial direction. Signs the daily Take column. Owns /editorial-standards/.
  2. The Strategist’s Notebook (columnist). Weekly pattern-naming column on operator strategy.
  3. The Production Floor (columnist). Weekly column on engineering and operations practice.
  4. Service Journalism Lead. Senior reviewer with testbed access; AnandTech / Wirecutter / ServeTheHome class.
  5. Service Journalism Reporter. AI cross-cut beat. Original reporting.
  6. Head of Sales. Sponsor program management.

Want to write for WikiWalls? See our pitch guide. Want to sponsor a column or cornerstone? See our sponsor program.

Last reviewed by WikiWalls editorial. Editorial standards.