Junior AI concept designer

Angel•Provo, UT

1d•Onsite

About The Position

This role is the product manager for those tools, and the person who builds and maintains tools and apps for operations teams. You'll work with leaders to decide what gets built and in what order, write down what each tool needs to do, and then build it yourself using AI coding tools such as Claude Code. After launch you own the product: keep it running, keep its data safe, and improve it as needs change. Your first product will be the internal app that runs our Performance Stock Unit program. This is an entry-level role for someone with a technical background. You don't need years of experience. You do need to understand what the AI wrote for you, to think like an owner of a product and not only its builder, and to care about the details when the data is pay, equity or personal information. Done well, this work means non-technical teams get tools that work and keep working, leaders always know what's being built and when, and nothing we rely on depends on one person's memory of how it was made.

Requirements

A technical background: a degree, coursework, bootcamp or work experience in computer science, information systems, software development or a related field.
At least one working tool, app or automation you built with AI coding tools, such as Claude Code or Cursor, which you can show us and walk us through.
Working ability to read and explain code in at least one common language, such as JavaScript, TypeScript or Python.
Experience using Git and GitHub to save, track and review changes.
Basic understanding of how data is stored, who can see it, and how to keep passwords and keys out of code.
Experience gathering needs from non-technical people and turning them into a written plan, in a job, internship or project.

Nice To Haves

Up to 2 years of experience in product management, business systems analysis, software development or IT, including internships.
Experience maintaining a tool after launch: fixing bugs, handling requests and releasing updates.
Experience building for non-technical teams, such as People & Culture, Finance or Operations.
Experience connecting business tools through their APIs, such as Slack, Google Workspace or an HRIS.
Experience working with confidential information.
Familiarity with a project tracking tool and with writing user stories or requirements.
Familiarity with Angel, the Angel Guild, and our body of work (films, series, and other projects).

Responsibilities

Own the list of internal tools for Operations and People & Culture: what exists, who uses it, and what state it's in.
Gather requests from leaders, ask questions until the real need is clear, and write short, plain requirements for each one.
Keep a prioritized roadmap, agreed with the Chief Operating Officer and the Vice President of People and Culture.
Plan each release, test it with the people who will use it, and train them before it goes live.
Track how each tool is used and what it saves, and recommend what to improve, replace or retire.
Build internal apps, automations and dashboards for Operations and People & Culture, using AI coding tools alongside your own judgment.
Sit with the person who has the problem, ask questions until you understand it, and show a working first version quickly.
Connect the tools Angel already uses, such as Google Workspace, Slack and our HRIS, so information moves without retyping.
Recommend when to build, when to buy, and when a spreadsheet is enough.
Take over and maintain existing internal apps, starting with the Performance Stock Unit program app.
Test your work before others use it, and fix problems quickly when they appear.
Keep all code in Angel's shared code repository, with a clear history of what changed and why.
Write plain instructions for each tool, so someone else could run it or pick it up.
Handle pay, equity and personal information with complete discretion, and only inside approved systems.
Set up each tool so people see only what they are meant to see.
Follow Angel's information security and AI-use policies, and work with Engineering and IT on access, hosting and review.
Keep a simple, current list of requests, priorities and status that both teams can see.
Tell leaders early when something will take longer or can't be done the way they pictured it.
Teach Team Members to use what you build.
If you need an accommodation to do any of this, tell us and we'll work with you.