Applicant Guidance for Technical and Engineering Roles

This document consolidates common guidance provided to applicants who were not selected for a role. The intent is to clarify typical screening criteria and outline practical steps to strengthen future applications for reapplying with our team. 

Key principle: demonstrate capability through targeted learning, small projects, and a portfolio that reflects permit-ready, code-aware work.

This document covers screening considerations, portfolio development, BCIN planning, and expectations for entry-level consulting roles.

Did you apply to the right position?

If you’re a graduate of an engineering program, an Engineering Intern (EIT), or you want to become a licensed engineer, make sure you’re applying to an engineering stream. If you apply to a Technician/Technologist role, your application may be moved to a different stream. If your goal is P.Eng, don’t apply to Technician/Technologist postings.

If you’re pursuing a career as a licensed engineer, we typically expect your NPPE to be completed. You can write NPPE anytime after graduation, and you don’t need EIT status to take it.

Common screening criteria (buildings roles)

This guidance is applicable across role levels (designer, technologist, engineering intern, new graduates, junior engineer). While our primary focus is civil and structural work, the recommendations are broadly applicable across disciplines.

·         Relevant qualifications or momentum: degree, BCIN progress, licensing steps—anything that shows you’re serious about buildings.

·         Screening questions are answered thoroughly using complete sentences, specific examples, and relevant details.

·         Proof of work: portfolio pieces, drawings, calcs, markups, memos—something I can actually review.

·         Genuine interest: candidates can clearly explain why they are pursuing buildings work and how their background aligns with the role.

·         Realistic expectations: this field takes effort; pay grows with skill and responsibility.

·         Self-motivation signals: sports teams, clubs, volunteering, side projects—evidence you follow through.

·         Judgement + accountability: you can work independently, and you ask when you’re stuck.

Primary performance indicator: communication

Communication is a strong indicator of success in consulting environments. This includes interview performance, written communication, and professional conduct in client and team settings.

·         Communication: clear writing, clear speaking, clear questions, clear emails. This is a skill—practice it.

·         Willingness to learn: you don’t need to know everything, but you do need to be coachable and improve quickly.

·         Curiosity: the best juniors ask “why” and build understanding, not just check boxes.

·         Organization: consulting can overwhelm you fast if you can’t track tasks, deadlines, and expectations. Simple systems win (lists, calendars, notes, follow-ups).

A simple organization system (so you don’t get overwhelmed)

Pick a system and use it consistently. Example rhythm: Monday = email triage + planning, Tuesday = protected focus time, and the rest of the week is production + coordination. We also use notebooks for quick daily notes, and tools like Odoo to track tasks and deadlines.

Consulting is hard (and that’s why it’s a great career)

Consulting isn’t just doing technical work. You’re juggling multiple clients, deadlines, and personalities while still doing good engineering. You’re accountable for what you produce, and small mistakes can turn into big downstream problems, including budget and schedule issues.

Remote work reality (especially at entry level)

Fully remote isn’t a guarantee in this industry. It’s usually something you earn with experience and trust. If you’re entry-level, being in-person (at least some of the time) will usually help you learn faster.

If you want to work in consulting, focus on skills that help clients: clear communication, permit-ready drawings/calcs, coordination across disciplines, and staying on top of deadlines and scope.

If you want to ramp up fast, expect to do some learning outside work hours. That’s just part of a technical profession. Employers will support you, but they can’t carry 100% of the training load while you’re building fundamentals.

·         Be deliverable-driven: what are you producing this week (drawings, calcs, responses, site notes), and what decision does it support?

·         Be assumption-aware: state what you assumed, where it came from, and what would change the answer.

·         Write like a consultant: short, scannable notes; clear markups; tidy calculation packages; professional email tone.

·         Think coordination first: buildings are full of trade-offs between structural, architectural, MEP, code, and construction. The job is making it all fit.

Do you have a professional portfolio?

We ask for a professional portfolio to understand your drafting and documentation skills. If you have examples of drawing packages you prepared, include them. If you don’t have work examples, draw a small garage or house independently and use TACBOC details and municipal checklists as your baseline.

A typical permit drawing package includes:

·         Title page with code matrix

·         Specifications / general notes

·         Foundation plan and details

·         Floor plans

·         Elevations

·         Sections

·         Standard details

You need experience to get experience (how to break the loop)

Newcomers often have strong fundamentals, but the gap is usually Canadian codes and light-frame construction (especially residential). That’s why BCIN is such a strong move in Ontario: it forces you to learn the local rules and it signals you can work to Canadian standards.

This is the biggest frustration I hear from people trying to enter buildings: "I need a job to get experience, but I can’t get the job until I have experience." It feels true until you realize a lot of hiring decisions are based on evidence, not job titles.

Create your own building-relevant experience with a personal project. When I was starting out, I learned 3D modelling, BIM/VDC, and documentation by modelling my parents’ house, testing renovation ideas, and producing a small drawing package. It wasn’t paid work, but it was real, reviewable output.

Self-study the Building Code with intent. Don’t just say “I’m learning the code.” Be specific: which code, which parts, and what kinds of projects you want to get good at. If you’re not sure where to start (especially for housing), start with Part 9—it touches a bit of everything and forces you to think like a permit set reviewer.

Keep your portfolio ethical. Don’t share drawings from a previous employer or client if you don’t have permission. If you can’t share paid work (which is normal), create new work (personal projects), re-create typical details from public references, or make “look-alike” sample calcs/sketches that show your thinking without using confidential info.

Build a portfolio that looks like real buildings work

Many entry-level buildings roles start with drafting and documentation. In 2026, that usually means you should be comfortable in a 3D workflow (BIM/VDC or similar)—not just 2D CAD. SketchUp is often the quickest on-ramp, but the key is the workflow: model → views → details → sheets → revisions.

Most juniors start with a mix of site visits and drafting, plus some light engineering tasks as trust builds. If that sounds “too basic,” don’t worry—that’s how you learn how buildings really go together.

If you’re building your first portfolio from scratch, progress in difficulty:

1.      One-car garage (unconditioned).

2.      Two-car garage (insulated) or garage with loft.

3.      Small house (~1500 sq.ft.) with a simple foundation and roof.

4.      Larger house with more complexity (openings, lateral system, stairs, energy considerations).

5.      Small commercial/industrial building concept (even if only schematic), to show you understand a different code/coordination context.

Everyone wants to work on big projects. That’s normal. But the fastest way there is usually: start small, get good, then level up. Small projects let you learn the full workflow (code → design → drawings → revisions → permit → construction questions) without getting buried.

What to include in a strong entry-level portfolio (pick what matches the role):

·         Permit-style drawing set (plans, elevations, key sections, typical details, notes).

·         Basic code summary / code matrix (occupancy, construction type, major assumptions).

·         Sample calculations (gravity loads, wind/seismic approach at a high level, member sizing, sketches).

·         A short technical memo explaining what you did and why (what you assumed, what you checked, what you’d verify in the field).

·         Coordination thinking: where structural, architectural, and MEP constraints collide (openings, penetrations, fire separations, stair/headroom, mechanical clearances).

·         Optional but powerful: a redline/markup example and a simple revision log showing how you iterate.

Portfolio can be simple. A strong portfolio can be as basic as a technical, permit-style package for a small garage. The goal is real work: code-aware decisions, clear notes, and buildable details. Purely artistic portfolios usually don’t demonstrate technical competence in buildings.

Once you have a few pieces, curate a portfolio that’s relevant to the role (not a 120-page thesis that doesn’t translate to day-to-day practice). School work is fine. Personal work is great. Just make sure anything from paid employment is shareable and not confidential.

Software & workflows to learn (2026)

·         3D workflows: be comfortable working in 3D and producing 2D sheets from a model (e.g., Revit or SketchUp).

·         Drawing packages: practice creating a clean permit-style drawing set (SketchUp + Layout is a strong, accessible start).

·         Structural modelling / analysis tools: use what fits your niche, but get fluent enough to set up models, document assumptions, and sanity-check outputs.

·         Mathcad (or equivalent): for clear, reviewable calculation sheets.

·         AI tools: use them to research, draft, and check—then validate with code, engineering judgement, and hand checks.

AI use: what’s helpful vs. what’s a red flag

·         Use AI for the “95% solution”: first-pass research, outlining, checklists, drafting emails/memos, and generating alternate approaches.

·         Validate everything: treat AI as a second opinion, not an authority. Check against the Ontario Building Code, manufacturer data, standards, and your own calculations.

·         Don’t outsource judgement: you’re still responsible for assumptions, safety, and constructability.

·         Don’t pass AI output as finished work: it needs review, edits, and verification before it’s “yours.”

Common application & portfolio mistakes (and how to avoid them)

These come up constantly, and they’re all fixable:

Pre-screening questions I see a lot (and how to answer them)

·         Do you have a portfolio? If you answer, “No, I need a job first,” that’s not it. If you’re new, the portfolio is how you prove you can do the work. Even 1–2 solid projects is better than zero.

·         Do you have experience or qualifications? Don’t be vague—list what you have (BCIN exams, NPPE progress, software, project types, construction exposure).

·         Can you come to the office? Be direct about your location/commute and availability. If you need accommodations, say it early so everyone can plan properly.

·         “I don’t have experience, therefore I don’t have a portfolio.” You can create building-relevant work without a job (personal projects, code-driven drawing sets, sample calculations). Your portfolio is the bridge.

·         Not answering pre-screening questions. Many postings have questions for a reason. One-word “yes/no” answers rarely help—write 2–5 sentences and be specific (what you did, what tools you used, what code/standards you referenced, what you can deliver).

·         Ghosting the application process. If your situation changes or you accept another role, it’s okay—send a short note. Professional follow-through is part of consulting.

How to ask good questions (and grow fast)

Asking questions is part of the job. The trick is asking them in a way that helps you grow and doesn’t dump the whole problem on someone else.

How to ask a senior engineer for help (without making them do your job)

·         Try first, then ask: do a quick pass yourself and bring a proposed approach.

·         Do some homework: check TACBOC standard details, the NRC Illustrated Guide, the Ontario Building Code, and any relevant manufacturer info.

·         Frame the problem: what decision are you trying to make, what constraints matter, and what you already tried.

·         Repeat back the task: “So you want me to do X, with Y assumptions, and deliver Z by Thursday—right?”

·         Don’t be scared of seniors: we can seem intimidating, but we’d rather you ask than guess.

·         Make it easy to help you: share screenshots/markups, references, and context so someone can respond fast.

Your first 90 days (what great looks like)

One thing that surprises people: in consulting, admin skills are technical skills. If you can’t track your time, it’s hard to run projects, forecast budgets, or even know if you’re improving.

Mini-skills that matter more than you think

·         Communication: updates, emails, markups, and questions that save time instead of creating confusion.

·         Accountability: if you own a task, you own moving it forward (and flagging issues early).

·         Timesheets (honest, accurate, and done as you work): don’t “rebuild your week” on Friday. Track as you go and write a real description of what you did.

·         Ask for help early when you’re stuck: the biggest junior mistake I see is spinning on a problem too long without asking. A 5-minute question can save hours (and prevent avoidable errors).

·         Know when to work independently vs. when to ask: push tasks forward, but escalate early when safety, code compliance, or deadlines are at risk.

·         Know where to find answers: code books, standards, manufacturer literature, internal templates, and asking the right person with a well-framed question.

·         Deliberate skill-building: invest time outside billable work to close gaps (software practice, code navigation, detailing, calculation writing).

A portfolio project brief you can copy

If you’re not sure what “good enough” looks like, anchor your portfolio to a real minimum standard: use TACBOC standard details and/or municipal permit checklists as a baseline for what a typical permit submission includes. Your job is to research the minimum standard, then meet it (clean sheets, clear notes, consistent dimensions, and code-aware decisions).

Credentials that can accelerate your entry (Ontario/Canada examples)

BCIN (Building Code Identification Number)

If you want to work in Ontario on small buildings and code consulting, BCIN is one of the best signals you can have. In Ontario, it’s basically a pseudo-architect licence for certain buildings under 600 m² and 3 storeys (within scope). With BCIN, you can work directly on permit-driven projects, learn the Ontario Building Code fast, and build a real portfolio.

How to think about BCIN: for many Ontario buildings teams, BCIN is recommended to be competitive. For our team specifically, having your BCIN exams completed is typically a minimum expectation (especially if you want to work on permit-driven projects).

Minimum BCIN recommendation (for most civil/structural building design work): Legal, House/Small Buildings, and Structural. Beyond that, pick exams based on your track.

Recommended BCIN focus to be competitive (common combinations by discipline):

·         Architectural Engineering: Legal, Complex Buildings, Building Services

·         Civil Engineering: Legal, House, On-site Sewage Systems

·         Structural Engineering: Legal, House, Structural

·         MEP (Mechanical / Electrical / Plumbing): Legal, Large Buildings, Plumbing, Building Services

BCIN exams are multiple-choice and typically written online. They’re open-book (using the code), which means success comes from knowing where things are and how to apply them—not memorizing paragraphs.

NPPE / licensing progress (EIT → P.Eng)

If you’re on the P.Eng path, be clear about your status (EIT, exam completed, application in progress, date you expect to be licensed). For many roles, momentum matters: a candidate actively completing NPPE and Canadian licensing steps often screens better than someone “planning to someday.”

Energy / building science credentials (optional, role-dependent)

If you’re targeting energy, HVAC, plumbing, electrical, or building performance work, see the MEP: additional credentials section below for a simple shortlist (this is where I usually see HRAI/NRCan-type credentials make the biggest difference).

MEP: additional credentials that can help (beyond BCIN)

If you’re targeting MEP roles (HVAC, plumbing, electrical, or building performance), I see these as strong differentiators—especially for newcomers and career switchers—because they translate directly to day-to-day deliverables (loads, equipment selection, energy/retrofit programs, and compliance documentation).

·         HRAI Heat Loss & Heat Gain: a practical credential for residential/light-commercial HVAC work. If you have it, highlight that you can produce (or review) heat loss/heat gain calculations, zoning assumptions, and basic equipment selection rationale.

·         NRCan energy-related training/certifications (as applicable): valuable if you’re aiming at energy advising/auditing, retrofit programs, or building performance. On your resume/LinkedIn, be specific about what you can now do (e.g., audit workflow familiarity, modelling concepts, report outputs).

Call to action (if you want to work in buildings)

If you have your BCIN exams completed, a portfolio ready, and you’re interested in buildings engineering work in Ontario, apply here (submission details are on the posting): portal.ineng.ca/jobs

Resources (code + construction references)

BCIN info (Ontario): https://www.ontario.ca/page/become-registered-building-practitioner

·         Ontario: request a digital copy of the 2012 OBC Compendium (Ontario website): https://www.ontario.ca/page/request-digital-copy-2012-building-code-compendium

·         Ontario Part 9 reference: Part 9 Construction Guide (paid, but very well organized): https://www.publications.gov.on.ca/301299

·         National (useful for learning fundamentals): NRC’s Illustrated Guide (Part 9): https://nrc-publications.canada.ca/eng/view/object/?id=a7a505fa-519c-436b-a23b-6f418df87e6a

·         TACBOC standard details (great for learning how permit sets are structured): https://www.centralfrontenac.com/en/township-office/resources/building-and-planning/TACBOC-Standard-Details.pdf