Business Solutions Engineer

About TruKKer and the Role TruKKer is hiring a Business Solutions Engineer who owns the full journey from a business problem to a solution people actually use, building with Claude Code on top of our existing systems. TruKKer is a technology-driven road freight and logistics company. Our business teams run on fast-moving, process-heavy workflows, and many of their pain points are best solved by small, well-targeted software rather than long project cycles.

The Business Solutions Engineer sits inside that gap: one person, embedded with the business, who can understand a problem, decide what to build, build it, prove it works, roll it out and keep it useful. There are no hand-offs between a business analyst, a product manager, a developer and a tester. The Business Solutions Engineer is all of them for the solutions they own.

If you prefer working from requirements someone else has already written, this is not the role. If you would rather spend a morning with an operations team, find where hours are leaking every week, and have something working in front of them soon after, read on. Role Summary The Business Solutions Engineer is the single owner of a solutions entire lifecycle.

You start by understanding what the business team is struggling with, and you finish only when the team is using the solution and getting value from it. In practice you will: Spend time with business teams to find and define real problems, not just take requests. Research the product options and gather requirements from the right stakeholders.

Build the solution end to end using Claude Code, either as an enhancement to an existing system or a new build from scratch. Test it yourself, end to end, before anyone else sees it. Train the business team, launch the solution and stay on as its owner.

Track adoption, and when usage is low, find out why and fix it.

Key Responsibilities

• The work runs in seven stages.
• You own every one of them. 1.
• Discover and understand business challenges
• Work closely with business teams to learn how they operate day to day and where time, money or accuracy is being lost.
• Identify and prioritise the problems worth solving, using impact, effort and urgency.
• Define each problem clearly, with a measurable outcome, before any solution is proposed. 2.
• Research and define the solution Research the product space: how similar problems are solved elsewhere, and whether to enhance an existing system or build something new.
• Gather and document requirements from the relevant stakeholders (business users, managers, data owners, engineering).
• Propose a solution with scope, trade-offs and success criteria, and get alignment before building. 3.
• Build end to end with Claude Code
• Design and develop the solution using Claude Code, either as an enhancement within TruKKer’s existing systems or as a new build from scratch.
• Handle the full stack of the solution: data, logic, integrations, interface and deployment.
• Make sound decisions on architecture, security, access control and maintainability, and review AI-generated code with care.
• Keep documentation current so others can understand and support what you have built. 4.
• Test it yourself
• Own end-to-end testing: functional, integration, edge cases, data accuracy and user-flow checks.
• Validate with realistic business data and scenarios, and fix issues before release. 5.
• Train and implement Set up and run training and walkthrough sessions with the business team.
• Prepare simple guides or demos so users can adopt the solution without hand-holding.
• Manage the rollout and go-live, including the first weeks of hypercare. 6.
• Support and enhance Be the point of contact for business queries, issues and enhancement requests on your solutions.
• Triage and resolve issues quickly, and scope, build and ship enhancements as needs evolve. 7.
• Drive adoption
• Monitor whether each solution is actually being used, by whom and how often.
• If usage is low, sit down with the business to find the real reason (workflow fit, trust, training, missing features, process change).
• Provide and deliver the fix, whether that is a product change, more training or a process adjustment, until the solution is part of how the team works.

Required Skills

• and Qualifications We care more about what you can build and own than about the title on your last job. 3 to 6 years of experience in software engineering, solutions engineering, product engineering or a similar hands-on role.
• Strong full-stack ability: you can read and write backend logic, work with databases and APIs, and build a usable front end.
• Hands-on experience building with AI coding tools, ideally Claude Code, and the judgement to review, test and correct AI-generated code.
• Proven ability to take a vague business problem, break it down, and turn it into clear requirements and a working solution.
• Comfortable working inside existing systems: reading unfamiliar code, integrating with current tools and making safe changes.
• Disciplined self-testing habits, covering functional checks, edge cases and data validation.
• Excellent communication: you can talk to a non-technical operations team and a senior engineer in the same day, and run a good training session.
• High ownership and follow-through, with a bias for action and for finishing what you start.
• Bachelor’s degree in Engineering, Computer Science or a related field, or equivalent practical experience.
• Nice to Have Experience in logistics, supply chain, freight, marketplaces or other operations-heavy businesses.
• Familiarity with ERP, TMS, CRM or similar enterprise systems and their integrations.
• Experience with BI and analytics tools for building dashboards and usage tracking.
• Prior experience in a forward deployed, solutions engineering or internal tools role.
• Product management exposure, such as writing PRDs, prioritising backlogs and running user research.
• Who You Will
• Work With You will work daily with business teams such as operations, sales, customer success and finance, and with the product, engineering and data colleagues who own the systems you build on.
• The business reaches out to you directly, so you must be comfortable being the face of the solution.
• How Success Is Measured The Business Solutions Engineer is judged on outcomes the business can feel, not on lines of code shipped.
• Targets are set with the hiring manager once the role is filled.
• Problem-solution fit — Solutions shipped that address a validated business problem, with a stated outcome Delivery speed — Time from problem identified to solution live Quality — Defects found after go-live, and rework needed after release Adoption — Share of intended users actively using the solution, and how that trends after launch Business impact — Time saved, errors reduced, or revenue or cost effect, versus the baseline Responsiveness — Time to respond to and resolve business queries and enhancement requests Stakeholder satisfaction — Feedback from business teams on trust, clarity and support