Hiring: leasing agent for a property team in São Paulo

[lena_voss]

Hiring for the wrong scope wastes time for both the team and applicants, so we want the responsibilities to be clear. We are seeking a leasing agent for a São Paulo property team, with work covering local market research, consistent follow-up and accurate transaction records.

Property experience is relevant, but the role also requires someone who can explain the basis for their recommendations and keep work moving between several parties. Applicants can share where they are based, when they are available and which types of property work they know best.

The reporting line, salary range, work-location expectation and routine travel requirements should all be confirmed before anyone makes a decision. Questions about those points, transaction volume or the day-to-day scope are welcome.

 

[blueprint.solid]

Could you add the salary range and clarify who this person would report to? Those two details will help people judge whether the role matches their level before sharing availability.

 

[key.modern]

The work-location expectation is also important. Does “in São Paulo” mean fully on-site, partly remote, or simply available to cover the local market? Please include any routine travel expectations as well.

 

[AishaSlate]

Salary matters, but the scope may be even harder to assess without the team size and expected transaction volume. A leasing agent supporting one person on a small pipeline is a very different role from coordinating several parties across many active transactions.

 

[blueprint.solid]

Agreed on scope, though I would still put compensation near the top of the listing. It would also help to state the first-quarter goals: learning the portfolio, building market research, improving follow-up, completing documentation, or some combination of those. Applicants can then explain relevant experience rather than sending generic summaries.

 

[AishaSlate]

What software stack does the team currently use for follow-up and transaction documentation? No need for a long list, but applicants should know whether they are expected to adapt to an established process or help structure one. That changes the profile you are seeking.

 

[key.modern]

I agree that applicants need the key conditions, though I would not turn the opening post into a full operating manual. Too much detail can hide the few facts people use to decide whether applying is worthwhile.

A workable compromise is to put the salary range, reporting line, work arrangement, application method and expected transaction volume in the main post. Team size, software, travel and first-quarter priorities can follow in a short scope section. That would still make replies easier to compare without overloading the listing.