Power Platform & AI Automation Specialist

The Safeguards and Security Solutions Enablement team is part of Safeguards and Security Directorate, forged to refine how the organization operates and keeps the Laboratory secure while enabling mission attainment. Safeguards and Security Solutions Enablement works like an internal digital creative agency, built around a single ethos: are we making it easier to be an employee, a manager, and a professional at INL, with a focus on continuous improvement.

Safeguards and Security Solutions Enablement consolidates five disciplines:
Systems Strategy, Business Analysis, AI & Automation Engineering, UX Research & Design, and Data Analytics. You're joining a small group wearing multiple hats, closer to a team of trained operatives than a five-department org chart. The Power Platform & AI Automation Engineer role lives inside AI & Automation Engineering, Safeguards and Security Solutions Enablement's build engine, translating the team's discovery work into delivered application and automation products.

This is not a heads-down coding role, nor is it a throw-it-over-the-fence one. You observe teams closely to discover how work actually happens. The nuanced details of work often remain unknown or misunderstood, yet these details can be what matters most. You'll document customer needs via wireframes, diagrams, or user stories, whatever facilitates rapid understanding. From there, you iterate through tangible drafts and honest feedback, with an eye on minimum viable product, to work agilely rather than waterfall and beholden to a completely nailed down requirements set.

The same requirement elicitor remains present through delivery, checking in throughout the short cycles instead of disappearing and reappearing at the end. Skip these methods, and we risk automating a bad process, which is the same bad process, just faster.

Here's your mission: you're not a one-trick automation pony. You understand the business well enough to know that not every need is an automation. Sometimes the right fix is a workflow. Sometimes it's recognizing that a new system is the real answer, and when that's the case, you're all over it: vetting the options, meeting with internal teams to gather requirements, working directly with vendors, and staying engaged through implementation, so the actual underlying problem gets solved.

This role owns full-stack solution delivery, with the Microsoft Power Platform as the default toolset:
Power Apps, Power Automate, and Power BI. But the platform serves the solution, not the other way around. When the problem calls for a Python web app in Django or Flask, a .NET service, or even the discovery of an appropriate 3rd party solution, you'll help there too. Layered on top is real AI engineering:
Python, generative AI, prompt engineering, and agentic automation through tools like Microsoft Copilot Studio, Claude, and other custom platforms as the work demands.

We're hiring a person into this role because demand for continual optimization is real and only growing. And none of this is order-taking: success means the people you serve end up more efficient, produce higher-quality work, and genuinely enjoy their jobs more, not just that a ticket got closed.

• Meet face-to-face and observe how work actually happens, not just how it gets described. What people say they do and what they actually do are often different, and the nitty-gritty details left out are often the insights that matters most.
• Elicit and document requirements through interviews and working sessions, translating what a team asks for into what they actually need. "Documented" might mean a wireframe, a diagram, or a user story, whatever is clear enough to execute on without having to rely on tribal knowledge.
• Wireframe and prototype early and throughout using tools like Lucid, MS Visio or Figma for process maps, wireframes, and data modeling when it helps, so stakeholders are reacting to something tangible within days, not approving a written spec weeks before anything visible exists.
• Catch a bad process before automating it as automating a bad process doesn't solve anything.
• Stay with the customer through delivery, checking in on working builds at short, regular intervals, refining requirements as understanding deepens rather than locking them in at kickoff and signing off.
• Understand full work streams, not just…