SAP Business One Developer
BluPax Pharma · New Jersey · Full-time · Onsite, with hybrid flexibility after ramp-up Reports to: Chief Technology Officer
About the role:
BluPax is a pharmaceutical distributor. SAP Business One runs the business — pricing, orders, warehouse operations, invoicing and the regulatory reporting that comes with distributing prescription product. A layer of custom automation sits on top of it, and that layer is what makes our operation work the way it does.
That work has always been done by outside vendors. We are bringing it in-house and building our own development team, and this is the first hire.
You would be our SAP developer. Not a consultant, not an architect — the person who writes the code, ships it, and fixes it when something goes wrong on the busiest morning of the year.
Coming in first means real scope. You would own this system outright, set how we work before any conventions exist, and shape what we build next rather than inheriting someone else's plan. It also means you would help choose and onboard the people who follow you. For the right person that is the appeal.
You would report directly to our CTO. There is no layer between you and the person setting technical direction, and no committee to route decisions through.
Where this leads: We are building a development function, not filling a vacancy. The intent is that the person in this role grows into our senior developer, with the engineers we hire afterwards reporting to them. How quickly that happens depends on you and on how fast we grow — but it is the plan, not a possibility we are dangling.
Responsibilities:
- Build and maintain the automations that run our order-to-cash and fulfilment operations
- Change pricing logic across contract, GPO and customer-specific agreements, where being right matters more than being fast
- Extend order approval, hold and payment-term rules as the business changes how it sells
- Debug automations that stopped overnight — work out what completed, what didn't, and how to safely re-run
- Maintain and extend Crystal Reports, pick lists and document layouts
- Trace an order end to end when it behaves oddly, across SAP, the automation layer and the carrier
- Build integrations between SAP and our customer portal, data warehouse, carriers and trading partners
Over your first year you would also make this estate more robust than you found it: source control, proper scheduling, error handling and tests on the paths that move money and stock.
What we need:
Two things are essential. Everything after them is preference.
-Proven experience taking over someone else's production system
This is the job. A working, business-critical system built by someone else, largely undocumented, with the reasoning behind most decisions never written down.
The developer who built it is available to hand it over, for a limited period. That is unusual and it is a real advantage — you would not be reverse-engineering this alone. It also means the first months matter disproportionately: the value of that window depends entirely on whether the person we hire knows what to ask, and asks it while the answers are still available. Knowing which questions matter when you have a finite amount of someone's time is a specific skill, and it is one we are hiring for.
We want to hear about a specific time you took on a system you did not build — what you inherited, how you built confidence in it, what you found that nobody had mentioned, and what you changed first. Candidates who have only worked on code they started tend to underestimate this, and it is the strongest predictor we have of who succeeds here.
-Proven development experience in the SAP ecosystem
Not certifications and not configuration — building against SAP as a developer. SAP Business One specifically is ideal, but experience with other SAP products transfers well, and we will take a strong developer from a comparable ERP who has genuinely built on it.
What matters is that you understand an ERP is not a database with a UI on top. You should know that there is a supported path for writing to it and an unsupported one, what the unsupported path silently bypasses, and how to tell which situation you are in. Our existing code takes shortcuts in places, and we need someone who recognises them as shortcuts rather than as house style.
Direct experience with any of the following moves you to the front: the DI API and the Service Layer, user-defined tables and fields, SAP B1 on HANA, stored procedures and transaction notifications, Crystal Reports, or Boyum (B1UP).
Our stack — ideally you know some of this
- Node.js — our automation layer runs on it. We care about judgement over frameworks: async control flow and how it fails under concurrency, long-running process behaviour, session and token lifecycle, error handling and retry.
- SQL against a live system — you will query and write against production during our busiest weeks.
- Windows server — COM and .NET interop, services and scheduled jobs, printers and spoolers. Unglamorous and genuinely necessary.
- Integrations — REST APIs, OAuth refresh, idempotency and reconciliation. You should be able to say what happens when the far end is down for six hours.
Nice to have:
- Pharmaceutical or medical distribution — GPO contracts, chargebacks, NDC and contract pricing
- DSCSA: serialization, EPCIS, T3 documentation, saleable returns
- EDI, particularly 845 and 856
- Carrier API integration, including label generation and printer routing
- A warehouse management system layered on SAP B1
- Git and code review as habits rather than imposed process
You will not be the only person here who knows SAP — our ERP owner has deep knowledge of the business logic and will be your counterpart on anything that touches it. You will be the person who writes and owns the code.
Where you would work:
Our facility is in New Jersey, and this role is based there.
For your first three months you would be onsite full-time. That isn't a probationary hoop — the knowledge you need lives in the warehouse and in the heads of the people running it, and there is no document that substitutes for standing next to the operation while you learn it. Printer and scanning problems in particular cannot be diagnosed from anywhere else.
After that we would expect you onsite three days a week, with the remaining two flexible. Deep code work benefits from uninterrupted time and we are happy for you to take it.
Some things stay onsite regardless: releases, peak season, and the days when something is going wrong. September through November is our busiest period and we would want you here for it.
How we work:
Every change is a ticket, with an estimate when we accept it and an actual when it's done — we track how far off our estimates were, on purpose, because that's what makes future commitments credible.
Nothing lives only in one person's head. This role exists because that was allowed to happen, and we are not doing it again. Documentation is part of the work, not an afterthought.
September through November is vaccine season. Order volumes rise several-fold, product is temperature-controlled and high-value, and a bad release affects patients rather than a dashboard. We freeze changes when we should, and we test before we ship.
You will spend time with the warehouse and operations teams. We expect you to understand a process before automating it.
What success looks like:
First month — you can work in the system unaided and have documented what exists.
Third month — you own it: the code is in our repository with a real deployment path, and nothing requires an outside party to be available.
Sixth month — the estate is measurably more reliable than you found it, and there is documentation good enough to onboard the next developer against. By this point you would be involved in hiring them.
Pay: $145,000.00 - $160,000.00 per year
Benefits:
- 401(k)
- 401(k) matching
- Dental insurance
- Flexible schedule
- Flexible spending account
- Health insurance
- Paid time off
- Parental leave
- Professional development assistance
- Retirement plan
- Vision insurance
Application Question(s):
- How many years of SAP or SAP B1 development experience do you have?
Education:
Ability to Commute:
- Edison, NJ 08837 (Required)
Work Location: In person
