A written breakdown of the role's tasks with rough time estimates for analysis work versus programming work, along with a description of who else handles each function on the team. This level of detail lets the reviewer see the actual weighting rather than a generic job description.
Ask for specifics, not a repeated job title
Request that the employer describe, in practical terms, what a typical week looks like for this position: meetings and design work versus coding sessions, and whether the applicant is the sole developer or part of a larger team with dedicated analysts. This detail is what distinguishes a genuinely analyst-weighted role from one where the title was kept for organizational reasons while the substance became development work. Two refinements make that description far more useful.
Ask for it in the form of a typical week with hours attached rather than a narrative, because a paragraph can accommodate almost any interpretation while a schedule cannot. And ask that it come from the person who will actually manage the role, signed, rather than from a recruiter or a template held by a central function, since the manager is the only person who knows what the week contains. Where the employer resists, that resistance is itself information worth noting: a role nobody can describe by the hour is usually a role that has not been defined.
Hypothetical example: an interior designer's offer describes concept development and specification work, and the manager's week-by-week breakdown shows a substantial share going to procurement administration, which is precisely the kind of detail a narrative description would have smoothed over.