Product Definition Intern (AI Systems)

About this internship 

For most of its history, software engineering has been the work of translation. A person who understood a problem handed it to a person who could write code, and the second person turned that understanding into instructions a machine would follow. The instructions were the artifact. The understanding lived upstream and rarely survived the trip intact. 

That arrangement is ending. Software can now generate working code from a clear description of what it should do and why. The scarce skill is no longer writing the instructions. It is stating the intent precisely enough that the rest can be handed to a machine. This is what spec-driven development means, and it changes who is good at this work. 

Stating intent well is not a coding skill. It is the ability to understand a problem, and to understand your own understanding of it at one level above. To notice an assumption nobody made explicit. To find ambiguity in a sentence before it becomes a defect. To know what a request means and not only what it says. Philosophy, psychology, linguistics, law, and design train these habits as deliberately as computer science trains data structures. 

So, this internship is open to students from any field. We are interested in how you think, rather than the specific field you come from. 

What you would work on 

• Turn real business and technical problems into clear specifications a development system can act on. 
• Work on the part that comes before the code, namely what the software should do, for whom, and what would count as getting it right. 
• Collaborate with engineers, designers, and domain experts in an international team, working in English. 
• Use AI tools to move from intent to a working solution and learn where they help and where they fail. 
• Document the reasoning behind decisions so the thinking survives, not only the result. 

Who we are looking for 

We are not looking for a finished engineer. We are looking for a way of thinking. 

• A student in any Bachelor's or Master's program, in the humanities, social sciences, design, or a STEM (Science, Technology, Engineering, Mathematics) field. 
• The habit of asking what a problem actually is before reaching a solution. 
• Comfort with ambiguity, and the patience to make it precise. 
• An interest in how AI is changing the way software gets built. 
• A good level of written and spoken English. 

Helpful, but not required 

• Some experience building things in any medium, whether code, research design, structured argument, or written work. 
• Familiarity with AI or machine learning tools, or simple curiosity about them. 
• Experience explaining complex ideas to people who do not share your background. 

What we offer 

• Real projects with real impact, with engineers and mentors working alongside you. 
• A close look at how enterprise software is being rebuilt around intent rather than instructions. 
• An international and multidisciplinary environment. 
• Flexibility around the requirements of your studies. 
• Room to develop in a field that is being redefined right now. 

A note on what this is really about 

Software used to ask people to think like machines, step by step, in the order the machine required. That is the part that is ending. The work that matters now sits upstream of the code, in the clarity of what we are trying to build and why. If you are studying how people think, how language carries meaning, how arguments hold together, or how systems behave, you have been preparing for this without calling it that. We would like to hear from you. 

 --------------------- 

Relevant fields of study include, among many others 

• Philosophy, linguistics, or cognitive science 
• Psychology or the social sciences 
• Design, human-computer interaction, or communication 
• Computer science, software engineering, or data science 
• Mathematics, physics, or any engineering discipline 
• Any program that trains you to understand a problem before solving it