My interview began around 2:30 pm using the team’s browser and mail communication, where I could get the chance to interact with my interviewer of Infosys.
A couple of information exchange where I was asked for the following questionaries:
- A brief introduction about my previous role and company.
- Currently, part of Symphony AI software product documentation DDLC process. Their products include AI based retail products for application engineers.
- Previously part of Applied Materials semiconductor based software product documentation team. Their products include semiconductor and data science-based software applications.
- My roles include performing a systematic DDLC process such as software requirement analysis, collaboration, gathering software application functionality details, drafting, illustrations, editing, proofreading, publishing and multichannel delivery.
- Developed software product documents, user guide, installation guide, troubleshoot guide, deployment document, functionality document, process document, integration document, application manual and Release notes.
- My collaboration roles include interacting with product developers, test engineers and SMEs followed by client consultation for gathering information inputs and converting into industry standard end user documents.
- A brief documentation showcase and demonstration based on my experience:
Could get the chance to show my previous work on end user guide, sample documents and blog portfolio topics. Could get the chance to show on how I created a user guide and its template.
- Scrum master experience.
I was part of the scrum meetings of designing and planning meeting that include product managers, design engineers and developers and technical writer.
- Portfolio showcase.
Here I could get the chance to showcase few of my articles in the blog, such as types of software documentations and tools of software documentation.
- Which of the tools I worked for reviewing.
In symphony AI, I used MS office and teams for reviewing documents and collaboration.
- How I proceeded at Symphony AI DDLC process.
A. Requirement Analysis
Key Activities:
- Gathering requirements from stakeholders (e.g., developers, product owners, end-users).
- Identifying the target audience (e.g., developers, administrators, end-users).
- Determine the type of documentation needed (e.g., user manuals, API docs, installation guides).
- Defining documentation goals, timelines, and deliverables.
B. Planning
Key Activities:
- Developing a content structure or outline.
- Defining tools and technologies to be used
- Establishing version control practices for the documentation.
- Assigning roles and responsibilities to the documentation team.
- Setting deadlines and milestones.
- Content Development
Key Activities:
- Drafting content based on the approved outline and requirements.
- Incorporating input from subject matter experts (SMEs), developers, or QA engineers.
- Using clear, concise, and consistent language.
- Adding screenshots/visuals (e.g., diagrams, screenshots, flowcharts) where applicable.
- Ensuring adherence to style guides and templates.
- Review and Editing
Key Activities:
- Peer reviewing by team members and SMEs for technical accuracy using MS office and teams.
- Address feedback from reviewers and editing th updates.
5. Publishing
Key Activities:
- Formatting the documentation for the chosen platform (e.g., web-based documentation, PDF files, or wikis).
- Hosting the documentation on platforms of Confluence, or custom websites.
- Ensuring compatibility with multiple devices (e.g., mobile, desktop).
- Testing hyperlinks, navigation, and search functionality.
6. Maintaining the updates in the platform.
Key Activities:
- Regularly updating content to reflect software changes or enhancements.
- Gathering user feedback to identify gaps or improvement areas.
- Maintaining version history for documentation updates.
- Removing outdated content as needed.
*Thereby I was asked to submitted a written on the interview event.
- Then I could get the chance to ask their domain tools and processes in their documentation field.
This is what I could know on the work profile –
Creating application User guide using tools Adobe editor and Visio, and reviewing training and knowledge-based documents along with a brief team process overview. It was a nice interaction. My interview ended around 3:00 pm.