A Burlington Job Offer Ran Into an Engineering Licensing Wall

The situation

The number that mattered most at the first meeting was $118,000, the salary Ayse's prospective employer had put on a written offer for a software developer role in Burlington, against a household that was otherwise doing well: Emre earned a stable salary as a university professor, comfortably enough that the family had never had to make an immigration decision under real financial pressure before. This one came with a deadline attached to that number, and getting it wrong risked losing the offer altogether.

Emre had been working in Canada for several years, first on a work permit and then with permanent residence secured through his university position. Ayse had come to Canada as a visitor, initially to be with him during a sabbatical term, without any immediate plan to work. Trained as an electrical engineer with a decade of experience overseas designing control systems for industrial equipment, she had not pursued Canadian licensing because she had not intended to look for engineering work here.

That changed when a mid-sized technology company in Burlington offered her a position building embedded software for equipment used in safety-critical settings, a role the company had titled software developer. Ayse's visitor status meant she could not simply start working once she accepted; she would need authorization to work in Canada first, and her circumstances, arriving as a visitor with no work authorization, had shifted overnight into something closer to a skilled worker with a concrete Ontario job offer in hand.

The complication ran deeper than status alone. Designing control logic for equipment where a design error could cause physical harm is the kind of work Ontario treats as the practice of professional engineering, whatever the job title says. Ontario does carve out employees working on machinery and equipment used by their own employer in-house, so whether a license is actually required depends on who the equipment is ultimately for. A software developer title does not exempt someone from that reservation if the actual work performed falls within it. Ayse would eventually need to be licensed by Ontario's professional engineering regulator to perform some of what the role envisioned, and the company had not thought through how that requirement interacted with a fast-moving hiring timeline or with Ayse's visitor status. The hiring manager who extended the offer had focused entirely on Ayse's technical background and how quickly she could start, without stopping to ask whether the title on the offer letter matched what Ontario law would actually require of the person doing that work.

What made this urgent

Three clocks were running at once, and none of them were aligned with each other. Ayse's visitor record had a defined period left on it, after which she would need to leave Canada or extend her stay on some basis; a bare visitor extension would not authorize her to work, so time on that clock did not actually help the job offer. The company wanted her working within a matter of weeks, having already delayed their own hiring plans once and telling her plainly they could not hold the role open indefinitely. And the licensing pathway for an internationally trained engineer to be recognized in Ontario is not fast under the best of circumstances; it typically runs months, sometimes longer, depending on how much of her overseas credential and experience the regulator could verify quickly.

None of those three timelines fit inside the others. If Ayse waited to begin the formal licensing process before accepting any work authorization, the company's patience would likely run out first. If she started work without addressing the licensing question at all, she risked practicing in a way Ontario reserves for licensed engineers, a problem for her professionally and a liability question for the company that had not occurred to their hiring manager, Sarah, until we raised it directly.

The urgency sharpened further once we asked the company for more detail about what the role would actually involve day to day. Sarah initially described the position as pure software work, coding and testing without engineering sign-off responsibilities, which would have kept it outside licensed practice and simplified everything considerably. But once we asked for the job description in writing and pressed on which parts of the equipment's control logic Ayse would be expected to approve independently, it became clear the company's own engineering lead expected her to sign off on safety-relevant design decisions, exactly the kind of work that does require licensure.

That was the moment the file changed shape. What had looked like a straightforward work permit application, timed to beat the visitor status deadline, was now also a professional licensing question that could not be resolved on the company's original timeline. We needed a work authorization path that did not depend on the licensing question being settled first, a role description honest enough not to expose Ayse or the company to a licensing violation, and a plan for the actual license that would run on its own realistic schedule rather than the company's original one.

What we did

1. Pinned down what the job actually required. We asked the company for a written description of Ayse's day-to-day responsibilities rather than relying on the job title, and specifically asked whether she would be expected to approve safety-relevant control logic independently. That single question surfaced the gap between what software developer suggested and what the engineering lead actually expected of the role, which was the fact the whole rest of the file turned on.
2. Mapped the regulated scope precisely. We reviewed which parts of the described work fell within activity Ontario reserves for licensed engineers and which did not, so that instead of treating the whole role as either fully open or fully off-limits, we could identify a narrower slice of duties Ayse could perform immediately without a license, freeing the company to bring her on while the rest waited on her licensing progress.
3. Pursued a work authorization route independent of licensing. Because Ayse's status as a visitor with a genuine, arm's-length Ontario job offer supported an application for authorization to work, we filed that application without making it depend on her engineering license being resolved first, so the two processes could run on separate, realistic timelines instead of one blocking the other and leaving her stranded on an expiring visitor record.
4. Negotiated a narrower interim role with the employer. When we first proposed limiting Ayse's early duties to work outside the regulated scope, Sarah initially agreed the company would accept that limitation and adjust the offer letter accordingly. Partway through drafting the revised terms, the company's internal counsel raised liability concerns about having an unlicensed engineer working near safety-critical systems at all, even in a limited capacity, and Sarah came back with a more restrictive position, requiring us to renegotiate what the interim role could include.
5. Rebuilt the compromise around what both sides could actually accept. We proposed a revised interim role confined strictly to code review and documentation work with no sign-off authority, paired with a written commitment from the company to expand her responsibilities and adjust her title and compensation once she obtained her license, giving the company the liability protection its counsel wanted while giving Ayse a genuine path to the fuller role she had been offered originally.
6. Started the licensing application in parallel. We helped Ayse assemble the credential and experience documentation Ontario's engineering regulator would need to assess her overseas qualifications, translating and organizing records from her prior employer, and submitted the file as soon as her work authorization was in hand so the licensing clock started running immediately rather than after the employment situation was fully settled.
7. Documented the final arrangement in writing. We made sure the revised offer letter, the interim scope limitation, and the company's commitment on future title and pay were all captured in a signed document rather than left as an email exchange, so neither side could later dispute what had been agreed once memories of the mid-negotiation reversal faded. Putting the final terms in a signed document also gave Ayse something concrete to point to if a new manager revisited the arrangement once her licensing application concluded.

The outcome

Ayse started work within the narrower interim role once her work authorization came through, several weeks after the visitor deadline that had originally worried the family, but inside the extended runway her authorization application provided. She was doing genuine, useful work from the first week, code review and documentation rather than the full systems design role the company had first put on the table, which was less than what she had hoped to be doing once the process finally resolved.

The compromise cost her income in the short term. Her salary through the interim period sat below the $118,000 figure on the original offer, closer to the mid-$90,000s, reflecting the narrower scope of what she was authorized to do until her license came through. The company's written commitment to restore the fuller title and compensation once she was licensed gave the arrangement some certainty, but it was a commitment, not a guarantee, and it depended on the licensing process concluding the way everyone expected.

Her licensing application continued after the employment question settled, moving through the regulator's assessment on a timeline measured in months rather than weeks. The interim work she was doing in the meantime, though narrower than the original job, kept her professionally active and building Canadian experience relevant to her field, which mattered for both her long-term career and her broader immigration history.

Sarah's company, for its part, kept an engineer with genuine relevant experience rather than losing the hire entirely over a liability question its own leadership had raised late in the process. Neither side got exactly what they had first agreed to. Ayse accepted a smaller role and lower pay than the original offer for a period she could not fully predict, and the company accepted the administrative complexity of running an interim arrangement it had not planned for, but both were better off than if the file had collapsed when the company's position changed midstream.

What you can learn from this