Role overview
GenAI Engineer / GenAI Developer Advocate
Location: Alpharetta, GA - Hybrid
100% hands-on engineer with strong enablement & communication skills.
Primary Focus:
Help internal development teams adopt GenAI tools
Build MVPs / starter code / SDKs
Run workshops and enablement sessions (not just close tickets)
This is not a traditional app dev role where they own a single product. It’s a central GenAI enablement/engineering role supporting multiple product teams.
MUST-HAVE REQUIREMENTS (NON-NEGOTIABLE)
Use this for hard filtering and first-pass screening.
- GenAI Engineering Experience
- Hands-on experience with GenAI tools such as (examples; at least one is required):
o GitHub Copilot
o Cursor
o Windsurf
o Other comparable AI coding assistants / GenAI dev tools
- Can describe how they used these tools in real engineering scenarios (not just playing around).
- Strong Prompt Engineering Skills
- Can demonstrate structured, thoughtful prompt design:
o Designing prompts for complex tasks
o Iterating and refining prompts based on output
o Understanding of context, system vs user prompts, constraints, etc.
- Able to explain prompt tradeoffs, guardrails, and failure modes in their own words.
- 100% Hands-On Engineer
Current or very recent role must be hands-on coding (not pure architecture, not pure management).
- Comfortable:
o Building prototypes / MVPs
o Writing starter code / SDKs
o Integrating GenAI tools into development workflows
- They should want to stay close to code and tooling.
- Exceptional Communication & Enablement Ability
This is critical and should be a heavy screen.
Candidate must:
Be able to run workshops and training / enablement sessions for engineering teams.
Be able to lead discovery sessions with dev managers:
o Understand their use case
o Suggest solutions
o Decide whether to build or connect to an existing solution
Be comfortable presenting to senior leadership and cross-functional stakeholders.
Speak clearly, logically, and confidently; able to explain complex technical GenAI concepts in simple terms.
Think: Engineer + Teacher / Developer Advocate, not a heads-down coder who avoids people.
- Mindset & Focus
- Enablement mindset, not “ticket taker.”
o They help teams adopt tools, don’t just close JIRA tickets.
- Obsessed or deeply interested in:
o GenAI
o LLMs
o New AI dev tooling
- Curious, self-directed learner who keeps up with the rapidly evolving GenAI ecosystem.
STRONGLY PREFERRED / NICE-TO-HAVE
Use these for priority ranking, not hard rejection.
Technical Preferences
- Cloud-heavy background, preferably AWS:
o Experience building or deploying solutions on AWS.
- Comfort with modern programming languages such as:
o Python
o Go / Golang
o Java
o Node.js
o .NET
- Experience with:
o MCP (Model Context Protocol) or similar context orchestration
o Agentic AI / workflow orchestration
Domain & Legacy Experience (Nice-to-Have)
Any exposure to mainframe or SAP / legacy systems is a plus (their tools are still catching up to AI capabilities).
Prior ADP experience can be helpful if they can speak to:
o Real-world dev pain points
o Past challenges and gaps in engineering workflows
o How GenAI could address those gaps
Soft-Skill and Career Profile
Has done internal talks, meetups, brown-bag sessions, or training for other engineers.
Has built personal or side projects with LLMs / GenAI (for themselves, family, etc.).
Shows critical thinking about:
o Code quality with AI
o When to trust / not trust AI-generated code
o How to evaluate outputs (not just produce them)