Posting record
Open 12+ days
- Simular's site dates the posting
- Ghostless first sees this listing
- Last checked: still up
How we know
It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.
Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Simular, so its true age is longer.
Last checked Nov 4, 2026.
How well do you match?
See how much of this posting your resume shows, and what it's missing.
Upload your resumeWhat the posting discloses
Not stated: Pay, real vacancy, AI screening.
Why these three
Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.
Some employers add pay only on their own site. Check the original posting before you rule it out.
Skills mentioned
About the role
Where multiple locations are listed for this role, the position may be based in any of those locations, with priority determined according to the order of listing.
We're looking for an engineer to work on the control layer - the system that translates an AI model's intent into precise, reliable actions on a real computer. This means mouse movements, keyboard input, window management, UI element detection, and error recovery across macOS, Windows, and Linux.
What you'll do
- Work on the low-level computer control stack: mouse/keyboard injection, screen capture, coordinate mapping, input simulation
- Implement UI element detection using accessibility APIs (AXUIElement, UI Automation), DOM/a11y trees, and visual grounding
- Help build the abstraction layer that lets our agent operate across OS platforms and application types
- Tackle reliability problems: element targeting under UI changes, window occlusion, resolution scaling, cross-app focus management
- Contribute to feedback loops: how does the agent know its action worked? How does it recover when something unexpected happens?
- Work closely with the model and planning team on the interface between intent and execution
You might be a fit if
- You've built OS-level input automation (CGEvent, SendInput, xdotool, or similar)
- You understand accessibility frameworks - AXUIElement on macOS, UI Automation on Windows, AT-SPI on Linux
- You've dealt with flaky element selectors, timing issues, resolution-dependent coordinates
- You think carefully about reliability and edge cases
- You've worked with tools like Playwright, Appium, PyAutoGUI, Hammerspoon, or similar
Bonus
Experience with screen reader internals, remote desktop protocols (RDP/VNC), game automation, LLM agent tool-use systems, or mobile device automation (iOS UIAutomation / XCTest, Android UIAutomator / Accessibility).
Something wrong with this posting?