A Day In The Life Of A Software Engineer At Workday
Ryan from Workday explains that a software engineer's day varies based on experience; entry-level engineers focus on "hands-on programming stuff" and learning industry basics, while more senior engineers may move into management or concentrate on "architecture and designing things," delegating the implementation to less experienced engineers. This illustrates how the role evolves from coding-focused to a blend of design, delegation, and potentially people management as a career progresses.
Software Engineering, Coding, Career Development, Management, Architecture
Advizer Information
Name
Job Title
Company
Undergrad
Grad Programs
Majors
Industries
Job Functions
Traits
Ryan Vivian
Software Engineer
Workday
California State University, East Bay
N/A
Computer Science
Technology
Product / Service / Software Development and Management
Honors Student, Scholarship Recipient, Worked 20+ Hours in School, Transfer Student, First Generation College Student
Video Highlights
1. Entry-level software engineers focus on hands-on programming, learning industry basics, documentation, and coding best practices.
2. Career progression offers two paths: management, involving people management and task delegation, or continued software engineering, focusing on architecture and design.
3. Senior software engineers in the technical path design solutions and delegate implementation to junior engineers.
Transcript
What does a day in the life of a software engineer look like?
It kind of depends. If you are just starting out, you'll be doing more hands-on programming and learning the ropes. You'll learn the ins and outs of the industry, like scheduling and documenting, and the basics of coding and best practices.
So you'll be doing a lot of coding in the beginning. As you move up in your career, there are a couple of different paths you can take. You can go into a management career, where you're doing more people management, ensuring people are working on the right things.
Or you can continue with software engineering and programming. If you go on that path, you'll start with actual architecture and designing things, and then directing people. You'll come up with the ideas and say, "This is how we're going to do it." Then you'll hand it off to someone at a lower level, and they'll implement and program it.
Advizer Personal Links