**Important Application Requirement**
All applicants must complete the Indeed screening questions in full.
This role requires clear thinking, written communication, follow-through, and the ability to work through detailed business problems. The screening questions are part of the evaluation process, not an optional formality.
Applications with missing, incomplete, generic, or one-word screening responses may be automatically rejected and may not be reviewed further.
We are looking for specific examples of what you have built, improved, automated, tested, or systemized. Résumés alone are not enough for this role.
Systems Builder, Operations Technology
Company: Cash 4 You
Location: Cambridge, Ontario
Work Location: 100% in office
Job Type: Full-time, Permanent
Compensation: $90,000 to $130,000 per year, based on experience and demonstrated ability
About Cash 4 You
Cash 4 You operates a 78-location retail financial services network across Ontario, supported by corporate operations, online lending, collections, compliance, technology, recruiting, training, reporting, and field execution teams.
We are redesigning how the business operates.
That means fewer manual processes, fewer disconnected spreadsheets, fewer unclear workflows, fewer unnecessary escalations, and fewer situations where the business depends on someone remembering to follow up.
We are building systems that make work visible, repeatable, measurable, and easier to execute.
We are looking for someone who can help build that operating infrastructure.
This is not a traditional developer role.
This is not an IT support role.
This is not a remote engineering role.
This is not a corporate product management role.
This is not a role for someone who waits for perfect requirements.
This is a builder role.
The Role
We are hiring a Systems Builder to work directly with leadership and operating teams to turn business problems into practical tools, workflows, automations, dashboards, and AI-assisted operating systems.
The work will often start messy.
A business problem may sound like:
- “We need to improve how candidates move from application to screening to phone interview to final decision.”
- “We need branch employees to know exactly what to do when scanner, printer, camera, or system issues happen before escalating.”
- “We need field operators to inspect branches more consistently and document what changed.”
- “We need reporting that does not require people to chase files, interpret spreadsheets manually, or wait for someone to explain what the numbers mean.”
- “We need training and coaching workflows triggered by actual employee behaviour, not generic reminders.”
Your job is to help turn that kind of operating friction into a system.
That may mean mapping the process, designing the workflow, choosing the tools, building a prototype, writing the logic, connecting systems, using AI tools to accelerate development, working with vendors, improving the user experience, and helping move the solution into production.
In-Office Requirement
This is a 100% in-office role based in Cambridge, Ontario.
This role requires direct collaboration with leadership and operating teams. The work depends on being close to the business, understanding how people actually work, observing problems directly, and moving quickly from discussion to design to build.
Remote or hybrid work is not available for this role.
Product Judgment Matters
We are not looking for someone who simply takes a business problem, prompts an AI tool, and ships the first generic output.
The value in this role is in the thinking after the first draft.
That means breaking the problem into units of work, identifying edge cases, testing assumptions, designing workflows, refining prompts or system logic, validating outputs, and shaping the product until it works inside the real business.
AI tools are part of the workflow. They are not the product.
A strong candidate should be able to explain:
- how they thought through the problem
- what the first version missed
- what edge cases they discovered
- what they changed through iteration
- why the final design was better
- how they tested whether it worked
- what business outcome the system improved
We care about builders who can move beyond the obvious version.
What You Will Do
You will:
- Break down messy business problems into clear workflows, requirements, data structures, and system logic.
- Build or prototype internal tools, dashboards, automations, and workflow systems.
- Use AI coding and productivity tools such as Claude Code, Codex, GitHub Copilot, Cursor, ChatGPT, or similar tools to accelerate work.
- Work with APIs, databases, cloud tools, automation platforms, and internal systems.
- Help design simple, practical user experiences for employees who need tools that are clear, fast, and hard to misunderstand.
- Work with Microsoft/Azure tools, internal platforms, vendors, and third-party systems where needed.
- Identify when to build, when to buy, when to automate, and when to keep something manual for now.
- Create documentation, process notes, and training material so systems can actually be used by the business.
- Review vendor work and challenge solutions that are too expensive, too slow, too fragile, or disconnected from the real operating problem.
- Think about security, privacy, audit trails, access control, error handling, and support before something becomes a problem.
- Help the business move faster without creating unnecessary risk or chaos.
What We Are Looking For
We are looking for someone who can show evidence of building real things.
You may come from software development, product engineering, solutions architecture, automation, technical operations, startup building, internal tools, RevOps, systems implementation, or a related background.
The exact title matters less than the ability.
You should be comfortable with:
- Modern AI development tools and AI-assisted workflows.
- Web applications, APIs, databases, and system integrations.
- Business process mapping and workflow design.
- Practical product design and user experience thinking.
- Cloud environments, especially Microsoft/Azure or similar platforms.
- Automation tools, internal tools, dashboards, and reporting systems.
- Working with imperfect information and turning it into a clear first version.
- Explaining technical decisions in plain business language.
- Moving from idea to prototype quickly.
- Knowing when something is good enough for version one and when something is risky, incomplete, or poorly designed.
Real Business Impact Matters
We care about systems that sell, save, solve, or scale.
That means we are looking for someone who has built or improved something that had real users, real business value, or real operating impact.
Examples could include:
- a product that generated revenue
- an internal tool that saved time or reduced manual work
- a dashboard that helped people make better decisions
- an automation that reduced errors or follow-up work
- a workflow system that improved execution
- an integration that connected disconnected systems
- a customer-facing product or feature that improved conversion, service, or retention
- a process redesign that made work easier, faster, or more reliable
If most of your work has been school projects, isolated code exercises, unused prototypes, or tasks where you were not exposed to real users or real business outcomes, this may not be the right role.
You Are Probably a Fit If
You have built tools, workflows, automations, apps, dashboards, or systems that solved real business problems.
You use AI tools as part of how you work, not as a novelty.
You can look at a broken process and see the system that should exist underneath it.
You can talk to non-technical operators, understand the real issue, and translate it into something that can be built.
You care whether the tool is usable by the person who actually has to use it.
You can work close to leadership, handle ambiguity, ask good questions, and still produce clear output.
You are comfortable saying, “Here is the first version we should build, here is what we should not build yet, and here is how we will know if it worked.”
You are willing to iterate until the solution is not just functional, but useful.
You Are Probably Not a Fit If
You need perfect requirements before starting.
You only want to write code from tickets.
You are looking for a remote or hybrid role.
You are looking for a narrow corporate technology role.
You mainly want to manage meetings, vendors, or roadmaps without building or deeply understanding the work.
You are uncomfortable using AI tools to accelerate development, research, documentation, prototyping, or problem-solving.
You think user experience is someone else’s problem.
You are not interested in learning how the business actually operates.
You think the first AI-generated answer is the finished product.
Example First Projects
Depending on business priorities, early projects may include:
- Designing an AI-assisted recruiting workflow from Indeed application through screening, phone interview, lane assignment, rejection, step-down, and reactivation.
- Building internal dashboards that convert operating data into clear action prompts.
- Creating branch issue-resolution workflows that reduce unnecessary escalations.
- Improving training and coaching systems tied to real employee behaviour.
- Mapping and improving internal approval workflows.
- Building prototypes for operations, finance, HR, collections, or field execution processes.
- Helping evaluate whether vendor-built tools are aligned with the actual business requirement.
Required Experience
We are open to different backgrounds, but you must be able to demonstrate relevant work.
Strong candidates will likely have experience with several of the following:
- Software development or technical product building.
- Internal tools, workflow systems, automations, or dashboards.
- APIs, databases, integrations, and cloud platforms.
- AI-assisted coding or AI-assisted workflow design.
- Microsoft/Azure, Power Platform, SQL, React, Laravel, Python, JavaScript, Retool, Airtable, Zapier, Make, Power Automate, or similar tools.
- Product design, UX thinking, or workflow design.
- Startup, agency, fintech, retail operations, financial services, or complex multi-location business environments.
You do not need to have used our exact tech stack.
You do need to be able to learn quickly, think clearly, and show what you have built.
Practical Assessment
Candidates who move forward may be asked to complete a paid practical assessment.
The assessment may involve a real business problem and ask you to produce a proposed workflow, system design, prototype or mockup, and implementation plan.
We use practical assessments because this role requires proof of thinking, building, judgment, iteration, and business understanding. Interviews alone are not enough.
Application Requirement
Please include a short note or portfolio example showing something you have built, automated, improved, or systemized.
This could be:
- a working app
- an internal tool
- an automation
- a dashboard
- a workflow design
- a prototype
- a GitHub repo
- a Loom or video walkthrough
- a product or process case study
- an AI-assisted build example
In your note, please explain not only what you built, but how the solution changed from the first version to the final version.
We are less interested in buzzwords and more interested in proof.
How to Apply
Apply with your resume and complete all Indeed screening questions in full.
The screening questions are part of the evaluation process. They are designed to help us understand how you think, what you have built, how you use AI tools, and whether you can work through messy business problems with judgment and clarity.
Strong applications will include specific examples of:
- systems, tools, workflows, automations, dashboards, or products you have built or improved
- how you currently use AI tools in real work
- a messy business problem you helped turn into a clearer process, tool, or system
- how you improved a first version after testing, feedback, user friction, or edge-case discovery
Applications with missing, incomplete, generic, or one-word screening responses may be automatically rejected and may not be reviewed further.
Résumés alone are not enough for this role. We are looking for proof of building, judgment, iteration, and real business impact.
Vacancy Status: This posting is for an existing vacancy.
AI Disclosure: We use AI-based tools to help screen, assess, and/or select applicants as part of our hiring process.
Pay: $90,000.00-$130,000.00 per year
Application question(s):
- This is a 100% in-office role based in Cambridge, Ontario. Remote or hybrid work is not available. Are you able to work in office full-time?
- Describe one real tool, automation, workflow, dashboard, app, or system you personally built or significantly improved. What problem did it solve, who used it, what tools did you use, and what changed after it was implemented?
- Tell us about a time when the first version of something you built was not good enough. What did the first version miss, what edge cases or failures did you find, and how did you improve the final version?
- Which AI tools do you currently use in your work, and how do you use them beyond basic writing or search?
- Describe a time when AI or automation gave you an answer that looked plausible but was incomplete, wrong, or too generic. How did you catch the issue and improve the output or system?
- A business leader says: “Our recruiting process is messy. Candidates come from Indeed, some should move forward, some should be rejected, some should be moved to another role, and some should be saved for later. We need a better system.” What would you do first?
- Have you worked with APIs, databases, cloud systems, automation tools, or integrations before? Briefly describe the most relevant example.
- When should a company build custom software, when should it buy an existing tool, and when should it keep a process manual for now?
- Please share a link to something relevant if available: GitHub, portfolio, Loom demo, case study, product walkthrough, workflow diagram, prototype, or example project.
Work Location: In person
