Solutions Engineer Internal Process & Systems

We're hiring an engineer to find what's broken across our business and fix it.

SB E Commerce Solutions is a manufacturing and e-commerce operation in Dallas TX and a manufacturing arm in Faridabad (NCR). We run injection moulding, tooling, industrial printing, warehousing and fulfilment in-house.

Our departments know their problems intimately. Our tech team can build almost anything. What we don't have is the engineer in between — and that gap costs us more than either problem would alone.

WHAT YOU'LL ACTUALLY DO

Your scope is the whole business: goods inward, inventory, manufacturing, the printing floor, packing, dispatch, shipping, quality, sales and finance. You go where the problem is.

You'll embed with a team, watch how the work really happens, and diagnose it as an engineer — observe, measure, form a hypothesis, test it, establish root cause. Then work out the right fix.

When the answer is software, you'll build a working prototype using AI tools (Claude, ChatGPT, Lovable, v0, Bolt), validate it with the people who'll actually use it, get sign-off from the affected teams, and hand a clear specification to our tech team for the real build.

THE MOST INTERESTING PART

Our departments are each run reasonably well. The expensive problems live in the gaps between them, because that's where nobody has ownership — material received but not yet visible in inventory, production complete but the print queue unaware, dispatch recorded in one system and invoiced from another.

You'll be one of very few people whose remit spans the entire flow. You'll see things department heads structurally cannot.

TWO THINGS MOST CANDIDATES GET WRONG

1. The prototype is disposable. You build fast so people can react to something real instead of imagining it. But it exists to remove ambiguity from the requirement — not to become the product. Our tech team should be able to throw your code away and lose nothing, because what you handed them was clarity. If you get attached to your prototypes, this role will frustrate you.
2. Software is one option among several. A changed sequence, a control point, a checklist at the right moment, or a deleted approval step are often better answers — cheaper, and nobody has to maintain them. We treat don't build this as a successful project.

WHAT WE NEED

• B.E. / B.Tech in any engineering discipline, or equivalent demonstrated rigour
• 4+ years owning real operational or technical problems end to end — process, industrial, production or quality engineering, operations excellence, continuous improvement, supply chain, or internal product
• Learning velocity. You'll go from a print defect to an inventory variance to a reconciliation delay in the same month. We need evidence you've picked up an unfamiliar domain and become useful in it quickly
• Structured problem-solving on real problems, with outcomes you can state in numbers — root cause analysis, 5-Why, fishbone, Pareto, hypothesis testing
• Ability to make a complex problem understandable on one page — process flows, material flow diagrams, clear data visualisation
• Demonstrated prototyping with AI tools. Show us things you've built, however rough
• Real skill at interviewing busy, sceptical, non-technical people and getting honest information out of them. This is the rarest thing on this list and we weight it heavily
• Strong written communication — your main output is documents engineers can build from without a meeting
• Data competence: you size a problem yourself rather than waiting for a report
• The spine to tell a department head their idea won't work, and the tact to keep them onside
• Comfort across a factory floor, a warehouse and a finance desk in the same day

NICE TO HAVE

Injection moulding, tooling or industrial printing exposure • warehouse and inventory operations • logistics and dispatch • Lean or Six Sigma as a toolkit • purchase order to GRN to invoice mechanics • ERP or WMS experience • SQL or Python • n8n, Zapier, Make, Retool, Airtable • e-commerce and marketplace operations • Hindi for shop-floor conversations

WHAT THIS ROLE IS NOT

Not a software development role — you prototype, you don't maintain production code. Not a project manager. Not an order-taker for the tech team; challenging requests is part of the job. Not a specialist role — if you want to go deep in one domain for years, the variety here will unsettle you. Not remote: the core skill is noticing what people don't say, and that needs you on-site.

HOW WE'LL ASSESS YOU

Our practical round mirrors the job. We'll show you a real broken process — from any department, and we won't say which in advance. You'll get 30 minutes to observe and interview the person who does that work, then produce a diagnosis, a one-page visualisation, and a proposed solution. You'll present it to us and to our tech lead, who will push back hard.

We don't expect prior knowledge of whatever domain we put in front of you. We're assessing your questions, your rigour, and how fast you get oriented — not the polish of your prototype.

HOW TO APPLY

Apply here, and in your message include:

• One problem you root-caused, with numbers — what you observed, what you measured, what the cause turned out to be, what changed
• One time you entered a domain you knew nothing about and became useful in it
• One time you recommended NOT building or buying something, and what happened
• Links to two or three things you've built with AI tools. Rough is fine

We care considerably more about these four answers than about your CV.

Reports to the COO. This role has responsibility across every department and authority over none, so it's backed directly from the top.