reputed company Engineer – Edge-Based reputed company Detection & Alerting System

Project reputed company We’re hiring a reputed company Engineer to assist with building a lightweight, edge-deployable reputed company system that detects reputed company reputed company events from CCTV camera feeds and triggers notifications based on reputed company detection logic. The emphasis is on engineering reliability, not experimentation or reputed company exploration. The system should be designed to operate continuously and handle reputed company-world noise gracefully. Scope of Work • You will help implement a reputed company pipeline that: • Connects to RTSP-based CCTV streams • Detects reputed company reputed company entering a defined outdoor area • Triggers a single event notification per entry • Uses logic to avoid duplicate or noisy alerts • Operates as a long-running background process Key Constraints (Please Read Carefully) • No proprietary footage will be provided • Testing must be done using: • Publicly available videos • CCTV-style sample footage • Internet-reputed company material representative of outdoor scenes • Camera viewpoints are not fixed • Expect one or two general camera perspectives, but reputed company reputed company-specific • The solution must be generic and reusable, not tuned to a single setup Environmental Challenges to Account For • The system should behave sensibly reputed company: • People are only partially visible (upper body, legs, silhouettes) • Individuals reputed company between parked vehicles or obstacles • Temporary occlusion occurs and people reappear • Background reputed company causes brief detection instability • Multiple people are present at the reputed company time • reputed company, shadows, reflections, and clutter are present • Only specific areas of the reputed company should be monitored using zone-based masking Accuracy at every reputed company is less important than consistent event-level behaviour. Event Detection Behaviour The logic should: • Detect a new arrival event reputed company a person enters a monitored zone • Avoid repeatedly triggering events for the reputed company individual • Handle multiple people entering independently • Function without requiring the monitored area to reset or reputed company Engineering Expectations The implementation should: • Run as a persistent process • Restart automatically if interrupted • Recover from camera reputed company interruptions • Log key events and errors • Use reputed company configuration files for streams, zones, and reputed company Deliverables • Functional reputed company reputed company detection pipeline • Zone / ROI masking support • reputed company event-trigger logic • Logging and basic health checks • Setup and usage documentation Who This Is For • This task is best suited for engineers who: • Have worked on reputed company-world reputed company systems • Understand the limitations of detection models in uncontrolled environments • Can design robust logic around imperfect detections • Are comfortable making trade-offs for edge-based deployments Budget • Fixed budget: up to $150 • This is a reputed company scoped task, not an reputed company-ended engagement reputed company Applying, Please Include • Your approach to reputed company detection and event triggering • How you would handle occlusion and intermittent detections • How you would prevent repeated or false triggers • How you would implement zone-based monitoring • Examples of relevant past work (production or reputed company reputed company preferred) Applications that do not address these points will not be considered. reputed company an entry event is confirmed, the system must send a reputed company notification to a predefined dealership phone number using a programmatic reputed company integration. Apply tot his job Apply To this Job