Business Analyst
Summary
A remote Business Analyst role focused on discovery and specification for an engagement that automates data retrieval from third-party web portals, producing dev-ready user stories and acceptance criteria. Core work uses web-app fluency, Agile mechanics, and AI-native tooling.
This is a remote position.
Experience Level
We're looking for a Business Analyst with 3–5 years of experience in business analysis, requirements gathering, and working closely with engineering teams.
Role Overview
You'll be working on an engagement that automates data retrieval from third-party web portals. The job is to understand how an unfamiliar portal behaves, figure out what data needs to come out of it, and turn that into requirements engineers can build automation against.
The hard part isn't the automation. It's the handoff. Most of the time on work like this goes into discovery and specification, and that's also where the quality of the eventual build gets decided. You'll own that whole path: getting into the system, pulling the domain knowledge out of the people who have it, and turning it into work a developer can pick up and finish without coming back to you with questions.
We want a crafter here, someone who gets creative about how they reach an answer and stays exact about how they write it down. Use AI to explore an unfamiliar system, sketch alternatives, throw together a quick prototype to see whether an idea holds up, and challenge your own thinking before it reaches a developer. Both halves matter. Creative work that isn't accurate turns into rework, and accurate work that isn't creative is just slow.
You won't need to arrive as a domain expert. You will need to get up to speed in an unfamiliar one quickly.
Key Responsibilities
- Discovery Work through unfamiliar web portals and document the flows, inputs, fields, and branches needed to produce a complete result.
- Data Definition Pin down exactly which data points matter, where each one comes from, and how it should be read and normalised.
- Specification and Work Breakdown Turn what you find in discovery into sliced, dev-ready work: user stories, acceptance criteria, business rules, and edge cases, sequenced so engineers can start straight away and finish without a second round of questions.
- Repeatable Onboarding Build the templates, checklists, and field taxonomies that make each portal faster than the last. Separate what's common across systems from what genuinely differs.
- Client Collaboration Work directly with client-side analysts and engineers. Get the access you need, run the sessions, and get to answers quickly.
- Time-Boxed Discovery Work inside short, outcome-driven spikes and come out with a clear recommendation you can back up.
- Variation Analysis Compare across systems and surface the differences that actually affect the build.
- Validation Check automated output against the manual process, quantify where it diverges, and tell acceptable variance apart from real defects.
- Process Improvement Treat the discovery-to-delivery pipeline as something you improve, not just something you work inside.
Requirements
What We're Looking For
- Requirements and Specification: You've turned messy, undocumented workflows into clear, testable requirements that engineers could actually build from.
- Work Breakdown: You can take an ambiguous problem, slice it into units of work with real acceptance criteria, and hand it to a development team. This is the heart of the role, not a side skill.
- Web Application Fluency: You're comfortable in browser developer tools and can reason about how a web application actually serves up its data. You won't be writing the automation, but you do need to specify it accurately.
- Analytical Depth: You can look across several similar systems and see what's genuinely shared and what's genuinely different, rather than treating each one as a brand new problem.
- Precision: A specification that's almost right still sends the engineer back to you. Getting it exactly right matters more here than getting a lot of it done.
- Communication and Elicitation: A large part of this job is getting domain knowledge out of busy stakeholders.
- Agile Ownership: Not just having worked in sprints, but having run the mechanics yourself: backlog refinement, story sizing, sprint planning, and keeping a development team unblocked.
- Visual Communication: You're comfortable sketching flows and wireframes to get stakeholders and engineers aligned on something before it gets built.
- AI-Native Working: We build with AI across the SDLC and we expect the same in your own work: exploring an unfamiliar system, generating and comparing options, prototyping something quickly to test an assumption, and stress-testing a specification before anyone builds against it.
- Creative Problem Solving: You look for the shortest honest route to an answer rather than the most obvious one, and you're willing to build something rough to find out whether an idea works.
- Domain Adaptability: Healthcare RCM or insurance experience is a plus. Being able to get productive in an unfamiliar domain within a few weeks is not optional.
- Nice to Have Scraping, data extraction, or browser automation projects. Exposure to automation frameworks, SQL, Excel, or Jira.
Benefits
Life at Incubyte
We are a remote-first company with structured flexibility. Teams commit to shared rhythms during core hours, ensuring smooth collaboration while maintaining autonomy. Twice a year, we come together in person for a co-working sprint and once a year for a retreat - with all travel expenses covered.
Our environment is built for crafters: pairing, refactoring, experimenting with AI, and pushing the boundaries of software excellence. We are all lifelong learners, and our work is our passion.
Perks
- Dedicated learning & development budget.
- Sponsorship for conference talks.
- Comprehensive medical & term insurance.
- Employee-friendly leave policies.
- Home Office fund
- Medical Insurance