About This Role
We are doing what many IT teams discuss but seldom achieve: giving end users practical tools to solve problems in real time without risking production systems.
You will do two things here: build lightweight applications in Python, HTML/CSS/JavaScript, and Node.js for plant floor, operations, finance, and engineering teams, and build the governance framework that determines how those tools get created, reviewed, and safely deployed across the company. Equal parts builder and architect. You write working code and you write the rulebook for how code gets into production.
We are a manufacturing company. Our users include plant supervisors, shift managers, and engineers. If a tool is not simple and fast, it will not get used. Keep that in mind in everything you build.
What You Will Own
- Governance framework: standards, templates, naming conventions, and the approval process that separates what is safe to self-serve from what needs architecture review
- Deployment risk model: the ruleset that keeps end user code away from production SAP, Salesforce, Snowflake, and MES systems unless it has been properly reviewed
- End user enablement: guided paths so business users can build simple tools themselves using sanctioned access, without opening a ticket every time
- Application delivery: working dashboards, data tools, forms, and utilities; documented so others can build from your work
What We Are Looking For
- Python: scripting and lightweight web apps (Flask, Streamlit)
- HTML, CSS, and JavaScript: functional interfaces without heavy frameworks
- Node.js: lightweight server-side logic and simple APIs
- SQL: you will pull from Snowflake and other sources regularly
- JSON and REST API consumption using pre-approved IT-published endpoints
- Git: if it is not tracked, it does not get deployed
- Basic AWS: S3, Lambda, and IAM at a working level
- Documentation: clear writing, policies people will read, written artifacts as source of truth
The governance side of this role matters as much as the code. We need someone who can write a standard, explain why it exists, train a non-technical user on it, and hold the line when someone tries to skip a step.
Background That Gets Our Attention
Degree or no degree, we want evidence you have built real things for real users and thought carefully about what happens when your code touches data that matters.
Strong signals: IT co-op or internship at a manufacturing or industrial company, a project where you built something and then trained users on it, any ERP or enterprise system exposure (even read-only), documentation or SOP writing in a prior role.
Fits well: Computer Science, Information Systems, MIS, Industrial Engineering with CS focus. Strong GitHub history with documented projects will be considered seriously.
What sets someone apart: Streamlit or Flask apps used by non-technical users, experience governing AI-generated code rather than just running it, any SAP or ERP data familiarity, manufacturing environment experience even outside of IT.
Who Will Thrive Here
This team runs lean. You will not get a fully scoped spec. You will be expected to figure out what needs to exist, build it, document it, and adjust based on feedback from users who may not know what they need until they see it.
We value transparency, direct communication, and written documentation over verbal agreements. If something is not working, say so early. If a decision is made, write it down.
Equal Opportunity Employer
Current is an Equal Opportunity Employer. We do not discriminate on the basis of race, religion, color, sex, gender identity, sexual orientation, age, non-disqualifying physical or mental disability, national origin, veteran status, or any other basis covered by law. All employment is decided on the basis of qualifications, merit, and business need. At Current, we are Always On and working to improve lives with the industry's most expansive portfolio of sustainable advanced lighting and intelligent controls that reliably meet our customers' needs. Learn more at CurrentLighting.com
