Content Engineer

Orkes is a platform for developers to build durable, distributed event driven applications. Based on the popular open source orchestration engine Conductor, Orkes lets developers focus on faster go to market with applications, scaling them to handle billions of workflows without having to worry about failures, scalability or visibility into the executions.

We're looking for a Content Engineer - This is a high-impact, high-ownership role for someone who enjoys wearing multiple hats and shaping how developers interact with a product from day one.

We’re looking for a unique hybrid: someone who is both deeply technical and naturally communicative. This role sits at the intersection of engineering, content, and community—owning how developers experience, understand, and engage with our product. Instead of splitting this across multiple roles, we’re looking for one person to connect the dots end-to-end—from building and understanding technical solutions, to creating high-quality content, to engaging directly with our developer community. If you’ve ever built something and immediately wanted to explain it, teach it, or share it, you’ll feel right at home here.

Technical + Product Understanding:

• →

  Get hands-on with our product, APIs, and platform capabilities

• →

  Build sample applications, integrations, and use cases

• →

  Translate complex technical concepts into clear, usable insights

Content Creation:

• →

  Create technical content such as:

  • →

    Blog posts

  • →

    Tutorials and guides

  • →

    Documentation improvements

  • →

    Use-case walkthroughs

• →

  Develop content that helps developers go from first touch → successful implementation

• →

  Experiment with modern content approaches, including AI-assisted workflows

Community Engagement:

• →

  Engage with developers across channels (Slack, Discord, forums, etc.)

• →

  Answer questions, unblock users, and gather feedback

• →

  Help foster an active, supportive developer community

• →

  Surface insights from the community back to product and engineering teams

Must-Haves

• Strong technical background (engineering, developer tools, APIs, or similar)

• Experience creating technical content (blogs, tutorials, documentation, etc.)

• Ability to clearly explain complex topics to a developer audience

• Hands-on experience working with modern architectures (APIs, cloud, microservices, etc.)

Nice-to-Haves

• Experience in Developer Relations (DevRel), Developer Experience (DX), or similar roles

• Open source contributions or public technical portfolio (GitHub, blog, etc.)

• Experience engaging or managing developer communities

• Familiarity with AI/LLM-driven tools or workflows

• This is not a traditional marketing role—you’ll be hands-on and technical

• This is not a pure engineering role—you’ll be externally facing and communicative

• You’ll have ownership across content, community, and developer experience

• You’ll help shape how developers discover, learn, and adopt our product

• Preferred: Bay Area or Seattle

• Open to remote for the right candidate, but prefer in-office

We’d love to see examples of your work:

• Blog posts or tutorials

• GitHub projects

• Documentation contributions

• Anything that shows how you think and communicate