Developer Relations Lead

STRAND is real-time architecture mapping for engineering teams running service-heavy systems. The product maps every dependency, tracks every change, and surfaces blast radius before anything ships. The engineers who need STRAND are not reached through ads or cold outreach. They are reached by building genuine trust in the communities where they already spend time. That is this role.

You will be STRAND's voice in the engineering community. Technical content, conference talks, open source contributions, developer feedback loops, this role builds the presence that earns STRAND's reputation over time. You have deep technical credibility, you communicate clearly, and you care about the quality of what you put your name on.

What you will work on

• Build STRAND's presence in engineering, DevOps, and platform communities through technical content and authentic participation.
• Write and produce technical content — blog posts, guides, demos, talks — that engineers find genuinely useful.
• Represent STRAND at conferences, meetups, and online communities where the target audience is active.
• Run structured feedback loops with developers to surface product insights that inform the roadmap.
• Work closely with the DX engineer and product team to ensure the integration and onboarding experience reflects community expectations.
• Build relationships with influential engineers and community leaders who can amplify STRAND's reach authentically.

What we are looking for

• 5 or more years in developer relations, developer advocacy, or a technical role with significant community engagement.
• You have shipped code professionally. You can read a pull request, understand an API, and have a credible conversation about infrastructure architecture.
• Track record of building developer community presence that drove adoption, not just followers.
• Strong written and verbal communication. Your content does not feel like marketing copy. It feels like it was written by an engineer for engineers.
• You are active in the DevOps, platform engineering, or observability community in some form that you can point to.
• You understand the difference between vanity metrics and signals that actually indicate developer trust and adoption.

How we work

• Fully remote. Work from wherever you do your best work.
• Async by default. Meetings exist when they need to, not as a reflex.
• Small team. Your decisions ship. There is no committee.
• We move fast and cut anything that does not serve the outcome.

What we offer

• Competitive salary and equity with straightforward terms.
• Five weeks paid vacation plus local public holidays.
• Health coverage based on your location.
• Home office or co-working stipend.
• Four months paid parental leave.
• Regular team off-sites.