Hi, I'm doing a research paper on Software Engineer and I am required to have an interview as a source. I have a few questions and if they could be answered, that would be great.

1.) What are your regular duties on the job?
2.) What type of training is needed to have a career as a Software Engineer?
3.) What is your salary?
4.) What type of degree is best for a Software Engineer?
5.) Which colleges provide good courses for this field?
6.) What type of environment do you work in?
7.) What are the work hours like?
8.) What do you enjoy about the job?
9.) What do you dislike about the job?
10.) What advice do you have for someone who is curious about a career as a Software Engineer.

Thanks in advance to whoever answers the questions. This will help me a lot.

Dani AI

Generated

This thread has the right starting questions. asked ten clear items and gave concise replies. To make those replies usable as a primary source in a research paper, expand each short answer with context, capture permission to quote, and record the date and region. The notes below convert brief forum replies into interview material that is citable and classroom-ready.

Essential metadata to record with every answer: exact job title and years of experience, company size and industry, geographic region (or "remote"), date of the response, and whether the figure given for pay is base salary or total compensation (bonuses, equity, benefits). Obtain written permission to quote or a stated preference for anonymity. When answers are short (as in 's post), ask for concrete examples and rough percentages so statements can be compared across sources.

Recommended follow-up prompts:

  • For duties: describe a typical week and estimate percent time on coding, meetings, design, testing, review, mentoring, and ops.
  • For training: list specific university courses, internships, bootcamps, certifications, or self-study resources that proved most useful.
  • For salary: give a range, state currency, say whether it is base vs total comp, and give the year/location that number applies to.
  • For degree: explain which degree (CS, Software Engineering, related) prepared the interviewee and which courses mattered most.
  • For colleges: name programs or departments and explain what made them valuable (faculty, internships, co-op, alumni network).
  • For environment/hours: describe team size, development process (agile/scrum), remote/office setup, typical day, and on-call or overtime expectations.
  • For likes/dislikes: give a recent project as an example for each.
  • For advice: suggest concrete first projects, learning milestones, and ways to get internships.

Methodology and reporting notes: include the interview in the Methods section, present verbatim short quotes with date and attribution (or anonymized label if requested), and treat the result as qualitative anecdote rather than a representative statistic. Triangulate claims about pay, job outlook, or degree value with authoritative sources (labor statistics, university pages, salary surveys) and note any differences.

Recommended Answers

All 5 Replies

1. Create and improve (parts of) our software package.
2. You need to be analytical and logical.
3. Although I wouldn't mind stating it, it really depends on your region and experience, I doubt you have any use in knowing that.
4. Don't know what's best. I have a bsc in technical software engineering.
5. Also, very bound to a region.
6. Office, very open, no doors.
7. Floating, as long as I do about 8 hours a day at the end of the month and get the job done.
8. Challenge of finding a solution, or fix.
9. Ad hoc changes.
10. Choose a project and build it. Get someone to act as a customer.

Thanks, but could you please elaborate more?

On what ?

I'm a high school student and I need enough information to draw from to put into my research paper. If you could give more information on each question, it would be very helpful.

So I have to say the same (because the answers are clear and concise) but then in 500+ words per question ? I don't think so.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.