top of page
Channing, Full-Stack Software Engineer at Software Company: Advize Career Interview
From college help desk to full-stack software engineer, this career path highlights the power of initiative and continuous learning!
Developing software for internal use propelled a transition into website creation and impactful contributions to a company's bottom line.
Expect a mix of focused coding, team collaboration, and problem-solving that requires both technical skill and clear communication.
While the role offers creative freedom and the satisfaction of building tangible products, navigate potential challenges like frequent meetings and unpredictable workloads by embracing lifelong learning, enjoying the process of coding, and constantly practicing to improve skill.
Advizer Information
Name
Job Title
Company
Undergrad
Grad Programs
Majors
Industries
Job Functions
Traits
Channing Robbins
Full-Stack Software Engineer
Software Company
University of Mississippi
N/A
Computer Science
Technology
Product / Service / Software Development and Management
Watch all of this Advizer's videos below
Career Path Of A Full-Stack Software Engineer At A Software Company
Channing's career path began with a college job at a help desk, assisting students and teachers with software and login issues, which led to a tier two technician role involving computer repair and software installation. The desire to "use [the] actual degree" prompted Channing to create software for internal use during the technician role, which ultimately transitioned career into software development, currently focusing on website creation.
Main Responsibilities Of A Full-Stack Software Engineer At A Software Company
As a Full-Stack Software Engineer, Channing's main responsibilities revolve around "making websites" that are user-friendly with a "decent user interface" that requires less text for explanation. Ultimately, the goal is to develop good and useful software that benefits the company by helping "make money" in addition to assisting with other company needs.
A Day In The Life Of A Full-Stack Software Engineer At A Software Company
A typical day for a full-stack software engineer at Software Company starts with a short team "stand" to discuss progress, plans, and potential roadblocks, followed by focused coding on project tasks, often within two-week "sprints." Depending on the project, coding can range from "adding a functionality to a button" to "making a full website," and is often accompanied by music to aid focus.
Most Important Skills for a Full-Stack Software Engineer at a Software Company
Channing, a Full-Stack Software Engineer, identifies critical thinking and problem-solving as paramount, emphasizing that often projects begin with vague requirements like, "Hey, we just wanna make a website," thus necessitating the ability to find solutions that solve business needs. Furthermore, they state that communication skills are crucial for bridging the gap between developers and non-technical stakeholders, allowing clear explanation of problems in multiple ways.
Favorite Parts of Being a Full-Stack Software Engineer at Software Company
Channing enjoys the tangible, creative aspect of software engineering, particularly front-end development, because of the ability to build something from scratch and see the immediate, visible results of the work: "I made this." The role also offers a degree of independent work, which is appealing because while collaboration is necessary, it's not the sole focus of the day-to-day.
Biggest Challenges Faced By A Full-Stack Software Engineer At A Software Company
Channing, a Full-Stack Software Engineer, finds "having to have meetings and deal with other people all the time" to be the biggest challenge, as they prefer working more independently; the frequency of meetings varies greatly depending on the team and company, ranging from minimal meetings to "meetings for an entire week."
What Type Of Person Thrives In The Software Industry, According To A Full-Stack Software Engineer At Software Company
Channing believes that people who "like to work alone, or at least can work alone" tend to do well in software engineering, particularly early in careers, however, as careers progress, the role shifts from coding to more meetings and planning. Channing prefers coding, indicating that individual preferences can guide career paths within the industry.
What A Full-Stack Software Engineer At A Software Company Wishes They Had Known Before Entering The Software Industry
Channing wishes someone had emphasized the unpredictable nature of the workload as a Full-Stack Software Engineer, specifically the varying degrees of "downtime between projects" which can range from days to months and is useful for learning or refactoring, but also the "very, very short deadlines" that sometimes necessitate rushing. Both of these factors are important to note as one enters the field to become a Full-Stack Software Engineer.
Significant Career Lesson From A Full Stack Software Engineer At A Software Company
Channing, a Full-Stack Software Engineer, believes that the most significant lesson in their career has been "learning new things and being able to apply what you've learned for stuff in the future," emphasizing the importance of enjoying the learning process itself. According to Channing, a refusal to learn and listen to others ultimately "makes things complicated later."
College Experiences That Helped A Full-Stack Software Engineer At A Software Company Succeed
To set up for a successful software engineering career, Channing emphasized the importance of immersing oneself in code through constant practice, by "looking at any piece of code" available and "writing code in general" to understand how things work, with the idea that the more one practices, the better they become and the more enjoyable and educational the process is. Essentially, consistent practice is the key ingredient for mastering software development and building a strong foundation for a future career.
Advizer Personal Links
bottom of page