From marketing student to product: a 90-day plan for non-IT students
· buildtolaunch
You study marketing, communications or business, and you keep hearing that "product" is where the interesting work is. This guide is for students with no computer science background who want to move toward product roles: what transfers, what is missing, and a 90-day plan to close the gap with real work. It is part of the full guide for non-IT students in the AI era (in Vietnamese).
Short answer
Marketing students already have half of what product teams need: customer insight, positioning, messaging and a feel for what makes people act. The missing half is evidence that you can define a problem, get something built, and learn from real users. Build and launch one small product with AI tools, write up what you learned, and use it as your case study when you apply.
What a marketing student already brings
Product work is about deciding what to build and why. Several things you practise already map onto it.
- Customer research. Surveys, interviews and persona work are the same muscle as product discovery.
- Positioning and messaging. Explaining who a product is for and why it matters is a core product skill.
- Funnels and metrics. If you can read a campaign dashboard, you can read a product dashboard.
- Experiments. A/B tests on ads or emails are small versions of product experiments.
What you probably lack is contact with building: writing a clear spec, making trade-offs when time is short, and seeing a real person struggle with something you made.
Which roles to aim at
"Product" is a family of jobs, not one. Titles vary by company, so read the job description rather than the title.
| Role family | What it focuses on | Good fit if you like |
|---|---|---|
| Product manager or product owner | Deciding what gets built and in what order | Prioritising, working with developers and designers |
| Product marketing | Positioning and launching products | Messaging, research, go-to-market |
| Growth or lifecycle roles | Improving sign-ups, activation and retention | Metrics, experiments |
| Product operations or project roles | Keeping the product process running | Organising, coordinating |
For entry-level or intern paths into product management specifically, see the Vietnamese guide to Product Manager and Product Owner internships without an IT degree.
The 90-day plan
Weeks 1 to 2: pick a real problem. Choose something you see around you: students splitting rent, a club tracking members, small shops answering the same questions daily. Talk to five people who have the problem. Write down what they actually do today, not what they say they want.
Weeks 3 to 5: build a first version with AI. You do not need to write code. Tools such as Lovable or Google AI Studio let you describe an app in words and get a working version you can share by link. If you have not used them, the free courses at /courses include material from Lovable and Google. Keep the first version small: one problem, one flow.
Weeks 6 to 8: put it in front of users. Share the link with 20 to 30 people who have the problem. Watch a few of them use it without helping. Note where they get stuck. This is the part most applicants skip, and it is what hiring managers want to hear about.
Weeks 9 to 10: improve one thing and measure it. Pick the biggest problem you saw, change it, and see whether it helped. Even small numbers (for example how many people completed the main task before and after) show product thinking.
Weeks 11 to 12: launch publicly and write it up. Post it somewhere people can react, such as the Launch League, then write a one-page case study.
What to put in the case study
Keep it to one page. Hiring managers read quickly.
- The problem and who has it (two sentences).
- What you learned from users (three bullets, with what surprised you).
- What you built and why you left things out (the trade-offs).
- What happened (users, completions, feedback) and what you would do next.
- A link they can open and try.
Your tools matter less than your decisions. If AI wrote most of the code, say so plainly and focus on what you chose, tested and changed.
How to talk about it in interviews
Describe your work in the order a product team thinks: problem, evidence, decision, result, lesson. Be ready for two questions: "What would you do differently?" and "What did users do that you did not expect?" A real answer to either is more convincing than a polished one. For more on what employers look for, see AI skills employers want from non-tech students and how to build a marketing portfolio with no experience.
Where buildtolaunch fits
buildtolaunch is free and open to students of any major, and you do not need to code to start. You can learn tools through 70+ free courses, practise with the AI tutor in Practice, build in a Space with an AI teammate, and post your launch to the Launch League (it resets every Monday). The opportunities page lists hackathons, competitions and programs for students, which are useful places to test a product idea with a team.
Back to the full guide for non-IT students for the wider picture on skills, portfolios and jobs.
FAQ
Can a marketing student become a product manager without a technical degree?
Yes, many product roles do not require a computer science degree, though requirements vary by company and role. What helps is evidence: a product you defined, built with available tools and tested with real users. Pair it with a clear case study and you give a hiring manager something concrete to discuss.
Do I need to learn to code first?
Not to start. AI app builders let you create a working product by describing it in plain language. Learn enough to talk with developers and to judge whether something is feasible, but spend most of your time on user problems and decisions, which are the core of the role.
What is the difference between product marketing and product management?
Product marketing focuses on positioning, messaging and launching a product to the right audience. Product management focuses on deciding what the product should do and in what order it gets built. Titles overlap between companies, so read the responsibilities in each job description.
How do I get product experience as a student?
Build and launch your own small product, join a student project or hackathon team where you own the "what and why", or help a club or small business improve a tool they already use. Each gives you a story with a problem, a decision and a result.
What should I put on my CV for a product role?
One line per project in the format: what you built, for whom, with what result, and a link. Include numbers you can defend, such as number of users interviewed or people who completed the main task. Do not list tools alone.
How long does it take to build a portfolio piece?
A focused student can go from problem to a launched first version in a few weeks, alongside classes. The 90-day plan above leaves room for user testing and one round of improvement, which is what makes the project credible.