Paid Short-Term Contractor Role

AI Agent Engineering Intern

DarrylBots is exploring a focused summer project to turn a bespoke agent system into a safer, documented, transferable starter kit that another employee or contractor can learn from and extend.

StructureIndependent contractor
TimeUp to 10 hours per week
DurationApproximately 8 weeks
RateCAD 25 per hour

Project Mission

The mission is to help turn Aria from a bespoke agent into a transferable, documented, safer, employee-handoff-ready agent system.

  1. Understand how the current Aria and DarrylBots agent system works.
  2. Map repositories, scripts, prompts, memory files, cron jobs, tools, credentials boundaries, and runtime dependencies.
  3. Separate reusable agent patterns from personal data, production credentials, live-capital workflows, and private memory.
  4. Create a safer development version or starter kit that can be used for onboarding.
  5. Improve documentation, setup instructions, safety rules, and handoff materials.

Expected Responsibilities

System Mapping

Inventory relevant repositories, scripts, prompts, cron jobs, tools, memory files, and runtime dependencies. Produce an architecture map showing what is reusable and what is production-sensitive.

Portable Agent Development

Help build or document a clean development clone or starter kit that can run basic workflows without production secrets or private memory.

Safety And Access Model

Draft a permissions matrix for read-only, write-limited, external-action, financial, messaging, and production-critical tool categories.

Testing And Handoff

Create smoke tests, checklists, setup instructions, troubleshooting notes, and a final runbook another operator can follow.

Suggested 8-Week Plan

Week 1Orientation, safety rules, initial architecture sketch, and questions list.
Week 2Inventory tools, repos, memory, external integrations, and credentials boundaries.
Week 3Stand up or document a sandbox agent clone with mock or synthetic memory.
Week 4Extract reusable setup, prompts, workflows, and onboarding documentation.
Week 5Add smoke tests, health checks, and minimal regression checklists.
Week 6Write runbooks for setup, operation, troubleshooting, and access boundaries.
Week 7Demo the clone and starter kit, then fix gaps found during review.
Week 8Deliver final repo/docs package, handoff demo, and recommendation memo.

Access Boundaries

Initial Access May Include

  • Project documentation and redacted architecture notes.
  • A sandbox or starter repository.
  • Selected public or low-risk source materials.
  • A private GitHub repository with appropriate collaboration permissions.

Initial Access Should Not Include

  • Production credentials or private personal memory.
  • Banking, brokerage, crypto, Stripe, payment, or live-trading authority.
  • Private messages or personal email access.
  • Authority to spend money, open accounts, make purchases, or bind DarrylBots LLC.

Success Criteria

  1. A documented Aria / DarrylBots agent architecture and dependency map.
  2. A working or clearly specified sandbox/development agent clone that does not require production secrets.
  3. A reusable agent onboarding or starter kit.
  4. A permissions and safety model for future agent work.
  5. A final handoff runbook another employee or contractor can follow.

Contractor Notes

This is intended as a paid independent-contractor engagement, not an unpaid internship. Final terms, classification, tax paperwork, payment method, start date, and signatures should be confirmed before work begins.

This page is a role summary for discussion and onboarding. It is not a signed agreement or legal advice.

Questions can be sent to [email protected].