Skip to main content

Toshiba Global Commerce Solutions - External

AI Software Engineering Intern

Durham, NCinternshipinternAdded today

About this role

Fall 2026 internship (20-30 hrs/week, Sept 14–Dec 4) designing and building AI-driven development processes and tools at Toshiba Global Commerce Solutions in Durham, NC. You'll help define a new POD operating model for feature development, create an AI skill for business requirements documents, and enhance existing AI tools based on team feedback.

What you'll do

  • Design and document a new AI-driven 'POD' operating model for end-to-end feature development with architects, BAs, and product managers
  • Identify and map human decision points within the AI-driven development process
  • Build and pilot a BRD Creation skill for the AI Dev Portal with cross-functional validation
  • Gather feedback from teams on existing BRD practices and consolidate into standardized documentation
  • Analyze usage data and implement enhancements to the existing BRD Reviewer skill
  • Participate in agile development sprints and collaborate with stakeholders across multiple teams

What they're looking for

  • AI systems development
  • Prompt engineering
  • Large language models (LLM)
  • Retrieval-augmented generation (RAG)
  • Vector databases
  • Analytical problem-solving
  • Stakeholder communication and synthesis
  • Agile software development
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Toshiba Global Commerce Solutions - External

Toshiba Global Commerce Solutions builds AI-enhanced retail applications and user interfaces that integrate with retail hardware. The company is hiring mobile developers and UI/UX engineers to create innovative, AI-driven customer experiences.

View all jobs at Toshiba Global Commerce Solutions - External

Likely interview questions

  • Walk us through a time you designed or built an AI system—what was your approach to prompt engineering or working with LLMs?
  • How would you handle identifying the critical human decision points in an otherwise automated process?