H-1B Visa Developer Relations Engineer Jobs
Developer Relations Engineer roles sit at the intersection of software engineering and technical advocacy, making them strong candidates for H-1B visa specialty occupation classification. Most employers filing LCAs for these positions code them under SOC 15-1252 (Software Developers) or 15-1299, which affects your prevailing wage tier and petition framing.
Find H-1B Visa Developer Relations Engineer JobsOverview
Showing 5 of 21+ Developer Relations Engineer jobs
See all Developer Relations Engineer Jobs
Sign up for free to unlock all listings, filter by visa type, and get alerts for new Developer Relations Engineer roles.
Get Access To All JobsAbout us
Gimlet is building the first multi-silicon neocloud designed for fast, efficient AI inference. We combine large-scale compute infrastructure with an execution platform that partitions AI workloads and maps each stage to the hardware best suited to run it. We work with foundation labs, hyperscalers, and AI-native companies, giving our team access to technical problems spanning frontier models, production infrastructure, and emerging hardware.
About The Role
Gimlet Labs is seeking an AI Developer Advocate to help developers discover, evaluate, and successfully build on our AI inference platform. You’ll sit at the intersection of engineering, product, and community. You’ll create technically credible demos and educational content, engage directly with AI builders, and turn their feedback into improvements across our APIs, SDKs, documentation, and product experience. This is a hands-on technical role for someone who enjoys building in public, explaining complex systems clearly, and helping developers move from their first API call to reliable production deployments. Developer advocacy is not simply promotion. The role succeeds when developers trust our technical guidance, enjoy building with the platform, and see their needs reflected in the product. You should be equally comfortable writing code, teaching a technical concept, talking with a developer who is stuck, and explaining to an internal team why a particular piece of developer friction matters.
What Success Looks Like
In the first 6 months, you will:
- Identify the best channels for Gimlet’s developer outreach and build initial presence
- Build trusted relationships within relevant AI developer communities
- Ship useful examples and educational content that developers actively adopt
- Establish a reliable feedback loop between developers and the product team
- Set an objective for developer experience on our upcoming developer cloud offering
You may be a good fit if you have
- Evidence of technical communication, including articles, talks, videos, documentation, open-source projects, or sample applications
- Strong empathy for developers and an instinct for recognizing friction in APIs, documentation, and tooling
- The ability to explain technical subjects clearly to audiences with different levels of expertise
- Comfort engaging publicly and representing a technical product
- The ability to operate independently in a fast-moving environment
- Hands-on experience building applications with LLM or multimodal-model APIs
- A practical understanding of AI inference concepts such as latency, throughput, context length, batching, quantization, model routing, and cost
- Professional software development experience, ideally with Python or TypeScript
Strong candidates may also have
- Experience with open-weight models and serving frameworks such as vLLM, SGLang, or TensorRT-LLM
- Familiarity with agent frameworks, retrieval systems, evaluations, observability, and fine-tuning
- Experience running workshops, hackathons, developer programs, or technical communities
- Contributions to open-source AI projects
- Experience working in developer relations, developer experience, solutions engineering, or developer education
- Familiarity with GPU infrastructure and production ML systems
Why join now?
Gimlet is expanding from its core technology into a production neocloud spanning new hardware, customers, and data centers.
- Solve hard problems
- Own meaningful work
- Build for production
- Help define what’s next
Agency Policy:
Gimlet Labs does not accept unsolicited resumes from recruitment agencies or search firms. Any unsolicited resumes submitted without a signed agreement will be considered the property of Gimlet Labs, and no fees will be paid.
About us
Gimlet is building the first multi-silicon neocloud designed for fast, efficient AI inference. We combine large-scale compute infrastructure with an execution platform that partitions AI workloads and maps each stage to the hardware best suited to run it. We work with foundation labs, hyperscalers, and AI-native companies, giving our team access to technical problems spanning frontier models, production infrastructure, and emerging hardware.
About The Role
Gimlet Labs is seeking an AI Developer Advocate to help developers discover, evaluate, and successfully build on our AI inference platform. You’ll sit at the intersection of engineering, product, and community. You’ll create technically credible demos and educational content, engage directly with AI builders, and turn their feedback into improvements across our APIs, SDKs, documentation, and product experience. This is a hands-on technical role for someone who enjoys building in public, explaining complex systems clearly, and helping developers move from their first API call to reliable production deployments. Developer advocacy is not simply promotion. The role succeeds when developers trust our technical guidance, enjoy building with the platform, and see their needs reflected in the product. You should be equally comfortable writing code, teaching a technical concept, talking with a developer who is stuck, and explaining to an internal team why a particular piece of developer friction matters.
What Success Looks Like
In the first 6 months, you will:
- Identify the best channels for Gimlet’s developer outreach and build initial presence
- Build trusted relationships within relevant AI developer communities
- Ship useful examples and educational content that developers actively adopt
- Establish a reliable feedback loop between developers and the product team
- Set an objective for developer experience on our upcoming developer cloud offering
You may be a good fit if you have
- Evidence of technical communication, including articles, talks, videos, documentation, open-source projects, or sample applications
- Strong empathy for developers and an instinct for recognizing friction in APIs, documentation, and tooling
- The ability to explain technical subjects clearly to audiences with different levels of expertise
- Comfort engaging publicly and representing a technical product
- The ability to operate independently in a fast-moving environment
- Hands-on experience building applications with LLM or multimodal-model APIs
- A practical understanding of AI inference concepts such as latency, throughput, context length, batching, quantization, model routing, and cost
- Professional software development experience, ideally with Python or TypeScript
Strong candidates may also have
- Experience with open-weight models and serving frameworks such as vLLM, SGLang, or TensorRT-LLM
- Familiarity with agent frameworks, retrieval systems, evaluations, observability, and fine-tuning
- Experience running workshops, hackathons, developer programs, or technical communities
- Contributions to open-source AI projects
- Experience working in developer relations, developer experience, solutions engineering, or developer education
- Familiarity with GPU infrastructure and production ML systems
Why join now?
Gimlet is expanding from its core technology into a production neocloud spanning new hardware, customers, and data centers.
- Solve hard problems
- Own meaningful work
- Build for production
- Help define what’s next
Agency Policy:
Gimlet Labs does not accept unsolicited resumes from recruitment agencies or search firms. Any unsolicited resumes submitted without a signed agreement will be considered the property of Gimlet Labs, and no fees will be paid.
See all H-1B Visa Developer Relations Engineer Jobs
Sign up for free to unlock all listings, filter by visa type, and get alerts for new H-1B Visa Developer Relations Engineer Jobs.
Get Access To All JobsTips for Finding H-1B Visa Sponsorship as a Developer Relations Engineer
Confirm your SOC code before filing
DevRel roles get classified under different SOC codes depending on the employer, which changes your prevailing wage requirement. Check the OFLC Wage Search using both 15-1252 and 15-1299 before your employer files the LCA to avoid a mismatch that triggers an RFE.
Document your technical depth on paper
USCIS scrutinizes DevRel petitions because the role blends engineering with advocacy. Your resume and support letter should quantify the software development work, not just the community or content output, to satisfy the specialty occupation standard for a bachelor's degree in a directly related field.
Target employers with cap-exempt filing history
Universities, nonprofit research organizations, and government contractors can file H-1B petitions year-round outside the annual cap. DevRel roles exist at these employers too, particularly in developer tooling and research platforms, so don't limit your search to commercial tech companies.
Use Migrate Mate to filter for verified sponsors
Search Developer Relations Engineer roles on Migrate Mate to see which employers have active LCA filing history for this job category. That data comes directly from DOL disclosure records, so you're targeting companies that have already cleared the prevailing wage certification process for similar positions.
Start the LCA process before your OPT expires
Your employer must file the LCA with DOL and receive certification before USCIS can accept the I-129 petition. For cap-subject H-1B filings, count back from the October 1 start date and confirm your employer's HR or legal team has the LCA submitted no later than late March.
Negotiate a job description that supports specialty occupation
If the offer letter describes your role primarily as community management or content creation, ask the employer to revise it to lead with the technical requirements, including programming languages, SDK integration, and developer tooling responsibilities, before the petition is drafted.
H-1B Visa Developer Relations Engineer: Frequently Asked Questions
Does a Developer Relations Engineer role qualify as a specialty occupation for H-1B purposes?
Yes, but the petition framing matters. USCIS evaluates whether the role normally requires at least a bachelor's degree in a specific technical field. DevRel positions that require hands-on software development, SDK work, or systems integration typically qualify. Roles described primarily as marketing or community management face higher scrutiny and are more likely to receive an RFE.
Which SOC code do employers typically use when filing an LCA for a Developer Relations Engineer?
Most employers classify Developer Relations Engineers under SOC 15-1252 (Software Developers and Software Quality Assurance Analysts and Testers) or the broader 15-1299 category for computer occupations not elsewhere classified. The SOC code your employer selects determines the prevailing wage level on the LCA, so confirm it before filing using the OFLC Wage Search. O*NET can also help you identify which classification fits your actual job duties.
How do I find employers who actively sponsor H-1B visas for Developer Relations Engineer roles?
Search Developer Relations Engineer positions on Migrate Mate, which surfaces employers based on verified DOL Labor Condition Application filing history. This lets you filter for companies that have already gone through the H-1B process for similar roles rather than relying on job postings that may not reflect actual sponsorship willingness. LCA data is publicly disclosed and updated regularly.
Can I transfer my H-1B to a new employer if I change Developer Relations Engineer jobs?
Yes. Under H-1B portability rules, you can start working for a new employer as soon as your new employer files an H-1B transfer petition with USCIS, without waiting for approval, as long as your previous H-1B was valid when the transfer petition was filed. The new employer files a fresh I-129 with an LCA that reflects the new role and location's prevailing wage.
Does remote work affect my H-1B status as a Developer Relations Engineer?
Yes. H-1B workers must have an LCA certified for every location where they work regularly, including a home office. If you work remotely full-time from a state different from your employer's listed worksite, your employer needs to file an amended petition with an updated LCA for that location. Short-term travel for conferences or customer visits generally doesn't require an amended filing.