Energy and performance software can produce a persuasive graph in minutes. Employers need to know whether you understand what went into it, what the result can support and what decision changed because of it. That is the difference between a useful building-performance specialist and a portfolio of colourful outputs.
ASHRAE’s description of its Building Energy Modeling Professional certification covers modelling new and existing buildings, interpreting results and evaluating options. The certification has experience requirements; it is not an entry-level shortcut. It does show the breadth of the discipline.
Start with a design question
Choose one decision from a real or clearly labelled hypothetical project: glazing ratio, shading depth, orientation, envelope improvement or ventilation strategy. State the climate, occupancy assumption and comparison you want to make. If you do not know the inputs, mark them as assumptions rather than pretending the model is precise.
Run or review a simple comparison with a qualified colleague. Record what changed and what remained constant. A model that changes ten inputs at once cannot tell the team which decision produced the result.
Make uncertainty visible
A performance estimate can be sensitive to occupancy, equipment, weather file, operation schedule, system assumptions and construction quality. Include a short sensitivity note: “If occupancy doubles, does the preferred option still make sense?” Do not turn a concept-stage study into a promised operating cost.
When presenting the result, show the design consequence in one sentence: “The added shading reduced the modelled peak solar gain in this scenario but affected the winter daylight target.” Replace that with your actual finding and measure. The result matters because the team can act on it.
Build a career sample that can be checked
Create a three-page case: question and assumptions; alternatives and method; conclusion and limitations. State your role, the reviewer and what was implemented, if anything. If you used a sample model for learning, label it as an exercise. Employers can learn more from your honesty about limits than from a perfect-looking chart.
Read job descriptions for the real scope
“Building performance” can mean early design analysis, code compliance, certification support, energy modelling, post-occupancy evaluation or sustainability coordination. Ask what tools the team uses, who validates models, what standards apply and how analysis enters design meetings. Some roles are primarily technical; others require strong facilitation and communication.
A portfolio page that proves analysis mattered
Choose one design question, such as whether deeper shading helps a west-facing room without making it too dark. Show the baseline option, the alternatives, assumptions about climate and use, the metric you compared and the design decision. State where the model is approximate and what would need more detailed verification. If you never tested the alternatives on a live project, label the page as an independent exercise.
Avoid a page made only of colourful simulation images. Explain the causal chain in plain words: “We changed this parameter; this result moved; the team accepted this tradeoff because of this project constraint.” A reviewer can then assess your judgement rather than the software’s graphics. Where a model’s precision exceeds the quality of its inputs, say so. Being honest about uncertainty is part of technical competence.
Read each vacancy carefully. A performance consultant may need detailed modelling and certification work; an architect embedded in a design team may need to ask better early-stage questions and translate results. Build the sample that matches the role, and ask how the employer validates assumptions and checks models.
Your architecture background is an asset when you connect assumptions, evidence and decisions so the building can improve for reasons the team understands.
Compare options without hiding the inputs
Build a small test with one variable: two shading depths, two glazing arrangements or two insulation approaches. Keep occupancy, weather file and other assumptions fixed, and state why you chose them. Show the result alongside a limitation: a concept model may compare options but cannot predict the final building’s utility bill. If the preferred option changes under a plausible alternative schedule, tell the design team before recommending it.
Translate the output into a decision record. What was the question, what alternatives were tested, what metric mattered, who reviewed the analysis and what did the team do? If nothing changed, say so; perhaps the study ruled out an apparently attractive option. That is still useful evidence. It demonstrates that the analysis served a project decision rather than decorating a presentation.
For job searches, distinguish a role that runs models from one that uses models to guide design. The first may demand specific technical methods and validation; the second may place more weight on framing questions and communicating trade-offs. Ask how the employer checks model quality and who is accountable when an assumption proves wrong. A thoughtful answer tells you whether you will learn rigorous practice or simply produce attractive charts.
Browse current architecture jobs on Jobs.archi and read our guide to the gap between architecture school and practice for a related next step.
The post From Architecture Studio to Building Performance: Show the Decision, Not the Model first appeared on jobs.archi.