“Entry level” asks for experience. You have a degree and a portfolio, but the applications disappear. In a discussion from a new graduate without connections, responses ranged from networking to relocation and smaller firms. None is a magic trick. The underlying challenge is that an employer must imagine how you will help a live project, while most student portfolios show final concepts and very little of the work behind them.
Your first architecture job search needs two tracks: show credible evidence of production and learning, and build a targeted pipeline of firms. Do both before sending another hundred identical applications.
Diagnose where your search stops
Keep a simple log: date, firm, role, location, contact, materials sent, response, interview and next step. After roughly 20 well-matched applications, look for the failure point. No replies may mean weak targeting, unclear first page, missing work authorisation information or a portfolio the firm cannot open. Interviews without offers suggest a different issue: project explanations, software evidence, role fit or salary expectations.
Do not interpret silence from one firm as a verdict on your ability. Hiring can pause or the advert can attract many applicants. But do change something when the same stage fails repeatedly. If 50 targeted applications produce no conversation, ask two practitioners to review your CV and portfolio against actual adverts. Change one variable at a time so you can learn from the next ten applications.
Make the first two portfolio pages answer the employer’s questions
An employer wants to know what you can do on a team, how you think and whether you understand the difference between a concept and a deliverable. Put your strongest relevant project first. On each selected project, state whether it is academic, competition or professional; your exact contribution; the tools used; one constraint; one revision; and the output you checked.
For a student housing project, do not show only a rendering. Include a plan that can be read, a section through a difficult interface and a short note: “I revised the circulation after testing an accessible route; the section shows the resulting level change.” If the accessibility check is incomplete, say so. The point is to demonstrate a habit of checking rather than imply a fictional building was approved.
The AIA’s interviews with hiring managers emphasise clear, shareable PDF portfolios and specific interest in a firm. Use a small file that opens easily and has legible labels. Keep a longer version ready for interviews, but let the first version make the case quickly.
Convert coursework into usable evidence
No professional experience does not mean no evidence. A measured survey, material study, model revision, group coordination or construction exercise can show useful skills. Label the context honestly. Explain what a tutor or peer challenged and what you changed. Employers know student work is not the same as a commissioned project; they still value learning, precision and teamwork.
If your portfolio lacks technical evidence, make a short, clearly fictional exercise. Draw one small detail, list the assumptions and ask a practitioner to critique it. Do not claim code compliance without a jurisdiction-specific check. Include the corrected version and what you learned. That is more informative than adding another atmospheric image.
For a visual role, show composition and fidelity to the underlying model. For a documentation role, show drawing clarity and controlled revisions. Tailor the first three pages to the role instead of changing the entire portfolio for every application.
Build a firm list beyond the biggest names
Start with three groups: firms advertising entry-level roles; firms doing work similar to your strongest project; and smaller studios in locations you can realistically work. Find them through specialist architecture jobs on jobs.archi, professional directories, project credits, school alumni and local practice networks. Check that each firm is active and has a legitimate contact route.
Record why each firm interests you. A small practice may have no open advert but may respond to a concise, relevant speculative email. Do not mass-mail every office in a city. Ten informed messages with a fitting portfolio are more useful than 200 emails that say only “I am passionate about architecture.”
Ask alumni and former tutors for a short conversation about their work rather than a job immediately. A specific question—”How does your team train graduates on construction documentation?”—is easier to answer and can reveal whether your target is realistic.
A cold email that respects the reader’s time
Use a short subject naming the role or project type. In the body, say who you are, why this firm’s work connects to one of your projects, what evidence you can show and what action you ask for. Link or attach the requested PDF in the format the firm accepts.
For example: “I am a recent architecture graduate seeking a junior role in adaptive reuse. Your published library project made me interested in how your team handles existing fabric. Pages 2–4 of my portfolio show a measured survey and the revisions it prompted. If your team expects to recruit this season, could I send a short application?”
Use the example as a structure, not as a claim about a real firm. Check the recipient’s name and the firm’s actual work. Follow up once after a reasonable interval; if there is no reply, move on. Harassing a small office will not improve your chance.
Prepare for the first interview as a project review
Choose two projects. For each, practise a two-minute explanation: brief, your role, one decision, one mistake or revision, and what you would check before construction. Be ready to open the drawing that supports the story. If a tool is listed on your CV, describe one task you completed with it and where you still need supervision.
Ask what the first assignment would be, who would review it and how the firm develops graduates. A first job is also an apprenticeship. A vague promise of “great exposure” is less useful than a named reviewer and an example of feedback.
Our earlier article on finding a first architecture job covers general routes. This guide addresses the no-experience loop with portfolio evidence, search diagnosis and outreach.
What to do after 50 applications without an offer
Separate the log into stages. If you receive no interviews, narrow the target and rebuild the opening pages. If you receive interviews but no second stage, practise explaining your role and ask for feedback when appropriate. If you reach final rounds, compare fit, availability, location and work authorisation; the problem may not be your portfolio.
Consider short paid work or a structured internship if it provides real supervision and a portfolio outcome you may legally share. Verify pay, scope, worker rights and licensing experience rules locally. Do not accept an indefinite unpaid “trial” simply to obtain a line on a CV. A small commission can help, but only if its responsibilities and safety are appropriate for your qualification level.
Protect your energy. Set a weekly target for quality applications, learning and rest. Endless refreshing of listings can feel productive while avoiding the harder task of improving evidence and asking for feedback.
A seven-day reset if your search feels stuck
On day one, choose one role family and location. Day two: collect five recent adverts and highlight the deliverables they share. Day three: rewrite the first page of your CV around those deliverables. Day four: replace one weak portfolio spread with a page showing process and a checked drawing. Day five: request blunt feedback from a practitioner or tutor. Day six: send three tailored applications or outreach messages. Day seven: review what changed and rest. The exact days are flexible; the point is to finish one measurable improvement before sending another batch.
Keep a copy of the earlier version. If response rates improve, you will know what helped. If they do not, seek another critique rather than assuming that one revision must work. Do not spend weeks polishing typography while the basic mismatch between your work and the vacancy remains.
FAQ: Should I apply when a junior role asks for one or two years of experience?
If the core work fits and you can show credible evidence, applying can be reasonable. Be honest about paid experience and explain the relevant student or internship work. Do not imply you meet a legal or licensing requirement that you do not.
FAQ: Are small firms easier to enter?
Some may be open to a direct conversation; others cannot spare time to train. Judge each firm’s work, capacity and supervision. Size alone is not a hiring strategy.
The takeaway
Break the no-experience loop by showing how you learn and produce, not by claiming experience you lack. Keep a small application log, target firms deliberately, make a readable portfolio and change your approach at the stage where the search actually stalls.
The post No Experience, No Architecture Job? Build Evidence Firms Can Actually Review first appeared on jobs.archi.