Product Engineer

Help us build something new

Spatial DNA connects GIS, asset management, ERP and finance systems for municipalities, utilities and other infrastructure organizations. We automate the work between systems so people can spend less time checking data and more time serving their communities.

We’re building a new product in a new category. Our first step is to bring better governance and tooling to the data movement problem: knowing what should move, which rules apply, what happened and what needs attention.

At the centre is an execution ledger: a record of data movement, including the rules applied, actions taken and results. On that foundation, we’re building tools to understand the lifecycle of work across systems, take action and preserve the information needed to explain decisions.

We’re looking for a Product Engineer to help design and build this product. You’ll work with our existing engineers on customer integrations and shared product capabilities. You’ll also strengthen the foundations: architecture, code repositories, testing, deployment and reliable operation.

This is a hands-on role. You’ll need to be comfortable working through questions that don’t yet have settled answers, testing ideas, and helping us decide what to build next.

What you’ll do

Build the product foundation

• Help design and build the execution ledger that records how data moves between systems.
• Capture enough detail to trace a transaction, understand a failure and explain what happened.
• Build controls for how integrations are configured, changed, approved and run.
• Develop tools that make integrations easier to create, test, deploy and support.
• Build on the ledger to support lifecycle analysis, actions and decision records.
• Test new ideas with small working versions before committing to a larger build.

Design and build integrations

• Work with customers and colleagues to understand how their systems and data need to work together.
• Build integrations using APIs, SQL, custom services and the tools that best fit the problem.
• Make it clear which system owns each record and how changes move between systems.
• Plan for missing data, duplicate messages, conflicting updates and failed transactions.
• Build safe ways to retry, reconcile and recover work.
  

Turn customer needs into reusable capabilities

• Look for needs that appear across customers and build solutions we can reuse.
• Keep shared product features, customer settings and custom extensions clearly separated.
• Design components that can be tested, deployed and updated independently.
• Manage changes so improvements for one customer don’t break another customer’s work.
• Help decide when to build, buy, configure or simplify.

Make our code easier to work on

• Help organize repositories so the team can find, understand and change the work.
• Establish practical habits for code reviews, automated tests, versioning and releases.
• Keep code, integration files, deployment instructions and configuration templates under version control.
• Write down important design decisions and explain the trade-offs.
• Leave work in a state that another developer can pick up and maintain.

Make deployment and support dependable

• Automate builds, tests and deployments.
• Help manage AWS infrastructure through repeatable setup and deployment scripts.
• Keep development, testing and production environments properly separated.
• Handle credentials, access and customer data securely.
• Build useful logging and alerts so we can see when something goes wrong.
• Test rollback and recovery procedures.
• Help resolve production problems and fix the underlying causes.

What we expect in your first six months

• You’ve helped turn part of the product design into working software that we can test with real integration needs.
• You’ve contributed to the execution ledger and shown how it helps trace data movement and explain what happened.
• You’ve helped deliver a production integration or product feature that is tested, documented and ready to support.
• The team has clearer repository, testing and release practices.
• At least one component can be built and deployed through an automated process.
• You’ve shown how your work handles a failure and how it can be recovered safely.
• Another developer can build, test and deploy your work using the tools and instructions you provide.

What you’ll bring

• Experience building and supporting production software or integrations.
• Strong programming skills in Python, JavaScript/TypeScript, C# or a similar language, along with strong SQL skills.
• A good understanding of APIs, authentication, databases and the challenges of keeping systems in sync.
• Experience with Git, code reviews and automated testing.
• Experience using AI coding tools, with the judgment to guide the work, review what they produce and test that it works.
  
• Hands-on experience in architecture, cloud infrastructure, deployment automation or production operations, with the interest and ability to grow across these areas.
• The ability to work through an unfamiliar problem, test your assumptions and explain what you learned.
• A habit of sharing knowledge and leaving work that others can maintain.
• Good judgment about when a simple solution is enough and when a stronger foundation is needed.

We care about what you can do and how you work. A particular degree, certification or number of years won’t tell us the whole story.

Knowledge that would help

• Event-driven systems, queues and background processing.
• Transaction histories, audit trails or systems that track changes over time.
• Spatial data, GIS or location-aware applications.
• AWS and infrastructure as code.
• Municipal asset management, work management, ERP, payroll or finance systems.
• Secure development and cloud operations.
• FME, Mulesoft, Boomi, Workato or other integration platforms.

FME is not a requirement. Spatial knowledge is useful because our customers’ work connects physical assets, locations and business records.

How we work

Tell the Truth. Be clear about what you know, what you don’t know and where you need help.

Show Your Work. Explain your choices and demonstrate what is working.

Keep Your Word. Make realistic commitments, raise problems early and follow through.

Make It Better. Improve the solution and make the next person’s work easier.

We work remotely and value clear communication, shared responsibility and a life outside work.