Product Engineer

Barrl Technologies; Lakeland (FL); On-site; USD 90,000 - 130,000; Full time

Job summary

Barrl Technologies is partnering with a travel management company to deliver production-ready initiatives. You will own two to three client-focused outcomes, turning business problems into measurable digital solutions that the client uses daily.

You will scope, ship, and prove results with rigorous metrics, work directly with client teams, and decide when AI is the right tool. Expect rapid ownership and frequent transitions between domains.

Qualifications

• Ability to translate vague business goals into scoped deliverables.
• Proven track record delivering projects in production, not pilots.
• Ability to quantify outcomes with metrics (hours saved, revenue impact, time-to-value).
• Experience working directly with clients and managing expectations.
• Ability to identify when AI is not the right solution and communicate trade-offs.

Responsibilities

• Scope the work from vague goals into defined projects with boundaries and success criteria.
• Ship fully functional solutions that are adopted by clients, not demos.
• Measure and report on impact, with pre-defined success metrics.
• Collaborate directly with client staff, facilitating demos and updates.
• Assess when AI approaches are appropriate and communicate limitations.
• Move rapidly to the next initiative after hand-off to client teams.

Skills

SQL

Data visualization

Client communication

Project scoping

Business analysis

Ambiguity management

Education

Bachelor's degree or equivalent

Tools

Power BI

Excel

Job description

Barrl is working with a travel management company that serves high-profile clients. Discretion and accuracy aren't nice-to-haves here. An error is visible immediately and expensive.

At any given time you'll own the outcome of two or three initiatives for them. Each one arrives as a business problem and leaves as something their team uses every day.

We're measured on results, not activity. An initiative counts when it's in production and we can show the client what changed.

What you'll do

About the work

Barrl is working with a travel management company that serves high-profile clients. Discretion and accuracy aren't nice-to-haves here. An error is visible immediately and expensive.

At any given time you'll own the outcome of two or three initiatives for them. Each one arrives as a business problem and leaves as something their team uses every day.

We're measured on results, not activity. An initiative counts when it's in production and we can show the client what changed.

What you'll do

• Scope the work. Take a vague business goal and turn it into something with a boundary, a sequence, and a definition of done. Push back when the ask doesn't match the problem.
• Ship it. Not a prototype, not a demo. Something the client's staff open on Monday morning and keep using.
• Prove it worked. Every initiative carries a number: hours saved, error rate, turnaround time, revenue touched. You set it before you build, instrument it as you go, and report it after. If you can't measure it, you haven't finished scoping it.
• Work directly with the client. Talk to their staff, run the demos, send the updates, manage expectations. You own the relationship on your initiatives.
• Know when AI isn't the answer. A lot of this work is AI-shaped. Some of it is a form, a database, and a clear owner. Knowing the difference, and being willing to say so, is a big part of the value.
• Move on. Ship, hand off cleanly, pick up the next thing. You'll be in an unfamiliar part of the business every few months.
  

First 90 days

• 30: You understand the client's business well enough to have an opinion about what's worth building.
• 60: One initiative in production, in daily use, with a number attached.
• 90: You're scoping the next one yourself and the client comes to you directly.
  

What we're looking for

• You've delivered for a business other than your own. Agency, consulting, internal tools, freelance. Anywhere you had to learn someone else's process and hand back something that held up in production.
• You finish. Your track record is things running in the wild, not pilots that stalled at 80%.
• You can point to outcomes. Not 'I built X' but 'I built X and it cut Y by Z.'. If you've never worked that way, this will be uncomfortable.
• You have real data skills. SQL at minimum. You can get to the data, join it, and build the measurement yourself. Reading someone else's dashboard isn't the bar, and spreadsheets alone won't cut it.
• You're precise. This client's work doesn't tolerate approximation, and neither does a system that automates it. You test the edges before you ship.
• You're discreet. You'll have visibility into a sensitive book of business.
• You learn unfamiliar domains fast. You'll be handed a process you've never seen and expected to be useful within a week.
• You're good in front of clients. Comfortable saying 'that'll take longer than you think' and 'I don't think you actually want that.'
  

What this isn't

• Not a heads-down engineering role. Expect to spend as much time with the client's staff as in the build.
• Not an advisory role. No decks, no recommendations you don't have to implement yourself.
• Not an R&D role. Proofs of concept are a step, never a deliverable. A PoC that doesn't reach production didn't happen.
• Not a role with scaffolding. You'll have a lot of latitude and nobody grooming your backlog.
  

Why take it

Direct ownership of outcomes for a real business, with a short line between deciding something should exist and it existing. You'll see the effect of your work on the client's operation within weeks, not quarters, and you'll have the numbers to point at.