Jobs Malaysia - Two95 HR HUB ’s Post

IF YOU HAVE EXPERIENCE AS A PROGRAMMER DO YOU STILL WANT TO BECOME A SYSTEM ANALYST? YES. YOU WANT TO BECOME A SYSTEM ANALYST. EVEN YOU KNOW PROGRAMMING YOU STILL NEED TO KNOW THE SOFTWARE DEVELOPMENT LIFE CYCLE ( SDLC ) SO THAT YOU CAN WORK WITH THE PROJECT PLAN AND SYSTEM DESIGN. MOST OF MY PROJECT INVOLVED WITH SYSTEM REDESIGN. WHAT IS THAT MEAN? YOU NEED TO REDESIGN AN EXISTING SYSTEM. YOU NEED TO HAVE SYSTEM ANALYST EXPERIENCE TO WORK WITH AS IS ANALYSIS, TO-BE ANALYSIS AND GAP ANALYSIS WHEN I CONVERTED THE LEGACY SYSTEMS TO ERP SYSTEM. AS YOU KNOW SYSTEM ANALYST CAN BECOME A PROJECT LEAD/MANAGER. SYSTEM ANALYST CAN ALSO BECOME A QA TESTER OR PERFORMANCE ENGINEER OR SYSTEM ADMINISTRATOR....:-)

IF CLERK/TYPIST IS OBSOLETE WHAT WILL I DO? EASY. SINCE I KNOW HOW TO TYPE I CAN DO ANYTHING RELATED TO TYPING. WHAT IS THE JOBS RELATED TO TYPING? INFINITY RIGHT? NO WORRIES. IF PROGRAMMER IS OBSOLETE WHAT WILL I DO? EASY. AM I NOT A PROGRAMMER/ANALYST? I AM NO LONGER DOING PROGRAMMING FOR A LONG TIME. I BECAME A SYSTEM ANALYST. SYSTEM ANALYST DON'T NEED TO PROGRAM. YOU CAN USE WHAT YOU KNOW TO GET A NEW JOB IF PROGRAMMING JOB IS OBSOLETE AND THERE ARE PLENTY OF JOBS RELATED TO PROGRAMMING. CAN YOU BECOME A QA ANALYST? CAN YOU BE A PERFORMANCE ENGINEER? CAN YOU BE A SYSTEM ADMINISTRATOR? THE LIST GOING ON AND ON MY FRIEND. SO DON'T WORRY ABOUT PROGRAMMING ...

Gaiane Sarkisian Objective: Dedicated Software Tester with experience in banking and ongoing training in software testing. Seeking opportunities to apply testing skills and contribute to the software development process. Education: Moscow State University of Economics, Statistics and Informatics (MESI) Higher education in Banking (with honors) Completed training at the 'UTEST' academy in the 'ISTQB Exam Preparation Course.' Testing Skills: Completed training at "UTEST" Academia in theory, testing, and practice. Proficient in exploratory testing, bug reporting, and testing desktop and web applications. Skilled in using testing tools: Zephyr Scale, Trello, Browser Shots, Check My Links, Fake Filler. Tested 22 products, participated in 29 test cycles, and documented bug reports with photos and videos. Familiar with Waterfall, Agile, Kanban, and Scrum methodologies. Basic SQL skills for queries. Ongoing education to deepen knowledge and skills in software testing. Language Skills: Czech: Beginner (A2) English: Intermediate (B1) Russian: Proficiency (C2) Armenian: Proficiency (C2) Technical Skills: Microsoft Office (Word, Excel, PowerPoint, Outlook) Adobe Photoshop, PRO100, Lotus Notes administration, EOD system Work Experience: Inter-district Inspection of the Federal Tax Office of Russia for the Largest Taxpayers No. 2 State Tax Inspector, Control Department No. 2 02/2017 – 02/2020 Employment terminated due to relocation Specialist 1st Discharge Control Department No. 5 09/2016 – 02/2017 Relocated to Inter-district Inspection of the Federal Tax Service № 48 in Moscow, which was later renamed the Inter-district Inspection of the Federal Tax Office of Russia for the Largest Taxpayers No. 2 Sberbank of Russia 02/2016 – 06/2016 Senior Service Manager Employment terminated due to relocation My experience in Banking and Tax is since 2011. Soft Skills: Attention to Detail Responsibility Analytical thinking Critical thinking Patience Teamwork

[ NEW JOB OPPORTUNITY AT KUALA LUMPUR] 🚀Position : Dev QA Tester (with Test Automation)🚀 Responsibilities: Leadership: >To deliver initial estimates of the testing effort needed for new developments & functional enhancements. > Participate in daily stand-up meetingsand defect triage calls >Responsible for working with third party suppliers/vendors for defect management >Monitor, measure, control & report to management on test progress, product quality, test results and test completion. > To provide leadership & guidance to the test team on best practice, mentoring & supporting development of team members with training & growth plans. > Manage resources effectively to ensure utilization is maximized, aligned to plan, budget & to timeframes. Testing: >To define, design & deliver all testing work, including Functional Testing, System Integration Test ing,Regression, & support User Acceptance Testing-UAT  >To ensure that all the requirements have corresponding test cases, & action should be taken on any requirements that could not be mapped to any test case and vice versa. The goal is to keep the mapping of requirements to test cases to 100%. >To review testing requirement for change requests, assessing the impact on test plans & schedules. >Improve and maintain an automation framework.Creation of both manual and automated test scripts. >Ensure configuration management of all Test ware artefacts produced and traceability of the tests to the test basis. >Drive standards and best practices in QA and Testing, champion the adoption of continuous quality improvement through automation. >Identify Test Automation opportunities, plan the effort, select the tools, and ensure training to team. >Production Ticket Retes. Delivery & Quality Management: >Ensure  performance  is  actively  managed,  work  is  prioritized  effectively,  individual/team  objectives  are consistently allocated, achieved and quality gate criteria is met. Requirements: Minimum 3-5 years of experience in the field Requirememnts • Passionate in software testing. • Experience in banking system will be an added advantage. • Previous hands-on experience and knowledge in Banking/Financial products such as CASA (Deposit), Term Deposit-i, Financing-i, Takaful, JomPay, IBG, DuitNow etc. • Broad knowledge of software development lifecycle (waterfall/agile) Cloud technologies, functional and non-functional test methodologies. • Experience of Testing websites and applications on large scale. • Excellent analytical skills with a good problem-solving attitude • Ability to take ownership of tasks with limited supervision. • Relevant & demonstrable experience of managing relationship with business & external stakeholders. • A proven track record in delivering on time. • Test management and defect management tools. . If you are interested, kindly connect with me or you can email -> syaza@amktechnology.com . Feel free to share with your friends and family 😉

New Role !! Role: BA – 2 positions Location – Princeton, NJ – Day1 onsite role  Job Description: ·         Facilitate Event Storming Sessions: Lead and facilitate event storming sessions with cross-functional teams to map out business processes, The BA/Test lead role needs a smart & dynamic person who is here in NJ, capable of leading conversations with Business, running a event storming or requirements session single-handed and most important open to travel to sites (10-20%) ·         identify domain events, commands, and aggregates, and collaboratively model complex systems. ·         Requirements Gathering: Work closely with stakeholders from various business units to elicit, analyze, document, and prioritize business requirements. Translate business needs into clear and concise user stories, functional requirements, and acceptance criteria. ·         Project Management: Utilize project management methodologies and tools to plan, execute, and monitor project activities. Develop project plans, timelines, and resource allocation to ensure timely delivery of project milestones. ·         Facilitate Event Storming Sessions: Lead and facilitate event storming sessions with cross-functional teams to map out business processes, identify domain events, commands, and aggregates, and collaboratively model complex systems. ·         Develop Test Scenarios: Collaborate with product owners, and development teams to identify and define test scenarios based on business requirements. Ensure test scenarios cover all relevant user interactions and system behaviors. ·         Write Test Scripts: Write clear, concise, and comprehensive test scripts based on defined test scenarios. Document test steps, expected outcomes, and test data requirements to facilitate test execution. ·         Identify Defects: Report and track defects identified during testing using designated defect tracking tools. ·         Work closely with development teams to ensure timely resolution of issues and retest fixes to validate defect resolution. ·         Maintain Test Documentation: Update and maintain test scripts, test cases, and other testing documentation to reflect changes in system requirements or enhancements. Keep test documentation organized and accessible for future reference. ·         Provide Test Support: Assist in test planning, test estimation, and test data preparation activities as needed. ·         Collaborate with QA analysts, developers, and other stakeholders to ensure effective test coverage and adherence to quality standards. ·         Stakeholder Communication: Serve as a liaison between business stakeholders, development teams, and other project stakeholders. ·         Communicate project updates, gather feedback, and manage stakeholder expectations throughout the project lifecycle ·         Risk Management: Identify project risks and develop mitigation strategies to address potential issues that may send me resume on rajesh@avi-soft.com 

Testing Apache Camel in a financial project for risk analysis is crucial to ensure the reliability and accuracy of your integration workflows. Here's a comprehensive approach to testing in the context of a risk analysis project: 1. **Unit Testing:** - Focus on testing individual Camel routes and processors. - Mock external dependencies such as database calls or external services to isolate components for testing. - Utilize Camel's testing utilities like `CamelTestSupport` to create unit tests for your processors and routes. 2. **Integration Testing:** - Test the interaction between various Camel routes and components to ensure seamless integration. - Set up test environments that resemble the production environment as closely as possible. - Leverage tools like Apache Camel's `CamelSpringTestSupport` for integration tests with Spring. 3. **Data Simulation:** - Simulate different types of financial data to test how your Camel routes handle variations in input. - Create test scenarios that represent diverse risk factors and market conditions relevant to your financial project. 4. **Error Handling Testing:** - Simulate errors and exceptions to ensure that error-handling mechanisms in your Camel routes function as expected. - Verify that error notifications or logging mechanisms are in place for risk-critical scenarios. 5. **Performance Testing:** - Assess the performance of your Camel routes under varying loads and transaction volumes. - Identify potential bottlenecks and optimize your routes for optimal performance, critical for real-time risk analysis. 6. **End-to-End Testing:** - Conduct end-to-end tests to validate the entire risk analysis workflow from data ingestion to risk assessment and reporting. - Use test data that reflects real-world scenarios to validate the accuracy of risk calculations. 7. **Regression Testing:** - Establish a robust suite of regression tests to ensure that any updates or changes to your Camel routes do not introduce new issues. - Automate regression tests to streamline the testing process and catch potential regressions early. 8. **Security Testing:** - Verify that your Camel routes adhere to security best practices, especially when dealing with sensitive financial data. - Conduct security testing to identify and address vulnerabilities in your integration solution. 9. **Continuous Integration (CI) and Continuous Deployment (CD):** - Implement CI/CD pipelines to automate the testing and deployment processes. - Ensure that your Camel routes are automatically tested with each code commit, reducing the risk of introducing defects into the project. 10. **Documentation and Reporting:** - Maintain comprehensive documentation for your tests, including test scenarios, data sets, and expected outcomes. - Generate test reports to track test results, identify issues, and monitor the overall health of your risk analysis integration.

The first thing that a QA Engineer should do when receives a new build for testing: When a QA Engineer receives a new build for testing, the first step is to perform a smoke test to ensure that the build is stable and meets the basic acceptance criteria. Smoke testing is a quick and simple test that verifies that the most important features of the application are working correctly. The following are the basic steps that a QA Engineer should follow when performing the smoke test: 1. Verify the Build Version: The first step is to ensure that the build version received for testing is the correct one. 2. Define Smoke Test Scenarios: Once the version is confirmed, the QA Engineer should define the smoke test scenarios. These may include critical functionalities, such as login, application startup, data entry, database connectivity, and basic navigation. 3. Execute Smoke Test Cases: The QA Engineer should execute the smoke test scenarios to ensure that the application is working as expected. This step involves installing the build, launching the application, and executing the defined test cases. 4. Analyze Results: After executing the smoke test cases, the QA Engineer should analyze the results to determine whether the build is stable or not. If any critical issues are found during the smoke testing, the QA engineer should report them to the development team immediately. 5. Decide Whether to Proceed: Based on the results of the smoke test, the QA Engineer should decide whether to proceed with further testing or stop testing if the build is unstable. #QA Engineer # smoke test #QA Analyst

Hi Everyone, Hope Everyone doing good! Let's learn about the question below. What will happen if customer needs to develop some application or things based on their requirements?? Requirements will be different like application develop , front end , back end , software , Cloud development, game ...etc Mostly the development lifecycle will be same , so let's learn about the steps involved in SDLC(Software Development life cycle) Step 1 Planning and Requirement Analysis - Business Analyst will be documenting the requirements with client and get it approvals with the stakeholders - Project Manager will be planning the project with scope,timelines and resources - Once requirements,scope and efforts gets approved the next steps begins . Step 2 - Developers: Write and implement the code according to design documents - Quality Assurance (QA) Engineers: Start developing test plans. - Once development completed code review and unit testing will be performed by developers Step 3 - Testers : Testing the code with test cases once test plan got approved , if any bugs identified they will be creating tickets to developers , developer will fix the issue and testing begins. - Regression testing will be performed , not only limited to regression there will be different testing(performance,system,...)based on needs. - UAT begins with stakeholders and with the end users for defect free code Step 4 Deployment Plan and Dry run - System Administrators: Deploy the software to production environments . - Developers: Assist with deployment scripts and tools. - QA Engineers: Verify the deployment. - Project Manager: Coordinates the deployment process. There will be a downtime if we are developing and upgrading in present system or app. I have added things based on my knowledge, kindly add up in comments if any other I have missed ! #SDLC #STLC #testing #development #frontend

Business Analyst

I'm an analyst so I don't have to test right? Looking for bugs is the job of the QA specialists right? Well Yes... but... also No 🙃 Scope of responsibilities of Business Analysts can vary. Depending on the role it can be more requirements gathering, synthesis and process mapping. Or it can be more a role connected with team management, tracking KPI's, creating reports. It may also required the analyst to deep dive in the area of software testing. 🏊♂️ This makes a lot of sense. Even if like in Sollers Consulting you have the opportunity to work with great QA specialists as a BA You will have plenty off hands-on testing. Who knows better how the new software feature should work? The developer who programmed the solution? The business owner, who has a vague understanding of the system? Or the BA who not only has experience in the business processes and IT, but also gathered requirements for the feature in question? 💡 In Sollers, analysts are often assisting in the testing role, helping with unit tests, functional tests, white box testing, etc. I highly recommend this route for anybody working with requirements gathering. It's very satisfying to see the gathered knowledge work in practice and it's a great path of quickly learning both the business and IT part of the project. Thanks to this with the help our great QA Competence (and some fantastic training materials prepared by our QA experts like Bartosz Gadomski ) also our business experts can get heavily involved in software testing and train business users in various methodologies and approaches or create testing strategies. After all we are all #drivenbypeople ! #businessanalysis #qa #softwaretesting