Career Dashboard
Current Target Role: AI Solutions Engineer
Original Time-to-Hire Estimate: 3–6 Months
Current Time-to-Hire Estimate: 2–5 Months
Confidence Level: High
Remaining Skill Gaps:
- Demonstrable AI project experience
- Cloud deployment experience
- Portfolio evidence
- Interview readiness
- End-to-end implementation experience
Progress Since Day 1:
✓ Created a structured learning roadmap
✓ Identified transferable experience from previous roles
✓ Established a target role and career direction
✓ Developed understanding of AI architecture patterns
✓ Shifted from learning-focused activities to project planning
Today’s Question
What makes a portfolio project valuable? At the end of my previous post, I committed to starting my first portfolio project.
At first, I assumed the difficult part would be building it. Instead, I discovered that the difficult part is deciding what to build.
The AI ecosystem contains an endless supply of project ideas. Chatbots, RAG systems, agents, copilots, document analyzers, recommendation engines, workflow automations, and countless combinations of them all seem like reasonable options.
The challenge isn’t finding ideas. The challenge is choosing the right one. The more I thought about it, the more I realized that selecting a portfolio project is not the same as selecting a learning project.
Those two goals may overlap, but they are not identical.
What I Worked On
Rather than diving directly into implementation, I spent time evaluating what I wanted Project 1 to accomplish. Initially, I was drawn toward ideas that seemed technically impressive. The temptation was to build something large, complex, and packed with features.
However, after reflecting on the role I’m pursuing, I began approaching the problem differently. If my goal is to become an AI Solutions Engineer, then the project should demonstrate skills that are relevant to that role.
That immediately changed the way I evaluated potential ideas. Instead of asking:
How advanced is this project?
I started asking:
What skills does this project demonstrate?
The answer to that question feels much more important.
What I Learned
One realization stood out this week. Portfolio projects are not simply demonstrations of technology. They are demonstrations of judgment.
A hiring manager reviewing a project is not only evaluating whether it works. They are also evaluating the decisions behind it.
Can the candidate identify a meaningful business problem?
Can they define realistic requirements?
Can they make sensible technology choices?
Can they explain trade-offs?
Can they design a solution that balances complexity with practicality?
The more I think about it, the more I believe these questions are highly relevant to solution-oriented roles. Building an overly complicated project may demonstrate technical curiosity, but it does not necessarily demonstrate solution thinking.
In fact, complexity can sometimes hide poor decision-making. A simpler project that solves a clear problem may be far more valuable. That perspective has significantly changed how I’m approaching Project 1.
Resources Reviewed
This week’s focus centered on project evaluation and portfolio strategy.
Documentation
- OpenAI Platform Documentation
- Google Cloud Vertex AI Documentation
- LangChain Documentation
Topics Explored
- Portfolio project selection
- Demonstrating technical capability
- Solution-oriented project design
- AI implementation patterns
- Business problem identification
Learning Focus
Understanding how portfolio projects support career positioning and communicate professional capability.
Progress Against Plan
The biggest outcome this week was clarity. A few weeks ago, I believed success meant learning as many AI concepts as possible.
Last week, I concluded that learning alone was insufficient. This week, I realized that building alone is not enough either.
What matters is building the right thing. A project should demonstrate the skills that employers are likely to evaluate.
It should tell a story.
It should create evidence.
Most importantly, it should help bridge the gap between existing experience and future opportunities.
That realization has helped narrow my focus considerably.
Strategy Changes
My original assumption was that portfolio projects should maximize technical complexity. I’m beginning to think the opposite may be true.
The best portfolio project may be one that clearly demonstrates problem-solving, architecture thinking, implementation capability, and business understanding without unnecessary complexity.
Going forward, I plan to evaluate project ideas using a simple framework:
- Does it solve a meaningful problem?
- Does it demonstrate relevant skills?
- Can it be completed within a reasonable timeframe?
- Can I clearly explain the design decisions?
- Does it align with my target role?
If the answer to those questions is yes, the project is probably worth building.
Next Steps
Over the next few days, I plan to narrow the scope of Project 1 and begin defining requirements.
My immediate goals are to identify:
- The problem being solved
- The target users
- The workflow
- The AI components involved
- The technologies required
Once those pieces become clear, implementation can begin.
Reflections
Throughout this journey, I’ve spent a considerable amount of time focusing on knowledge acquisition. More recently, I’ve shifted toward building. This week introduced another perspective.
Not all projects are equally valuable. The purpose of a portfolio project is not to prove that I can follow a tutorial or assemble technologies together. The purpose is to demonstrate how I think. A well-designed project can showcase technical skills, but it can also reveal problem-solving ability, decision-making, communication, and business awareness.
Those qualities are difficult to capture on a resume alone. As I begin planning Project 1, I’m finding that the project itself may be less important than the reasoning behind it. Learning helped me understand the landscape.
Building will help me demonstrate capability. Choosing the right project may be what connects those two things together.
