We built a product called MeterWorx. It’s the software a utility crew uses when they’re standing in someone’s front yard replacing a water meter. A mobile app for the installers in the field and a web portal for the people running the project. It’s live. Real crews use it every day on real projects, and it’s already generating revenue.
We’re looking for one student to join the small team that builds it.
This is not a fetch-coffee internship, and it’s not a ticket queue. You will be inside a production codebase that a paying customer depends on, in your first month.
What you’ll actually do
- Learn the MeterWorx codebase. Not a sandbox copy — the real thing. You’ll spend your first few weeks reading, asking questions, and shipping small changes.
- Build features and fix things. Front end in SvelteKit, backend and database on Supabase, deployed on Vercel. Mobile apps for iOS and Android.
- Work in our weekly release cycle. We ship every week. You’ll open pull requests in GitHub, get real code review, and — once you’ve earned it — help run deployments yourself.
- Use AI tools the way we actually use them. We build with Claude Code and Codex — as the primary method, not a novelty. You’ll learn to direct them well, review what they produce line by line, and catch them when they’re confidently wrong. That last skill is rarer than it sounds and it’s most of what we’re hiring for.
- Talk to the people who use the software. We’re small enough that you’ll hear directly what’s broken and what’s needed. Your opinion on what to build will be asked for and taken seriously.
What we’re looking for
You’ll need:
- To be roughly halfway through a bachelor’s in computer science, software engineering, data science, or something adjacent
- Real comfort in at least one programming language — JavaScript, TypeScript, or Python most likely
- The basics of Git: branches, commits, pull requests. You don’t need to be fluent, you need to not be starting from zero.
- Something you’ve built that wasn’t a class assignment. A side project, a hackathon entry, a script that automates something annoying in your life. It doesn’t have to be impressive. It has to be yours, and you have to be able to talk about why you made the choices you made.
- The ability to read code you didn’t write and figure out what it’s doing
These help, but we’ll teach you what you’re missing:
- React or Node.js — the concepts transfer directly to what we use
- Any experience with SQL or a hosted database (Supabase, Firebase, Postgres)
- Having deployed something, anywhere, that other people could visit
- Experience with AI coding tools — Claude Code, Cursor, Copilot
- Mobile development of any kind
We are not expecting you to already know SvelteKit. Almost nobody does. If you know React, you’ll be productive in Svelte inside of two weeks. Don’t screen yourself out.
The part that matters more than the skills list
We can teach frameworks. We can’t teach the instinct to poke at something until it makes sense.
The person who does well here is the one who, handed a bug report that says “the photo upload sometimes fails,” doesn’t wait to be told where to look. Who notices that a workflow is clumsy and says so, even though nobody asked. Who will tell a senior developer or an AI that the proposed solution seems wrong, and explain why.
If you like problems that don’t have a known answer yet, this is a good place to spend your junior year.
Logistics
- Location: Greenville, SC. We strongly prefer someone who can be in the office at least part of the week pairing in person is how you’ll come up to speed fastest.
- Hours: 15–25 per week, flexible around your class schedule. We mean that.
- What happens after: We are hiring this role because we want to hire a developer. If it works for both of us, there’s a full-time offer at graduation.
About IncWorx and the Innovation Team
IncWorx is a 25 year old technology firm built on a simple observation: most companies don’t have a technology problem. They have a process problem wearing a technology costume. Our job is to take the costume off — figure out what’s actually broken, then build the thing that fixes it.
We recently launched an Innovation Team to do exactly that. Here’s what that means concretely, because “cutting-edge” is what every job ad says:
Development runs through Claude Code and Codex as the primary way work gets done, not as an experiment on the side. We write our own reusable AI skills so the tooling gets better the longer we use it. We ship to production every week. And the whole product — SvelteKit, Supabase, Vercel, iOS and Android — was built by a small enough group that you’ll be able to name everyone who touched it.
MeterWorx is the first thing out of the team. We saw a problem in the water utility industry that nobody had solved well, so we built the product ourselves. It’s live, and crews are using it in the field right now.
