Technical Solution Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to extract from posting: About Miovision (company description) maybe not needed? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". We need to include sections like About the role? The posting includes "Position Summary" and "Objectives And Responsibilities". Also "Ideal Profile". Also "This posting is for an actual vacancy." Then "Your Rewards & Well-being". Also maybe "Pay" not mentioned. "Schedule" not mentioned. So we include sections where we have content: About the role (maybe Position Summary), Responsibilities (Objectives And Responsibilities), Requirements (Ideal Profile maybe includes technical pre-sales etc), Qualifications (Preferred Education, Domain Expertise), Skills (maybe Python Proficiency etc), Benefits (Your Rewards & Well-being). Pay and Schedule not present, so omit. We must preserve all substantive information, not invent or summarize away detail. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the equal opportunity employer statement, fraud warning, recruitment agencies note, etc. Also remove "This posting is for an actual vacancy." maybe not needed? It's minor metadata; we can fold into short

  or drop it. Probably drop. We need to keep the company description? Not required as a section; maybe we can include as part of About the role? But "About Miovision" is company overview, not role. Could be part of About the role? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can have About the role heading and include position summary and maybe company description? But better to keep About the role as position summary. The company description could be omitted as not role-specific? Might be considered substantive but not required. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep company description somewhere. Could be placed under About the role as a paragraph before responsibilities? Or we could create a separate section like "About Miovision" but not in allowed headings list. The allowed headings are examples; we could still use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections; but we could also add other headings if needed? Safer to stick to those. We can incorporate company description into About the role paragraph. Thus:

  About the role

  At Miovision, we’re unlocking transportation networks that move you. Our vision and mission is to enable smart, fast, safe communities that simply flow, as we drive the Intelligent Mobility Revolution. Backed by the world’s most advanced traffic AI, Miovision’s innovations in traffic signal planning and operations are making it possible for cities to improve the transportation experience for drivers, cyclists and pedestrians. Our values drive us. They’re at the core of everything we do. If they align with yours, proceed through the GREEN light! All in to win: We're driven by a winning mindset, approaching every challenge with intensity, clarity, and speed. One Miovision: We succeed as one team, uniting diverse talents, building on trust, and putting our shared mission before ego. Be better every day: We're committed to continuous growth, staying curious, building mastery, and embracing challenges as learning opportunities. Make it happen: We are proactive and results-driven, taking ownership, acting with urgency, and focusing on solutions that deliver real impact. Earn the customer: We are deeply customer-centric, focused on earning our customers' partnership every day by delivering exceptional experiences that drive their success.

  Then Responsibilities: we have "Objectives And Responsibilities" with subparts: Technical Pre-Sales and Customer Enablement (list of bullet-like sentences) and Engineering, Prototyping & Solution Architecture (list). We'll combine into a single
  • list. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep each bullet as a list item. Let's extract bullet points: Under Technical Pre-Sales and Customer Enablement: - Pre-Sales Support: Provide expert pre-sales technical support for complex hardware and software deployments across customer environments. - Demos and Presentations: Lead compelling sales presentations and product demonstrations for both technical and executive audiences. - Infrastructure Assessment: Assess customer infrastructure and map Miovision solutions directly to agency pain points. - Training and Change Management: Deliver on-site technical training and lead change management for customer engineers and solution architects. - Sales Collaboration: Collaborate directly with Account Executives to hit individual and team sales incentive quotas. - Value Discovery: Analyze daily customer operations to uncover new value and accelerate software expansion. Under Engineering, Prototyping & Solution Architecture: - Hands-On Engineering and Prototyping: Spend the majority of your working time on hands-on technical work, including building rapid prototypes, automating technical tasks, and delivering internal technical reporting. - Requirement Translation: Absorb complex operational and agency needs, translating them into technical task breakdowns and product requirements. - Proof of Value (POV) Validation: Design and implement rapid prototypes or custom workflow configurations, and own the Proof of Value (POV) documentation to prove technical feasibility, validate ROI, and secure technical wins. - Data and Quantitative Analysis: Structure ambiguous technical challenges, analyze system data, and apply mathematical modeling to evaluate performance patterns. - Scalability and Product Strategy: Translate successful custom solutions into long-term engineering specifications and scalable product features across the solution lifecycle. - Cross-Functional Collaboration: Partner internally with Account Executives, Product Management, and Engineering colleagues to drive technical alignment and support growth opportunities. We'll put these as
  • items. Next Requirements: The "Ideal Profile" includes many bullet-like items. We'll treat as Requirements section. List: - Technical Pre-Sales: Prior experience in solutions engineering, technical consulting, software engineering, or technical pre-sales and deep knowledge of networking products, hardware/software integration, and rapid prototyping. - Python Proficiency: Strong, hands-on experience with Python for software prototyping, deep debugging, and automation workflows. - Mathematical Modeling and Machine Learning: Solid understanding of mathematical modeling, machine learning algorithms, and practical AI tooling. - Technical Problem Solving: Proven ability to analyze complex data sets, structure ambiguous technical challenges, test hypotheses, and implement practical solutions. - Self-Starter Mindset: Highly adaptable builder capable of independently learning new programming languages, platforms, and AI tools to create novel solutions. - Business Analysis: Strong capability in process mapping, workflow redesign, and creating clear ROI business cases. - Persuasive Communication: Exceptional ability to adapt highly technical messaging for non-technical buyers to influence purchasing decisions. We could also include Preferred Education and Domain Expertise under Qualifications. Qualifications: - Preferred Education: Bachelor’s degree in Computer Science, Engineering, or a related technical field (or equivalent demonstrated experience) and/or a advanced technical degree (Master’s or Ph.D.) is an asset. - Domain Expertise: Experience in Intelligent Transportation Systems (ITS), transportation infrastructure, fleet/telematics, or connected vehicle technology is an asset. Skills: Could be overlapping with Requirements; but we could separate Skills as maybe Python Proficiency, Mathematical Modeling, etc. However we already have them in Requirements. To avoid duplication, we could put Skills as a separate section listing technical skills: Python, mathematical modeling, machine learning, etc. But the instruction says prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one? But they ask for headings like Requirements, Qualifications, Skills. We could have Requirements (experience), Qualifications (education/domain), Skills (technical proficiencies). Let's do that. Thus:

    Requirements

    • Technical Pre-Sales: Prior experience in solutions engineering, technical consulting, software engineering, or technical pre-sales and deep knowledge of networking products, hardware/software integration, and rapid prototyping.
    • Business Analysis: Strong capability in process mapping, workflow redesign, and creating clear ROI business cases.
    • Persuasive Communication: Exceptional ability to adapt highly technical messaging for non-technical buyers to influence purchasing decisions.
    • Self-Starter Mindset: Highly adaptable builder capable of independently learning new programming languages, platforms, and AI tools to create novel solutions.

    Qualifications

    • Preferred Education: Bachelor’s degree in Computer Science, Engineering, or a related technical field (or equivalent demonstrated experience) and/or a advanced technical degree (Master’s or Ph.D.) is an asset.
    • Domain Expertise: Experience in Intelligent Transportation Systems (ITS), transportation infrastructure, fleet/telematics, or connected vehicle technology is an asset.

    Skills

    • Python Proficiency: Strong, hands-on experience with Python for software prototyping, deep debugging, and automation workflows.
    • Mathematical Modeling and Machine Learning: Solid understanding of mathematical modeling, machine learning algorithms, and practical AI tooling.
    • Technical Problem Solving: Proven ability to analyze complex data sets, structure ambiguous technical challenges, test hypotheses, and implement practical solutions.
    Benefits: from "Your Rewards & Well-being". We'll extract bullet points: - Comprehensive Coverage: Your well-being is covered from day one with comprehensive health benefits, 24/7 virtual healthcare access, and dedicated wellness programs. - Financial Future: Build for tomorrow with our RRSP/401K Matching Plan and share in the company's success through our Variable Incentive Plan. - Time to Recharge: Truly unplug with our unique Mio-Days and flexible vacation policy. - Work & Life Support: We support you with flexible work options, an internet subsidy, a remote work allowance, and enhanced leave for new parents. We'll put as
    • . We must not include Pay or Schedule sections. We must not include boilerplate like equal opportunity, fraud warning, recruitment agencies note, etc. We must not include "This posting is for an actual vacancy." maybe drop. We must not include "Apply now and let's start building together!" maybe that's application instruction; we should remove application instructions. So drop that sentence. We must not include "We are an equal opportunity employer..." etc. We must not include "Please indicate if you require accommodation..." etc. We must not include "Miovision may use artificial intelligence..." etc. We must not include "PLEASE BE AWARE OF FRAUD:" etc. We must not include "To all recruitment agencies:" etc. Now produce HTML fragment. Check that we haven't missed any substantive info: The company values and vision are included in About the role paragraph. The position summary is included there as well? Actually we included the company description but not the explicit "Position Summary" paragraph: "Miovision is seeking a Technical Solution Engineer to act as a core builder and technical solutions architect bridging customer operational needs, product capabilities, and software engineering execution. In this role, you will tackle complex operational problems, assess infrastructure, systems, data, and technical constraints, and rapidly prototype and validate solutions that demonstrate tangible value. You will work across the solution lifecycle, from technical discovery and proof of value through field validation and iterative improvement, translating successful approaches into scalable product capabilities, engineering requirements, and operational solutions. Unlike traditional pre-sales roles, this position is heavily engineering-focused: over 80% of your time will be spent on hands-on prototyping, technical problem-solving, automation, and data modeling rather than client sales presentations. You will work closely with cross-functional team members to support initiatives and translate custom engineering implementations into scalable product features