At ClassLink, we believe learning should be accessible, engaging, and empowering for every student, every educator, everywhere. That’s why we build secure, intuitive tools that empower more than 26 million students and educators worldwide. From simplifying access with single sign-on, to advancing equity with usage analytics, to automating secure rostering, our platform helps schools focus on what matters most: teaching and learning.
We’re not just building tools, we’re building what’s next in education. By removing barriers and enabling data-driven decisions, our solutions help educators lead with confidence and students thrive in and out of the classroom every day.
Our team is driven by purpose and grounded in three core values:
- Strive to Grow - always learning, improving, and innovating.
- Deliver Worthwhile Experiences - for our users, our partners, and each other.
- Contribute with Heart - putting people first in everything we do.
These values shape how we work, innovate, and support the communities we serve. If you’re ready to do work that makes a real difference, and grow alongside a team that values collaboration, support, and continuous improvement. ClassLink is the place for you.
ClassLink is always building, improving, and releasing products. We’re looking for someone who’ll dig into the details, ask good questions, and get to the part that makes someone say, “Oh, I could use that.”
As our Product Communications Specialist, you’ll help us figure out how to talk about what we’re building. That starts before you write a word. You’ll work out who needs to know, why it matters to them, and what we should create. Then you’ll carry that thinking into launches, nurturing campaigns, webpages, product news, and internal communication. You’ll also think about what comes after launch, because hitting publish is only part of the job.
Some days, you’ll turn a complex feature into three useful sentences. Other days, you’ll see how those three sentences could become a campaign. We’ll count on you to spot what’s missing, suggest what comes next, and keep the details and deadlines straight along the way.
And if you’ve already tightened a sentence or three in this description, we should probably talk.
A Day in The Life….
Product Communication & Messaging
- Get to know our products, features, and releases well enough to explain them to someone who doesn’t speak fluent ClassLink.
- Dig into workflows, use cases, and limitations. Keep asking questions until you can explain what a feature does, who it helps, and why they’d care.
- Build messaging, value statements, FAQs, talking points, and terminology other teams can trust and reuse. A good explanation shouldn’t have to start from scratch every time.
- Keep product webpages current and useful. If a page is telling last year’s story or leaving readers wondering what to do next, you’ll help fix it.
- Spot where a new page, FAQ, or resource would help someone find the answer they need, whether they’re searching on Google or asking AI.
- Adjust the story for clients, prospects, partners, and employees. They bring different questions, and you’ll help answer them without losing the facts along the way.
Campaigns & Content
- Get involved early with Product and Marketing to understand what’s coming and what communication is needed.
- Turn those conversations into communication plans that make the audience, message, channels, content, owners, and timing clear. Everyone should know their part.
- Match the communication to the release. Sometimes a useful update is enough. Sometimes we need a full campaign.
- Spot missing information and creative needs early, giving Creative, Web, Learning Design, Technical Writing, and other teams time to do their best work.
- Keep the product story consistent across webpages, email, campaigns, product news, presentations, events, and internal communication. Consistent doesn’t mean copied and pasted.
- Keep useful product content coming between launches, too. Think blog series, explainers, comparisons, FAQs, use cases, and resources people will still need six months from now.
- Write the content yourself or give another writer a brief they can work from. Bring in customer stories and proof when they help make the point.
Cross-Functional Collaboration
- Build relationships across Product, Marketing, Sales, Client Services, Learning Design, Technical Writing, and Creative. Knowing who to ask is a real part of this job.
- Keep owners, deadlines, and next steps clear, including who needs what before they can move forward. We’ll count on you to notice when something needs a follow-up.
- Know when to pull in the right people across events, webinars, social, PR, newsletters, customer stories, case studies, and other channels to make the product story stronger.
- Use good judgment when customer needs, technical details, marketing goals, and business priorities pull in different directions. Help us find language that’s both accurate and worth reading.
- Build repeatable ways to plan, create, update, and reuse communication. Use AI where it helps, with your judgment and fact-checking still very much on the job.
- Stay curious about buyer questions, product marketing, search and AI discovery, and new ways to communicate. Bring back the ideas worth trying and help us put them to work.
What Success Looks Like
First 30 Days: Learn Products, People & Processes
Start by getting curious. Learn the products, meet the people, and get a feel for how communication happens here. Before you suggest a better way, understand why we do it this way.
- Get comfortable with our products, terminology, and audiences, and learn how a release moves from Product to market.
- Meet the people involved in product communication. Understand what they own, what they need from you, and where your work connects.
- Look through recent launches, webpages, nurture campaigns, product content, internal communication, and enablement resources. Notice what’s working, too. We want to keep the good stuff.
- Follow the product story across events, social, customer stories, PR, newsletters, and blogs to see how the pieces fit together.
- Notice where communication starts too late, useful stories go untold, or someone says, “Didn’t we already write this?” Those are worth a closer look.
By 60 Days: Put What You're Learning to Work
You’ll still have questions. You’ll also have enough context to say, “Here’s how I think we should handle this,” and start making it happen.
- Take ownership of communication for assigned releases and features, from the first planning conversation through delivery.
- Build launch plans that make it clear who we’re reaching, what we’re saying, what we’re creating, and who’s doing what by when.
- Develop product messaging for webpages, nurture campaigns, client communication, and resources our internal teams can use.
- Start lining up product campaigns and content ideas before the next request arrives. You’re getting to know the products well enough to see what’s worth talking about.
- Flag missing information and content or creative needs while there’s still time to act. If something is unclear, help get it sorted.
By 90 Days: Own the Work
By this point, we should be able to talk through a goal and trust you to work out the next steps. You’ll know when to move something forward and when to pull someone in.
- Independently take assigned product communication projects from planning through completion, keeping the people involved informed along the way.
- Keep an active pipeline of launches, nurture campaigns, product content, and webpage opportunities, with a clear view of what’s next.
- Bring recommendations when you spot a gap. “Here’s what I noticed, and here’s what I think we should do” is a good place to start.
- Put repeatable launch plans and reusable messaging to work so each project starts a little further along.
- Use product priorities, audience feedback, and what people actually engage with to recommend the stories we should tell next.
- Become someone teams trust to help answer, “How should we communicate this?”
NOTE: This job description is not intended to be all-inclusive. Employees may be asked to perform other related duties as assigned to meet the ongoing needs of the organization
