Posting record
Open 6+ days
- Powertown's site dates the posting
- Ghostless first sees this listing
- Last checked: still up
How we know
It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.
Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Powertown, so its true age is longer.
Last checked Nov 3, 2026.
How well do you match?
See how much of this posting your resume shows, and what it's missing.
Upload your resumeWhat the posting discloses
Not stated: Pay, real vacancy, AI screening.
Why these three
Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.
Some employers add pay only on their own site. Check the original posting before you rule it out.
About the role
Overview
Powertown is hiring a Software Engineer to maintain the brain of our company. We call it BESS - a centralized platform for executing Powertown’s process. This is the command center for a battery storage company: the place where projects, people, documents, decisions, and execution come together. We want someone who can build internal tools that make a serious team move faster.
What you'll do
- Execute the product roadmap for internal tooling and member experience portals for Powertown
- Design the hidden logic that makes the product feel simple
- Create systems that make information easier to find, trust, and act on
- Own the feature space for Powertown’s site prospecting process
Preferred majors
Computer Science, Software Engineering, Computer Engineering, Electrical and Computer Engineering, or a similarly rigorous technical field.
Ideal candidate
- You are a product-minded builder with real engineering depth and strong UI/UX intuition
- You can sit with an ambiguous problem, reduce it to its core, and build the first version before most people finish debating the requirements
- You have taste. You know when a workflow is clunky. You know when a data model will age badly. You know when a product is almost useful but not quite there yet
Preferred qualifications
- Evidence of exceptional building ability: shipped products, startup work, serious side projects, open-source contributions, research systems, internal tools, or technically ambitious independent work
- Experience building products where workflow, permissions, data quality, and usability matter
- Exceptional ability exemplified through personal projects
Something wrong with this posting?