Manchester vacancy — acquisition analyst

[GreenPost]

Manchester availability is the first condition for this property acquisition analyst opening. The team needs someone who can research the local market, maintain transaction records and follow up with the different people involved in a deal.

Applicants should have relevant property experience and be comfortable showing how they reached a conclusion rather than simply presenting a number. Please include where you are based, when you could start and which part of property acquisition you know best. Candidates may also want to ask about the team size, reporting line and software stack during the initial discussion.

 

[AdaHope]

Could you add the salary range and clarify whether this is office-based, hybrid or remote? The reporting line would also help candidates judge the level of the role. “Acquisition analyst” can mean anything from research support to managing substantial parts of a transaction.

 

[GreenPost]

Fair questions. Those details weren’t included in the information I have, so I don’t want to guess at them. Salary, working pattern and reporting line should all be clarified before anyone commits to the process. In the meantime, expressions of interest should still include location, availability and the property work the person understands best.

 

[gardensAndJournal]

It would also help to describe the first-quarter goals. For example, is the initial priority building a Manchester pipeline, improving documentation, or supporting transactions already under discussion? That tells applicants more than a long software list. A short application could then explain how they would research an opportunity, record assumptions and keep follow-ups moving.

 

[talia_details]

I partly disagree on the software point. The tools may not define the job, but the stack matters if the analyst will inherit live files and established workflows. Team size, expected transaction volume and who owns final decisions are equally important. Without those details, it is difficult to tell whether this is mainly analysis or coordination under an analyst title.

 

[bakesAndView]

Travel expectations need stating too. A Manchester role might involve local site visits, wider regional travel or mostly desk-based research, and those are quite different working weeks. I’d ask shortlisted candidates for one concise example showing an assumption, the evidence behind it, what changed during follow-up and how that change was documented.

 

[AdaHope]

Agreed. The practical next step is a fuller role outline covering salary range, work location, reporting line, team size, transaction volume, software and travel. Until that is available, applicants can still respond usefully with the three requested details and a brief example of explaining an acquisition assumption clearly. That should make the first conversation more focused without asking people to prepare a large unpaid exercise.