The lack of skilled IT workers is hurting the deployment of emerging technology, according to a new survey from Gartner. In areas from cloud to cybersecurity, this crisis is expected to last for years to come.
The Web is full of good advice for software engineers looking for a job. You should have great communication skills, show an ability to learn, be a good teammate, bring a strong portfolio, build business domain expertise, and exude enthusiasm. These are important, and they will help get you a job at the right company.
But how do you decide which company is the right one for you?
Great engineers have an understandable bias to work for brand name tech companies or Series A startups. But they consistently skip important questions they should be asking a company as they consider whether to take a role or not.
Here are four questions all IT professionals should ask before deciding to take a new role (or stick with the one you’re in):
Professional career development happens in a hyper-growth environment. High-growth companies are constantly building new products, hiring new developers and establishing new teams.
Revenue growth, especially in technology, correlates highly with headcount growth and both correlate with opportunities to grow skills and lead. Some engineers will seek out stability and a low-stress environment, but for professional development, choose a high-growth company.
Companies run their technology cycles through planning, coding, and support phases as they build and maintain products.
Many rely on dedicated product and marketing teams who scope a problem and send detailed instructions to engineering teams to code. That arrangement can be effective, but it limits access to the full product development cycle and starves engineers of critical product-building experience.
If the engineering teams responsible for custom engineering work start seeing a spike in requests to integrate data from one platform into other platforms; their mandate as engineers would be to look for patterns in custom work and then turn those builds into platform capabilities.
In the best companies, a quick feedback loop between customers and developers leads to better development and better products. Being close to customers will make you a better engineer by helping you see how to build and what to build.
This will help you build much of the engineering organization around customer pulses. When you know what’s working and what’s not, you can build faster and build better. Proximity to users and customers is the fastest way to build. And, as important, it helps you see the impact of your product.
These questions are easier to answer as an intern or a new hire, but they’re perhaps the most important for a developer who wants to progress in their career.
You’re going to spend more waking hours with colleagues than with anybody else. Do you enjoy spending time with them, and do they bring out your best?
You should be learning new technical and business skills on every project.
You should be able to see how your projects are helping the company be successful. And you should receive credit for good work.
Caring about the product is a huge intrinsic motivator. If you don’t have it now, can you find one in the company that is? (Not universally applicable, but can you find fulfillment in the work itself and the challenge.)
A company is hiring you to do great work and build great products. But you’re hiring a company to teach skills and provide career growth. Before you hire one, make sure you ask the right questions.