Whether you want to become a go-to problem-solver or a business-minded CTO, your first engineering job is an opportunity to build the skills and habits to get you there.
Source: Builtin – As in all things, the best way to learn is by doing. But longtime engineers Laura Buzek and Brian Campbell still have a few tips.
Buzek is an engineering manager at human resource software company Gusto, where she works on the platform’s integrations with other apps. She encourages new engineers to focus hard on bolstering their technical skills, even if it means saying no to other responsibilities early on.
One way to do that, she said, is wringing all the knowledge you can from code reviews.
“Even if you’re pretty junior yourself, pair with someone who doesn’t have the same skills you have,” she said. “One of the most effective things I’ve seen is someone who knows back-end programming pairing with someone who knows the front end really well, and they can teach each other those skill sets.”
For Campbell, who holds the title of distinguished engineer at identity management company Ping Identity, cultivating excellent communication skills should be a primary focus for early career developers.
“Building and maintaining relationships and being able to have respectful conversations about topics that can be complex, and even charged, is a lot more valuable than I realized early on,” he said.
Tips for success in your first engineering job
- It’s OK to ask a lot of questions. Think of them as investments in future projects.
- Be honest about what you want. Even the small stuff can make a big difference to your fulfillment and productivity.
- Job loyalty can open unexpected doors. Before you start looking for your next move, consider what you could gain by building expertise where you are.
- Consider where your motivation comes from. Are you building a rewarding career — or just a good-looking resume?
- Shake off the side project pressure. Coding at midnight is fine, but not necessary.
- Learn to persuade rather than argue. Showing the technical logic of your idea isn’t always enough.
It’s OK to ask a lot of questions
When a tricky problem arises, asking coworkers for advice is often the fastest path to a solution. However, asking a question means admitting you don’t know, and that can be tough for new hires who want to prove themselves.
If you feel sheepish asking questions, try to think of those questions as investments in future projects, rather than distractions from a current one.
“Don’t hold yourself to such a high standard that you start to think it’s wasting someone else’s time,” Buzek said. “As a junior engineer, that’s time well spent, and it should be treated that way.”
Kicking things off by telling your team member you look up to their work can’t hurt either, Campbell said.
“A lot of people don’t hear that sort of thing a lot, and it can be really fulfilling and a big motivator,” he said. “Knowing someone wants to emulate your work makes you want to give back to that person and help them achieve whatever they’re trying to do. As long as it’s genuine, it can be really powerful.”
If you’ve researched the problem yourself, come up with some preliminary ideas and still feel uncomfortable asking a question, a negative team culture may be to blame.
“If you’re in a space that discourages that energy, maybe find a new one,” Buzek added.
Be honest about what you want
Similarly, staying quiet about what you want at work — whether that’s something big, like a dream role, or something small, like different software tools — doesn’t serve you.
Buzek said she wants her direct reports to come to her with requests that can help them do their jobs better. When they succeed, she succeeds, so going the extra mile to reorient a tech stack or shift some assignments is no sweat.
