中级业务分析师

Langate is an award-winning provider of web development services in three main categories: business, healthcare, and education. At Langate, we are passionate about crafting digital solutions that make a real impact, and we take immense pride in our strong collaboration with the U.S. market.

In addition to professional expertise, we value excellent communication skills. Collaboration and effective teamwork are the cornerstones of our success, and we believe in fostering an environment where everyone's voice is heard and valued.

About the project

You will join the team behind a large online store that sells durable medical equipment to customers across the United States, including products for people with physical and cognitive disabilities. The business is mature and high-volume, with active marketing and merchandising teams that generate a steady flow of new requests.

The platform is being modernised step by step: it is moving from a legacy Adobe ColdFusion codebase to an Angular front end with a .NET Core back end. The customer-facing storefront went live on the new stack in early September. The admin area and several internal modules that cover inventory, supplier and service workflows are still on the old technology and will be migrated next, alongside new features requested by the business.

Much of the existing logic is custom-built and only partly documented, so a meaningful part of the work is reconstructing how the current system behaves and turning that into requirements the team can build against.

What you will do

• Gather high-level business requests from client stakeholders and turn them into clear, buildable requirements for the development team.

• Run feature kick-off and clarification calls with the client two to three times per week, prepare the questions in advance and follow up until the open points are closed.

• Investigate how existing functionality works, form and validate assumptions with stakeholders, and document the behaviour that has never been written down.

• Write well-structured user stories, functional descriptions and acceptance criteria, following the team's established documentation standards, and keep them current as decisions change.

• Walk the development and QA team through each feature, stay available during implementation and confirm that what was delivered answers the original business need.

• Analyse edge cases, dependencies and cross-module impact before development starts, and challenge requests that are unclear, contradictory or unlikely to deliver the expected value.

• Create basic wireframes and UI mockups to illustrate feature concepts and support developer hand-off.

• Support QA by reviewing test scenarios against the documented acceptance criteria.

Requirements

• 3+ years of hands-on experience as a Business Analyst on software development projects.

• Strong requirements analysis and documentation skills: the ability to translate vague business needs into clear, structured specifications, including functional and non-functional requirements, user stories and acceptance criteria.

• Proven ability to work independently with stakeholders: you dig into a vague request, ask the uncomfortable questions and keep going until the real need is clear.

• Strong attention to detail, including edge cases, permissions, validation rules and alternative flows.

• Strong command of English at B2 level or above. Written documentation is the primary deliverable, and stakeholder communication is daily.

• Strong proficiency with generative AI tools (Claude, ChatGPT or similar) for accelerating documentation, analysis and research tasks.

• Familiarity with Agile/Scrum methodology and with tools such as Azure DevOps and Confluence; basic wireframing skills in Figma, Balsamiq or similar.

Nice to have

• Experience with e-commerce platforms, checkout flows or digital retail is a strong plus.

• Exposure to accessibility standards (WCAG) or to admin and back-office systems is a plus. The audience of the store includes people with disabilities, so accessibility is treated seriously; this knowledge can also be built up on the project.

• Experience on projects that migrate a legacy system to a modern stack.

• Experience documenting reports and back-end logic is a plus.

Team

You will be part of a collaborative, cross-functional team that includes four developers, two QA Engineers with automation expertise, a Project Manager, and two Business Analysts. The development team includes dedicated Front-End and Back-End Engineers.

You will also work directly with the client’s Software Director and in-house Business Analyst, with regular opportunities to collaborate with Marketing, Merchandising, and other business teams.

Schedule

Full-time, remote, 40 hours per week, 5/2. The start of the day is flexible; the working day is planned so that it overlaps with the client in the US Eastern time zone, with calls typically taking place in the afternoon and early evening Kyiv time.

Hiring process

Interview with the recruiter, then one joint interview with the project manager and the current business analyst (about 1.5 hours, including practical cases). No test assignment and no separate client interview.

We offer

• B2B contract, paid sick leave and 20 days of paid vacation

• Official Ukrainian holidays are non-working days

• Flexible work schedule and remote work

• Free English lessons, paid courses and certifications

• Career development plan and mentoring

• Coach and psychologist consultations, workshops

• Medical health insurance

Why this role is worth your attention

This is a large, living product with real growth ambitions, and the analyst sees all of its levels: from the storefront a customer uses to the internal processes that keep orders, suppliers and service moving. There is a substantial backlog and a clear modernisation roadmap, so the work is varied rather than repetitive.
The client is reasonable and collaborative, meetings are scheduled around the team, and the analyst's opinion genuinely influences what gets built. The role suits someone who prefers to shape the solution rather than pass requirements along, and who is comfortable taking ownership of a domain over time.

Need more information? Welcome!

Originally posted on Himalayas