Recognition Technology Project Lead

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Auror" intro, then "The Role", then "Location and hours", then "Responsibilities", then "Requirements", then "Benefits". Also maybe "Compensation Range" is separate but we have Pay section: we have salary range and bonus. So we need Pay section. Also maybe Schedule? Not present. So we include sections where content exists: About Auror? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They say do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings. They want sections only when posting has real, specific content. So we need to decide which headings to use. We have content: About Auror (company description). Could map to "About the role"? Actually "About Auror" is about company, not role. But they gave example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list "About the company". However we could still use "About the role" to include the role description (The Role). The "About Auror" could be considered part of role description? Might be better to put under "About the role". The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings if we have content. We have content for About the role (The Role section). Responsibilities (list). Requirements (list). Benefits (list). Pay (salary range + bonus). Schedule? Not present. Qualifications? Could be part of Requirements. Skills? Not separate. We'll not create empty sections. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out things like "What are the next steps?" and application instructions. Also remove "Compensation Range: $139K - $165K" duplicate? Already have salary range in Benefits? Actually they have Benefits section includes Competitive salary range etc. At end they also have "Compensation Range: $139K - $165K". We'll keep only one. We need to output only HTML fragment, no /, no markdown fences. Let's extract content: About Auror paragraph: "About Auror At Auror, we’re empowering the retail industry to tackle theft and Organised Retail Crime, a $150 Billion problem globally. It’s high volume crime that’s increasingly organised in nature and is putting people, retailers, and communities at risk every day. Founded in New Zealand 12 years ago, we’re working with some of the best and largest retailers in the world across the US, Canada, Australia, New Zealand, and the UK. Auror is connecting people and intelligence to reduce crime. We’re using technology for good. Our mission is clear: reduce violent retail crime by 50% in 5 years. It's an ambitious goal - and one we believe is achievable. In partnership with our leading retail partners, we need people with the passion, determination, and innovation required to overcome one of the world's largest problems. If you’re looking to make a difference with and for the people dedicated to stopping crime, for good, then we want you on our team. We're also embracing the potential of AI to supercharge our impact - whether that's enhancing the way we detect trends, support our customers, or improve internal workflows. As a company, we're committed to responsibly incorporating AI into how we work and what we build, and we encourage all Aurors to be curious about how AI can elevate their work, regardless of role or function." The Role paragraph: "Auror’s mission is to reduce violent crime in retail stores by 50% over the next 5 years and we believe that recognition technology, when deployed with privacy at the forefront, has a major role to play in helping us in achieving this goal. Our market-leading Risk Recognition modules help retailers to solve and prevent crime by sending real-time alerts to store teams about high-risk individuals entering their locations. This critical intelligence empowers teams to respond proactively, enhancing the safety of both staff and customers and improving loss prevention results. Our customers across the United States are increasing their adoption of Auror’s Vehicle Recognition and Subject Recognition modules; as such, we are seeking a hands-on leader to spearhead the successful implementation of this technology in thousands of retail locations across the US. As the Recognition Technology Project Lead, you will be at the forefront of Auror's innovative recognition technology. Having deep technical expertise in both License Plate Recognition (LPR) and Facial Recognition (FR) technologies, you will lead end-to-end projects with customers, partnering with a diverse set of internal and external stakeholders, to deliver successful pilots and full-scale rollouts. You’ll become the in-market subject matter expert on Auror’s Vehicle Recognition and Subject Recognition modules, understanding our technical integrations and product capability inside and out. This role requires someone with experience deploying end-to-end solutions that involve both hardware and software, exceptional project management skills, and the ability to collaborate effectively with various internal and external stakeholders." Location and hours: "This is a Denver, Colorado-based role; we value co-location and have a hybrid flexible working model. Our recognition technology product modules are leveraged by customers in New Zealand, Australia, the US, and the US, and while this role is focused on the US, you will need to be flexible with your working hours to effectively support our customers and internal teams globally. This role will also involve some travel to customer sites to provide on-the-ground support for pilots and rollouts, averaging 2–5 days per month." Responsibilities: bullet list (multiple paragraphs). Let's extract each bullet: - Project management: Partner with relevant stakeholders to oversee the scoping, design, and delivery of Vehicle Recognition and Subject Recognition pilots and rollouts, both for customers with a handful of sites as well as those with thousands of sites. You’ll act as a project manager for these deployments, ensuring successful planning, rollout, and ongoing support. - Technical subject matter expertise: Deep understanding of LPR and FR systems and the various deployment models, including on-camera and on-premise deployments; Practical knowledge of networking requirements for software running in customer environments; Solid understanding of SaaS platforms, databases, and cloud environments - Technical pre-sales: Provides in-depth technical expertise during the sales cycle, understanding client needs and communicating the technical value proposition. Supports the commercial team with presentations, RFPs, and ensures a smooth transition to project implementation. - Engineering collaboration: Work closely with the engineering team to: Set up monitoring and alerting systems; Configure and optimize recognition technology deployments; Troubleshoot network and hardware issues; Provide technical feedback for product improvements - Supplier relationship management: Build and maintain a network of suppliers for direct supply of recognition technology hardware and software. You will also work closely and in partnership with our integrators (external to Auror) to ensure a smooth roll out and maintenance of the systems. - Market awareness: Understand market differences and use of LPR and FR technology across our global markets. - Customer success Collaboration: Partner with Customer Success teams to facilitate seamless customer Vehicle Recognition and Subject Recognition pilots and rollouts, ensuring the team is equipped for success. - Ownership and communication: Take ownership of technical issues and questions, communicating clearly with relevant teams, providing updates and following through to resolution. Requirements: list of bullet-like sentences (some are paragraphs). Let's extract: - Experienced in rolling out and leading complex technical programmes of work that involve collaborating and liaising with a wide range of internal and external stakeholders - You’re someone who thrives in a lean team environment where you’re operating with autonomy and accountability for the delivery of projects. - You have exceptional communication, with a strong preference for documenting over synchronous discussion. - You understand commercial drivers and can leverage that business context along with your technical domain knowledge to support business objectives in a meaningful way. - You can think strategically, looking beyond day-to-day projects, to identify opportunities for growth or new integrations and partnerships. - Experienced in picking up new technologies and concepts quickly, as we build new integrations and develop further partnerships, you’ll upskill on the go to become an expert on these areas as well - You’re curious and excited about how AI tools can enhance technical workflows, improve efficiency, or scale support — and may have already experimented with AI tools for documentation, monitoring, or knowledge management. - We are looking for people who demonstrate a strong alignment to our Guiding Principles (you can find these on our Careers page). With diversity and inclusion at the forefront of Auror’s guiding principles, we promote a culture that celebrates diversity and inclusiveness at Auror, regardless of, but not limited to, race, gender, sexual orientation, family status, religion, ethnicity, national origin, physical disability, veteran status, or age. - Bonus: As this role requires an in-depth understanding of the technology, both with hardware and software, a background in Engineering will be an advantage. You’ve worked in a product organisation and have recent experience in a growth business. Benefits: list: - Competitive salary range: Depending on level of experience, between USD$139,000 - 165,000 (IC4). - Annual bonus: Eligibility for a USD $5,500 bonus at the end of the financial year if we’ve hit our revenue goals together. - Employee share scheme: You’ll own part of a company making a real difference! - Flexibility: We are hard-working and outcome focused, but recognise there is more to life than work. We promote a healthy work/life blend. - Shorter work weeks (at full pay): Everyone gets Friday afternoons off, so you can start your weekend early, and do more of whatever it is that makes you happy. - Focus on mental and physical health: We understand how vital our health is and have policies to support your wellness, including Wellness Days, and up to $500 for expert sessions every year. - Health care plan (Medical, Dental & Vision): Auror covers 100% of the cost of your individual health insurance plan with Anthem & Metlife. - Family-friendly: We offer comprehensive paid parental leave - 12 weeks for birth parents and 6 weeks for non-birth parents following birth, adoption, or surrogacy, available to all Aurors from day one. - Personal growth: We support our team to participate in courses, conferences, or events that will help them develop their skills. - Team love: We have regular team lunches and social events where most (if not all) activities are during work hours. Pay: we already have salary range and bonus in Benefits; but they asked to include Pay section if posting actually states them. The posting states salary range and bonus under Benefits. Could still create a Pay section with that info, but we must not duplicate. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Pay into Benefits, or keep separate Pay section. Since Benefits already includes salary and bonus, we could keep Benefits and not create separate Pay. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state salary and bonus, so we could create Pay section with that info, and Benefits section for other benefits. But that would be thin sections. Better to keep Benefits inclusive of salary and bonus, and not create Pay. The instruction says "Prefer a few substantive sections over many thin ones." So we will not create Pay separate. Schedule: not present, so omit. Qualifications: not separate; we can incorporate into Requirements. Thus sections: About the role (maybe combine About Auror + The Role), Responsibilities, Requirements, Benefits. We need to use

for each section heading. Inside each, use

for prose,

• for lists. We must not repeat