About the Role
Report authoring is one of the highest-effort, lowest-leverage activities our scientific and operational teams do. This role will be a small intern team that will spend 10 weeks experimenting – cheaply and quickly – with how modern AI tooling (LLMs, OCR, and adjacent systems) could move our report authors from blank templates to populated first drafts that humans then review, edit, and finalize. The project starts from a blank canvas. The team will focus on one line of business and one document type, work directly with report authors to understand the current workflow, and deliver a working prototype plus an honest recommendation on whether to invest further. The project will be shaped to align with the team's strengths and interests – what you see here is the starting point, not the finish line.
What You'll Do Here
- Building and breaking small prototypes – trying things, throwing them out, trying again
- Working with real document content (templates, historical reports, source data) to figure out what's possible
- Wiring together LLM APIs, OCR tooling, and whatever else the problem calls for
- Pair-programming and reviewing each other's work; you won't be siloed
- Sitting in on user interviews with report authors so you understand who you're building for
- Presenting what you've built (and what hasn't worked) to stakeholders, including senior leadership
What You'll Need to Succeed
High School Seniors through rising college Juniors with a serious interest in computer science or software engineering. We are not looking for a long resume – we are looking for curiosity, the habit of building things, and comfort sitting with ambiguity. If you've taught yourself something outside of class, broken and fixed your own code, or have opinions about how software should be built, we want to hear from you. You should apply even if you don't tick every box. If the project sounds exciting and you can point to one or two things you've built or figured out on your own, that's enough to start a conversation.
In lieu of a Cover Letter
Please choose 2 of the 4 questions below and answer each in 30–60 words.
We're looking for answers that sound like you. Specifics – real people, actual questions, and genuine moments – matter more than polish. The questions themselves are viable parts of your answer; you don't need to repeat them back. Short and honest beats long and impressive.
- Describe your personal approach to when you do or don't use AI.
- Describe a system – technical or otherwise – you use to keep yourself organized on a project, and what about it works for you.
- Describe a problem you noticed outside of school or work and decided to do something about. Focus on what made you notice it, not what you did about it. Include at least one detail that's specific to your situation.
- What's something you find yourself thinking about that most people you know don't?
Skills Required
- Be a High School Senior through a rising college Junior
- Serious interest in computer science or software engineering
- Curiosity and habit of building things; comfort with ambiguity
- Be able to point to one or two personal projects or things you've built
- Experience or familiarity with LLMs, LLM APIs, or OCR tooling
- Answer 2 application questions in 30-60 words each (choose 2 of 4)
