Business Analyst jobs

We are a software agency that has been building products for over 5 years. We’ve shipped 100+ applications for clients in the US, UK, and EU and AU. We don't work the "old way." We heavily use AI to move fast. If you love clear thinking and staying ahead of tech trends, you'll fit right in.

About the Role

This is a client-facing role. Fluent English and the confidence to lead a call are non-negotiable.

This role is roughly 60% Business Analyst, 40% Project Manager.

You work directly with our clients, who are small business owners, not enterprises. They are non-technical, busy, and they describe what they want in vague, incomplete, sometimes contradictory terms. Your job is to work out what they actually need, which is rarely what they first say.

You find the gaps. You spot the edge cases nobody mentioned. You push back when a request will cause problems later. You turn it into something a developer can build, and you test it yourself.

Before anything goes live, you are the one who makes sure what we ship is what the client actually meant. You greenlight the deployment, and you own the result.

A senior developer writes the code. You don't build or architect, but you are technical enough to hold your own: you know APIs and webhooks, and you can read a JSON response and tell us which field matters. You own everything around the code: the client, the requirement, the spec, the testing, and the delivery.

What You'll Do

Business analysis (the heart of the job)

• Understand the client's business and their existing tools well enough to hold a real conversation, not just take notes.
• You ask the questions the client didn't think to.
• Treat the first version of any requirement as incomplete until you've proven it isn't. Find the gaps, surface the edge cases, push back where it doesn't add up.
• Turn it into something a developer can build without 10 follow-up questions: a clear spec, a diagram or mockup or spec. Whatever is needed.
• Shape requirements toward what can be built efficiently. You keep goals realistic without overengineering.

Project management and delivery

• Run the project end to end: Monday sprint planning, Friday retros, task breakdown, prioritisation, and progress tracking in ClickUp.
• Coordinate with the developer, keep things moving, and keep the client updated. No surprises. Ever.
• You test features yourself before the client sees them. You make sure everything works just as the client expected and not just trust the dev team.
• Own delivery to production: you make the call that it's ready, you greenlight the deploy, and you own the result.

Perks for you

• Quarterly Performance Bonus- (based on performance and client outcomes)
• Company equipment (up to PKR 130k allowance to upgrade workstation)
• Laptop allowance (when you use your own laptop)
• Internet backup
• Medical insurance (dependents and parents included)
• Directly communicate with clients and PMs (US, UK, EU) on a regular basis
• Paid time off and leave encashment
• Fully remote and open work culture

Pay: Rs150,000.00 - Rs250,000.00 per month

Application Question(s):

• What is the CGPA/aggregate result of your undergraduate degree?*
• This is a 100% remote role. But our office timings are 9am-6pm (Pakistan).

Please write this sentence below, "I understand that the office timings are 9am-6pm Monday to Friday and remote does not mean I can work any time I want"

• What is your expected salary (PKR)?
• What are your favourite MCP servers, if any? (Write "no" if you don't use any.)
• Which AI agent is your favourite, and why?
• You will be required to work from home. Can you please describe your computer/internet specs and home working environment?
• Are you currently employed in a full-time role? (If no, please elaborate.)
• Think of the last wireframe or mockup you made: what tool did you use, and how exactly did you make it, step by step?
• Walk us through your workflow from a client call to a developer-ready spec. How do you capture what's said on the call? And what exactly does the developer receive from you at the end? Describe or paste a real example.
• How many clients have you personally led requirement-gathering with? Name the projects where you were the sole requirement gatherer, with no PM or BA above you doing it.
• How many projects have you owned end to end as the person accountable for delivery? Name them, and for each: who else was on the team, and what was your role versus theirs?
• Tell us about a time you delivered something that looked right, but it later turned out the client meant something different (you found out on a follow-up call, or once people were using it). How did you discover the gap, and what did you change about how you gather requirements afterwards?

Work Location: Remote