Look Beyond the Job Description
Congratulations on getting the interview. You have read the job description, which sounds like a perfect list of responsibilities and requirements. But here is a secret every experienced professional knows: the job description is often more of a marketing
document than a manual. It is the company’s best attempt to summarise a complex role into a few bullet points. The reality of any job is shaped by unwritten rules, team dynamics, and company culture. Your first job is your launchpad; it sets the tone for your entire career. Accepting a role that sounds prestigious but is a poor fit for your working style can lead to frustration and burnout. On the other hand, a role at a lesser-known company that allows you to build foundational skills can be a much better strategic move. To build a career you love, you must first understand what you are signing up for. The interview is not just about the company evaluating you; it is your opportunity to evaluate them.
Are You a Builder or a Maintainer?
One of the most important distinctions to understand is whether a role is primarily about creation or maintenance. A 'builder' role is focused on creating something new. This could be launching a new product, starting a new marketing channel, coding a new feature, or establishing a process where none existed. These roles are often found in startups or new teams within larger companies. They require a high tolerance for ambiguity, a proactive mindset, and the ability to work with minimal guidance. A 'maintainer' role, in contrast, is about optimising, managing, and improving existing systems. This might involve managing existing client accounts, ensuring the smooth operation of a software platform, or refining a well-established marketing process. These roles demand attention to detail, consistency, and a knack for problem-solving within a defined structure. Neither role is inherently better, but they suit different personalities and career goals. Knowing which you prefer is a critical piece of self-awareness.
Specialist vs. Generalist Trajectory
Another crucial aspect of a role is whether it will set you on a specialist or a generalist path. A specialist role encourages you to go deep into a single domain. Think of a cybersecurity analyst, a machine learning engineer, or a tax accountant. The value you provide comes from your deep, focused expertise in one area. This is a great path if you have a clear passion and want to become the go-to expert. A generalist role, often found in operations, project management, or smaller startups, requires you to wear many hats. You might handle a bit of marketing, a bit of finance, and a bit of client management all in one day. This path builds a broad skill set and makes you adaptable, preparing you for future leadership roles where you need to understand how different parts of a business connect. Ask about the career paths of previous people in the role. Did they move up to manage the same function (specialist) or move laterally into different departments (generalist)?
How to Ask the Right Questions
Understanding these distinctions is one thing; getting the answers during an interview is another. You need to ask smart, insightful questions without sounding demanding or critical. Instead of asking, “Is this a builder or maintainer role?”, try phrasing it differently. You could ask, “Could you walk me through a typical project a person in this role would own from start to finish?” or “What are the key priorities for this role in the first six months?” To understand the specialist versus generalist nature, you could ask, “What does the growth trajectory for this position look like? What skills would I need to develop to be successful long-term here?” For team dynamics, ask, “Could you describe the team I will be working with and how we would collaborate on a daily basis?” These questions show you are thinking strategically about your contribution and your career, which is a trait all good employers look for.
