Field AI
Product QA & Data Engineer
About this role
Field AI seeks a Product QA & Data Engineer to ensure software quality and data integrity for their construction intelligence platform. You'll manage testing protocols, validate 3D spatial data and BIM outputs, and work across engineering teams to maintain release standards and customer deliverables.
What you'll do
- Own quality assurance for all software releases, serving as final gate before deployment
- Develop and execute comprehensive manual and automated testing frameworks for UI workflows and software functionality
- Identify, document, and triage software defects with reproducible test cases in Jira
- Validate 3D spatial data, point cloud processing, and architectural model accuracy end-to-end
- Create lightweight automation scripts to streamline testing pipelines and QA workflows
- Collaborate with engineering and data teams to resolve anomalies and improve data delivery
What they're looking for
- Software QA and test engineering
- UI/UX automation tools (TestComplete, Selenium, PostHog)
- Defect tracking and root-cause analysis
- 3D point cloud data and spatial data validation
- Building Information Modeling (BIM)
- Python or Bash scripting
- CI/CD pipeline integration
- JavaScript, HTML, CSS (foundational)
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Field AI
Field AI develops embodied AI and autonomous robotics systems for real-world deployment in industrial environments like oil & gas and mining. The company is hiring software engineers to build web-based systems, perception and validation pipelines, test infrastructure, ROS-based robotic software, and customer-facing products that integrate AI with field-deployed hardware.
View all jobs at Field AILikely interview questions
- Walk us through your experience with UI automation tools—which have you used most extensively and how did you integrate them into CI/CD?
- Tell us about a time you delayed a release or data delivery because quality standards weren't met. How did you handle that conversation?