Developer Relations Engineer

Limrun is seeking a Developer Relations Engineer in San Francisco (hybrid) to help developers discover Limrun and successfully apply it in their own projects. The role focuses on building practical examples, delivering technical content, and refining everything based on real developer feedback.

What You Will Do

• Build, publish, and maintain sample applications and reference workflows that demonstrate how to use Limrun with coding agents and mobile development tools.
• Take ownership of each example as developers use it, helping them get started, address friction, and iterate on what they encounter.
• Write quickstarts, tutorials, and technical guides; validate the instructions yourself and keep them current as the product evolves.
• Create short demo videos, technical posts, and live sessions that walk through specific workflows or resolve real developer problems.
• Maintain an active social media presence with consistent publishing, including hands-on demos, technical tips, and practical examples of what developers can build with Limrun.
• Participate in community conversations by responding to comments and following up on questions.
• Run developer onboarding calls or office hours to support getting a first workflow running.
• Convert recurring questions into improved documentation, clearer examples, or concrete product changes.
• Engage regularly in developer communities by joining discussions, answering technical questions, sharing useful work, and building relationships with people working on mobile apps and coding-agent tools.
• Reproduce reported issues and provide engineering feedback with the steps taken, expected behavior, and where the developer got stuck.
• Test tutorials, demos, and community activities to determine whether they help developers try Limrun, complete a working example, and continue using it; apply what you learn to plan next steps.

Role Requirements

• At least 3 years of relevant professional experience.
• Ability to write and debug software independently, work with APIs and command-line tools, and build examples that another developer can run.
• Hands-on experience with at least one mobile development stack: Swift, Kotlin, React Native, or Flutter.
• Clear technical communication in writing and spoken English.
• Comfort recording demos and walking someone through code.
• Demonstrated experience creating something useful for other developers, such as documentation, an open-source project, a tutorial, a talk, or a tool.
• Experience using coding agents in your own work, including checking output, investigating failures, and describing the limits of an example accurately.
• The ability to select a useful problem, complete the work, and follow up on how people use it.

Helpful Background

• Experience with mobile build systems, automated testing, cloud development environments, or open-source communities.
• Familiarity with multiple mobile frameworks is not required.
• Experience building a developer audience is a plus, though an existing audience is not required.

Technologies

• Swift
• Kotlin
• React Native
• Flutter

Location and Work Style

San Francisco, CA with 3–4 days per week in the office (hybrid).

How to Apply

Submit links to a project, tutorial, demo, or technical explanation you created. In your note, include who it was for, what you personally contributed, and what you changed after someone tried it.

If available, include evidence such as developer feedback, completed workflows, or repeat use. A small project with clear evidence is welcome, and you do not need a large audience.