Interview with IT Professional
I believe I know how Alice felt in Wonderland; as a matter of fact, I have felt
the same during this one hour interview. Luckily, at the moment, I do not feel the
same, as Mr. Karim (the interviewee) explained business-technical terms related
to his work in an easy way. MR. Karim is a Software Engineer at ITWORX, which is
a global IT Services firm providing Cloud-based and On-premise solutions to the
world’s leading organizations with an emphasis on Advanced Analytics,
Enterprise Mobility, Performance Management, and CRM.
there are two main project he has been working on: CLG and Winjigo. Both
projects are educational platforms similar to Coursera and D2L. Mr. Karim stated
that the he is not currently working CLG, as it is an old technology that is not
desired neither by the market nor the developers, so the developers decided to stop
working on it, and they have implemented and are currently upgrading Winjigo.
Winjigo was developed in-house from A to Z. It started with a business
developer having the idea of that project, who tells the marketing department
to perform a marketing research in order to determine the target market needed
in that project. Then, a business owner, who is an employee that acts as a
client, specifies the main features required in that product/project, and at
that point they had a business plan.
Mr. Karim explained that any project they implement they use a platform called
Agile or Scrum. Agile helps developers to organize a project by seeing the full
picture of the project’s business plan, and transform it into technical tasks
and codes, then shatter in down allocating tasks over teams. Winjigo is
customizable; in other words, anyone can use the online version of it, or any
organization can buy the system/application not the code, customize it to the
features they want, and add it to its servers including its own private beta,
base, and domain so that only the organization can have access to it.
but not least, Mr. Karim clarified that gathering requirements for his task is
a meeting he has with the business owner that takes about 3-4 hours in order to
illustrate the required task. Depending on the complexity of the task, it takes
Mr. Karim no time to research hardware/Software options in a best-case
scenario, but in a worst-case scenario it may take him up to two weeks
researching. According to Mr. Karim there are two types of documenting he is
mandated to do, which take 3-5 hours depending on the complexity of a
task/sprint: comments that he writes while performing a sprint to record the
history and reasons of writing lines or codes, and an ABI or a contract between
developers in order for other developers to know how he uses a service, its
inputs, and expected outputs. Mr. Karim explained that programming a story is
called a sprint and it takes around two weeks or 45 hours. Customizing a project according to a
customer’s need may take months because it requires changing actual codes that
needed months to be developed, but innovation and upgrades required by the
market is a continuous process that goes along with working on the project. It
takes Mr. Karim 15-20 hours per story for software maintenance in order to fix
issues and bugs, refactoring, and stability.
and large, Mr. Karim was a perfect resource for my interview. I have to admit
that the information that I have been exposed to was great, and I believe the
rest of the information I have not got the chance to add to this interview;
they will be helpful for my experience in class.