[Demand Gen / DevRel hybrid, open to data, analytics, platform or software engineers]

Location: Bengaluru (in-office / hybrid) Team: Marketing / GTM Experience: 1-3 years

About the role

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 role is for someone with hands-on data experience, whether that's data engineering, analytics engineering, platform engineering, or software engineering work that touched pipelines, who wants to spend less time shipping and more time getting other practitioners to hear about OLake, try it, and stick around. You know this audience because you've been part of it, so we're looking for someone who can bring that credibility to our top of funnel, not a marketer trying to learn CDC from scratch. Think of it as a DevRel-flavored growth seat.

Half the job is showing up daily as a real, technical voice on LinkedIn, X, Reddit and in developer communities. The other half is running the programs that turn that attention into signups. It's hands-on: you'll be working in a team of three, writing posts and shipping campaigns yourself.

What you'll do

Distribution & community (the core of the role)

- Be a genuine, technical voice for OLake in developer communities (Reddit, Slack groups, dev.to, Hacker News), answering questions, sharing benchmarks, and contributing in ways that earn attention instead of pitching.
- Own the day-to-day publishing calendar across LinkedIn, X and YouTube. You write the posts from real technical understanding (not a brief handed to you), pick the visuals, and hit publish.




- Build a light employee and founder amplification motion so the team's own accounts carry reach.
- Watch the conversation: competitor moves, Iceberg and data engineering discourse, and what the audience is actually complaining about that week.

Demand generation (you'll grow into this)

- Help run programs across paid and organic social, search, and newsletter sponsorships, from creative and copy to reporting metrics. You bring the technical judgment on what will land with data practitioners, and we'll help you pick up the channel mechanics.
- Run newsletter and creator partnerships in the data engineering space (sponsorships, co-marketing, guest content).
- Maintain lifecycle nurture: email sequences, retargeting, and follow-up flows that move people from “starred the repo” to “running a sync in production.”
- Support event demand: pre-event promotion, on-ground capture, and post-event follow-up for meetups and conferences.

Measurement

- Own reporting on pipeline-relevant metrics: qualified traffic, trials, signups, active users, and channel-level cost efficiency.
- Report weekly on what's working and what isn't.

What we're looking for

- 1-3 years of hands-on experience with data, as a data engineer, analytics engineer, platform engineer, or software engineer who has worked on data pipelines or infrastructure. This is the core qualification. Marketing experience is not required.
- A real,



demonstrated pull toward writing, community and distribution. You've written technical posts, threads, or blogs, answered questions in developer communities, or built some kind of audience, even informally.
- Comfort with the subject matter goes without saying. You should be able to read a benchmark and write about CDC and Iceberg without being corrected by the engineering team, because this is close to work you've already done.
- Strong writing. Explicit, specific, no jargon padding, with an original voice.
- Curiosity about the numbers side of marketing: GA4 or equivalent, campaign analytics, basic spreadsheet work. You don't need to arrive fluent, but you should want to be able to answer “did that work?” with data.
- Willingness to learn paid social and search platforms and a marketing automation or email tool on the job.

Nice to have

- Experience using or contributing to an open-source project, as a user, contributor, or maintainer.

Great to have

- Some prior public writing or speaking: a blog, a conference talk, a well-followed X or LinkedIn presence, even if it was built casually rather than professionally.

What success looks like

- First 30 days: you're writing and publishing in your own technical voice, you've audited our current channels, and the social calendar is running on schedule.
- First 90 days: you're co-running two to three demand gen programs end to end, social output and engagement are measurably up, and reporting is clean enough that we can make budget decisions from it.
- First 6 months: you own a defined pipeline contribution number and a repeatable playbook for launches and events, and you're a recognizable voice in the data engineering community in your own right.

📌 Data Practitioner, Developer Relations & Growth (Bengaluru)
🏢 OLake
📍 Bengaluru