Property team in Rotterdam seeking a leasing agent

[drawTheGrain]

A poor match here would slow follow-up and leave transactions badly documented, so we want to be clearer about the role before speaking with applicants. A Rotterdam property team is seeking a leasing agent for market research, transaction records and coordination with the parties involved.

Relevant property experience is important, as is the ability to manage several active matters without losing track of assumptions or next steps. When responding, please give your current location, availability, strongest area of property work and any limits on travel or office attendance. It would also help to describe the transaction volume you have previously handled.

 

[ari.brooks]

If this is an employed position, applicants need the pay range; if it is a contract assignment, they need the rate or fee basis. Leaving both possibilities open makes it difficult for suitable people to judge the opportunity.

The advert should also say whether regular attendance in Rotterdam or travel to properties is expected. Those terms are harder to resolve later than differences in preferred experience, so publishing them now would give the team a more relevant shortlist.

 

[holdTheMeter]

I’d also want to know the reporting line and team size. “Keep several parties aligned” could mean coordinating a small internal team, or managing owners, tenants and external parties across many transactions. Those are quite different roles.

 

[leo.oak]

The work-location expectation needs spelling out too: Rotterdam office, hybrid, or mostly remote with local visits? I wouldn’t assume that someone who knows the local market necessarily lives in the city.

 

[yard.steady]

Some applicants may focus too much on years of experience. The request to explain assumptions suggests the team values how someone reaches a recommendation, not just whether they already have Rotterdam contacts. A short example of market research leading to a leasing decision could make an application more useful.

 

[yard.steady]

Perhaps, but I’d be cautious about asking candidates for a substantial case study before the basics are published. Salary, expected transaction volume and first-quarter goals should come first. Then applicants can give a relevant example rather than guessing what kind of leasing work the team actually handles.

 

[yard.steady]

Two other practical points: which software stack is used for follow-up and documentation, and how much travel is expected? Neither needs a long explanation, but both affect whether someone can become productive quickly.

 

[countTheLens]

A clearer posting could separate essentials from details that can wait for an interview. I’d publish the salary range, engagement type, normal work location and reporting line now. Then outline two or three first-quarter goals, such as establishing a follow-up routine or improving documentation, without promising transaction numbers that may depend on the current pipeline. Team size, volume, software and travel expectations would complete the picture.