How social background affects opportunities at work

Knowing what you are allowed to ask for

Two new employees begin in similar positions. From the outset, one asks for a mentor, a training budget and a place on a board-level project. The other waits for someone to offer such opportunities because they believe they must first prove their worth. After a year, their paths begin to diverge. This example does not prove that social background shaped this particular story. It does show how familiarity with unwritten rules can become an advantage that is later interpreted as a difference in ambition or confidence. Social background encompasses more than current income. The circumstances in which someone grew up, their parents’ education, access to networks and experience with institutions may all matter. A high earner may still be learning the codes of an environment they are the first in their family to enter. Yet this must not be turned into a uniform profile. People from similar backgrounds differ in experience, personality and ways of working, and their resources change over time. Unwritten rules may concern very ordinary matters: how to speak with a manager, ask for a raise or build relationships outside one’s department. Someone who previously observed similar situations may take these behaviors for granted. Someone else learns them only at work, often through trial and error. The difference does not prove lower ambition or ability. It may reflect unequal access to knowledge about how a particular environment works. At the same time, we should avoid assigning every person a story based on their background. People gain experience in many ways. The organization’s task is to make necessary rules clear, not to guess who ought to know them already.

What is competence, and what is familiarity with the code?

A review by Kish-Gephart and colleagues organizes the links between social class and work across multiple levels of analysis. It helps show that behaviors treated as natural may previously have been learned in particular environments. This does not mean that every confident conversationalist comes from a privileged background. It does mean we should ask what we are actually measuring when we assess “fit,” “maturity” or “leadership potential.” Kish-Gephart et al., 2023. In recruitment, this may concern a person’s self-presentation, familiarity with certain activities or ease when speaking with someone of high status. In everyday work, it may involve readiness to negotiate, ask for resources or treat a manager as a partner in discussion. Some of these behaviors are professionally useful and can be learned. The problem arises when prior familiarity with a code is treated as an innate personal quality and those who learn it later are judged less talented before their actual capabilities have been tested.

Hidden requirements also carry a material cost

An unwritten norm may assume attendance at expensive after-hours events, previously acquired unpaid experience or the ability to relocate without financial security. These may be viable options for some people and real barriers for others. If the organization overlooks the cost, it may interpret non-participation as a lack of commitment. It is therefore worth asking what resources are needed to take advantage of an opportunity and whether the company genuinely provides access to them. This does not require asking employees about their family’s financial history. Rules can be improved without collecting private data: describe costs, provide funding, hold important events during working hours and do not make access to information depend on private gatherings. A review of organizational inequality by Stainback and colleagues reminds us of the role played by company structures and practices. Individual determination operates within particular conditions, not outside them. Stainback et al., 2010. The error occurs when familiarity with an environment’s codes is taken as proof of overall potential. A candidate may use certain references with ease, know the informal conversational style and seem to fit the group. They may indeed have the required skills, but similarity alone is not enough to assess them. Ask which elements of the impression relate to the task and which come from a sense of familiarity. Likewise, a cautious speaking style need not indicate a lack of independent thought. Sound criteria help distinguish problem-solving ability from experience presenting oneself in a particular setting. This remains important after hiring, when informal judgments shape project assignments and access to decision-makers.

How to make the rules accessible

Explain clearly how people express interest in a project, who may request training and how candidates for promotion are selected. Saying “the door is always open” is not enough if only some people know what they can bring through it and when. Good onboarding also explains how to obtain help and communicate aspirations. Success then depends less on whether someone encountered a similar organization earlier through family, friends or prestigious experience. A mentor can help interpret the rules but should not require someone to imitate the dominant group’s entire identity. Useful feedback sounds like this: “Present your recommendation before the details because the audience has limited time.” Less useful is: “You need to sound more like the board.” The first message identifies a behavior and its purpose. The second may conceal a hard-to-define set of preferences about accent, style or confidence that are not necessary to perform the task well.

How to discuss your own needs

An employee can ask about the rules without recounting their entire social history: “How are people selected for these projects?” or “What does readiness for the next level mean in concrete terms?” If they see a financial or organizational barrier, they can describe it in terms of access to the opportunity. They do not have to present themselves as a representative of a group or prove an exceptional history of overcoming obstacles. The organization should be able to answer a question about fair access even when the employee does not want to disclose private context. It can reduce ambiguity by explaining the development process: how project participants are chosen, who makes the decision and what experience is needed for the next role. It also helps to invite questions without suggesting that asking them betrays a lack of sophistication. A mentor or manager can explain context that others learned informally earlier. They should not, however, require someone to abandon their own way of being in favor of a single approved version of professionalism. The aim is access to knowledge and opportunity, not standardized biographies. It is also worth checking whether the cost of informal events excludes some employees. Professional opportunities should not depend solely on willingness to spend money or participate outside agreed working hours.

Unwritten codes can shape careers before anyone recognizes them as part of the system. Making rules explicit and using precise criteria help distinguish competence from prior access to a particular environment. The goal is to broaden people’s opportunities to demonstrate their skills, not assign traits to them on the basis of their background.

Using Empatyzer to discuss unwritten expectations

Empatyzer can help you prepare questions about rules that are obvious to some team members and unclear to others. In Talk to Em about yourself, you can identify an area of uncertainty and determine what information you need to make a professional decision. Talk to Em about a specific person then helps you prepare how to ask your manager about promotion criteria, participation in a project or expectations in a new role. The available profile helps adapt the language; it is not a basis for inferring the other person’s social background. Empatyzer does not reconstruct employees’ life histories or explain inequality solely through personality traits. It can support communication that makes room for questions without shame. Transparency of rules, access to projects and fair assessment of competence still require concrete organizational decisions. The tool helps prepare a conversation about those conditions; it does not create them.