Developer Evangelism Intern

Job Description

Location : Remote, based in the US   Team : Marketing / GTM  

 Who this is for : students and recent grads

We're building OLake, an open-source CDC ingestion tool that replicates production databases into Apache Iceberg lakehouses and helps maintain them. Our audience is data engineers and data platform teams, the kind of people who read benchmarks, check the repo, and can smell marketing fluff from a mile away.

This is an internship for someone who wants to learn evangelism and distribution from the ground up, by actually doing it. You'll be the face of OLake at meetups and conferences across the US, the person writing the migration guide that gets someone unstuck at 2am, and a regular voice in the communities where data engineers actually hang out. It's less about running campaigns from a desk and more about being out there: at events, in comment sections, in Slack threads, writing docs people bookmark. The rest of the team is based in Bengaluru, so you'll effectively be running US presence on your own, with the team backing you up remotely.

This starts as an unpaid internship. If it's working for both sides, there's a clear path to a paid contract, and from there to a full-time role, based on how you perform.

Events & evangelism (the core of the role)

\n
• Represent OLake at meetups, conferences and community events in the US, on the ground, taking notes, capturing conversations, and following up with people you meet.
\n
• Give lightning talks or demos where the opportunity comes up, and help prep talks and materials when someone else from the team is presenting.
\n
• Build relationships with organizers, meetup groups and communities in the data engineering space so OLake has a standing invite, not a one-off booth.
\n
• Be a real, technical presence in developer communities (Reddit, Slack groups, dev.to, Hacker News), answering questions and contributing in ways that earn attention instead of pitching.
\n

Content & distribution

\n
• Write migration guides, tutorials and how-tos that help someone go from “heard of OLake” to “running a sync in production.”
\n
• Help run the day-to-day publishing calendar across LinkedIn, X and YouTube: drafting posts, picking visuals, and getting them out on schedule.
\n
• Repurpose long-form content (docs, release notes, talks) into shorter posts and threads that travel well on social.
\n
• Watch the conversation: competitor moves, Iceberg and data engineering discourse, and what the audience is actually complaining about that week.
\n

Growth support (you'll pick this up along the way)

\n
• Support newsletter and creator partnerships in the data engineering space: sponsorships, co-marketing, guest content.
\n
• Help track pipeline-relevant metrics like qualified traffic, trials, signups and engagement, so you can see what your content and events are actually driving.
\n

\n
• Currently studying (or recently graduated) in computer science, data or a related field, with some hands-on exposure to databases, pipelines or data infrastructure, coursework and personal projects count.
\n
• Genuinely comfortable talking to people. You'd rather work a booth or answer a Slack thread than sit behind a content calendar all day.
\n
• Can write clearly and simply. If you've written a README, a project writeup, or a blog post explaining something technical, that's exactly the muscle we need.
\n
• Some presence in developer or open-source communities already, even informally: a GitHub profile with real activity, a Discord or Slack you're active in, a few posts online.
\n
• Based in the US and able to travel to meetups and conferences in your region. Comfortable working async with a team that's mostly online while you're asleep.
\n

Nice to have

\n
• A talk, workshop or demo you've given, even to a small audience.
\n

Great to have

\n
• A real contribution to an open-source project, code, docs, or otherwise.
\n
• Comfort with the subject matter that you can read a benchmark and talk about CDC and Iceberg without needing everything explained twice.
\n