About Us;
Saras AI is the world's first AI-only higher studies institute based in the United States. We are on a
mission to create the most student-centric higher education institution globally, offering degrees exclusively in AI for both students and working professionals. Our founding team comprises industry experts from the US and India, united by a shared vision to make high-quality AI education accessible to everyone, with a personal touch of humanity. This is an in-office role based out of Gurugram.
FIRST, SOME HONEST CONTEXT
Saras AI Institute trains working engineers to build and ship production-grade AI systems. Our MS in AI Engineering covers everything from multi-agent orchestration and LLM fine-tuning to MLOps, data engineering, and responsible AI. The people we're selling to built their first neural net from scratch before LLMs existed and are deeply unimpressed by hype.
Our content needs to match that. Not explain what is AI. Not write thought leadership that sounds like it was prompted from a business school case study. Actual technical depth, with an editorial spine.
The content strategy is already built. The calendar exists. The pillars are defined. What's missing is someone who can execute it with both speed and credibility- write the B2B whitepaper AND the LinkedIn carousel AND the student case study AND not make any of them sound like the others.
WHAT YOU'LL ACTUALLY DO
Own the editorial output, not just the strategy
- Write the flagship pieces yourself long-form B2B articles, whitepapers, AI maturity reports, technical case studies, email nurture sequences. This is not a role where you commission everything and edit everything. You write.
- Produce B2B sales assets that engineering leadership will read: ROI comparisons, capability gap frameworks, hiring-vs-upskilling breakdowns. Things that end up forwarded in Slack between a CTO and their VP Eng.
- Write LinkedIn posts in a voice that doesn't sound childish in front of engineers.
- Script masterclass sessions and fireside chat outlines in collaboration with our faculty to create conversations that aspiring product leaders and tech entrepreneurs would want to indulge in.
Build the student and outcomes content engine
- Interview enrolled engineers, extract the real story (what they were doing before, what they built, what changed), and turn it into something worth reading not a testimonial but a narrative.
- Create the case study format we'll use for all future outcomes content. This doesn't exist yet. You'll own it from scratch.
- Build a pipeline that pulls student voices into the content calendar consistently.
Run the calendar across multiple tracks
- Own the 10-week rolling B2B content calendar and the B2C engineering track simultaneously thematic coherence.
- Brief and edit external contributors: faculty, guest CTOs, student writers, technical reviewers. Set the bar. Hold people to it.
- Produce decks and reports for B2B pitches, sales outreach, and cohort retrospectives. Yes, this is part of the job. The Content Lead here makes PowerPoints that don't make engineers want to close the tab.
Collaborate with design and social
- Brief the Design Lead on every asset you write the concept, structure, and editorial direction; they execute the visual. This handoff needs to be clean.
- Give the Social Media Manager adapted, platform-native versions of every major asset. The whitepaper becomes a Reddit thread. The case study becomes a LinkedIn carousel. You see the original; they see the translation.
WHAT WE'RE LOOKING FOR
The signal that matters most
You have a BTech or BE. You did not become a software engineer or you did for a bit, and then switched. The reason this matters is not a credential check. It's that our readers are engineers. They will notice immediately if you're describing their work from the outside. We need someone who has been inside enough to know what an MLOps pipeline actually breaks like, what it feels like to review someone else's PR at midnight, and why the debate between RAG and fine-tuning is genuinely interesting and not just a topic to cover.
You don't need to code. You need to have cared about code at some point and still care about it enough to write about it with specificity and respect.
Non-negotiable
- B.Tech / B.E. CS, IT, ECE, or adjacent. Something technical was your starting point.
- 36 years of content, editorial, or communications work. B2B SaaS, developer tools, technical journalism, policy research, or similar environments strongly preferred.
- A portfolio that includes at least one long-form piece you wrote for a technical audience not about tech, for tech people. Engineers read it. Engineers shared it. You know why it worked.
- Can write a 2,500-word whitepaper and a 150-word LinkedIn post in the same week without making either feel like the other.
- Has managed or edited contributors before. You know the difference between giving feedback that improves a piece and feedback that just makes it sound like you.
Strong signal (not required, but we will notice)
- You've written something blog, newsletter, thread on your own, for engineers, with no employer behind it. You did it because you had something to say.
- You can read a content audit and diagnose what's wrong in under 20 minutes. (We will literally do this in the interview.)
- You know what RAG is. You know why someone would choose it over fine-tuning. You don't need to implement it you need to be able to write about the tradeoff without it sounding like a Wikipedia summary.
- You have a favourite technical writer or publication and you have opinions about why it works.
WHAT THIS IS NOT
This is not a role for someone who produces polished content slowly. Our calendar is a machine. If your portfolio is full of The Future of Work and How AI is Transforming Industries, this is not the right fit.
This is also not a role for someone who outsources their curiosity to whatever the content brief says. The Content Lead at Saras AI has to be genuinely interested in what engineers are building, what they're frustrated by, and what makes them respect an institution. That interest has to come from the inside.
LOCATION & COMPENSATION
- Gurgaon on-site. The team brainstorms in person, we'd like you to be present for it.
- 36 years experience
- Compensation competitive with content lead roles at B2B SaaS companies in NCR
