Experienced Devs

3978 readers

1 users here now

A community for discussion amongst professional software developers.

Posts should be relevant to those well into their careers.

For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:

Logo base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 2 years ago

MODERATORS

[email protected]

150

Senior Devs in huge corps: Do you even code? (programming.dev)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

44 comments fedilink hide all child comments

I have been working at a large bank for a few years. Although some coding is needed, the bulk majority of time is spent on server config changes, releasing code to production, asking other people for approvals, auth roles, and of course tons of meetings with the end user to find out what they need.

I guess when I was a junior engineer, I would spend more time looking at code, though I used to work for small companies. So it is hard for me to judge if the extra time spent coding, was because of me being a junior or because it was a small company.

The kicker, is when we interview devs, most of the interview is just about coding. Very little of it is about the stuff I listed..

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 1 year ago (3 children)

"Managing engineer," here. 4-5 developers of various skill levels report to me at any given time.

My time as a whole is roughly spent like this:

30% paired programming (assisting developers, helping them troubleshoot, static code analysis looking for a bug they can't find, diagramming a project for them to actually implement)
30% administrative (management meetings, performance feedback meetings with my direct reports, weekly one-on-one meetings with my direct reports, approving PTO, etc)
10% personal assignments (some sort of debugging/trouble shooting that requires my experience, or maybe putting presentations together to show off new technologies or some projects that we're working on)
10% pull request review, providing feedback
20% meeting with business stakeholders, gathering requirements, providing estimates, creating agile stories, breaking agile stories into tasks, etc

[–] [email protected] 2 points 1 year ago

This is pretty much what my day looks like (2 years since being promoted to tech lead).

load more comments (2 replies)