10 answers
Emeric
Student
Upper Marlboro, Maryland
4
Questions
Asked
1181 views
What other responsibilities are involved for a software developer, apart from the technological responsibilities and skills, when (for example) working for a company? What are the skills required for these responsibilities (social/communication skills, teamwork skills, work ethic, etc.)?
I am a 10th grader in a dual enrollment program for IT. I am interested in becoming a software developer in the future. I am rather decent at using technology, and I learn more everyday. However, I am rather lacking in other skills. I am a large introvert and typically don't talk to people I don't already know, I find teamwok more difficult than working alone, and I admittedly could have a better work ethic. I tend to procrastinate a lot. Despite these setbacks, I am ready and willing to learn and get better at these skills to better do the thing I am passionate about. I would find it helpful to get some advice from experienced professionals on the topic.
Login to comment
10 answers
Sanjana Tiwari
Investment Advisory and Management Consulting
3
Answers
England, England, United Kingdom
Updated
Sanjana’s Answer
Technology / software engineering is one of the few areas where you are allowed to grow as a technical specialist. While people skills and work ethics are important requirements to be successful in most work environments, software development is one area where these skills matter the least. What matters most is your learnability and keeping pace with the new technologies and growing as a developer. Having said that, not all countries facilitate growth in this specialist track. Countries where real innovation is happening are best for a career like this. Where tech product maintenance and services are more prominent, growth happens with people management, and hence, as you grow, the softer skills start gaining more importance.
Erica Kinch
Sales Specialist - 10 year retail sales management professional - Computer Science, Data
5
Answers
Horseheads, New York
Updated
Erica’s Answer
Working as a software developer involves more than just coding. Here are some key areas to focus on:
Communication - You'll often explain your work, ask questions, and write updates or documentation. Clear and concise writing is more important than talking a lot.
Teamwork - While you won't always work in groups, you will share code, review others' work, and ensure your part fits the project. Teamwork in tech is organized and focused, which suits many introverts.
Time management and work habits - To avoid procrastination, break tasks into smaller steps, set mini-deadlines, and seek help early if needed. These are skills you can develop.
Adaptability - Be ready to adjust as requirements change, bugs appear, and plans shift. Staying flexible is crucial.
Openness to feedback - Code reviews are common. Accept feedback, use it to improve, and keep moving forward. It's about getting better, not being perfect.
You don't need to be outgoing to succeed. Focus on clear communication, good habits, and a willingness to learn. Reflecting on your weaknesses helps you grow into a strong developer.
Communication - You'll often explain your work, ask questions, and write updates or documentation. Clear and concise writing is more important than talking a lot.
Teamwork - While you won't always work in groups, you will share code, review others' work, and ensure your part fits the project. Teamwork in tech is organized and focused, which suits many introverts.
Time management and work habits - To avoid procrastination, break tasks into smaller steps, set mini-deadlines, and seek help early if needed. These are skills you can develop.
Adaptability - Be ready to adjust as requirements change, bugs appear, and plans shift. Staying flexible is crucial.
Openness to feedback - Code reviews are common. Accept feedback, use it to improve, and keep moving forward. It's about getting better, not being perfect.
You don't need to be outgoing to succeed. Focus on clear communication, good habits, and a willingness to learn. Reflecting on your weaknesses helps you grow into a strong developer.
Teklemuz Ayenew Tesfay
Electrical Engineer, Software Developer, and Career Mentor
517
Answers
Ethiopia
Updated
Teklemuz Ayenew’s Answer
Software developers need a mix of technical expertise and soft skills to work effectively, meet deadlines, and deliver reliable products. Clear communication is essential for explaining feasibility, timelines, and potential challenges to clients and teammates, and visual aids such as diagrams or prototypes can enhance understanding. As an introvert, I prefer writing to speaking, and it has taken me many months to adapt to interacting with new people and team members. I can improve by preparing notes, sending clear emails, summarizing ideas concisely, and practicing active listening.
Collaboration is equally important, even when developers focus on individual tasks. Sharing progress, reviewing code, and coordinating with teammates keeps projects on track. While I often find teamwork more challenging than working alone, I have gradually learned to contribute effectively by starting with small collaborations, observing communication styles, engaging in focused pair programming, documenting work clearly, and offering thoughtful feedback. These strategies allow introverted developers like me to participate meaningfully in team efforts.
Time management, problem-solving, attention to detail, and adaptability are also vital for meeting deadlines and handling changing requirements. I sometimes struggle with procrastination and work ethic, but I am ready to improve by breaking tasks into smaller steps, using calendars or to-do lists, practicing coding exercises, and reflecting on mistakes. Emotional intelligence, self-awareness, and openness to feedback help developers respond constructively to setbacks, and by combining structured communication, incremental collaboration, organized task management, and methodical problem-solving, I am confident I can grow into a well-rounded software developer.
Collaboration is equally important, even when developers focus on individual tasks. Sharing progress, reviewing code, and coordinating with teammates keeps projects on track. While I often find teamwork more challenging than working alone, I have gradually learned to contribute effectively by starting with small collaborations, observing communication styles, engaging in focused pair programming, documenting work clearly, and offering thoughtful feedback. These strategies allow introverted developers like me to participate meaningfully in team efforts.
Time management, problem-solving, attention to detail, and adaptability are also vital for meeting deadlines and handling changing requirements. I sometimes struggle with procrastination and work ethic, but I am ready to improve by breaking tasks into smaller steps, using calendars or to-do lists, practicing coding exercises, and reflecting on mistakes. Emotional intelligence, self-awareness, and openness to feedback help developers respond constructively to setbacks, and by combining structured communication, incremental collaboration, organized task management, and methodical problem-solving, I am confident I can grow into a well-rounded software developer.
CHIRANJEEVI Tati
Telecom Software Developer
3
Answers
Ottawa, Ontario, Canada
Updated
CHIRANJEEVI’s Answer
Coding is a key part of being a software developer, but there's so much more to it. Developers also create documentation, give technical presentations, and constantly learn new things. Good time management is another important skill that can help you stand out. Many developers are introverts, so most communication is written, and teamwork tends to be calm and organized. You can learn these skills step by step. It's normal to have concerns, but small habits can help you overcome them. You're already ahead of many because you're thinking about this early and are eager to improve. Keep going, and you'll do great!
Greetings, thank you for your response. It is very helpful and I'll be able to refer back to it in the future. Do you have any specific exercises or means of doing things that could help me improve my weak points?
Emeric
Andras C
Software Engineering
5
Answers
Budapest, Hungary
Updated
Andras’s Answer
Great that you are willing to prepare for non-technical aspects as well. No worries, most of the tasks of a developer can be performed on your own and anyway, majority of software engineers are rather introverts. Still, most of the projects are executed by teams and as a team member time to time you will need to speak up a bit to report your progress or ask for help. But a team usually means 6-10 people with whom you will be in a close and friendly relationship, so it is no stress to discuss with them. I hope this helps, but feel free to comment in case you have further questions.
cassandra Harris
Social / Emotional learning Teacher
38
Answers
Tucson, Arizona
Updated
cassandra’s Answer
What responsibilities do software developers have beyond technical skills?
Software developers do much more than just write code. When working for a company, many responsibilities involve communication, collaboration, and professionalism. The good news is that these skills are learnable, and many successful developers started out exactly the way you describe.
1. Communication (More important than most people expect)
Developers regularly need to:
Explain technical ideas to non-technical people
Ask clarifying questions about requirements
Write clear emails, messages, and documentation
Participate in meetings (sometimes short updates, sometimes discussions)
Skills needed:
Clear written communication
Basic speaking confidence (not public speaking)
Asking questions when something is unclear
👉 Important: You do NOT have to be outgoing or talkative. Many developers are introverts. What matters is being clear, respectful, and honest.
2. Teamwork & Collaboration
Most software is built by teams. This includes:
Working with other developers
Collaborating with designers, testers, and managers
Reviewing other people’s code and receiving feedback
Skills needed:
Listening
Respecting different ideas
Giving and receiving constructive feedback
Compromising when needed
👉 If teamwork feels hard, that’s normal. Team skills improve with practice, especially in structured environments like group projects.
3. Time Management & Work Ethic
Developers are expected to:
Meet deadlines
Break large tasks into smaller ones
Make steady progress, even when motivation is low
Communicate early if something is taking longer than expected
Skills needed:
Self-discipline
Planning and prioritizing
Avoiding procrastination
👉 Procrastination is extremely common—even among professionals. The key is learning systems that help you start.
4. Problem Ownership & Responsibility
Developers are often responsible for:
Fixing bugs they introduce
Supporting their code after it’s released
Learning new tools as technology changes
Skills needed:
Accountability
Willingness to learn
Patience and persistence
5. Professionalism
This includes:
Being reliable
Showing up on time
Respecting others
Handling feedback maturely
Skills needed:
Emotional regulation
Respectful communication
Growth mindset
Advice Based on Your Situation
Being an introvert
Introversion is NOT a disadvantage in software development.
Many excellent developers are quiet, thoughtful, and observant.
Focus on:
Writing clearly (emails, chat messages, documentation)
Preparing what you want to say before meetings
Speaking up when it affects your work (this gets easier with time)
Struggling with teamwork
Start small:
Join small group projects
Pair program with one person
Contribute to open-source projects online (low-pressure teamwork)
Teamwork is a skill, not a personality trait.
Improving work ethic & procrastination
Try practical tools:
Break tasks into very small steps
Use timers (Pomodoro method)
Set daily goals instead of big ones
Reward progress, not perfection
Consistency matters more than motivation.
What experienced developers wanted me to share with you
“Nobody starts out great at everything. Technical skills, communication, and discipline are all learned over time. What matters most is your willingness to improve.”
Your self-awareness and honesty already put you ahead of many people.
What you can do right now (as a 10th grader)
Practice explaining your code in simple terms
Work on small team projects
Use planners or task apps to manage deadlines
Ask for feedback and apply it
Keep learning: technology changes, but good habits last
Final encouragement
You do not need to become a different person to succeed as a software developer. You just need to build habits, communication skills, and confidence over time, and you’ve already taken the first step by asking these questions.
Software developers do much more than just write code. When working for a company, many responsibilities involve communication, collaboration, and professionalism. The good news is that these skills are learnable, and many successful developers started out exactly the way you describe.
1. Communication (More important than most people expect)
Developers regularly need to:
Explain technical ideas to non-technical people
Ask clarifying questions about requirements
Write clear emails, messages, and documentation
Participate in meetings (sometimes short updates, sometimes discussions)
Skills needed:
Clear written communication
Basic speaking confidence (not public speaking)
Asking questions when something is unclear
👉 Important: You do NOT have to be outgoing or talkative. Many developers are introverts. What matters is being clear, respectful, and honest.
2. Teamwork & Collaboration
Most software is built by teams. This includes:
Working with other developers
Collaborating with designers, testers, and managers
Reviewing other people’s code and receiving feedback
Skills needed:
Listening
Respecting different ideas
Giving and receiving constructive feedback
Compromising when needed
👉 If teamwork feels hard, that’s normal. Team skills improve with practice, especially in structured environments like group projects.
3. Time Management & Work Ethic
Developers are expected to:
Meet deadlines
Break large tasks into smaller ones
Make steady progress, even when motivation is low
Communicate early if something is taking longer than expected
Skills needed:
Self-discipline
Planning and prioritizing
Avoiding procrastination
👉 Procrastination is extremely common—even among professionals. The key is learning systems that help you start.
4. Problem Ownership & Responsibility
Developers are often responsible for:
Fixing bugs they introduce
Supporting their code after it’s released
Learning new tools as technology changes
Skills needed:
Accountability
Willingness to learn
Patience and persistence
5. Professionalism
This includes:
Being reliable
Showing up on time
Respecting others
Handling feedback maturely
Skills needed:
Emotional regulation
Respectful communication
Growth mindset
Advice Based on Your Situation
Being an introvert
Introversion is NOT a disadvantage in software development.
Many excellent developers are quiet, thoughtful, and observant.
Focus on:
Writing clearly (emails, chat messages, documentation)
Preparing what you want to say before meetings
Speaking up when it affects your work (this gets easier with time)
Struggling with teamwork
Start small:
Join small group projects
Pair program with one person
Contribute to open-source projects online (low-pressure teamwork)
Teamwork is a skill, not a personality trait.
Improving work ethic & procrastination
Try practical tools:
Break tasks into very small steps
Use timers (Pomodoro method)
Set daily goals instead of big ones
Reward progress, not perfection
Consistency matters more than motivation.
What experienced developers wanted me to share with you
“Nobody starts out great at everything. Technical skills, communication, and discipline are all learned over time. What matters most is your willingness to improve.”
Your self-awareness and honesty already put you ahead of many people.
What you can do right now (as a 10th grader)
Practice explaining your code in simple terms
Work on small team projects
Use planners or task apps to manage deadlines
Ask for feedback and apply it
Keep learning: technology changes, but good habits last
Final encouragement
You do not need to become a different person to succeed as a software developer. You just need to build habits, communication skills, and confidence over time, and you’ve already taken the first step by asking these questions.
Clayton Martin
Computer Engineer
4
Answers
Austin, Texas
Updated
Clayton’s Answer
Software development has come a long way over the years. Today, working well with your team is really important. Focus on building strong communication skills, especially being a good listener. It's also important to manage your time wisely. Learn to tell the difference between tasks that are urgent and those that are truly important. Remember, urgent tasks aren't always as important as those with later deadlines.
Chris Maertz
Partner Software Sales
4
Answers
Milwaukee, Wisconsin
Updated
Chris’s Answer
My answers builds on all the great advice above. It is always best to reframe the way you think about your role and ask the question of "What is the most important thing for our company?" Is it to sell more widgets? Provide better service? Improve the quality of life for our constituents? Etc. Once you have an idea of what the company exists to do, find ways to align your work to those goals. Networking with others outside of your group is a fantastic way to accomplish this. Lead with curiosity, reach out to others and ask if you can learn about their role in the company and try to tie your work to their work, and to the overall company goals. As you start to understand the entire machine of the organization you work for, you'll naturally start to think like a team player and operate accordingly. This will show up in all the ways you work and will benefit you greatly.
Rebecca Tang
Banking
2398
Answers
Hong Kong
Updated
Rebecca’s Answer
Thank you for your question. I am glad to know that you have interest in software development.
Below are my suggestions:
1. There are many different types of software developers,eg Web Developer, ERP developer, apps developer, AI developer, System Developer, etc. Each have specific knowledge domain and programming language. You san find out more different programming streams online.
2. Find out more on different types of developers and determine what you have interest
3. Learn more different programming languages and practice programming
4. Attend the information session hosts by computer science department of colleges
5. Explore the entry criteria of computer science courses in colleges
Hope this helps! Good luck!
May Almighty God bless you!
Below are my suggestions:
1. There are many different types of software developers,eg Web Developer, ERP developer, apps developer, AI developer, System Developer, etc. Each have specific knowledge domain and programming language. You san find out more different programming streams online.
2. Find out more on different types of developers and determine what you have interest
3. Learn more different programming languages and practice programming
4. Attend the information session hosts by computer science department of colleges
5. Explore the entry criteria of computer science courses in colleges
Hope this helps! Good luck!
May Almighty God bless you!
Ann C
Learning & Development, Software, Administrative, Tech, Systems
52
Answers
Atlanta, Georgia
Updated
Ann’s Answer
Here’s a clear breakdown of the day-to-day responsibilities beyond coding.
1. Planning & Requirements Gathering
Developers frequently:
• Meet with product managers or clients to clarify requirements
• Break features into tasks
• Estimate time and complexity
• Help refine user stories in Agile environments
Why it matters: Good planning avoids rework and reduces bugs later.
2. Testing & QA (Quality Assurance)
Even with a dedicated QA team, developers still:
• Write and run unit tests
• Perform integration testing
• Reproduce bugs reported by users
• Verify fixes before release
Goal: Ensure changes won’t break anything else.
Debugging & Issue Investigation
A big part of the job is:
• Tracking down the root cause of issues
• Reviewing logs or monitoring dashboards
• Analyzing unexpected behavior
• Studying error reports or crash logs
Debugging can easily take more time than coding.
4. Code Review (Reviewing Others’ Work)
Developers review teammates’ code to:
• Ensure consistency
• Maintain quality
• Find bugs or design issues
• Share knowledge and best practices
This is critical in team environments.
5. Meetings & Collaboration
Typical meetings include:
• Daily stand-up
• Sprint planning
• Sprint retrospectives
• Design/architecture discussions
• Cross-functional collaboration with QA, DevOps, UX, support, etc.
Developers spend a lot of time communicating.
6. System & Architecture Design
Especially in senior roles, developers spend time:
• Designing new features
• Making technical decisions
• Choosing technology stacks
• Diagramming system interactions
• Ensuring scalability and security
It’s strategic and collaborative.
Documentation
Developers create:
• API docs
• README files
• Internal technical documentation
• Comment explanations for complex logic
• Postmortem reports after incidents
Documentation keeps the team aligned.
Supporting Production Systems
Often called DevOps or on-call duties:
• Monitoring systems for performance or errors
• Responding to outages
• Investigating slowdowns
• Deploying updates
• Maintaining CI/CD pipelines
This ensures the software keeps working after release.
9. Assisting Customer Support or Internal Teams
Developers sometimes help:
• Explain issues to support teams
• Analyze customer-reported problems
• Provide technical insight to stakeholders
• Clarify expected behavior
Especially at smaller companies, this is common.
10. Refactoring & Technical Maintenance
Ongoing work that isn’t feature development:
• Cleaning up old code
• Updating dependencies
• Optimizing performance
• Improving architecture
• Reducing tech debt
This keeps the codebase healthy.
11. Continuous Learning
Technology changes constantly, so developers often:
• Try new tools or frameworks
• Read documentation
• Experiment with new languages
• Watch tutorials or attend workshops
This learning usually happens on the job.
12. Mentoring & Team Support
Senior developers help juniors by:
• Pair programming
• Explaining architecture
• Giving guidance on best practices
• Helping plan career goals
Mentorship strengthens the whole team.
How a Developer’s Day Typically Breaks Down
(Varies by company, but a common pattern)
• 30–60% Coding
• 10–20% Meetings
• 10–20% Debugging
• 10–15% Testing
• 5–10% Code reviews
• 5–10% Documentation, learning, communication
Best of luck!
1. Planning & Requirements Gathering
Developers frequently:
• Meet with product managers or clients to clarify requirements
• Break features into tasks
• Estimate time and complexity
• Help refine user stories in Agile environments
Why it matters: Good planning avoids rework and reduces bugs later.
2. Testing & QA (Quality Assurance)
Even with a dedicated QA team, developers still:
• Write and run unit tests
• Perform integration testing
• Reproduce bugs reported by users
• Verify fixes before release
Goal: Ensure changes won’t break anything else.
Debugging & Issue Investigation
A big part of the job is:
• Tracking down the root cause of issues
• Reviewing logs or monitoring dashboards
• Analyzing unexpected behavior
• Studying error reports or crash logs
Debugging can easily take more time than coding.
4. Code Review (Reviewing Others’ Work)
Developers review teammates’ code to:
• Ensure consistency
• Maintain quality
• Find bugs or design issues
• Share knowledge and best practices
This is critical in team environments.
5. Meetings & Collaboration
Typical meetings include:
• Daily stand-up
• Sprint planning
• Sprint retrospectives
• Design/architecture discussions
• Cross-functional collaboration with QA, DevOps, UX, support, etc.
Developers spend a lot of time communicating.
6. System & Architecture Design
Especially in senior roles, developers spend time:
• Designing new features
• Making technical decisions
• Choosing technology stacks
• Diagramming system interactions
• Ensuring scalability and security
It’s strategic and collaborative.
Documentation
Developers create:
• API docs
• README files
• Internal technical documentation
• Comment explanations for complex logic
• Postmortem reports after incidents
Documentation keeps the team aligned.
Supporting Production Systems
Often called DevOps or on-call duties:
• Monitoring systems for performance or errors
• Responding to outages
• Investigating slowdowns
• Deploying updates
• Maintaining CI/CD pipelines
This ensures the software keeps working after release.
9. Assisting Customer Support or Internal Teams
Developers sometimes help:
• Explain issues to support teams
• Analyze customer-reported problems
• Provide technical insight to stakeholders
• Clarify expected behavior
Especially at smaller companies, this is common.
10. Refactoring & Technical Maintenance
Ongoing work that isn’t feature development:
• Cleaning up old code
• Updating dependencies
• Optimizing performance
• Improving architecture
• Reducing tech debt
This keeps the codebase healthy.
11. Continuous Learning
Technology changes constantly, so developers often:
• Try new tools or frameworks
• Read documentation
• Experiment with new languages
• Watch tutorials or attend workshops
This learning usually happens on the job.
12. Mentoring & Team Support
Senior developers help juniors by:
• Pair programming
• Explaining architecture
• Giving guidance on best practices
• Helping plan career goals
Mentorship strengthens the whole team.
How a Developer’s Day Typically Breaks Down
(Varies by company, but a common pattern)
• 30–60% Coding
• 10–20% Meetings
• 10–20% Debugging
• 10–15% Testing
• 5–10% Code reviews
• 5–10% Documentation, learning, communication
Best of luck!