New opportunity

AI Automation Specialist

RSS, LLC. · Sacramento, United States

About this role

The AI Automation Specialist builds and operates business automations, integrations, and AI-powered workflows for Rex Moore’s Office of Operational Intelligence & Automation (OOIA). Reporting to the Director of OOIA, the role turns department priorities into working systems across pre-construction, estimating, project delivery, and back-office operations. It focuses on capturing and activating operational data, not architecting or managing central data infrastructure.

Responsibilities

  • Build, monitor, troubleshoot, and improve automations for data capture, document handling, work routing, approvals, and other operational processes. Identify manual work that can be reduced and propose improvements.
  • Connect ERP, CRM, and other enterprise systems using APIs, webhooks, JSON, and workflow platforms such as n8n, Power Automate, or Make. Maintain reliable connectors as the company’s tools evolve.
  • Manage AI tool integrations and prompt libraries. Build workflows for document processing, data extraction, summarization, and decision support; refine prompts and track output quality, usage, and cost. Extend AI assistants through connectors, including MCP or API integrations.
  • Capture, clean, and transform field and departmental data for automations, reporting, and AI workflows; provide clean operational data to the central infrastructure team.
  • Support tool configuration, rollout, onboarding, and training. Write guides for non-technical colleagues and reinforce responsible-use and data-handling practices with IT. Develop maintainable Python scripts for API calls, file processing, and data transformation.

Required qualifications

Hands-on experience with business automation platforms, system integrations, APIs, webhooks, JSON, and practical AI/LLM tools and prompting; Python proficiency; ability to work with data from multiple sources and learn ERP and CRM platforms; strong troubleshooting, communication, and teaching skills. No specific years of experience or education requirement is stated.

Preferred

Production use of AI provider APIs; ERP or CRM integration; SQL or other database queries; enterprise tool rollout and training; responsible-AI practices; Git; and interest or experience in construction, contracting, or project-based industries.

The full-time, day-shift position is based in an office in Sacramento, California, with possible travel to other offices. The posted salary range is $140,000–$160,000 per year. Employees may be eligible for health, retirement, leave, training, wellness, and tuition-reimbursement benefits.

For full details about this role, click “Apply on company site” to view the employer’s original posting.

Skills for this role

AI workflow automationLarge language modelsPrompt engineeringPythonAPIsWebhooksJSONn8nPower AutomateMakeZapierMCP connectorsData transformationData extractionDocument processingERP integrationsCRM integrationsTroubleshootingTechnical documentationUser trainingSQLGitResponsible AI

Your skill match

Checking your profile…

YOUR NEXT STEP

Get interview-ready for this role

A focused preparation guide, built around this job’s responsibilities and requirements.

✦ AI-generated guide
Preparation suggestions, not the employer’s actual interview questions. Always check the original posting for current requirements.
01

Understand the role

What matters most

  • Ship and sustain useful automations

    Turn priorities set by the Director of OOIA into workflows for data capture, documents, routing, and approvals. The posting calls for monitoring and troubleshooting deployed work, and describes first-90-day success as taking ownership of existing automations and shipping new ones that save measurable time.

  • Keep enterprise systems connected

    Build and maintain ERP, CRM, and other integrations using APIs, webhooks, JSON, workflow platforms, and Python where needed. The posting emphasizes reliable, maintainable connections as the enterprise toolset changes.

  • Operate AI workflows with measurable quality

    Manage AI integrations and prompt libraries for document processing, extraction, summarization, and decision support. Test and refine recurring workflows, extend assistants through connectors, and track output quality, usage, and cost.

  • Make operational data usable at the source

    Capture, measure, clean, and transform field and departmental data for automation, reporting, and AI. Feed clean data to the central infrastructure team; architecting that infrastructure is explicitly outside this role.

  • Enable adoption across departments

    Support configuration, onboarding, and ongoing use of AI and automation tools. Create guides non-technical colleagues can follow, teach responsible use, and reinforce data-handling practices with IT.

Likely challenges to think through

  • Deliver quickly without creating fragile workflows

    Likely preparation challenge, not a confirmed problem: early expectations to take over existing automations and save time may compete with the need to keep them healthy. Prepare to explain how to choose a small improvement, measure its effect, and build in error handling, monitoring, and documentation.

  • Integrate systems while tools evolve

    Likely preparation challenge, not a confirmed problem: changing ERP, CRM, or workflow platforms could make a fast connector choice costly to maintain. Prepare to compare platform workflows with Python or API-based integration on reliability, failure recovery, and ease of change.

  • Balance AI usefulness, cost, and responsible use

    Likely preparation challenge, not a confirmed problem: document and decision-support workflows need useful outputs without uncontrolled errors, usage costs, or mishandling of internal data. Prepare an approach to testing prompts, checking output quality, tracking cost, and coordinating data-handling practices with IT.

  • Resolve source-data issues without owning central infrastructure

    Likely preparation challenge, not a confirmed problem: field and departmental inputs may need cleaning before they can drive dependable workflows. Prepare to describe source-level validation and transformation, plus how to hand usable data to the central infrastructure team without assuming ownership of its architecture.

03

Practice your answers

Technical practice

How would you decide whether a manual approval or document-routing process is worth automating?

What to coverThe posting calls for reducing manual effort and errors and delivering measurable time savings. Suggested preparation: explain how you would map the process, establish a baseline, identify exceptions, and compare expected value with maintenance effort.

How would you connect an ERP or CRM to another business system using APIs, webhooks, and JSON?

What to coverThe role builds and maintains integrations across enterprise systems. Suggested preparation: discuss data mapping, authentication, event versus scheduled updates, duplicate handling, and how you would verify that records remain consistent.

When would you use a workflow platform rather than a Python script?

What to coverThe posting names workflow platforms such as n8n, Power Automate, and Make, alongside Python for logic off-the-shelf tools cannot handle cleanly. Suggested preparation: compare simplicity, reliability, visibility, and ongoing maintainability without assuming a particular platform is in use.

How would you diagnose and recover a deployed automation that stopped routing work correctly?

What to coverThe role owns day-to-day monitoring, troubleshooting, and improvement of deployed automations. Suggested preparation: walk through detecting the failure, tracing inputs and connector changes, protecting affected work, restoring service, and preventing recurrence.

How would you build an AI workflow that extracts information from business documents?

What to coverDocument processing and data extraction are stated AI workflow tasks. Suggested preparation: describe input preparation, structured output, checks for missing or uncertain fields, and when a person should review the result before it drives another process.

How would you test and refine prompts for a recurring summarization or decision-support workflow?

What to coverThe posting calls for maintaining prompt libraries and improving output quality while tracking usage and cost. Suggested preparation: explain how you would assemble representative cases, define quality checks, compare revisions, and weigh accuracy against cost.

What would you consider when connecting an AI assistant to internal data or systems?

What to coverThe role may extend assistants through MCP connectors, APIs, or platform extensions and reinforces data-handling practices with IT. Suggested preparation: discuss limiting access to the intended data and actions, checking outputs, and coordinating safeguards with IT.

How would you turn inconsistent field and departmental data into usable operational data?

What to coverThe role captures and cleans source data for automations, reporting, AI workflows, and handoff to the central infrastructure team; it does not manage that infrastructure. Suggested preparation: cover source definitions, validation, transformations, exception handling, and a clear handoff of data meaning and quality.

How would you make a Python integration script maintainable as systems change?

What to coverThe posting specifies Python for API calls, file processing, and transformation, with error handling, version control, and documentation. Suggested preparation: explain how you would organize the code, handle failed calls and malformed JSON, test changes, and document operational behavior.

How would you assess whether an AI or automation rollout is working across departments?

What to coverThe role supports configuration, onboarding, training, and ongoing adoption, and tracks AI usage, output quality, and cost. Suggested preparation: distinguish tool usage from useful outcomes, gather user feedback, and identify where guidance or workflow changes are needed.

Behavioural practice

Tell me about a time you took ownership of an automation after it went live.

What to coverThe posting emphasizes keeping deployed workflows healthy, not just building them. Suggested preparation: use a situation, action, and result example that shows what you monitored, how you resolved an issue, and what changed afterward.

Describe a time you had to learn an unfamiliar platform to deliver an integration.

What to coverAdaptability matters because the enterprise toolset is evolving. Suggested preparation: use situation, action, and result to show how you learned the system, made a practical integration choice, and verified the outcome.

Tell me about a time you helped non-technical colleagues adopt a new tool.

What to coverThe role includes onboarding, training, and guides that employees can follow. Suggested preparation: use situation, action, and result to explain how you learned users’ needs, taught the workflow, and assessed whether they could use it effectively.

Describe a time you delivered a directed priority while proposing another improvement.

What to coverThe posting asks this role to execute priorities set by the Director of OOIA while bringing forward ideas. Suggested preparation: use situation, action, and result to show how you handled the assigned work, supported your proposal with evidence, and communicated the trade-off.

Tell me about a time you addressed a data-handling concern in an AI or automation workflow.

What to coverThe role reinforces responsible-use and data-handling practices in partnership with IT. Suggested preparation: use situation, action, and result to describe the concern, who you consulted, what you changed, and how you checked the outcome.

02

Sharpen your knowledge

Topics to prepare

  • Workflow design and operational ownership

    Map a hypothetical document approval from intake to routing, exception handling, monitoring, and improvement; identify where time or errors could be reduced. The posting calls for building automations and keeping deployed workflows healthy.

  • Integration reliability across changing systems

    Compare an API call, webhook, and workflow-platform connector for a hypothetical ERP-to-CRM update; explain how you would handle changed fields and failed transfers. The role connects enterprise systems and favors reliable, maintainable integrations over mastery of one stack.

  • AI workflow quality and cost

    Define a small set of test documents and criteria for checking extraction accuracy, summary usefulness, usage, and cost. The posting calls for refining recurring prompts and tracking the quality and cost of deployed AI workflows.

  • Operational data scope

    Sketch how field and departmental records would be captured, cleaned, structured, and passed to the central infrastructure team. This matches the role’s source-side data work; central data-infrastructure architecture is explicitly outside its remit.

  • Responsible rollout and non-technical support

    Outline an onboarding session that explains an automation’s purpose, its limits, and appropriate data handling, then list likely support questions. The role includes training colleagues, writing guides, and reinforcing practices with IT.

Skills to revise

  • Configure a business automation

    As a practice exercise, build a document-intake and approval-routing workflow in n8n, Power Automate, Make, Zapier, or a comparable platform; test a missing field and a rejected approval. These platforms are examples in the posting, not a mandated stack.

  • Build and troubleshoot a connector

    Using sample JSON, configure an API call and webhook-driven update between two simulated business systems; inspect a failed payload and document the fix. APIs, webhooks, JSON, and connector troubleshooting are explicit requirements.

  • Write maintainable Python processing code

    Write a Python script that reads sample files, validates and transforms records, calls an example API, and reports errors clearly. The posting specifies Python for file processing, API calls, JSON, transformation, and error handling.

  • Test a reusable AI prompt

    Draft a prompt for extracting fields from a sample document, test it against varied examples, revise it for failures, and record output-quality and usage observations. This practices the listed document-processing, prompt-library, and AI-workflow duties.

  • Diagnose an operating workflow

    Practice tracing a hypothetical failed automation from its trigger through each integration, then write a short recovery note and monitoring checklist. The posting emphasizes day-to-day ownership, rapid troubleshooting, and continuous improvement.

  • Explain a tool to non-technical users

    Create a one-page plain-language guide for the practice workflow, including how to start it, check its result, and seek help when it fails. User-facing documentation, onboarding, and teaching are explicit parts of the role.

04

Your preparation checklist

  • Map the role’s first-90-day priorities

    The posting expects ownership of existing automations and new workflows that save measurable time. Prepare a short plan for learning the tools, assessing workflow health, and choosing an initial improvement with the Director of OOIA.

  • Build an automation project walkthrough

    Prepare a diagram and brief account of a workflow you built or a clearly labeled practice example. Show the manual process, platform choice, routing or approvals, monitoring, troubleshooting, and any measured results.

  • Rehearse an integration design exercise

    Sketch a hypothetical ERP-to-CRM or document-routing flow using an API, webhook, and JSON. Explain connector choice, data mapping, error handling, and how the integration would remain maintainable as tools change.

  • Show Python and operational-data evidence

    Prepare a small, sanitized code sample or design showing an API call, file processing, data cleaning, and error handling. Explain how clean field or departmental data would feed workflows and the central infrastructure team—not how you would manage that infrastructure.

  • Prepare an AI workflow evaluation

    Outline a document-extraction or summarization workflow with a sample prompt, test cases, human review points, and a way to track output quality, usage, and cost. Note how you would handle access to internal systems and sensitive data responsibly.

  • Draft a non-technical rollout guide

    Create a one-page example guide covering what a workflow does, how colleagues use it, common failure steps, and when to seek help. Be ready to explain how you would support adoption across departments.

  • Write targeted questions for OOIA

    Ask which existing automations need attention first, how the Director sets priorities, which enterprise tools are changing, and how the team measures time saved, workflow health, and responsible AI use.

AI-generated from the job information · Prepared Sep 30, 2026 (UTC)Useful preparation, not a guarantee of eligibility or an offer.

Availability last checked: Nov 4, 2026. Status can change after a check; confirm on the employer’s website. Report an issue · Our checking policy

KEEP EXPLORING

Similar AI jobs

Related skills and specializations in United States. Matched to this role, not your profile.

Explore more jobs
Finding similar opportunities…