System Analyst

In which tools do you draw ER diagrams (not in email)?

What data do you always try to clarify, even if the customer does not voice it? What questions do you ask to make the customer think about what they haven't thought of yet?

Describe the classic software development cycle (SDLC).

Is there an exit from the software development cycle?

Have there been cases where requirements changed after development had already started? How did you act?

Tell us about yourself, what sets you apart from other candidates for the position of systems analyst

How do you determine the limits of task decomposition, and what guides you when deciding on the depth of decomposition?

How do you understand that a developer correctly understood the requirements? Were there cases when the developer implemented something that was not needed? At what stage did you notice and what was the reason?

What factors are important to you when looking for a new place? What is a green flag, and what is a red flag?

Who determines the level of decomposition — you yourself or do you coordinate with the team lead and stakeholders? At what level is coordination with the business customer?

For what types of tasks is an Activity Diagram needed?

What UML diagrams have you used besides Sequence and Activity diagrams?

What modeling languages and notations do you know besides BPMN and UML?

For what types of tasks is a Sequence Diagram needed?

What tools have you used in your work? Please provide examples of successful cases.

Are you familiar with DFD (Data Flow Diagram) and CJM (Customer Journey Map)?

Why is the development lifecycle called a cycle?

Tell about your work experience: projects, team, responsibilities, specific tasks you did manually.