Architectural Assistant Part I

A Part I CV should be clear, honest and easy to scan. You are not expected to sound like a Project Architect — you need potential, care and relevant evidence. Put practical details near the top: name and contact, location and availability, education and graduation date, portfolio link, and software with honest confidence levels. Practices usually scan whether you are available, whether the portfolio opens, whether software matches and whether the work shows enough promise.

Academic projects can be strong evidence if you explain them clearly. Mention the brief, scale, design idea, tools used and what the project proves about your thinking. Avoid long abstract descriptions — a practice wants to know whether you can communicate, learn, draw, think and contribute. Keep the opening useful and let the portfolio do the visual work.

Architectural assistant pay varies by location, practice type, project exposure, software skill, experience and market conditions. Factors include Part I, Part II or equivalent level; London, regional UK or international location; sector, project scale and practice size; Revit, BIM, technical and coordination experience; live project responsibility and client exposure; and market demand when you apply. Prepare a realistic range rather than guessing late in the process.

If you list Revit, Rhino, SketchUp, AutoCAD, Adobe, Enscape or Grasshopper, be honest about how you have used them. A simple project example is more useful than a long software list with no context. Connect the CV to the portfolio — if you claim interest in housing, public space, retrofit or computational design, the portfolio should support that claim.

Common mistakes include trying to sound senior too early; using an overdesigned CV that hides key information; forgetting a working portfolio link; listing every software tool without evidence; and sending the same application without reading the job advert properly.

Early-career cover letters should show potential, evidence and care without pretending you have done everything already. Name the role and why it interests you; point to relevant project, sector, software or stage experience; keep the tone professional and direct; and finish with a simple next step. Do not overclaim — say what you have done, what you are learning and why the role makes sense.