Developer Relations Engineer

Location: San Francisco, with min. 3-4 days per week in the office. Base salary: $165,000–$175,000 USD per year. About Limrun Limrun gives cloud coding agents access to remote Xcode and iOS and Android environments so they can build and test mobile apps, then share the results through demo videos and interactive previews. Limrun is backed by Y Combinator and is in production at companies including Replit, Rork, and Momentic. More about Limrun: https://limrun.com The role We're hiring a Developer Relations Engineer in San Francisco to help developers discover Limrun and use it in their own projects. You'll build working examples, publish technical content consistently, and spend time with developers in the communities where they already work and learn. You'll take projects from an idea to a working demo, help people try it, and improve it based on their feedback. You'll work closely with the founder and engineering team. Success means developers can complete useful workflows with Limrun and return to use it again. What you'll do

• Build, publish, and maintain sample apps and reference workflows that show developers how to use Limrun with coding agents and mobile development tools. Own each example through developer use, helping people try it and fixing the friction they encounter.

• Write quickstarts, tutorials, and technical guides. Test the instructions yourself and keep them current as the product changes.

• Create short demo videos, technical posts, and live sessions that explain a specific workflow or solve a real developer problem.

• Maintain an active social media presence and publish consistently, sharing hands-on demos, technical tips, and useful examples of what developers can build with Limrun. Engage with developers in the comments and follow up on their questions.

• Run developer onboarding calls or office hours to help people get their first workflow running. Turn repeated questions into better documentation, examples, or concrete product improvements.

• Be an active, regular participant in developer communities. Join discussions, answer technical questions, share useful work, and build relationships with people developing mobile apps and coding-agent tools.

• Reproduce issues and give engineering clear feedback, including the steps taken, expected behavior, and where the developer got stuck.

• Test different tutorials, demos, and community activities. Track whether they help developers try Limrun, complete a working example, and continue using it. Use what you learn to decide what to do next. What we're looking for

• You have at least 3 years of relevant professional experience.

• You can write and debug software independently, work with APIs and command-line tools, and build examples that another developer can run.

• You have hands-on experience with at least one mobile development stack, such as Swift, Kotlin, React Native, or Flutter.

• You explain technical ideas clearly in writing and spoken English. You're comfortable recording a demo or walking someone through code.

• You've created something useful for other developers: documentation, an open-source project, a tutorial, a talk, or a tool.

• You use coding agents in your own work and can check their output, investigate failures, and explain the limits of an example honestly.

• You can choose a useful problem, finish the work, and follow up on how people use it. Previous DevRel experience is welcome, but it isn't required. Engineering experience with a record of helping other developers is relevant too. Useful experience Experience with mobile build systems, automated testing, cloud development environments, or open-source communities would help. You don't need to know every mobile framework. Experience building a developer audience is a plus, but an existing audience isn't required. Apply Share links to a project, tutorial, demo, or technical explanation you created. Tell us who it was for, what you personally contributed, and what you changed after someone tried it. Include any evidence that it helped, such as developer feedback, completed workflows, or repeat use. A small project with clear evidence is welcome; you don't need a large audience.