> Markdown version of [/jobs/ext/4719588-manufacturing-scada-engineer-optimus](https://www.wearedevelopers.com/jobs/ext/4719588-manufacturing-scada-engineer-optimus). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Manufacturing SCADA Engineer, Optimus - **Company:** Tesla Motors - **Location:** Austin, TX, United States - **Experience:** Experienced - **Contract:** Permanent contract - **Skills:** Clean Code Principles, Query Performance, C++ (Programming Language), Databases, Computer Engineering, Data Systems, Database Design, Supervisory Control and Data Acquisition (SCADA), Standard Sql, Screenshots, Concurrency, Indexer, Tia Portal, Eplan, Information Technology, Industrial Software, Software Version Control - **Published:** November 14, 2026 - **Apply:** https://jobs.localjobnetwork.com/apply/add/88865059/1 ## About the Role * Bachelor's Degree in Electrical Engineering, Computer Engineering, Computer Science, Mechatronics, or equivalent experience * 3-5 years building and supporting industrial software in a manufacturing environment (SCADA, HMI, PLC, or plant data systems) * Demonstrated PLC programming (Siemens TIA Portal preferred) with structured, maintainable code and clean interfaces to higher-level systems * Hands-on Ignition, or a comparable industrial SCADA/HMI platform you have actually deployed (WinCC, FactoryTalk, iFIX). Screenshots are not experience * Production experience in Rust, or a systems language you have shipped (C, C++, or Go) and the discipline to write Rust as the service language. We care that you understand memory, concurrency, and failure * Strong SQL: schema design, indexing, query performance. Time-series or historian experience is a plus * Comfort on the shop floor: reading a live PLC, walking a line, talking to operators and technicians * Able to work under competing deadlines without shipping fragile systems. A smaller reliable surface beats a large one that lies * Clear written and verbal communication. You will write for operators, controls engineers, and software peers ## Description This is an on-site role at OFTX. You will work on the floor with controls, manufacturing engineering, and operations as equipment lands and ramps. It is not a panel-design, robot-programming, or EPLAN role. You make sure the data reported is readily available, easy to understand, and broadcast to the right audiences. What You'll Do * Design, build, and operate Ignition SCADA and HMI for Optimus manufacturing: line overview, equipment state, alarms, and operator workflows that stay simple when the line is not * Own the tag architecture end to end - UDTs, naming, scan classes, deadbands, and scaling. Structured, documented, reusable. The next cell should inherit a pattern, not start over * Set and enforce the HMI design standard: screen hierarchy, navigation, layout grid, color and symbol conventions, and alarm presentation. High-performance HMI principles - color means something, and most of the screen is grey because of it * Own HMI at both tiers - the local panel at the machine and the plant-level SCADA client. Same state names, same alarm text, same colors, same navigation logic. An operator who walks from the cell to the line view should not have to translate * Design alarm presentation that operators trust. Rationalize priorities, suppress the noise, and make the display answer "what do I do now" instead of "what happened". An alarm that fires should mean someone moves * Build screens that hold up on the floor: readable at distance, usable with gloves, legible under plant lighting, and fast on the panel hardware actually mounted at the station - not on your workstation * Validate designs with the people who use them. Watch an operator work a screen during a real fault before calling it donem and change the screen rather than the training material * Build the engineering and management views as well as the operator ones: downtime pareto, OEE, throughput, process traces. Different audience, same discipline * Strong database design and querying skills across relational, non-relational, and time-series databases. A trend over a year of data should open as fast as a trend over an hour. Keep reads fast, keep writes honest, and do not paper over a bad contract with a view * Write the queries behind every tag, UDT, screen, dashboard, and report. Named, parameterized, in version control, and reviewed like any other code