Responsibilities

• - Tell both halves of the story. Sit close to the teams shipping these systems, understand what was actually hard, and translate it into video, writing, and demos that travel.
• - Then go a level up: what the system changed for the operator, what it cost, what it replaced, why the CFO signed.
• - Shape how Provectus is positioned. Not just the case studies but the argument above them. What we stand for, which problems we claim, where we say no.
• - Build the tools that make the marketing work. A scraper that watches what our market is saying.
• - An agent that drafts case studies from delivery artifacts.
• - A microsite for a launch.
• - A dashboard showing which stories moved pipeline.
• - You write the code. You do not file a ticket and wait.
• - Own channels outright. Write, publish, and measure across LinkedIn, YouTube, X, and whatever channel matters six months from now that does not matter today.
• - Run experiments and kill the ones that lose.

Requirements

• - You have shipped things people used.
• - A side project, a channel with an audience, a tool, a launch.
• - We care more about what you made than where you worked.
• - You write well, and you have a point of view.
• - You can hold attention for 90 seconds on video and 900 words on a page.
• - You are curious about how companies make money.
• - You can read a business case and find the part that actually matters.
• - You can sit with a CFO or a PE operator and not reach for features.
• - You code. Python or TypeScript, comfortably.
• - You use Claude Code, Cursor, or equivalent every day and you have opinions about them.

Benefits

• - Direct access to the people building the systems and the executives selling them. Small team, no layers between you and the work.
• - A budget for tools, models, and experiments, with no approval chain under a threshold.
• - Promotion tied to output, not tenure.
• - 401(k) profit sharing plan after probation period
• - Unlimited PTO policy
• - Medical, Visual and Dental insurance