Operations Automation Engineer

Forma.ai is looking for an Operations Automation Engineer to build automation, internal tools, and workflow systems that help our Customer Operations and Customer Delivery teams scale with greater speed, consistency, and efficiency.

This role sits at the intersection of engineering, operations, and customer delivery. Forma operates in a complex customer domain, and our teams support sophisticated commission and incentive workflows for enterprise customers. As we continue to grow, we are investing in automation that improves operational leverage, reduces repetitive work, and helps teams focus on higher-value customer outcomes.

You will work closely with Customer Operations, Customer Delivery, Product, and Engineering leaders to identify high-impact automation opportunities, design practical technical solutions, and ship tools that create measurable business value.

This is a great role for someone with strong software development skills who enjoys practical engineering, fast iteration, close collaboration with business stakeholders, and visible operational impact.

What You’ll Do

• Build automation, internal tools, scripts, integrations, and workflow systems that improve how Customer Operations and Customer Delivery teams work.
• Partner with Customer Operations and Customer Delivery teams to understand workflows, identify bottlenecks, and prioritize opportunities with clear operational impact.
• Use APIs, scripting, workflow automation tools, internal systems, and AI-assisted capabilities where they are the right fit.
• Translate operational pain points into pragmatic technical solutions that are reliable, maintainable, and easy for teams to adopt.
• Prioritize work based on impact, speed to value, implementation complexity, and risk.
• Define clear success metrics for automation initiatives, including time saved, process consistency, quality improvements, and reduced manual effort.
• Track and communicate the impact of automation work to stakeholders and leadership.
• Improve existing workflows by reducing manual handoffs, repetitive data lookups, status checks, reporting tasks, and operational friction.
• Create reusable automation patterns that can scale across teams and workflows.
• Help shape the foundation for a broader internal automation function at Forma.

What Success Looks Like

• You quickly understand operational workflows and identify high-value automation opportunities.
• You ship useful automation in days or weeks, not months.
• Your work measurably improves operational efficiency, consistency, and team capacity.
• Customer Operations and Customer Delivery teams trust you because you understand their workflows and solve real problems.
• You balance speed with sound engineering judgment.
• You use AI and automation tools thoughtfully, without treating any single tool as a silver bullet.
• You help create a repeatable approach for identifying, building, measuring, and scaling automation opportunities.

30/60/90 Day Expectations

First 30 Days: Understand the Workflows and Identify Opportunities

By the end of your first 30 days, you should have a clear understanding of the core workflows across Customer Operations and Customer Delivery, along with an initial view of where automation can create the most leverage.

Expected outcomes:

• Build strong working relationships with Customer Operations, Customer Delivery, Product, and Engineering stakeholders.
• Shadow Customer Operations and Customer Delivery team members to understand recurring workflows, handoffs, customer processes, reporting tasks, data lookups, and operational constraints.
• Review existing ticket, task, and workflow data to identify repeat patterns and high-volume requests.
• Create an initial automation opportunity backlog, ranked by estimated impact, complexity, risk, and speed to implement.
• Define a lightweight measurement approach for tracking the impact of automation initiatives.
• Ship at least one small automation, or workflow improvement that demonstrates early value.
• Identify access, tooling, data, or permission gaps that may slow down automation work.

First 60 Days: Ship Practical Automation and Prove Impact

By the end of 60 days, you should be delivering useful automation against high-priority opportunities and showing measurable improvements in operational efficiency.

Expected outcomes:

• Deliver multiple practical automations or internal workflow improvements.
• Validate impact with Customer Operations and Customer Delivery stakeholders using agreed-upon metrics.
• Establish a simple reporting mechanism for automation shipped, teams impacted, time saved, quality improvements, and remaining opportunities.
• Improve early automations based on real user feedback and adoption.
• Identify where scripts, workflow tools, APIs, AI-assisted workflows, or internal tools are the best solution for each problem.
• Start creating reusable patterns for common automation types, such as data lookups, status checks, report generation, validation tasks, ticket triage, and workflow routing.
• Demonstrate good judgment on when to build lightweight automation versus when a more durable internal system is required.

First 90 Days: Create a Repeatable Automation Engine

By the end of 90 days, you should have proven that the role can consistently turn operational complexity into measurable leverage for the business.

Expected outcomes:

• Maintain a prioritized automation backlog with clear estimated impact and implementation effort.
• Show measurable improvement in Customer Operations and Customer Delivery efficiency through shipped automation.
• Establish a repeatable process for identifying, scoping, building, validating, and measuring automation opportunities.
• Partner effectively with Customer Operations and Customer Delivery to continuously surface high-value targets.
• Document key automations, including ownership, maintenance expectations, risks, and known limitations.
• Recommend where automation should be expanded, standardized, or productized.
• Provide leadership with a clear summary of ROI, including examples of workflows improved, measurable impact, remaining opportunity size, and constraints slowing further progress.

What We’re Looking For

• 1–5 years of experience in software development, automation engineering, technical operations, solutions engineering, support engineering, or a similar technical role.
• Strong scripting and automation skills, especially with tools and languages such as Python, JavaScript/TypeScript, SQL, APIs, workflow automation platforms, or internal tooling frameworks.
• Ability to understand operational workflows quickly and translate them into technical solutions.
• Strong bias for action and comfort working with imperfect or evolving requirements.
• Practical engineering judgment: you know when to build something simple and fast, and when something needs to be more robust.
• Strong business instincts: you naturally think about impact, adoption, time saved, and whether a solution is worth building.
• Comfort working directly with non-technical stakeholders.
• Strong communication skills and the ability to explain technical work in terms of business outcomes.
• Relentless follow-through and a desire to create visible, measurable impact.
• Sound judgment around when to use AI, agents, or LLM-based tools — and when a simpler solution is better.

Nice to Have

• Experience building internal tools or automations for operations, support, customer success, finance, or delivery teams.
• Experience working with workflow automation platforms such as n8n, Zapier, Make, Retool, Airplane, or similar tools.
• Experience integrating with SaaS tools, internal APIs, data warehouses, or ticketing systems.
• Experience using AI tools or LLMs to improve operational workflows.
• Experience in a high-growth B2B SaaS environment.

What This Role Is Not

• It is not a generic AI enablement role.
• It is not a research role focused on experimenting with AI for its own sake.
• It is not a traditional product engineering role focused only on long-term roadmap features.
• It is not a role for someone who needs perfect requirements before making progress.

This role is for someone who enjoys practical engineering, close stakeholder collaboration, and measurable impact.

Compensation Philosophy

The expected base salary range for this role is $100,000–$120,000 CAD, with flexibility for exceptional candidates.

In addition to base salary, this role includes substantial performance-based compensation tied to verified operational impact. We believe people who create significant business value should participate directly in that value creation.

Performance incentives are designed around measurable outcomes such as operational cost savings, efficiency improvements, time reduction, increased delivery capacity, and other quantifiable business results.

For high-performing individuals, performance-based compensation may exceed the value of base salary.

How This Role Works With the Team

You will report into the VP of Engineering and work closely with Customer Operations and Customer Delivery. Customer Operations and Customer Delivery will help identify target workflows, validate pain points, and measure operational improvements. Your job will be to turn those opportunities into working automation, internal tools, and scalable workflow improvements.

If successful, this role could become the foundation for a dedicated automation function focused on improving operational leverage across Forma.ai.