Technical Software Engineering Interview Questions
Technical Software Engineering Interview Questions
Technical Software Engineering Interview Questions
Q1. Describe the process you have for a programming task, from
requirements to delivery.
The software development process or life cycle is a structure applied to the
development of a software product. There are several models for such processes (such
as the agile method), each describing approaches to a variety of tasks or activities that
take place during the process.
Having some scripting experience with Perl or Python is also a big plus.
Q4. What is the software development life cycle? What are the
differences between them?
SDLC or the Software Development Life Cycle is a process that produces software with
the highest quality and lowest cost in the shortest time. SDLC includes a detailed plan
for how to develop, alter, maintain, and replace a software system.
SDLC involves several distinct stages, including planning, design, building, testing, and
deployment. Popular SDLC models include the waterfall model, spiral model, and Agile
model.
Q5. What has your experience been like as part of an Agile software
development process, if any?
Agile software development refers to software development methodologies centered
around the idea of iterative development, where requirements and solutions evolve
through collaboration between self-organizing cross-functional teams. The ultimate
value in Agile development is that it enables teams to deliver value faster, with greater
quality and predictability, and greater aptitude to respond to change.
Q6. What is responsive design? What is the difference between fixed and
fluid layouts?
1. Responsive website design. Websites that are built with responsive design use media
queries to target breakpoints that scale images, wrap text, and adjust the layout so that
the website can ‘shrink to fit’ any size of screen, such as the difference between
desktops and mobiles.
2. Fluid website design. Websites that are built with fluid design use percentages as
relative indicators for widths.
3. Fixed design. Websites that are built using fixed design rely on fixed pixel widths. While
a design with fixed dimensions can sometimes be the quickest way to get up and
running, it’ll provide a less user-friendly experience across multiple devices.
Usually, this means viewing the application as a whole and as their component pieces,
then setting priorities in any areas that you think are more at risk than others. Tests are
then conducted to confirm the functionality, and the detected defects are subsequently
recorded. These defects can then be prioritized depending on their impact and severity.