NISC
Software Developer - Meter Data Management Software (Full Stack, Back End)
About this role
NISC seeks a full-stack software developer with backend focus to join the Meter Data Management team, building enterprise solutions for utilities handling Advanced Metering Infrastructure (AMI) data. The role involves designing scalable applications that help utility staff analyze and validate billing data while contributing to a collaborative team supporting over 1,200 utility companies.
What you'll do
- Design, develop, test, and maintain full-stack applications and scalable data engineering solutions
- Analyze and resolve complex technical issues across application and data platforms
- Collaborate with team members on shared development goals and product enhancements
- Build solutions for data storage, analytics, and Advanced Metering Infrastructure (AMI) systems
- Contribute to troubleshooting and validation tools for utility billing and engineering analysis
What they're looking for
- Full-stack development with backend specialization
- Data engineering and scalable system design
- Problem-solving and technical troubleshooting
- Collaborative teamwork and communication
- Software testing and quality assurance
- Enterprise application development
- Database and data analytics experience
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.
NISC
NISC builds software solutions for utilities, broadband, and telecommunications companies, including provisioning systems, meter data management, and intelligent automation platforms. The company is hiring Software Developers II for full-stack development roles focused on web applications, data analytics, and emerging technologies across multiple locations.
- Website
- nisc.coop
Likely interview questions
- Describe your experience with full-stack development and which backend technologies you're most proficient in.
- Tell us about a complex technical issue you debugged across application and data layers—how did you approach it?