Feeny
Nango

Technical Content Engineer at Nango (United States)

Nango· United States· $30–$150/hr·

Role details

Salary
$30–$150/hr
Work type
Remote
Employment
Contract

Job description

(Remote — North America, LATAM or Europe)

Nango nango.dev (YC W23) lets developers build product integrations with AI. It enables applications to connect to the real world through integrations.

More than 500 paying customers rely on Nango today, including Replit & Ramp. We are a YC-backed, mid-seven-figure ARR company with a team of 14 from AWS, GitHub, Okta, Snyk, Netlify, Uber, Samsara, Workato, and other top-tier dev tools.

We are hiring a freelance Technical Content Engineer to scale our content for engineers building product integrations. This role is paid hourly ($30 to $150).

WHAT YOU’LL DO

  • Write deeply technical content that educates developers on APIs, integrations, agents, and AI infrastructure.
  • Build prototypes and write code to understand firsthand what you write about.
  • Stay at the forefront of AI infrastructure and develop strong perspectives on where the industry is going.
  • Shape Nango’s vision and technical narrative alongside the founders and engineering team.
  • Make technical content a major driver of Nango’s awareness, adoption, and word of mouth.

WHO YOU ARE

  • You’re a software engineer with a strong computer science foundation.
  • You have experience with developer tools, APIs, infrastructure, or adjacent technologies.
  • You can explain complex technical ideas clearly and precisely. Professional writing experience is a plus, not a requirement.
  • You have the curiosity and technical depth to understand how things actually work.
  • You closely follow AI, agents, and the emerging infrastructure around them.
  • You have strong independent judgment: you can research a topic, find the interesting angle, and form your own point of view.

-

Why work at Nango

  • Fully remote – team distributed across the US, Europe, and LATAM; outcomes over hours.
  • Open-source culture – transparency, community, and developer friendliness are core values.
  • Expert-led – colleagues come from developer infrastructure companies (e.g., Datadog, GitHub, Snyk); engineers work on hard problems (distribution, scale, API fragmentation).
  • Impact & ownership – small team (7–9 people) means direct contribution to product decisions and architecture; engineers do support and shape the roadmap.
  • Technical challenges – from building a custom Postgres-based scheduler to handling OAuth flows, rate limits, and schema quirks across hundreds of APIs.
  • High growth trajectory – 7-figure ARR, fast-growing user base, and a fresh $7.5M round signal momentum without sacrificing quality of life.

Application questions