Content Engineer

The Role

We’re hiring a Content Engineer – someone who sits at the intersection of technical curiosity and creative instinct. This isn’t a DevRel role, and it isn’t a traditional product marketing role. It’s something in between: a person who can spin up a working integration of our API on a Tuesday and turn it into a compelling LinkedIn thread by Wednesday.

You’ll own Sent’s creative output. You’ll understand the product well enough to actually build with it, and you’ll care enough about craft to make every post, campaign, and experiment feel intentional. You’ll be one of our earliest marketing hires, defining what Sent’s voice and presence becomes.

What You’ll Do

Build and experiment with the product

Use the Sent API to build real things – side projects, creative integrations, technical examples – and turn those builds into content that earns attention
Run a high-velocity experiment cadence across LinkedIn, X, newsletters, and other channels: form a hypothesis, ship something, read what happened, and iterate
Develop an instinct for what resonates with a technical audience and what falls flat, and build a feedback loop around it
Own product marketing and brand presence

Define and evolve how Sent communicates its product to the market – feature launches, positioning updates, messaging for new channels and use cases
Own our presence on LinkedIn, X, and any other channels that earn distribution – building a consistent, interesting voice over time
Develop creative campaigns that sit at the intersection of what Sent can do technically and what makes for compelling storytelling
Drive growth and measure it honestly

Instrument the top of funnel: track where developers come from, what converts, and what doesn’t – with the rigor to know when a result is real
Build tooling when you need it: spin up landing pages, set up automations, and connect the marketing stack without waiting on engineering
Partner with the demand gen function to ensure creative work ties to pipeline, signups, and activated accounts

What You Bring

2+ years in marketing, content, or a creative role – at a startup or somewhere you had to figure things out without a playbook
You can build with APIs – you’re comfortable reading docs, writing integration code, and shipping something functional without a lot of hand-holding
You have a strong creative instinct and a portfolio that shows it: posts, campaigns, projects, or work that actually connected with an audience
An eye for design and UX – you have a point of view on what good looks like and can produce visuals that don’t need a designer to fix them
You think experimentally – hypotheses, tests, results, iterations – and you’re honest about what the data is telling you
You write well: concise, clear, technical when it needs to be – you understand the difference between writing for developers and writing for everyone else
You’re genuinely interested in the tech-marketing space: how great dev tools earn attention, how communities form around them, and what makes a brand feel authentic versus forced
Experience with messaging, telecom, or API infrastructure is a plus, but intellectual curiosity about those spaces matters more