What stood out this week
Focus FS, which builds field-safety software for industrial operations, went from zero open roles to four in a single week, including an AI Engineer, a Full Stack Developer, and a Product Designer. It sounds like they are scaling, and the early hires get the widest scope.
NetBenefit Software, which builds stakeholder-engagement and impact-tracking software for resource and energy companies, did the same: zero to three, all fresh this week.
A quick baseline so the rest of the issue has context. 118 jobs in the feed, 93 of them reachable from NL. 39 are fully remote, 11 hybrid, only 3 strictly on-site. Nine postings are less than a week old. And five postings disclosed salary, from NetBenefit, CoLab, WSP (twice), and Intact.
Three positions worth a closer look
New grad or early-career, watching the big names: Junior Electrical Engineer at Kraken Robotics. Three early-career openings right after it closed a stack of senior ones points to a company rebalancing toward people it can grow. Ask who you'd report to and what the first project is, because "junior" at a hardware shop can mean real ownership or fetching test results.
Career-changer moving into tech: Content Marketing Specialist at NetBenefit Software. St. John's, and rare for this feed, comp is posted: $60,000 to $80,000. The listing openly targets "a motivated, fast-learning candidate" who wants to grow into B2B SaaS marketing, which is code for "we'll train the right person." If you're coming from a writing-heavy field, it's a genuine bridge into a software company.
Mid-career engineer who wants to build, not maintain: Senior Software Developer at CarteNav Solutions, new this week. CarteNav builds mission-systems software that ends up on real aircraft and vessels (defense, search-and-rescue, surveillance), so the work is concrete, on a broad stack (AWS, Azure, GCP, Java, Spring, Kubernetes, TypeScript).
Under the Surface
The shape of all those "AI" requirements
A reader asked after last week's issue: what's the actual shape of the AI requirements, how are employers framing the skills? Good question. The cleanest way to show you is to take one company and read two of its postings side by side.
SiftMed, in St. John's, builds AI that processes and organizes medical records. This week they're hiring a Senior Software Developer and a Growth Market Manager. Both postings mention AI. They mean completely different things by it.
The Senior Software Developer posting mentions AI only to describe the product ("SiftMed is an AI-driven system that processes medical files"). The actual requirement is engineering depth in document processing. AI is the thing you'd build, not a skill they're screening for.
The Growth Market Manager posting is all about using it: "AI fluency," "you use AI tools in your daily workflow, ad copy, creative, campaign analysis," "piloted at least one AI-enabled marketing tool." Here AI is a productivity expectation, not a specialism.
So at one company, the non-technical role leans on AI harder than the role actually building it.
Across the whole feed, only three postings put AI in the title (Spellbook, CoLab, Focus FS), the roles that genuinely want machine-learning depth. The surprise runs the other way: more non-engineering roles ask for hands-on AI fluency than engineering ones do. SiftMed's marketer, CoLab's strategy lead, Spellbook's GTM manager, and a handful of designers all name it as an expectation, while most developer postings stay quiet. So if you're a marketer, a designer, or in revenue ops, "I use AI tools well" isn't a bonus line on your resume here anymore. It's the ask.
So for most readers, the shape of the AI requirement isn't "be an AI engineer." It's "understand the problem well enough to point AI at the right thing." Which is almost word-for-word what someone on the hiring side told me this week.
Get the Full Signal
Subscribe for the full tagged roles list, company-by-company hiring reads, and short interviews with NL tech hiring leads.