An architecture CV and portfolio need to answer one simple question for employers: how can this person actually contribute to a real project team? Just listing qualifications, software skills, and finished projects doesn’t cut it. Practices want to see how you approach design decisions, how you work through problems, and where your experience actually fits into the professional process.
Plenty of applicants have strong academic work or solid experience but struggle to explain their own role clearly. The applications that stand out connect creativity with practical awareness showing not just what was designed, but why those decisions were made and how the ideas actually turned into workable proposals.
It’s worth remembering the CV and portfolio do different jobs, even though they’re usually submitted together. The CV gives a quick, structured overview of your background and skills; the portfolio demonstrates how you think and design. Treating them as separate documents with separate goals usually produces a stronger application.
What UK Architecture Practices Are Actually Looking For
An architecture application is more than a folder of drawings or a list of academic achievements. It gives a practice an early read on how you think as a designer and how well you can communicate in a professional setting.
A portfolio packed with polished renders might show off your visual skills, but it often leaves the important questions unanswered. How did the concept actually develop? What constraints shaped the design? How were the technical or planning considerations handled?
Practices are generally looking for evidence that you understand architecture as a process, not just a final image. The strongest applications show a clear progression from research and concept development through to technical decisions and delivery.
Using the RIBA Plan of Work to frame your experience
The RIBA Plan of Work can help you describe your experience in a way that actually reflects professional practice. Instead of just writing that you “contributed to a housing project,” explain the stage you were involved in and what that involvement looked like.
For instance, your experience might include helping with concept proposals, preparing planning documents, developing BIM models, producing technical drawings, researching materials, or supporting construction information.
Graduates and junior applicants aren’t expected to have worked across every stage of a project. But showing that you understand how projects move from early ideas toward delivery goes a long way toward demonstrating you’re ready for professional work.
It also helps to be specific rather than vague. Saying you “assisted with a residential scheme” tells an employer very little. Saying you helped develop massing options during the concept stage, produced planning drawings for a submission, or coordinated design changes following client feedback shows exactly what you did. Even short placements or academic live projects can be described this way, making a graduate CV read more like the work of someone who understands how a practice operates.
Turning Your Experience Into a Focused CV
One of the most common problems with architecture CVs is trying to cram in everything. A long list of university projects, software programmes, and achievements often makes it harder for an employer to spot what actually matters.
A stronger CV picks out information that supports the specific role you’re going for. Each project entry should explain your contribution, not just name the building type.
Worth including:
- The scale and purpose of the project
- Your individual responsibilities
- The design or technical challenges involved
- The tools and methods you used
- How the work developed or turned out
Software skills land better when they’re tied to actual tasks too. Writing “Revit, AutoCAD, Rhino, Adobe Creative Suite” shows familiarity, but it doesn’t say much about capability. Explaining that you used Revit for BIM modelling, AutoCAD for technical drawings, Rhino for design exploration, or Adobe software for presentation work gives real evidence of how you’ve actually applied those tools.
It’s not unusual for applicants to search for the best architecture cv writing service in UK when they’re struggling to strike this balance, but understanding what practices are actually looking for is usually more valuable in the long run than outsourcing the document entirely the CV should still sound like you, and reflect your own understanding of your work.
Layout matters more than people assume, too. Architecture CVs are usually expected to look considered, since presentation is part of the job itself though overdesigning the document can be just as distracting as a plain one. A clean structure, clear hierarchy, and consistent typography usually communicate professionalism better than heavy styling. Keeping the CV to one or two pages forces you to prioritise what actually matters.
Building a Portfolio That Shows How You Think
A strong architecture portfolio doesn’t just present finished visuals it reveals the thinking behind the work.
A reviewer should be able to follow the development of a project just by moving through the pages. Early research, sketches, diagrams, design testing, technical exploration, and final outcomes should read as a clear narrative rather than a stack of disconnected images.
The best portfolios make the design process visible. They show how an idea evolved, what challenges shaped the decisions along the way, and how different factors influenced the final proposal.
It’s also worth thinking about pacing across the portfolio as a whole. Opening with your strongest, most complete piece of work sets the tone, but the projects that follow don’t all need to be full case studies a shorter piece showing a specific skill, like a construction detail or material study, can round out the picture. What matters is that every page earns its place.
Balancing creative thinking with technical understanding
Practices value creativity, but they also need confidence that you understand the practical side of the job.
Including technical drawings, environmental analysis, material studies, construction details, or regulatory considerations can show a broader grasp of architectural work.
That doesn’t mean bolting on technical pages just to look professional, though. Every element should serve the project story a construction detail earns its place when it explains a design decision, and an environmental strategy is stronger when it’s clearly tied to the proposal.
When talking about UK regulations, it’s worth being honest about your actual level of experience. Rather than overstating your expertise, explain where your projects genuinely engaged with issues like accessibility, fire safety, sustainability, energy performance, or planning constraints.
Ultimately, both the CV and the portfolio work toward the same goal: giving a practice enough confidence in how you think and work that they want to meet you in person. That isn’t about producing the most polished documents possible it’s about being clear, honest, and specific about what you’ve actually done, and letting that speak for itself.