Find & Apply For Software Developer / Engineer Jobs in Roxbury Township, New Jersey

(

Note:

Recruiters will contact you via Indeed Messages. ) Build the product. Masterthe craft. Deliver results. Three things to know before you read further: This job is C. Not "embedded, generally." C at the register level is required to get started, even though many of our developers work on web-based tools and other projects later. This job is fully in-person , on-site every day in Ledgewood, NJ. No remote. No hybrid. Our screening is a real hands-on hardware challenge , not a whiteboard algorithm quiz (see details below). We need sharp, technically-driven engineers who want full responsibility for embedded product development, from schematic design through firmware delivery and into the client's hands. You won't be handing off pieces of a puzzle. You'll architect, build, and ship complete solutions in C and Python, with measurable impact on every project. Our engineers talk directly to the people who use what we build. You will need to be a committed lifelong learner to succeed at this job.

The Challenge:

This is a high-mix, low-volume engineering environment. Every project is different. Deadlines are firm. You'll tackle new technical problems constantly, including bare-metal firmware, network protocols, PCB layout, and database integration, and you'll be expected to deliver production-quality results on schedule. We are increasingly an "AI-first" company. We use these new tools aggressively wherever they help us serve clients better, from accelerating development to making sure nothing a client sends us sits unanswered. BUT we hire engineers who understand the WHY behind every line, because you can't review what you can't reason about. We don't ship anything we haven't thoroughly tested and validated ourselves.

Our clients run critical infrastructure:

emergency communications, utilities, railroads, fire alarm networks. When their equipment has a problem, they call us, and an engineer picks up (we don't have some separate "tech support" crew). Some of the most valuable work you'll do here starts on a screen-share with a technician standing at a remote site with a voltmeter in his hand, and ends with improvements to the mainline firmware that all clients can use. About the

C Requirement:

C is the foundation of every remote-monitoring device we build. It is not a "nice to have," and general "embedded" or "programming" ability is not a substitute for it.

That said:

if you're a strong, flexible developer without direct C experience, you're welcome to apply and give our take-home challenge a shot. We've found the right kind of engineer can pick this up quickly, and the challenge is how you show us (and yourself) that you're that engineer.

Our Two-Part Hardware Challenge:

Part 1 is a take-home. Part 2 is on-site. Both are the same kind of work: bit-banging the I2C protocol on an Arduino, toggling the lines yourself, with no Wire library to hide behind. Part 1: Take-Home (Tinkercad, virtual Arduino) Early in our process, you'll get a take-home challenge in Tinkercad. It's a virtualized Arduino on your screen, talking to a simulated I/O expander chip. You don't need any hardware. You just need a web browser. You build the circuit, read the datasheet, write the C, and debug it one step at a time, on your own schedule. The point of Part 1 is simple: it tells you (and us) that you have enough skill to get started, before anyone makes a trip here unnecessarily. It's low-stakes, and it's worth doing regardless of outcome. We don't want to plunge you into a role that isn't going to work well for you, and you don't want that either. At minimum, trying it will show you exactly where you stand. If the answer is "not yet," you'll know what to study, and you're welcome to come back. Candidates who are right for this job tend to enjoy it. Several have told us they finally understood how I2C actually works because they weren't allowed to use the library. Part 2: On-Site (physical Arduino) If Part 1 goes well, you'll come to Ledgewood for an in-person interview. That visit definitely includes a second challenge: the bit-banging exercise on a real, physical Arduino at our bench, plus a short handwritten coding worksheet and a conversation with us. This is the real technical bar for the job. If you worked through Part 1 yourself and understood what you wrote, you'll likely arrive ready for Part 2.

What You'll Be Responsible For:

Full-cycle embedded firmware development in

C and Python:

design, implementation, testing, and optimization Network protocol performance at the register level:

TCP/IP, UDP, SPI, I2C

Systematic debugging and root-cause analysis of firmware and communication issues, including live troubleshooting sessions with client technicians Schematic review and PCB layout using professional CAD tools (this comes later on; we'll train you on the toolchain) Clear written documentation at every step: what you changed, why, how it was tested, and what the next engineer needs to know The reasonable application of AI tools (including some running on in-house hardware) to all of the above challenges whenever it creates real value

Technical Standards We Expect:

C language. Demonstrated proficiency, or the demonstrated ability to get there fast (that's what the two-part challenge is for) Strong working knowledge of bare-metal and embedded Linux environments Practical experience with MCU platforms (Arduino, Raspberry Pi, or equivalent) Competence with network protocols and hardware interfaces Functional ability in HTML, CSS, JavaScript, and SQL Some basic electronics background, enough to learn PCB design quickly Fluency with AI tools as an accelerator, paired with the ability to work through a hard problem without them. We'll ask you to do both The ability to explain a technical finding plainly, in writing or on a call, to someone who is smart but doesn't work with our product every day

What Sets You Apart:

You've completed projects independently: hobbyist builds, personal engineering challenges, or self-directed technical work carry significant weight here School or work projects count, provided you were a primary technical contributor, not an observer You have a systematic approach to learning new tools and can demonstrate rapid skill acquisition You've helped someone else solve a technical problem and found that satisfying rather than annoying, and your instinct afterward was to fix the thing that made the problem possible. Teaching, tutoring, tech support, help forums, and lab partners all count Is This You? Some engineers want to be left alone with a compiler. That's a legitimate preference, but this is not the job for it. Here, the hardest problems arrive through a client. You get on the call, you find the actual cause, and you give them something that works today. Then, once you understand the root cause, you close it out permanently: a change to the mainline firmware, a hardware revision, a clearer web interface, a piece of documentation that stops the question from being asked again. One client's bug report gets solved for every other client forever. That's the standard here. This is not a support desk. You are not going to spend your career answering the same question. You're going to answer it once, well, and then go engineer it out of existence. If that appeals to you, keep reading.

Schedule and Pace:

We work hard. The baseline day is from 9am to about 6pm, and overtime is a normal part of the job when client deadlines call for it. We say so up front because we'd rather you know now than find out later. There is flexibility for the right person.

Location and Commute:

This role is fully in-person, on-site every day, in Ledgewood, NJ. There is no remote or hybrid option, now or later. All interviews are in person. You don't need to live in New Jersey. We have people commuting from Pennsylvania. What matters is drive time, and we'll be honest about what we've seen: commutes of about 45 minutes or longer have not usually worked out long-term in this role. You should already be within that range, or have a genuine, concrete plan to relocate in the near future.

The Opportunity:

We will invest directly in your technical development. You'll gain hands-on expertise across the full embedded product stack: firmware, hardware, networking, and systems integration. You'll work in an environment where AI is part of the standard toolkit, and where finding exactly what parts the AI got wrong is also part of the job. You'll even get to build something rarer, which is a reputation with clients who remember your name.

But this requires commitment:

consistent effort, disciplined learning, and a refusal to settle for "good enough." If you want to build real competence, not just credentials, and you're driven to take on challenging technical work that matters to real people, this is the role.

Details:

Job Type:

Full-time Schedule:

9am to 6pm baseline, overtime as needed

Location:

On-site every day, Ledgewood, NJ (no remote or hybrid)

Process:

Take-home Tinkercad challenge and short online assessments first, then an on-site interview that includes the bit-banging exercise on a physical

Arduino Job Type:

Full-time Pay:

Up to $62,000.00 per year

Benefits:

401(k) 401(k) matching Dental insurance Health insurance Life insurance Paid time off Vision insurance

Work Location:

In person