Business Systems Analyst
smr worldwideGarland (TX)
Business Systems Analyst
Posted yesterday
smr worldwideGarland (TX)
SENIORITY
Lead
About the role
Business Systems Analyst Sprout is a global IT hardware retirement provider for hyperscaler and enterprise clients. We leverage a nationwide footprint combined with proprietary software to enable efficient end-to-end IT asset disposition with a focus on data-bearing devices from the client to the cloud. The company is headquartered in Charlotte, NC with additional operations near Sacramento, Dallas, and Boston. Sprout provides software and services to clients in the form of our IT Asset Disposition, Certified Destruction, and Responsible Recycling solutions. Since our founding as an electronic waste startup from a Duke University dorm room in 2014, we have been expanding at an average rate of >66% each year. By adhering to our 3 values (One Sprout, Deliver Excellence, and Integrity Matters), we are proud of our culture to move at #SproutSpeed to become the emerging leader in our industry. As a Business Systems Analyst at Sprout, you are the bridge between our operations teams and our technology group. Sprout runs on SmartERP, an operational platform we build and maintain ourselves, and nearly every process on our production floor — receiving, testing, data sanitization, refurbishment, resale, recycling, and customer reporting — is executed and recorded in it. Your job is to understand how operations actually works, translate that understanding into requirements our engineers can build against, and configure and support the business rules that make the system behave the way the business needs it to. This is a hands-on role, not a purely documentary one. You will spend meaningful time onsite with the people doing the work, and you will own configuration and business rules end to end — specifying them, implementing them, and supporting them once they are live. Over time you will become one of the company's deepest experts in how Sprout's core systems work and the first person operations turns to when something needs to change.
Responsibilities:
- Work directly with operations. Spend time onsite with warehouse, technical services, and logistics teams to understand their processes, constraints, and pain points. Bring back problems worth solving, not just feature requests.
- Develop business and functional requirements. Write clear, detailed requirements that are grounded in how our existing software actually works, so engineering starts from a realistic design rather than discovering constraints mid-build.
- Evaluate requirements for impact, completeness, and accuracy. Identify conflicts with existing workflows, downstream reporting, compliance obligations, and customer commitments before they become rework.
- Implement and support business rules. Own configuration for routing, product mapping, workflow rules, and similar use cases — including validation, rollout, and ongoing maintenance as the business changes.
- Specify integration requirements and data mappings. Define how data moves between SmartERP and customer, partner, and internal systems, including field-level mapping, error handling, and reconciliation expectations.
- Analyze Data. Use SQL and our BI tools to investigate issues, validate changes, and produce ad-hoc operational reporting.
- Support testing and rollout. Describe test cases, coordinate user acceptance testing with operators, triage defects, and help teams adopt what ships.
- Document what you learn. Maintain plain-language documentation of workflows, business rules, and system behavior so operations leaders can make informed decisions without needing an engineer in the room.
Qualifications:
- 7+ years in a business systems analyst, applications analyst, or similar role bridging technology and operations.
- Hands-on experience with ERP or operational systems in aftermarket services, reverse logistics, repair and refurbishment, or manufacturing.
- A background in applications development — you do not need to be writing production code today, but you should be able to discuss data models, APIs, and system design credibly with engineers.
- SQL familiarity. You can write your own queries against a relational database to investigate a data question without waiting on someone else.
- Demonstrated experience configuring business rules, workflow engines, or similar system behavior — and supporting it afterward.
- Experience specifying system integrations and data mappings between platforms.
- Clear written communication. Much of your output is documents other people have to act on.
- PostgreSQL, Databricks, or Power BI semantic model experience.
- Product owner or business analyst experience in an agile environment — user stories, backlog grooming, sprint planning.
- Experience with work management tooling (GitHub, Jira, monday.com)EEO – Equal Employment Opportunity
The Company is an equal opportunity employer and does not discriminate on the basis of and all qualified applicants will receive consideration for employment without regard to race, creed, color, sex, affectional or sexual orientation, gender identity or expression, gender, ethnicity, religion, national origin, ancestry, nationality, age, disability, marital status, veteran status, genetic information, or on any other basis prohibited by law (except where an attribute is a bona fide occupational qualification)
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.