Technology1 min read

Questions Worth Asking as a New Developer

By · Published by Everything Blog

In short

New software engineers can optimize their daily productivity by asking teammates about specific editor extensions and debugging aids that eliminate slow, repetitive tasks. Seeking guidance on non-technical resources like payroll, benefits, and cross-departmental software creates an essential internal network early on. Furthermore, clarifying whether initial milestones involve handling simpler stories or participating in meetings helps engineers align personal ambitions with team realities. Probing the reasons behind existing coding patterns also uncovers technical limitations the team resolved in prior projects.

Key points

  • Identifying specific tooling preferences from colleagues immediately accelerates day-to-d…: Identifying specific tooling preferences from colleagues immediately accelerates day-to-day software development workflows.
  • Establishing clear performance expectations early on provides realistic milestones while…: Establishing clear performance expectations early on provides realistic milestones while adjusting to a team codebase.
  • Inquiring into established development patterns uncovers the historical reasons and techn…: Inquiring into established development patterns uncovers the historical reasons and technical constraints behind current codebases.

Sources checked by our analysis pipeline: 1

So, you’ve just been hired as a new software developer. When I started, one of the most common pieces of advice I received was to ask lots of questions. There’s plenty to learn as a new developer, and asking questions is a great way to build your knowledge.

What I heard less often, though, was which questions to ask. The advice was always, “Ask lots of questions,” but rarely, “Here are some useful questions to get you started.”

Now, about four and a half months into my role, I’ve found a few questions that have been especially helpful—and a few I wish I’d asked sooner.

What tools do you use?

The answer depends on where you work, but your company likely provides a core set of tools you’ll use regularly. As you settle into your role, you’ll learn how those tools fit into your team’s day-to-day work.

Your coworkers may also use additional tools they’ve discovered through experience. An editor extension might help them navigate the codebase, or a debugging tool might make it easier to investigate an issue. These…

Technology