Understanding professional work and describing your development

You do not need to be in a full-time professional role to use SFIA. You can use it while studying, preparing for a placement, applying for internships, undertaking an apprenticeship or planning your first career steps.

SFIA is useful because it describes more than technical knowledge. It helps explain:

• the kinds of professional work people do
• the professional behaviours and business skills (e.g. how you communicate, plan, collaborate, and solve problems) that help people work effectively
• the level of responsibility someone is taking
• the knowledge needed to contribute in a role
• the evidence you can use to describe your development.

This can help you connect academic learning with professional practice.

Professional work can feel unfamiliar

Starting professional work can feel daunting. Many students are unsure what employers expect beyond technical knowledge or academic achievement.

Professional work is not just about knowing a subject or using a tool. It often involves working with others, planning tasks, communicating progress, checking assumptions, solving problems, asking for guidance and understanding how your work affects other people.

At early career levels, you are not expected to know everything. It is normal to receive guidance, have your work reviewed and ask for help when something is unclear or outside your experience.

As you develop, you may be trusted to work with more independence, handle more varied tasks and contribute more to team outcomes. SFIA gives you a way to understand this progression.

Professional work is usually not a solo test

Academic work often asks you to show what you can do as an individual. You study, complete assignments and sit exams so your own knowledge and ability can be assessed.

Professional work is different. In most workplaces, you are not expected to prove yourself by working alone or hiding uncertainty. You are expected to contribute to shared outcomes.

This means asking for help is often part of working responsibly. If you are unsure about a task, a decision, a tool or a deadline, colleagues and managers will usually prefer you to ask early. This helps the team avoid wasted effort, missed expectations or avoidable mistakes.

The same applies when something has gone wrong. A common early-career reaction is to try to fix a mistake before anyone notices, or to hope the problem will disappear. In professional work, it is usually better to raise mistakes, risks or blockers early. This gives the team more options and reduces the chance of a small issue becoming a bigger problem.

At early career levels, good professional behaviour often includes:

• checking that you understand the task
• asking questions when something is unclear
• sharing progress before a problem becomes urgent
• raising mistakes, risks or obstacles early
• using feedback to improve your work
• recognising when something is outside your current experience
• contributing to the team’s result, not only your own task.

SFIA can help make these expectations clearer. It shows that professional capability includes how you communicate, collaborate, plan, solve problems, learn and take responsibility.

The two sides of SFIA

SFIA describes capability through two connected parts. Together, the professional skills and these generic attributes give a fuller picture of what is expected as you take on more responsibility.

Professional skills

Professional skills describe the type of work being done. Examples include software development, testing, data analysis, service support, business analysis, cybersecurity, project support and many others.

You can use SFIA professional skills to explore different kinds of work and understand how they are described in industry.

Generic attributes and behavioural factors

Generic attributes (the core expectations that apply to every role) describe the level of responsibility involved in work. They include:

• Autonomy: How much independence and trust you have to manage your own work. (At first, you will receive clear directions and have your work closely reviewed; over time, you’ll be trusted to choose your own approach and take responsibility for the final results.)
• Influence: The reach and impact of your decisions and actions. (At first, your focus will be on completing your own tasks and working well with your immediate teammates; over time, your ideas and decisions will begin to guide others and affect people outside your team.)
• Complexity: The variety and difficulty of the tasks you handle. (At first, you might work on small, straightforward tasks; over time, you’ll tackle larger, more complicated projects.)
• Knowledge: How deeply you need to understand a topic, and how well you can use that understanding to help others.
• Business skills & Behavioural factors:  They describe how people work effectively, including collaboration, communication, planning, problem-solving, adaptability, learning and development, decision-making, openness to using new technologies (digital mindset) and security, privacy and ethics.

For many students, these behaviours may be the best place to start. Even if you have limited professional experience, you may already have examples from coursework, group projects, volunteering, part-time work, student societies, placements or personal projects.

Start with how you work

You may not yet have strong evidence of professional experience in a specific role. That is expected.

However, you may already have evidence of how you approach work. For example:

• collaborating with others in a group project
• planning your work to meet deadlines
• explaining technical ideas in a report or presentation
• solving problems when something does not work as expected
• learning a new method, tool or concept
• adapting when requirements or priorities change
• handling data, privacy or AI tools responsibly
• asking for feedback and using it to improve your work.
• asking for guidance when something was unclear
• checking assumptions before continuing with a task
• sharing progress, risks or obstacles with others
• contributing to a shared outcome rather than only completing your own part.

These are not “soft” extras. They are part of professional effectiveness. SFIA helps make them visible.

Explore professional skills

Once you have started to describe how you work, you can explore SFIA professional skills.

You might begin by asking:

• what kind of work have I tried, studied or observed?
• which SFIA skills sound closest to that work?
• what tasks or activities have I actually performed?
• what methods, tools or standards did I use?
• how much guidance did I need?
• what evidence do I have?
• what would I like to develop next?

You do not need to claim that you fully meet a SFIA skill level. SFIA can still help you recognise relevant experience and understand what further development may look like.

Knowledge, skill and competency

SFIA can also help you understand the difference between knowledge, skill and competency.

Knowledge means you understand a topic.

• You may show this through study, reading, exams, discussion or explanation.

Skill means you can apply knowledge to perform tasks.

• You may show this through coursework, labs, projects, simulations or supervised activities.

Competency means you can apply knowledge and skills reliably in a professional context, with responsibility for outcomes.

• This is usually shown through real work, such as placements, apprenticeships, internships, employment, volunteering or other situations where there are real stakeholders (the people affected by your work) and consequences.

These are connected, but they are not the same. Academic study can build knowledge and skill. Work experience can help you build evidence of competency.

Using SFIA to describe your experience

SFIA can help you describe your experience more clearly.

Instead of only saying:

I worked on a group project.

You might explain:

I collaborated with others to plan tasks, agree responsibilities, solve problems and present the final outcome.

Instead of only saying:

I used Python.

You might explain:

I developed, tested and improved software components using agreed requirements and feedback.

Instead of only saying:

I helped with testing.

You might explain:

I prepared test cases, recorded results, reported issues and reflected on how testing improved the quality of the product.

This kind of language helps employers understand what you did, how you worked and what you learned.

A simple way to start

Choose one piece of experience. This might be a coursework project, placement task, internship, part-time job, volunteering role, society activity or personal project.

Write down:

• what was the situation?
• what were you asked to do?
• what did you personally do?
• who did you work with?
• what guidance or support did you need?
• what decisions did you make?
• what problems did you solve?
• what was the result?
• what did you learn?
• what might you do differently next time?

Then look at SFIA and consider:

• which behavioural factors does this demonstrate?
• which professional skills might it relate to?
• what evidence would help you explain it to someone else?
• what would be a useful next development step?

Using SFIA to plan your development

SFIA can help you think beyond a single assignment, module or job application.

You can use it to:

• explore roles and career areas
• identify professional skills that interest you
• understand the behaviours employers value
• recognise evidence you already have
• identify gaps in your experience
• plan what to practise next
• prepare examples for applications and interviews.

A simple development cycle is:

1. explore the skills and behaviours relevant to your interests
2. compare them with your current experience
3. choose one or two development goals
4. look for opportunities to practise
5. record evidence and reflect on what you learned.

This can support your professional development alongside your academic development.

For educators, careers teams and placement staff

SFIA can provide a common language for discussing employability, professional development and work-based learning.

It can help students connect their academic learning with the expectations of professional work. It can also support learning from your experiences (reflective practice), placement preparation, apprenticeship development, portfolio evidence and career conversations.

SFIA does not replace academic judgement, employer judgement or professional assessment. It provides a structured reference point that can help students, educators and employers talk about skills, behaviours, responsibility and development in a consistent way.

Next steps

You can start by exploring:

• the SFIA professional skills
• the SFIA levels of responsibility
• the generic attributes
• the behavioural factors
• examples of how SFIA is used in placements and apprenticeships.

You do not need to understand the whole framework at once. Start with one example of your own experience and use SFIA to describe what it shows.