Rpa Developer

We need to output HTML fragment only, with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarized away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Must not include sections with filler like "commensurate with experience". Pay and Benefits: posting includes pay range and benefits details, so we should include Pay and Benefits sections? The instruction: "Prefer a few substantive sections over many thin ones." Also "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states Pay And Benefits with pay range and benefits list. So we can include a Pay section (maybe combine Pay and Benefits? The headings list includes Pay and Benefits separate. We could make a Pay section with pay range, and a Benefits section with benefits list. Or combine into one Benefits? But they said use headings for those categories. We'll create separate sections if content exists. Schedule: posting mentions "Workplace Type This is a fully onsite position in Oklahoma City,OK." Also maybe schedule not given. No explicit schedule like full-time, part-time, shift. So we should not create Schedule section because no specific schedule content. About the role: The description includes overview: "Our client is looking for a hands-on individual contributor for a contract role focused on building and supporting enterprise automation." That's about the role. We'll put that in About the role. Responsibilities: The "Immediate Priorities Are" list: Build new automations, stabilize/troubleshoot, use Cursor daily, work independently while partnering... That's responsibilities. Requirements: The "Target contract profile" includes hands-on individual contributor, 3+ years experience, development experience, owning work across lifecycle, able to enter environment, etc. Also "UiPath — non-negotiable" etc. That's requirements. Qualifications: Might overlap with requirements. But we can separate: maybe "Skills" for technical skills list. The posting includes "Skills uipath, Sql, robotic process automation" and "Additional Skills & Qualifications". We'll treat Skills section for technical skills list. Qualifications maybe for experience level etc. But we need to avoid duplication. Let's decide: - About the role: overview paragraph. - Responsibilities: bullet list of immediate priorities. - Requirements: bullet list of target contract profile and UiPath non-negotiable items (maybe combine). - Qualifications: maybe "Experience Level Expert Level" and "Job Type & Location" (Contract position based out of Oklahoma City, OK). Also "Supporting technical capabilities" etc? Actually those are skills. We'll treat "Skills" for technical skills list (UiPath, Sql, RPA, etc.) and "Additional Skills & Qualifications" for supporting capabilities. - Benefits: list of benefits. - Pay: pay range. We must not include boilerplate like About TEKsystems etc. Remove all that. Also remove duplicated lines: there are two "About TEKsystems" sections; we drop them. We must preserve all substantive information: need to include details like "Uses Cursor daily in a professional development workflow, not merely as an occasional autocomplete tool." etc. That's part of Requirements or Skills? It's under "Cursor — core requirement". We'll include that in Requirements or maybe a separate section? But we have only allowed headings list; we could put under Requirements or Skills. Since it's a core requirement, we can put under Requirements. We need to ensure we don't invent or summarize away detail. Must keep specifics like "Strong SQL and database skills required." etc. Let's extract substantive content: From description: - Overview: "Our client is looking for a hands-on individual contributor for a contract role focused on building and supporting enterprise automation. The strongest candidates will have deep UiPath delivery experience, daily professional use of Cursor for software development, and the judgment to use AI-assisted development without weakening testing, security, maintainability, or production ownership." - Immediate Priorities Are: * Build new, reliable UiPath automations from validated business requirements through production deployment. * Stabilize, troubleshoot, and improve existing production bots. * Use Cursor every day to accelerate development, debugging, refactoring, testing, documentation, and integration work. * Work independently while partnering effectively with business process owners, business analysts, IT teams, and security or infrastructure partners. - Target contract profile: * Hands-on individual contributor; focused on delivery rather than primarily managerial. * Typically three or more years in automation development, software development, systems integration, or a related field. * Needs development experience. * Comfortable owning work across discovery, design, development, testing, release, documentation, production support, and continuous improvement. * Able to enter an existing enterprise environment, learn its standards quickly, and deliver with limited supervision. * Equivalent practical experience is more important than a specific degree or title. - UiPath — non-negotiable: * Strong development experience with UiPath Studio and UiPath Orchestrator. * Experience designing both attended and unattended automations. * Hands-on knowledge of workflows, queues, triggers, retries, exception handling, logging, notifications, testing, deployment, and monitoring. * Experience with Orchestrator environments, service accounts, secure credentials, permissions, assets, and production configuration. * Ability to build maintainable automations using reusable components, libraries, templates, and consistent development standards. * Experience with UiPath REFramework or a comparable enterprise automation framework. * Proven delivery from process assessment and requirements clarification through go-live and production support. * Ability to analyze bot failures, read logs, identify root causes, and implement durable corrective actions rather than one-off fixes. * Strong SQL and database skills required. - Cursor — core requirement: * Uses Cursor daily in a professional development workflow, not merely as an occasional autocomplete tool. * Uses Cursor for repository navigation, code or workflow scaffolding, refactoring, debugging, test creation, documentation, and integration work. * Can provide effective context and instructions to Cursor, validate generated output, and revise it to meet project standards. * Maintains disciplined engineering practices when using Cursor: code review, testing, security review, version control, documentation, and human accountability for production changes. * Understands how to use AI assistance safely around proprietary code, credentials, sensitive data, and enterprise integrations. * Can explain a specific example where Cursor materially improved delivery speed or quality while preserving reliability. - Skills uipath, Sql, robotic process automation (Top Skills Details uipath,Sql,robotic process automation) - Additional Skills & Qualifications Supporting technical capabilities: * Integrations with SQL Server, APIs, enterprise applications, structured and unstructured files, and data platforms such as Databricks. * Familiarity with AI-assisted development, document processing, data matching, validation, and human-in-the-loop workflows. * Working knowledge of source control, work-item tracking, release practices, and collaboration tools such as Azure DevOps. * Ability to design for security, data quality, auditability, observability, scalability, maintainability, and supportability. - Useful professional characteristics: * Takes ownership of outcomes and follows work through to production stability. * Strong analytical troubleshooting and root-cause problem solving. * Business-minded technical judgment; knows when to automate, when not to automate, and when to escalate risk. * Communicates clearly with nontechnical stakeholders and can explain tradeoffs, constraints, risks, and dependencies. * Works well with a dedicated business analyst and can add technical feasibility, integration, estimation, and readiness guidance. * Detail-oriented and operationally reliable, especially when handling exceptions, credentials, data quality, and release controls. * Balances fast delivery with long-term maintainability and technical debt reduction. * Comfortable managing multiple priorities, working independently, and asking for guidance when scope or risk warrants it. * Collaborative, adaptable, and committed to continuous learning and practical innovation. - Experience Level Expert Level - Job Type & Location: This is a Contract position based out of Oklahoma City, OK. - Pay And Benefits: * Pay range: $50.00 - $75.00/hr. * Individual compensation offered ... (we can keep that sentence) * Benefits list: Medical, dental & vision; Critical Illness, Accident, and Hospital; 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available; Life Insurance (Voluntary Life & AD&D for the employee and dependents); Short and long-term disability; Health Spending Account (HSA); Transportation benefits; Employee Assistance Program; Time Off/Leave (PTO, Vacation or Sick Leave). - Workplace Type: This is a fully onsite position in Oklahoma City,OK. (Could be part of Schedule? but we don't have Schedule section; maybe we can include location in About the role or Requirements. But we already have location in Job Type & Location. We'll keep that. - Application Deadline: Sep 17, 2026. This is application instruction; we should remove per instruction: remove application instructions. So drop. - About TEKsystems etc: remove. Now we need to output HTML fragment with headings

for each section we include. We need to decide which sections to include: - About the role (overview) - Responsibilities (Immediate Priorities) - Requirements (Target contract profile + UiPath non-negotiable + Cursor core requirement) - Skills (Top Skills + Additional Skills & Qualifications + Useful professional characteristics? Actually those are more like qualifications/characteristics. Could be under Qualifications. But we have a Qualifications heading allowed. We could put Experience Level Expert Level and maybe professional characteristics there. But we also have Skills heading for technical skills list. Let's allocate: * Skills: technical skills list (UiPath, Sql, RPA, integrations, AI-assisted development, source control, Azure DevOps, design for security etc.) * Qualifications: Experience Level Expert Level, Job Type & Location (Contract position based out of Oklahoma City, OK), plus maybe useful professional characteristics (ownership, troubleshooting, judgment, communication, detail-oriented, etc.) These are more like qualifications/attributes. - Benefits: list of benefits. - Pay: pay range and compensation note. We should not include Schedule. We must not repeat job title as heading. We must not include filler like "commensurate with experience". Not present. Now produce HTML. Structure:

About the role

Our client is looking for a hands-on individual contributor for a contract role focused on building and supporting enterprise automation. The strongest candidates will have deep UiPath delivery experience, daily professional use of Cursor for software development, and the judgment to use AI-assisted development without weakening testing, security, maintainability, or production ownership.

Responsibilities

• Build new, reliable UiPath automations from validated business requirements through production deployment.
• Stabilize, troubleshoot, and improve existing production bots.
• Use Cursor every day to accelerate development, debugging, refactoring, testing, documentation, and integration work.
• Work independently while partnering effectively with business process owners, business analysts, IT teams, and security or infrastructure partners.

Requirements

• Hands-on individual contributor; focused on delivery rather than primarily managerial.
• Typically three or more years in automation development, software development, systems integration, or a related field.
• Needs development experience.
• Comfortable owning work across discovery, design, development, testing, release, documentation, production support, and continuous improvement.
• Able to enter an existing enterprise environment, learn its standards quickly, and deliver with limited supervision.
• Equivalent practical experience is more important than a specific degree or title.
• Strong development experience with UiPath Studio and UiPath Orchestrator