Selenium ide in camelot

Manual QA have to learn automation writing

2024.06.05 23:14 qaengineer83 Manual QA have to learn automation writing

Hey all! I’ve been in QA for 10 years as a manual tester.
They’re asking me to learn writing test cases and editing them in RubyMine. Where do I start?! I’ve taken Ruby language classes online and an rspec class but I’m lost in both. They were short courses on Udemy.
I have barely any knowledge…I only know html that I learned for editing a small company website about 20 years ago. I used Selenium IDE about 10 years ago. I can get around pretty comfortably in the shell but that’s it - we check out our own branches, pull, merge code in, etc. I have basically no knowledge of programming.
Will I ever understand it?!
submitted by qaengineer83 to QualityAssurance [link] [comments]


2024.05.23 18:40 softwaretraining1234 Selenium Training in Hyderabad

Selenium is a powerful and widely-used open-source tool for automating web browsers. It allows developers and testers to write scripts in various programming languages such as Java, C#, Python, and Ruby, making it a versatile choice for testing web applications across different platforms and browsers. Selenium supports a suite of tools, including Selenium WebDriver, Selenium IDE, and Selenium Grid, each serving specific purposes in the automation process.
Key Features of Selenium:
RS Trainings: Premier Selenium Training in Hyderabad
RS Trainings stands out as a leading provider of Selenium training in Hyderabad, offering comprehensive courses designed and delivered by industry IT experts. Here’s why RS Trainings is the preferred choice for Selenium training:
1. Experienced Instructors: RS Trainings prides itself on its team of seasoned IT professionals who bring a wealth of real-world experience to the classroom. These experts provide insights into the latest industry trends, best practices, and practical challenges, ensuring that learners gain a robust understanding of Selenium.
2. Comprehensive Curriculum: The Selenium training program at RS Trainings covers all essential aspects of Selenium, from the basics to advanced topics. The curriculum includes:
3. Hands-On Training: RS Trainings emphasizes practical learning. The courses include numerous hands-on exercises, real-world projects, and live demos that help students apply theoretical knowledge in practical scenarios. This approach ensures that learners are well-prepared to tackle real-world automation challenges.
4. Flexible Learning Options: Understanding the diverse needs of learners, RS Trainings offers flexible learning options, including classroom training, online sessions, and weekend batches. This flexibility ensures that both working professionals and full-time students can find a schedule that suits them.
5. Career Support: Beyond technical training, RS Trainings provides career support services such as resume building, interview preparation, and job placement assistance. This holistic approach helps students transition smoothly into the workforce and secure positions in reputed organizations.
6. State-of-the-Art Infrastructure: RS Trainings boasts modern training facilities equipped with the latest tools and technologies. The learning environment is designed to enhance the educational experience and provide students with the resources they need to succeed.
Conclusion
For those seeking to master Selenium and advance their careers in test automation, RS Trainings in Hyderabad offers a compelling blend of expert instruction, comprehensive curriculum, and practical experience. By enrolling in their Selenium training program, students can gain the skills and knowledge needed to excel in the competitive field of software testing.

submitted by softwaretraining1234 to u/softwaretraining1234 [link] [comments]


2024.05.11 13:48 baramuk Any suggestions for recording browser actions and get script tools

Hi guys, Im Berke a Jr Software Tester, greetings from Turkey. I don't have a lot of experience in test automation, but I am trying to improve myself. I would like to ask you a few questions about how I can solve a situation I am experiencing.
In the company I work for, we mostly do test manualy. But I am working on preparing automation as a side-project. I am doing this in the test environment yet. Software language and tools I use Java Selenium Cucumber. My biggest blocker is the time loss I experience when I get locations of the elements and write bunch of scripts. While I don't have much time to develop my automations, sometimes I need to spend hours to automate some scenarios. On top of that, even though this is a side-project, I expected to write both Web, Android and IOS automations.
Regarding to this, I think there are some programs. These programs can record the actions you take in the browser with their locations and present you the whole scenario in script form as Junit or TestNG code. I did a little research and it seems possible to do this kind of operation with Katalon Studio, Selenium IDE or TestProject.
I would like to ask you these questions; 1. Have you used these programs before, can you share your experiences? 2. Can you recommend an alternative program? 3. Which one is available for free? 4. Can I include such programs in my own Intellij project? (Because my goal is to run these codes on AWS Device Farm) 5. Will these programs really shorten my scripting process?
I think these are all the questions I have in my mind for now, I would be very grateful if you can help me. I know that learning another tool has a learning curve, but I'm open to any suggestion if it will finally solve this problem.
submitted by baramuk to QualityAssurance [link] [comments]


2024.04.21 00:02 Hupp1 Newbe needs help. Automation for booking events in advance on pike13

Hi,
i need some help with my first idea for a bot i want to build, but i dont know where to start and hope you can help me with finding the right tools and code for this.
So plan is: I want to create bot, that automatically books an Event on a pike13 sports page at a special day and time. So e.g. every Saturday at 10:30 the bot should login to my account, open up the upcoming event in the next week and should book me a spot.
I already looked in the Selenium, but i cant get it working because pike13 seems to be build with angular, and i cant get ids or classes for the Elements that should be clicked.
So do you guys have an ide how i can get this done?
submitted by Hupp1 to automation [link] [comments]


2024.04.18 16:14 Yam3488-throwaway What exactly is the docs-as-code process?

I'm a tech writer hoping to get into developer documentation. Right now, I write instructions for software users but not the developers. Our current engineer who writes the software that my department uses is retiring, and they're hiring a replacement. This is my opportunity to offer to help with the transition by documenting the code.
The problem is I have only a slight idea of where to start. I'd really like to use a docs-as-code model. Can someone tell me what the process looks like? What programs are used and when? Do I start by viewing the code in GitHub, then test the code snippets in a developer tool like Selenium (if just testing a part of the code is even possible), then write my docs in an IDE like Visual Studio, then publish to a page? As you can see I've done enough research to be dangerous but not enough to actually know what I'm doing.
I know a little Python, Git, and Github, and the software is written in a few languages, but Typescript and JavaScript are two that I know, and the software is built on top of SharePoint.

submitted by Yam3488-throwaway to technicalwriting [link] [comments]


2024.04.16 07:10 dave8055 How to do automation testing for an app that is built on PFC and Modern controls?

I tried test studio and it wont work with components. I read the documentation for Test Engine and it says it wont support modern controls. I tried Selenium IDE, its not detecting any controls in PowerApps. How can I automate the testing of an application?
submitted by dave8055 to PowerApps [link] [comments]


2024.04.11 11:26 markpetersonuae IT Infrastructure For Software Development – The Why’s and How’s

IT Infrastructure For Software Development – The Why’s and How’s
IT Infrastructure For Software Development – The Why’s and How’s
Are you wondering why IT infrastructure software development is becoming increasingly vital for businesses? Well, you're in the right place. In this article, we will explore the why's and how's of IT infrastructure software development, and why it is essential for the growth and success of modern organizations.

Understanding IT infrastructure software development

The IT infrastructure of a software development company in Dubai plays a crucial role in today's digital age. Businesses heavily rely on technology to streamline their operations and achieve their goals, and IT infrastructure software development is at the heart of this process. It involves designing, building, and maintaining software applications and systems that enable businesses to efficiently manage their IT infrastructure.
From developing custom software solutions to integrating existing systems, there are various aspects to consider. It requires a deep understanding of infrastructure architecture, programming languages, databases, and security protocols.
To ensure the success of IT infrastructure software development, businesses need to have a clear understanding of their objectives and requirements. They need to align their software development efforts with their overall business strategy and goals. By doing so, organizations can leverage technology to enhance their efficiency, productivity, and competitiveness in the market.

Importance of IT infrastructure software development

Software development offers numerous benefits for businesses. Firstly, it improves productivity and efficiency by automating manual processes and streamlining operations. By developing customized software applications tailored to their specific needs, organizations can eliminate repetitive tasks and optimize resource allocation.
Cost reduction is another significant advantage of IT infrastructure software development. By creating efficient systems and applications, businesses can minimize operational costs and achieve better ROI. For example, automating inventory management processes can reduce errors, prevent stockouts, and save money on unnecessary inventory.
Enhanced security is another crucial aspect of IT infrastructure software development. With the increasing number of cyber threats and data breaches, organizations need robust security measures to protect their valuable information. By developing secure software applications and implementing stringent security protocols, businesses can safeguard their data from unauthorized access and potential vulnerabilities.
Furthermore, the IT infrastructure of software development company UAE enables businesses to adapt to technological advancements and stay competitive in the market. By continuously updating their software systems, organizations can leverage emerging technologies, such as artificial intelligence and machine learning, to drive innovation and gain a competitive edge.

Key components of IT infrastructure software development

Successful software development involves several key components. Firstly, businesses need to have a strong understanding of their current IT infrastructure and identify areas that require improvement. This includes assessing hardware, software, networks, and databases to determine the scope of software development projects.
Next, organizations need to define clear objectives and requirements for their custom software development in dubai efforts. They need to identify the specific functionalities and features they require and ensure that they align with their business goals. By defining clear requirements upfront, businesses can avoid scope creep and ensure a smooth development process.
Once the requirements are defined, businesses need to engage a skilled team of developers and engineers. These professionals will be responsible for designing, coding, and testing the software applications. Collaboration between developers, project managers, and stakeholders is crucial to ensure the software meets the desired specifications and is delivered on time.
Throughout the development process, businesses need to prioritize quality assurance and testing. Rigorous testing ensures that the software is free of bugs, performs as intended, and meets the user's expectations. This includes functional testing, performance testing, and security testing to ensure the software is robust and reliable.
Finally, organizations need to have a plan for deployment and ongoing maintenance of the software. This includes ensuring seamless integration with existing systems, training users on the new software, and providing ongoing support and updates. Regular maintenance and updates are essential to keep the software secure, functional, and up to date with changing business needs.

The benefits of implementing IT infrastructure software development

Implementing infrastructure of software development brings a multitude of benefits for businesses. Improved productivity and efficiency are among the most significant advantages. By automating manual processes and streamlining operations, businesses can save time and resources, allowing employees to focus on more strategic tasks.
Cost reduction is another key benefit. By developing customized software applications, businesses can eliminate the need for multiple off-the-shelf solutions and reduce licensing and maintenance costs. They can also optimize resource allocation and minimize wastage, leading to better cost management.
Enhanced security is of utmost importance in today's digital landscape. Software development company allows businesses to implement robust security measures and protocols to protect their sensitive data. By developing secure applications and regularly updating them, organizations can safeguard their information from cyber threats and potential breaches.
Flexibility and scalability are also benefits of IT infrastructure software development. Custom software applications can be tailored to meet the specific needs of the business and can easily adapt to changing requirements. As businesses grow and evolve, their software systems can scale accordingly, ensuring seamless operations.
Furthermore, implementing IT infrastructure enables businesses to gain a competitive edge. By leveraging technology, organizations can differentiate themselves in the market, enhance customer experiences, and improve overall satisfaction. It allows businesses to stay ahead of the curve and meet customer demands effectively.

Steps to successful IT infrastructure software development

Successful infrastructure of software development in IT sector requires careful planning and execution. Here are the key steps to follow for a successful implementation:
  • Define objectives and requirements: Clearly define the objectives and requirements of the software development project. Identify the functionalities and features needed and align them with your business goals.
  • Assemble the right team: Build a skilled team of developers, engineers, and project managers who have the expertise and experience relevant to your project.
  • Design and development: Create a detailed design and development plan. Break down the project into manageable tasks and set realistic timelines for each phase.
  • Testing and quality assurance: Conduct thorough testing to ensure the software meets the desired specifications and performs as intended. Implement functional testing, performance testing, and security testing.
  • Deployment and integration: Plan for seamless integration with existing systems and ensure a smooth deployment process. Train users on the new software and provide ongoing support.
  • Maintenance and updates: Regularly maintain and update the software to keep it secure, functional, and up to date. Monitor its performance and address any issues that arise promptly.
By following these steps, businesses can ensure a successful IT infrastructure software development project that meets their objectives and delivers tangible results.

Challenges and solutions in IT infrastructure software development

Its fair share of challenges for IT. Some common challenges include:
  • Scope creep: The scope of the project expanding beyond the initial requirements, leading to delays and increased costs. To mitigate scope creep, businesses need to define clear objectives and requirements upfront and have a change management process in place.
  • Resource constraints: Limited availability of skilled developers and engineers can pose challenges. To address this, businesses can consider outsourcing some aspects of the project or investing in training and development programs for their existing staff.
  • Security vulnerabilities: With the increasing sophistication of cyber threats, ensuring the security of software applications is crucial. Implementing robust security measures, conducting regular security audits, and staying updated with the latest security practices can help mitigate vulnerabilities.
  • Technical debt: Technical debt refers to the accumulation of shortcuts and compromises made during the development process, leading to suboptimal software quality. Regular code reviews, refactoring, and following best practices can help manage technical debt.
By being aware of these challenges and implementing appropriate solutions, businesses can navigate the complexities of IT infrastructure software development more effectively.

Best practices for IT infrastructure software development

To ensure the success of IT infrastructure software development, businesses should follow these best practices:
  • Clear communication: Foster open and transparent communication between all stakeholders, including developers, project managers, and business leaders. Regularly update stakeholders on the progress of the project and address any concerns or issues promptly.
  • Agile methodology: Adopt an agile development approach that emphasizes flexibility, collaboration, and iterative development. This allows for quick feedback and adjustments, leading to better outcomes.
  • Continuous integration and delivery: Implement continuous integration and delivery practices to ensure regular updates and enhancements to the software. This allows businesses to respond quickly to changing requirements and market demands.
  • Code quality and documentation: Prioritize code quality and maintain thorough documentation throughout the development process. This ensures the software is easy to maintain, scalable, and understandable for future developers.
  • Regular testing and quality assurance: Implement a robust testing and quality assurance process to identify and address any issues early on. This includes unit testing, integration testing, and user acceptance testing.
  • Collaboration and teamwork: Encourage collaboration and teamwork between developers, project managers, and stakeholders. Foster a culture of shared responsibility and ownership to ensure the success of the project.
By following these best practices, businesses can streamline their IT infrastructure software development process and increase the chances of success.

Tools and technologies for IT infrastructure software development

There are numerous tools and technologies available to support IT infrastructure software development. Some commonly used ones include:
  • Integrated Development Environments (IDEs): IDEs such as Visual Studio Code, Eclipse, and IntelliJ IDEA provide a comprehensive set of tools for writing, debugging, and testing code.
  • Version control systems: Version control systems like Git and SVN enable developers to track changes in code, collaborate effectively, and manage multiple versions of the software.
  • Project management tools: Tools like Jira, Trello, and Asana help manage tasks, track progress, and facilitate collaboration between team members.
  • Automated testing frameworks: Frameworks like Selenium and pytest automate the testing process and ensure the software meets the desired specifications.
  • Containerization and virtualization tools: Technologies like Docker and VirtualBox allow for the creation and management of isolated environments, making it easier to deploy and test software across different systems.
  • Cloud platforms: Cloud platforms like Amazon Web Services (AWS) and Microsoft Azure provide scalable and cost-effective infrastructure for hosting and deploying software applications.
The choice of tools and technologies depends on the specific requirements and preferences of the business. It is crucial to select tools that align with the development team's expertise and the project's needs.

Conclusion and future trends in IT infrastructure software development

In conclusion, Infrastructure with software development is essential for the growth and success of modern organizations. By investing in customized software applications and systems, businesses can improve productivity, reduce costs, enhance security, and stay competitive in the market. Successful implementation requires a clear understanding of objectives, meticulous planning, and adherence to best practices.
Looking ahead, the future of IT infrastructure software development is promising. Emerging technologies such as artificial intelligence, machine learning, and blockchain are expected to revolutionize the way businesses manage their IT infrastructure. Organizations that embrace these technologies and adapt their software systems accordingly will be well-positioned for success in the digital age.
With the right approach, tools, and expertise, businesses can harness the power of IT to unlock their full potential and achieve their goals.
submitted by markpetersonuae to u/markpetersonuae [link] [comments]


2024.04.06 14:22 smartybrome + 90 online courses worth almost $4000 all yours for FREE - added Today [100% Off]

Udemy Free Courses for 06 April 2024

Note : Coupons might expire anytime, so enroll as soon as possible to get the courses for FREE.
GET MORE FREE ONLINE COURSES WITH CERTIFICATE – CLICK HERE
submitted by smartybrome to udemyfreeebies [link] [comments]


2024.04.06 14:22 smartybrome +90 online courses worth almost $4000 all yours for FREE - added Today [100% Off]

Udemy Free Courses for 06 April 2024

Note : Coupons might expire anytime, so enroll as soon as possible to get the courses for FREE.
GET MORE FREE ONLINE COURSES WITH CERTIFICATE – CLICK HERE
submitted by smartybrome to udemyfreebies [link] [comments]


2024.04.05 23:37 RickSayingCoral How to format this part of my resume?

I worked for the same company and in the same position, but for 2 different teams. Here's what I currently have:
WORK HISTORY:
Usability Engineer (Team 2) November 2022 - Current Software Quality Assurance (QA)/Test Engineer (Team 1) May 2019 - November 2022 Company/Location
Two of those bullet points are for team 1 only, but the rest are for both. Is there a "prettier" way of formatting/writing this?
submitted by RickSayingCoral to Resume [link] [comments]


2024.04.05 20:10 RickSayingCoral How to write this part of my resume?

WORK HISTORY:
Usability Engineer (Team 2) November 2022 - Current Software Quality Assurance (QA)/Test Engineer (Team 1) May 2019 - November 2022
Company/Location
A couple of those bullet points are for team 1 only, but the rest are for both. Is there a "prettier" way of formatting this?
submitted by RickSayingCoral to resumes [link] [comments]


2024.03.22 09:58 Original_Primary_601 Navigating the Mac vs. Windows Dilemma for Selenium Automation and C#

Hey there!I'm diving into Selenium using C# and a BDD framework, and I'm stuck between choosing a Macbook Air M2 or a Windows PC for my personal development journey in automation testing. I've heard rave reviews about Visual Studio 2020 for C# programming and BDD frameworks, but then there's the catch – Visual Studio for Mac isn't exactly top-notch and it's phasing out by 2024.So, here's the million-dollar question: Should I go for a Mac or stick with Windows? And if I lean towards the Mac side, what's the go-to IDE for Selenium and C# that you'd recommend?I'm all ears for your thoughts and advice on this. Thanks a ton in advance for lending a hand!
submitted by Original_Primary_601 to softwaretesting [link] [comments]


2024.03.20 06:18 lakshuseeniappan Selenium Automation Testing: Basics And Getting Started

Selenium Automation Testing: Basics And Getting Started
https://preview.redd.it/xhb89suibfpc1.png?width=900&format=png&auto=webp&s=b5acfb2adc76863a3c1cc407f31cc26bf5ce3e38
Introduction
In today's fast-paced software development environment, ensuring the quality of applications is paramount. Manual testing, while essential, can be time-consuming and prone to errors, especially in agile and DevOps-driven workflows. This is where automation testing comes to the rescue, offering efficiency, repeatability, and accuracy in testing processes. Selenium stands out as one of the most popular and powerful choices among the various automation testing tools available. This post will go over the fundamentals of Selenium automated testing and provide a detailed guide on getting started with Selenium. If you want to enhance your automation testing skills, consider enrolling in Selenium Training In Chennai for comprehensive and hands-on learning.
Understanding Selenium Automation Testing
Selenium is an open-source testing framework primarily used to automate web applications. It provides tools and libraries that enable testers and developers to automate web browser interactions and perform functional testing across different browsers and platforms.
Key Components Of Selenium:
Selenium WebDriver: WebDriver is the core component of Selenium that allows users to interact with web browsers programmatically. It provides a set of APIs for controlling browser actions such as navigating to URLs, clicking elements, filling forms, and extracting data from web pages.
Selenium IDE (Integrated Development Environment): Selenium IDE is a browser extension for recording and running test scripts. It enables testers to easily construct automated tests by capturing their interactions with the web application and writing Selenium WebDriver scripts.
Selenium Grid: Selenium Grid enables parallel execution of tests across multiple browsers and platforms simultaneously. It allows for distributed testing, where tests can be run on different machines to reduce execution time and increase test coverage.
Getting Started With Selenium Automation Testing:
Now, let's walk through the steps to get started with Selenium automation testing:
Setting Up The Development Environment:
Install the Java Development Kit (JDK): Because Selenium WebDriver is primarily used with Java, you must have the JDK installed on your PC. The JDK is available for download and installation from Oracle's official website.
Set Up Integrated Development Environment (IDE): Choose an IDE for writing and executing Selenium tests. Popular choices include Eclipse, IntelliJ IDEA, and Visual Studio Code. Install the IDE that fits your preference and configure it for Java development.
Adding Selenium WebDriver Dependencies:
Create a new Java document in your IDE that meets the Selenium WebDriver criteria. You can manage dependencies using build tools like Maven or Gradle. Add the following Maven dependencies for Selenium WebDriver and WebDriver bindings:

org.seleniumhq.selenium
selenium-java
3.141.59

Writing Your First Selenium Test:
Make a new Java module for your Selenium test and include any relevant libraries. Write a simple test case to open a web browser, navigate to a URL, and verify the page's title. Here's an example test case using WebDriver:
Import org. openqa. Selenium.WebDriver;
import org. openqa. Selenium. Chrome.ChromeDriver;
public class FirstSeleniumTest {
public static void main(String[] args) {
//Set system property to specify the location of the chrome driver executable
System.setProperty("web driver.chrome.driver", "path/to/chromedriver");
// Initialize WebDriver instance
WebDriver driver = new ChromeDriver();
// Open the browser and navigate to the URL
driver. get
// Verify the title of the page
String pageTitle = driver.getTitle();
System. out.println("Page Title: " + pageTitle);
// Close the browser
driver.quit();
}
}
Executing The Selenium Test:
Before executing the test, make sure you have the WebDriver executable (e.g., chrome driver for Chrome) downloaded and placed in your system's PATH or specify the path to the executable in your test code.
Run the Selenium test from your IDE. The test will launch the browser, navigate to the specified URL, verify the page title, and then close the browser. Additionally, if you want to enhance your software development skills, consider enrolling in Dot Net Training In Chennai for comprehensive learning and practical experience.
Conclusion
Selenium automation testing offers a powerful solution for streamlining the testing process and ensuring the quality of web applications. By leveraging Selenium WebDriver and its rich Set of features, testers and developers can create robust and efficient automated tests that validate the functionality and performance of web applications across different browsers and platforms. In this article, we've covered the basics of Selenium automation testing and provided a step-by-step guide to getting started with Selenium. As you continue your journey with Selenium, explore its advanced features, best practices, and integration with other tools to maximise its potential and drive quality assurance in your software development projects. Happy testing!
submitted by lakshuseeniappan to u/lakshuseeniappan [link] [comments]


2024.03.20 06:02 frompadgwithH8 Some API Calls take 44 seconds and make over 1k database calls, compiling takes minutes

I just got a job as a software engineer at a company that I will not name. It has over 1000 engineers in the engineering department. It has a program that is almost 30 years old that originally powered a web application through a SOAP API. It has a ton of logic written as stored procedures at the database layer, and it uses old and outdated binaries for the framework it is written in. It is so old that it has an in-house framework to do things that later versions of the framework brought out of the box.
At point in time the code base was copied, and then the two code bases slowly diverged. One code base stayed faithful to the web application, and so calling a route would do everything that the web application page needed. The other application was built as a RESTful API and it attempts to ditch the SOAP endpoints in favor of making smaller and more granular, and thus much more efficient, changes to the database.
Here’s the problem: while watching multiple coworkers of mine, over video calls, go to run a test in debug mode, I noticed that it took one to two minutes before the first debugger statement paused the runtime. The application is so big that it cannot actually run on the local machine. So there is a database in the cloud that the local tests make calls too. Like I said, it can take over a minute before the debug statement catches.
I only have a few years of experience under my belt. But I was thinking. There’s got to be a better way.
For example, I know with the end to end test framework selenium, you can cache all of the network responses. That way, once you have a “golden path”, you can just cache everything and then not actually make real API calls. Obviously, there are downsides to this, but it is certainly faster. Because I was thinking, “what if I miss my debugger statement and I have to restart the test and wait several minutes just to get to that debugger statement again?”
I mean the iteration rate sounds like it’s gonna be so slow. I am really not looking forward to this. Not to mention I’m going to have to be running everything from the remote machines since the code will not actually work on the computer that I have. For some reason, they asked me which computer I wanted, they never should have asked, they should have just sent me a windows machine.
Anyways, what are some ways that I can speed things up? Can I somehow use docker or some other tool to magically reduce the iteration cycle time? What if I want to rerun a test, can I run the test in some mode that will cache all of the network responses? I have access to fully paid IDE’s like Visual Studio and literally every Jetbrains product.
I’m basically trying to work smarter not harder here. But I don’t think I have enough experience to know how to work smarter in this situation. But at the same time, the developer experience seems so fucking slow and awful that I can’t believe that there’s not a way to make things better. I’m sorry that things are abstract and vague in this post, obviously I cannot really reveal which company I work for or what the software stack actually is etc.
submitted by frompadgwithH8 to AskProgramming [link] [comments]


2024.03.08 08:27 lakshuseeniappan Beginners Can Use These Methods To Advance Their Careers In Selenium.

Introduction
The field of automated testing, especially with tools like Selenium, offers a promising and rewarding career path for individuals interested in quality assurance and software testing. As a beginner, diving into Selenium is a challenging endeavour. Still, with the right methods and a systematic approach, you can learn the ropes and advance your career in this dynamic domain. This comprehensive guide will explore various methods beginners can employ to master Selenium and carve a successful career path. If you want to enhance your automated testing skills, consider enrolling in Selenium Training In Chennai for comprehensive and hands-on learning.

Establish A Strong Foundation

Before delving into Selenium, it's crucial to establish a strong foundation in programming. Choose a programming language—such as Java, Python, or C—and familiarise yourself with its syntax and basic concepts. This foundational knowledge will serve as the backbone for your Selenium journey.

Learn The Basics Of Web Technologies

They understand how web applications are built and how function is integral to effective automated testing. Learn the fundamentals of HTML, CSS,Selenium Script, as these are the foundational elements of web pages. This understanding will allow you to manage the complexities of web elements when working with Selenium.

Dive Into Selenium Basics

Begin your Selenium Selenium by understanding its fundamental components. Selenium WebDriver is a pivotal tool for automating interactions with web browsers. Learn how to set up a WebDriver instance, open browsers, and navigate through web pages. Acquaint yourself with the different locators, such as ID, name, class, and xpath, to identify and interact with web elements.

Select Your Programming Language

Selenium supports multiple programming languages. Choose the one that aligns with your preferences or is commonly used in your workplace. If you need more clarification, consider the prevalence of languages like Java, Python, and C in the Selenium community.

Set Up Your Development Environment

A well-configured development environment is essential for smooth Selenium automation. Install the necessary tools, such as the chosen programming language, an Integrated Development Environment (IDE) like Eclipse or IntelliJ, and a build tool like Maven or Gradle.

Master Core Selenium WebDriver Concepts

Building on the basics, delve into core Selenium WebDriver concepts. Develop proficiency in locating web elements using different strategies, interacting with them through various actions like clicking and typing, and understanding how to handle dynamic content on web pages.

Embrace Synchronisation Techniques

Synchronisation is a critical aspect of Selenium automation, ensuring that your tests interact with elements only when ready. Learn about implicit and explicit waits to enhance the reliability and stability of your test scripts.

Explore Advanced WebDriver Concepts

Expand your Selenium knowledge by exploring advanced WebDriver concepts. Understand how to handle multiple browser windows and tabs, deal with alerts and pop-ups, and capture screenshots to aid debugging.

Introduce Testing Frameworks (Optional)

While not mandatory, integrating testing frameworks like TestNG or JUnit can significantly enhance your test organisation and execution capabilities. Familiarise yourself with these frameworks and understand how they can complement your Selenium automation.

Implement The Page Object Model (POM)

Implement the page object model (POM) to enhance test maintainability and reduce code redundancy. This design pattern promotes a structured approach to organising your Selenium code by representing web pages as objects.

Logging And Reporting

Implement logging mechanisms in your automation scripts to facilitate effective debugging. Additionally, explore options for generating reports to communicate test execution results.

Cross-Browser Testing

Expand your Selenium skills by performing cross-browser testing. Learn how to execute your tests on different browsers, ensuring your web applications are compatible across various platforms.

Incorporate Continuous Integration (CI)

Integrate your Selenium tests into Continuous Integration (CI) tools like Jenkins or Travis CI. Automate the execution of your tests as part of the build process, fostering a seamless and efficient testing workflow.

Frameworks And Design Patterns

Explore testing frameworks and design patterns that can bring structure and scalability to your Selenium projects. Gain insights into how frameworks like Keyword-Driven Testing (KDT) or Behavior-Driven Development (BDD) can be integrated.

Real-World Projects And Contribution

Apply your knowledge in real-world projects or help open-source Selenium projects. Practical experience is invaluable for reinforcing your skills and building a portfolio that showcases your capabilities.

Stay Updated With The Selenium Ecosystem

Selenium, like any technology, evolves. To stay informed, engage with the community through forums, blogs, and social media to stay abreast of the latest updates, best practices, and emerging trends within the Selenium ecosystem.

Networking And Community Engagement

Join online communities dedicated to Selenium users. Actively participate in discussions, ask questions, and learn from the experiences of seasoned professionals. Networking within the community can open doors to valuable insights and opportunities.

Build A Portfolio

Create a portfolio showcasing your Selenium projects, achievements, and any contributions to the Selenium community. A well-documented portfolio is an excellent way to demonstrate your skills to potential employers.

Explore Additional Topics (Optional)

Consider exploring advanced topics based on your interests and career goals. Mobile application testing, headless browser testing, and performance testing can add depth to your skill set.

Pursue Certifications (Optional)

While certifications are optional, they can formally recognize your skills. Consider taking Selenium certifications offered by reputable organisations to validate your expertise. Enrol in our comprehensive Dot Net Training In Chennai to obtain in-depth knowledge and practical experience in .NET development, laying the groundwork for a successful career in software engineering.

Conclusion

Embarking on a career in Selenium as a beginner may seem daunting, but by following this coSeleniumive guide and employing these methods, you can navigate the learning curve effectively. Remember that hands-on practice, continuous learning, and engagement with the Selenium community are key to advancing your career. With dedication and perseverance, you'll be well on your way to becoming a proficient Selenium automation tester and contributing to the world of software quality assurance.
submitted by lakshuseeniappan to u/lakshuseeniappan [link] [comments]


2024.03.01 02:19 kryptikos Can I get into QA Automation with no QA experience?

Heyo!
I went through a few posts talking about getting into QA with no experience, but most of what I came across was geared towards manual testing. I currently work IT Help Desk and have a few years of experience in crowdsourced UI testing sites like UserTesting. I'm currently going through a Udemy course that goes over both manual and automation, and I plan to go for my ISTQB Core Foundations certificate once I'm done with the course.
Ideally, I'd like to get into automated QA for a variety of reasons, namely the role sounds more interesting, the pay is higher, and from what I've heard about the job market for trying to get into manual QA, it would be nice if I could skip manual and go straight to automated. Is that feasible, or am I going to have to hunker down and try to work my way into a manual role first? If it makes any difference, I live in the US and I'm ideally going to be looking for something remote.
Also, here's a list of some of the things the course goes over, is there anything beyond this that I should look into before applying for automation roles?

I'd really appreciate the input if y'all have any. :)
submitted by kryptikos to QualityAssurance [link] [comments]


2024.02.21 14:37 jabed70 How to Execute run Command in Selenium IDE?

How to Execute run Command in Selenium IDE? submitted by jabed70 to SmallYoutubers [link] [comments]


2024.02.17 14:37 jabed70 How to run times command in Selenium IDE?

How to run times command in Selenium IDE? submitted by jabed70 to SmallYoutubers [link] [comments]


2024.02.17 10:18 LIA_dating Sfaturi legate de CV si interviuri

Salutare,
Fac aceasta postare proactiva ca forma de ajutor pentru cei care isi cauta loc de munca, dar nu numai.
Context – lucrez ca HR, in IT, de 20 de ani, cu focus majoritar pe recrutare. In toti acesti ani am oferit feed-back pe CV, solicitat sau nu 😊 (eu dau sfaturi nesolicitate, ca si cele de acum), multor mii de persoane. De cele mai multe ori, cei care mi-au ascultat indrumarile si-au gasit repede loc de munca si au avut oferte mai bune. In ultimele luni am dat cateza zeci de feed-backuri pe CV si nu mai fac fata, dar vreau sa ajut. Asa ca las acest text aici pentru cei care au nevoie de ajutor.
Bon, iata sugestiile mele legate de CV si profilul de linkedin.
CVul
  1. Poza – NU mai puneti poza de la chefuri, de pe munte etc. Nu sunt deal breaker, dar, pe o piata inundata de profesionisti cu experienta, o poza profi, din fata, fara fundal de mare, munte etc in spate etc. va crea impresie mai buna.
Uitati-va in camera cand faceti poza, asigurati-va ca aveti lumina pe fata si ca zambiti putin.
O camasa sau un tricou uniforme la culoare sunt suficiente.
2. Titulatura
Titulatura voastra trebuie sa fie relevanta pentru ceea ce stiti si ce cautati. Practic ii spuneti in cateva cuvinte cheie recrutorului cam care e treaba cu voi.
NU software developer, ci .net developer, java developer.
Daca sunteti seniori (in teorie 5 ani+ experienta), puneti si asta – Senior java developer etc.
Testerii – daca sunteti manual tester asta e titulatura voastra – manual software tester (puneti software, ca sa faceti diferenta de games). Automation tester, games etc. pueti chiar sa punel toolul pe care il stiti cel mai bine – de exemplu, Selenium automation software tester.
Devops/ SRE – puneti si cloud-ul pe care il stiti, AWS, Azure, Google. Exemplu, Senior devops (AWS).
Customer support – pe ce anume faceti suport. Exemple, Microsoft Office technical support; networking customer support; infrastructure customer support; invoices customer support; first level subscription customer support. Ati prins idea.
HR – IT recruiter; HR admin; Conflicts management HR; retention HR; training HR etc.
De ce sa faceti efortul?
Ca sa fiti mai smecheri ca altii. Ca sa faceti recrutorul sa ia o decizie usoara de a va selecta din marea de CVuri pe care o are de analizat acum, cand multa lume isi cauta.
Va place sau nu, hateriti sau nu, trebuie sa treceti de recrutor ca sa ajungeti la interviu.
3. Summary
Scurta prezentare de la inceput, daca alegeti sa o faceti (va recomand sa da), trebuie sa includa:
· date de contact (daca e pentru Linkedin, daca nu, aveti in CV datele de contact, ca sectiune separata). Mail e suficient, daca nu vreti sa va expuneti prea mult. Va va pune in legatura si cu recrutorii din firmele bogate care nu dau tooluri de recrutare echipei de HR, adica majoritatea 😊. Mai exact sunt o gramada de firme care fac o gramada de bani, dar nu cumpara pt HR abonamente la LI care sa le permita sa va contacteze direct. Asa ca trebuie sa treaca prin procesul de a va adauga in reteaua proprie, sa astepte sa ziceti da si apoi sa va scrie. Daca puneti mail/telefon la summary le faceti viata mai usoara si deja va simpatizeaza.
· Puneti datele de la contact in primul rand. La fel si interesul vostru – exemplu: interested only in full remote, B2B, min 20 euros/h. Ati prins ideea.
· Daca sunteti deja disponibilizati, sau junior la primul loc de munca, ori nu va pasa – puneti – open for work si apoi datele de contact. Exemplu – Senior IT Recruiter Open for Work; full remote/hybrid/office; [lia@lia.best.com](mailto:lia@lia.best.com)
· Precizati ce fel de colaborare acceptati, asa cum am aratat in exemplu - full remote/hybrid/office
· Pe randul 2 puneti ce stiti – tooluri si tehnologii sau ce inseamna puncte forte in meseria voastra (vanzari, recrutari tehnice, support, etc). Le puneti primele pe cele pe care le stiti cel mai bine si care sunt relevante pentru postul pe care il doriti. Dar e musai sa le scrieti. Dati informatie mura in gura cat mai multa.
· Abia apoi puneti detalii despre personalitatea voastra minunata.
4. Experienta:
· Nu imi vine sa cred ca trebuie sa spun asta in 2024, dar experienta si educatia se pun invers cronologic, intotdeauna. De la cel mai recent job avut pana la primul, de la cel mai recent curs pana la liceu, maxim.
· Structura de prezentare a fiecarui job in parte, pe care o recomand, este cea de mai jos:
Name and town of the employer: exemplu, LIA, Brasov, Romania
Company’s description: exemplu – dating platform, start-up
Position: NU mai scrieti ce titulatura interna ati avut acolo. Sunt prea multe companii care au tot felul de cucuri de denumiri interne care inseamna fix pix in ochii cuiva care nu lucreaza acolo. Developer 4 inseamna nimic pentru cineva care nu lucreaza pentru Amazon. Banuie ca esti smecher, dar nu stie CAT de smecher esti.
Cand va puneti titulatura alegeti denumiri relevante, ca in vazul variabilelor in cod. Trebuie sa aiba sens pentru toata lumea, nu doar pentru voi si inca cativa oameni.
Titlul postului avut trebuie sa vorbeasca de la sine legat de ce anume ati facut in firma respectiva ; - .net developer; java developer etc. exact ca mai sus, da.
Responsibilities
NU le mai scrieti text, bulk. Ne omorati ochii.
Puneti-le una sub alta, cu bulinuta.
Accesati acest site:
https://resources.workable.com/java-developer-job-description
Cautati fisa postului pentru ce faceti voi. Copy-paste. NU este necesar sa reinventati roata, nici sa fiti mega originali. JD-urile de aici sunt scurte, sintetice, super bine facute. Doar daca ati avut responsabilitati mai deosebite completati fata de ce gasiti aici.
Used Tools and technologies:
Puneti aici TOT ce ati folosit in firma respectiva, like TOT. Ganditi-va ca aveti de-a face cu un tool de analiza de profil/CV care NU stie ca React e javascript by default, nici ca spring e java, etc. Dati mura in gura, TOT.
Mentionati inclusiv ca ati folosit git, confluence, jira, whatever. Nu stiti niciodata ce pitici are managerul care recruteaza.
Ce va pot spune este ca exista o gama extraordinar de variata de pitici activi in recrutorii si managerii care au decizia finala pe o candidatura. Sugestia mea este sa acoperiti cat mai multi.
Indraznesc sa va sugerez sa puneti si versiunile cu care ati lucrat, mai ales in cazul programatorilor, dar nu numai. Eu m-am lovit de intrebari sceptice din partea celor de la tehnic – “daca nu a lucrat cu react 17? Intreaba inainte de il programa la tehnic”.
Developed projects:
Ce trebuie sa includeti aici:
- Scurta descriere functionala a proiectului – complex dating platform 😊
- Durata, daca o aveti. Nu e musai
- Ce ati facut voi din acel proiect
- Daca era proiect de la zero sau cu legacy code. Ambele experiente sunt extrem de bine cotate in ochii recrutorilor. Daca ati facut de amandoua deja aveti puncte in plus.
- Ce tooluri si tehnologii ati folosit pentru acel proiect
Cu ce va ajuta descrieri atat de detaliate?
- Indica munca, care va fi apreciata, de a va prezenta complet experienta voastra, fara ghicit
- Proiectele la care ati lucrat, cu tot cu industrie, sunt indicator foarte bun al experientei acumulate. O eventuala compatibilitate de industrie va poate scoate in fata comparative cu alti candidati cu experienta similara pentru ca ati inteles deja cum functioneaza industria. De exemplu, daca ati lucrat deja la un tool bancar va va fi mai usor sa mai dezvoltati unul.
- Tools si technologies la fiecare proiect pentru ca sunt multe persoane, mai ales cei din outsourcing care au lucrat cu tooluri si tehnologii diferite pe proiecte diferite. Daca acestea au fost uniforme, atunci faceti descrierea, spuneti ce ati facut pe proiect si la finalul descrierii proiectelor puneti toolurile si tehnologiile folosite. DAR, in cazul profilului de LI repetarea lor ajuta enorm pentru ca va creste SEO pe profil.
- Daca ati lucrat in firme de outsourcing si ati trecut prin proiecte cu diverse tehnologii, dar voi vreti sa va specializati pe una anume, treceti in CV doar proiectele in care ati lucrat cu ce vreti sa continuati. La interviu puteti povesti si despre altele.
- Daca ati lucrat la multe proiecte in aceeasi firma alegeti-le doar pe cele complexe, grele, din care ati invatat mult, de care sunteti mandri, la care ati avut contributia cea mai mare. Cele care va vor vinde, mai pe romaneste
Foarte important
Daca ati lucrat la aceeasi companie si ati avut diverse pozitii acolo NU le puneti ac experiente separate. Daca recrutorul este neatent sau oboist NU va remarca ca este aceeasi companie si vac rede ca schimbati des locul de munca. Cumulate-le in aceeasi experienta. Titulatura experientei este cea pe care o aveti in present. Exemplu:
2010 – present, CTO, LIA
2018 – present – CTO – puneti aici responsabilitati, proiecte etc, conform sugestiilor de mai jos
2015-2018 – department manager (mobile division)
2012 – 2015 – mobile (React native) team leader
2010 – 2012 – react Native (mobile) developer
5. Proiectele
· NU le mai puneti la final de CV. Nu aveti idee cat de putina lume chiar citeste CVul pana la capat. Dar cam toata lumea citeste experienta. Prin urmare, puneti proiectele la jobul la care le-ati facut.
· Daca aveti proiecte personale, creati-le ca experienta de sine statatoare de munca, NU le puneti la sectiunea de proiecte, nici in CV, nici pe LI. Din nou, nu se uita nimeni din pacate sau extrem de putina lume. Creati o sectiune in CV, ca o experienta de munca, care sa se numeasca, Personal Projects, si faceti descrierea proiectelor conform sugestiilor de mai sus.
6. Daca aveti joburi irelevante (pentru ca aveti alta directie de cariera) in trecut
- Nu le stergeti. Va aparea perioada lipsa in evolutia voastra profesionala si se gandeste lumea la prostii. Adunati-le intr-o singura experienta. Va dau exemplul meu:
Other jobs and activities: sept 2000 - May 2004 · 3 yrs 9 mos iasi, romania
o 2008-12 <> 2010-04, Polirom Publishing House, Iasi, Romania, Translator 2003-09 <> 2003-12, SC Forum Intermed SRL, real estate company in Iasi, Romania, Site managereal estate agent 2003-02 <> 2003-09, Polirom Publishing House, Iasi, Romania, Proofreader 2002-09 <> 2003-01, SC Univers’all SRL, supermarket, Suceava, Romania, Department manager
A le pastra in CV il lungeste degeaba si il incarca cu informatii irelevante
7. Educatie
Invers chronologic pusa
Puneti si liceul
Chiar daca nu ati terminat facultatea puneti facultatea inceputa. Puneti anul de incepere – present. BTW, Cei care nu aveti nicio diploma – faceti ceva facultate no name, la ID, luati hartia. Nu va ajuta cu nimic, dar va poate incurca daca nu o aveti.
Cei care nu ati dat lucrarea de licenta, dar sunteti absolventi. Faceti un proiect de 2 bani, dar functional, si dati licenta. Nu intereseaza pe nimeni ce ati facut la licenta sau la scoala oricum, ci ce stiti.
Da, diploma asta nu ne ajuta cu nimic, dar ne incurca daca nu o avem. As fi vrut sa imi spuna cineva asta cand ma agitam ca sprayul sa fac o lucrare de licenta interesanta cu care nici la fund nu s-a sters comisia. M-au scos din sala in 7 min, dupa un an de munca.
Profilul de linkedin
Sfaturile legate de profilul de LI provin din experienta de utilizare – in 2023 am facut 18 ani de cand sunt membru in retea si am avut la un moment dat un premiu pentru 1% cei mai frecventi utiliatori de LI la nivel global. Deci suntem prieteni vechi.
Cand un recrutor cauta candidati pe linkedin – asa numitul headhunting – foloseste ceva cuvinte cheie si dupa aceste cautari I se afiseaza o lista de profiluri care sunt puchinoase si una sub alta, cu informatiile esentiale despre persoana returnata – nume, poza, titulatura si titulatura jobului actual. Modulul de search de la LI s-a dus naibii odata cu Microsoft asa ca, majoritatea recrutorilor folosesc 1, max 2 cuvinte cheie in aceste cautari pentru ca altfel LI se zapaceste si returneaza porcarii sau prea putine profiluri. De asemenea, majoritatea candidatilor au informatii insuficiente sau vagi in profil, asa ca folosirea de cuvinte cheie prea specifice iti poate scoate din cautare persoane cu care ai vrea sa stai de vorba.
LI functioneaza ca orice alta aplicatie web, are SEO organic, adica returneaza cu prioritate profilurile care au cuvantul cheie present de cel mai multe ori.
In acest context sugestiile mele sunt urmatoarele:
  1. Completati sectiunile de skills de peste tot, de la LI – la summary, fiecare experienta, scolarizare. Puneti java, de exemplu, si adaugati la profilul vostru tot ce vi se potriveste din sugestiile oferite de aplicatie
Va atrag atentia ca la export LI NU exporta si aceste skilluri pt ca este un tampit, prin urmare le completati doar ca sa iesiti printre rpimii la cautari dupa cuvinte cheie. Este chestiune de clickuri, deci nu e bataie de cap
  1. La Summary, fiecare experienta profesionala, fiecare proiect si educatie introduceti o sectiune de skills, dedicata, de tools and technologies ca parte a descrierii jobului, in aceeasi sectiune cu responsabilitatile. Acestea vor fi exportate, in caz ca trimiteti CVul asa sau decide recrutorul sa faca export.
  2. CVul si LI trebuie sa fie in oglinda. Majoritatea recrutorilor tehnici fac aceasta comparatie si se uita si pe githubul vostru sau ce alte informatii mai oferiti in CV. Asa ca alegeti intelept ce informatii treceti aici, adica sa fie ceva ce chiar ati facut si stiti sa raspundeti la intrebari despre X sau Y din CV.
In final, desi vi se pare redundant, treceti TOATE detaliile tehnice.
De exemplu, multa lume scoate din CV, LI informatii banale, de gen HTML/CSS, pentru ca sunt by default. Asa este, dar sunt o gramada de recrutori non tehnici acre lucreaza in IT de putin timp, asa cum exista un numar tot mai mare de companii care faca analiza profiluriloCVurilor folosind tooluri de analiza de CV – nu intotdeauna performante. Aceste tooluri primesc niste cuvinte cheie si, daca nu le gasesc, nu treceti de selectie. Asa ca mai bine safe than sorry, mai ales in vremurile astea.
Criza de acum este la pitici fata de cea din 2008. Si atunci s-au facut disponibilizari, dar nu ca acum. Ca si context piata salariala romaneasca era MULT MULT mai competitiva decat acum (romanii cereau salarii mici si erau foarte buni), si erau MULT MULT mai putini oameni pe piata decat acum, mai ales in IT. Si atunci am avut guvern cretin, dar parca nu totalmente brainless ca acum si nu atat de obraznic, sa ne badjocoreasca pe fata si cu zambetul pe buze.
Asa ca cei care sunt in situatia de a isi cauta loc de munca, mai ales dintr-o tara cu zero protectie sociala, trebuie sa straluceasca. Si primul pas sunt CVul si profilul de LI.
Alte sfaturi
CV-ul format European
- Cine a factu acest format de CV este o persoana cu un singur neuron care nu a vazut vreodata un CV. Est incredibil de enervant pt recrutor. Exceptand situatia in care aplicati pe EU sau vi se cere specific format European evitati-l.
CV tabel
- Ma refer la cel care are informatii pe 2 coloane. Nu stiu cine a venit cu moda asta, dar NU e una buna. Senzatia este de inghesuit, de aglomerat. Obligati recrutorul, care citeste sute de profiluri, sa caute pe pagina informatile ca sa vada daca va potriviti sau nu. Il iritati. Este si el/ea om, obosit, stresat. Va reamintesc – daca ii dai mura in gura ii faceti viata usoara si treceti de selectia CVuurilor.
CVuri foarte colorate
- No no, nici daca esti designer. Intrati pe profilul meu de LI, am facut o postare dedicata pentru designeri, ca majoritatea candidaturilor sunt praf pur si simplu.
- Alegeti o singura culoare, de preferat un albastru elegant, si o folositi DOAR pentru a marca sectiuni MARI din CV – titulatura si nume, experienta, educatie, hobbyuri. In rest alb si negri
CVuri cu mult text
- No no. Nu citeste nimeni. De aceea v-am sugerat sa cautati JD pe workable, sunt puse frumos responsabilitatile, cu bulinuta, unele sub altele. Sunt usor de citit si de inteles. Folositi principiul KISS aici.
CVuri de o pagina
- Pot sa inteleg temerea asta. Cine pune presiune pe un CV de o pagina angajeaza doar juniori sau este o persoana care nu respecta munca celorlalti. DAR, pentru ca stiu ca se cere asta, am creat o struto-camila de format care impaca si capra, si varza. Pe prima pagina faci sinteza experientei si apoi detaliezi experienta si proiectele fara stresul ca e prea lung CVul.
- Am pus in linkul de la final modele de CV pe care le-am create/salvat pentru ca erau foarte bine facute si au trecut de selectia tehnica cu succes.
CV in Engleza
- Faceti CVul in enegleza by default. Aproape toate firmele din Romania lucreaza, intr-un fel sau altul, cu firme din strainatate, engleza e ca a doua limba nationala.
- Daca totusi vreti sa aveti ambele variante creati-le si trimiteti-le pe amandoua, daca se poate. Mai bine au de ales decat sa fie insuficient
Titlul CVului ca fisier
- Prenume, nume, post
- Multa lume denumeste CVul aiurea si, daca avem o scapare ca recrutori, si uitam sa il redenumit cand il salvam ne ia gaia pana il gasim.
Tineti CVul si LI actualizate, constant
- Uitam chestii pe care le facem, chiar daca ni se pare ca nu
- Asa ca este o practica iteleapta sa tinem CVul la zi. Am facut un proiect, pun in CV, am mai invatat sa fac ceva – pun in CV. Este o practica care va va si ajuta sa puteti trimite CVul instant la cerere.
Persoana non-IT
- Formatul sugerat este acelasi, eliminati parte de proiecte daca este cazul
Interviu HR
- Dozati sinceritatea. Este impotriva principiilor mele de viata sa sugerez asta, dar parerea mea este ca trebuie. Lasati la o parte sefii si kkturile pe care le fac. Motive care au sens intotdeauna pentru cei de la HR – inchiderea firmei (aveti grija ca asta se poate verifica); dorinta de a lucra pe proiect intern vs outsourcing; dorinta de a lucra pe alt proiect; nevoia de a invata lucruri noi, de a testa alte industrii si stiluri de lucru, oportunitatile de promovare. Sugestia mea este sa va abtineti de la a spune mai multe de atat.
- Zambiti cat mai mult, chiar daca interviul este telefonic – conteaza mult si se vede/simte.
- Ca si in cazul pozei, un tricou simplu/camasa simpla, blugi intregi si drepti; o rochita simpla, pana la genunchi, cu machiaj discret sunt suficiente pentru interviu. Daca va place sa purtati haine colorate, cele pastelate transmit cel mai bun mesaj (sociabilitate, comunicare).
- Raspundeti la subiect, incercati sa nu va pierdeti in detalii.
- Daca nu stiti sa raspundeti la intrebare spuneti fix asta “nu stiu”, dar profitati de ocazie sa cereti raspunsul corect.
- NU mentionati ca ati facut freelancing si job in paralel – indica lipsa de loialitate si focus. Majoritatea dintre noi facem asta, dar, cumva, asta a ajuns sa fie motiv de isterie in randul managerilor spalati pe creier, prin urmare se cere dedicare 100% pentru companie. Daca va ajuta experienta de freelancer facuta in paralel cu jobul precizati ca vreti sa aveti un worklife balance mai bun si doriti ca la urmatorul loc de munca sa fiti 100% dedicati. Ulterior, dupa ce luati jobul NU va laudati cu proiectele de freelancing.
- Creati o lista detaliata si clara de intrebari pentru interviu – administrativ si tehnic. Majoritatea candidatilor se lasa furati de interviu si omit sa puna intrebari. Ceea ce va face sa va lamuriti care e treaba cu firma dupa ce ati inceput sa lucrati acolo. O decizie informata este una asumata. Asa ca anuntati intervievatorul ca aveti o lista de intrebari, inca de la inceputul interviului, ca sa isi aloce timp pentru voi. Daca nu vi se raspudne la intrebari sau primiti raspunsuri vagi aveti semnale de alarma vizavi de firma
Cum verificati daca firma este ok?
- Undelucram.com – aveti grija CINE a scris reviewul. In general departamentele de support – HR, legal, conta, support si IT sunt caii de bataie ale companiilor, asa ca au tendinta de a fi mai putini fericiti in evaluare. Incercati sa gasiti o evaluare facuta de cineva cu aceasi functie.
- Glasdoor.com
- Linkedin:
o Analizati angajatii actuali – de cat timp sunt in firma? Ideal este sa vedeti cat mai multe profiluri mai vechi de 2 ani in firma respectiva
o Analizati angajatii care au plecat – cat timp au stat cu firma? Daca majoritatea au stat sub 2 ani e posibil sa fie o problema
o Abordati unul din fostii angajati, care a lucrat in acelasi department si rugati persoana sa va dea feed-back. Fostii angajati au tendinta de a fi mai liberi in exprimare si mai onesti decat oricine altcineva care are de-a face cu firma.
o Daca vedeti reviewuri negative aveti de ales – riscati pt ca va arde somajul si tineti cu dintii de jobul asta pana gasiti altul sau trece criza SAU ziceti pas. Voi stiti care va sunt posibilitatile.
In final, dar nu in ultimul rand, tineti minte – interviul de angajare este reciproc. Atitudinea cu care mergeti la interviu este de egal cu egal, nu disperat si stapan. Chiar daca angajatorul are tendinta de a se comporta ca un stapan tratati-l ca pe un egal. Macar in interiorul vostru.
Si ultimul lucru – angajatorii care se comporta acum ok cu candidatii si angajatii sunt si cei de calitate. Este o perioada de putere pentru angajatori – ce fac cu ea spune multe despre caracterul liderilor si implicit a angajatorului. Sa ii tineti minte pe cei buni.
Link catre modele de CV cu care am avut rezultate foarte bune (aka oferte de munca/interviu):
https://www.dropbox.com/scl/fo/tpiytp30khm462n7ubr3o/h?rlkey=ib8sdeo783j4sk0vcqctrtl2d&dl=0
submitted by LIA_dating to RO_LIA_Dating_Relatii [link] [comments]


2024.02.17 10:17 LIA_dating Sfaturi legate de CV si interviuri

Salutare,
Fac aceasta postare proactiva ca forma de ajutor pentru cei care isi cauta loc de munca, dar nu numai.
Context – lucrez ca HR, in IT, de 20 de ani, cu focus majoritar pe recrutare. In toti acesti ani am oferit feedback pe CV, solicitat sau nu 😊 (eu dau sfaturi nesolicitate, ca si cele de acum), multor mii de persoane. De cele mai multe ori, cei care mi-au ascultat indrumarile si-au gasit repede loc de munca si au avut oferte mai bune. In ultimele luni am dat cateza zeci de feedbackuri pe CV si nu mai fac fata, dar vreau sa ajut. Asa ca las acest text aici pentru cei care au nevoie de ajutor.
Bon, iata sugestiile mele legate de CV si profilul de linkedin.
CVul
  1. Poza – NU mai puneti poza de la chefuri, de pe munte etc. Nu sunt deal breaker, dar, pe o piata inundata de profesionisti cu experienta, o poza profi, din fata, fara fundal de mare, munte etc in spate etc. va crea impresie mai buna.
Uitati-va in camera cand faceti poza, asigurati-va ca aveti lumina pe fata si ca zambiti putin.
O camasa sau un tricou uniforme la culoare sunt suficiente.
2. Titulatura
Titulatura voastra trebuie sa fie relevanta pentru ceea ce stiti si ce cautati. Practic ii spuneti in cateva cuvinte cheie recrutorului cam care e treaba cu voi.
NU software developer, ci .net developer, java developer.
Daca sunteti seniori (in teorie 5 ani+ experienta), puneti si asta – Senior java developer etc.
Testerii – daca sunteti manual tester asta e titulatura voastra – manual software tester (puneti software, ca sa faceti diferenta de games). Automation tester, games etc. pueti chiar sa punel toolul pe care il stiti cel mai bine – de exemplu, Selenium automation software tester.
Devops/ SRE – puneti si cloud-ul pe care il stiti, AWS, Azure, Google. Exemplu, Senior devops (AWS).
Customer support – pe ce anume faceti suport. Exemple, Microsoft Office technical support; networking customer support; infrastructure customer support; invoices customer support; first level subscription customer support. Ati prins idea.
HR – IT recruiter; HR admin; Conflicts management HR; retention HR; training HR etc.
De ce sa faceti efortul?
Ca sa fiti mai smecheri ca altii. Ca sa faceti recrutorul sa ia o decizie usoara de a va selecta din marea de CVuri pe care o are de analizat acum, cand multa lume isi cauta.
Va place sau nu, hateriti sau nu, trebuie sa treceti de recrutor ca sa ajungeti la interviu.
3. Summary
Scurta prezentare de la inceput, daca alegeti sa o faceti (va recomand sa da), trebuie sa includa:
· date de contact (daca e pentru Linkedin, daca nu, aveti in CV datele de contact, ca sectiune separata). Mail e suficient, daca nu vreti sa va expuneti prea mult. Va va pune in legatura si cu recrutorii din firmele bogate care nu dau tooluri de recrutare echipei de HR, adica majoritatea 😊. Mai exact sunt o gramada de firme care fac o gramada de bani, dar nu cumpara pt HR abonamente la LI care sa le permita sa va contacteze direct. Asa ca trebuie sa treaca prin procesul de a va adauga in reteaua proprie, sa astepte sa ziceti da si apoi sa va scrie. Daca puneti mail/telefon la summary le faceti viata mai usoara si deja va simpatizeaza.
· Puneti datele de la contact in primul rand. La fel si interesul vostru – exemplu: interested only in full remote, B2B, min 20 euros/h. Ati prins ideea.
· Daca sunteti deja disponibilizati, sau junior la primul loc de munca, ori nu va pasa – puneti – open for work si apoi datele de contact. Exemplu – Senior IT Recruiter Open for Work; full remote/hybrid/office; [lia@lia.best.com](mailto:lia@lia.best.com)
· Precizati ce fel de colaborare acceptati, asa cum am aratat in exemplu - full remote/hybrid/office
· Pe randul 2 puneti ce stiti – tooluri si tehnologii sau ce inseamna puncte forte in meseria voastra (vanzari, recrutari tehnice, support, etc). Le puneti primele pe cele pe care le stiti cel mai bine si care sunt relevante pentru postul pe care il doriti. Dar e musai sa le scrieti. Dati informatie mura in gura cat mai multa.
· Abia apoi puneti detalii despre personalitatea voastra minunata.
4. Experienta:
· Nu imi vine sa cred ca trebuie sa spun asta in 2024, dar experienta si educatia se pun invers cronologic, intotdeauna. De la cel mai recent job avut pana la primul, de la cel mai recent curs pana la liceu, maxim.
· Structura de prezentare a fiecarui job in parte, pe care o recomand, este cea de mai jos:
Name and town of the employer: exemplu, LIA, Brasov, Romania
Company’s description: exemplu – dating platform, start-up
Position: NU mai scrieti ce titulatura interna ati avut acolo. Sunt prea multe companii care au tot felul de cucuri de denumiri interne care inseamna fix pix in ochii cuiva care nu lucreaza acolo. Developer 4 inseamna nimic pentru cineva care nu lucreaza pentru Amazon. Banuie ca esti smecher, dar nu stie CAT de smecher esti.
Cand va puneti titulatura alegeti denumiri relevante, ca in vazul variabilelor in cod. Trebuie sa aiba sens pentru toata lumea, nu doar pentru voi si inca cativa oameni.
Titlul postului avut trebuie sa vorbeasca de la sine legat de ce anume ati facut in firma respectiva ; - .net developer; java developer etc. exact ca mai sus, da.
Responsibilities
NU le mai scrieti text, bulk. Ne omorati ochii.
Puneti-le una sub alta, cu bulinuta.
Accesati acest site:
https://resources.workable.com/java-developer-job-description
Cautati fisa postului pentru ce faceti voi. Copy-paste. NU este necesar sa reinventati roata, nici sa fiti mega originali. JD-urile de aici sunt scurte, sintetice, super bine facute. Doar daca ati avut responsabilitati mai deosebite completati fata de ce gasiti aici.
Used Tools and technologies:
Puneti aici TOT ce ati folosit in firma respectiva, like TOT. Ganditi-va ca aveti de-a face cu un tool de analiza de profil/CV care NU stie ca React e javascript by default, nici ca spring e java, etc. Dati mura in gura, TOT.
Mentionati inclusiv ca ati folosit git, confluence, jira, whatever. Nu stiti niciodata ce pitici are managerul care recruteaza.
Ce va pot spune este ca exista o gama extraordinar de variata de pitici activi in recrutorii si managerii care au decizia finala pe o candidatura. Sugestia mea este sa acoperiti cat mai multi.
Indraznesc sa va sugerez sa puneti si versiunile cu care ati lucrat, mai ales in cazul programatorilor, dar nu numai. Eu m-am lovit de intrebari sceptice din partea celor de la tehnic – “daca nu a lucrat cu react 17? Intreaba inainte de il programa la tehnic”.
Developed projects:
Ce trebuie sa includeti aici:
Cu ce va ajuta descrieri atat de detaliate?
Foarte important
Daca ati lucrat la aceeasi companie si ati avut diverse pozitii acolo NU le puneti ac experiente separate. Daca recrutorul este neatent sau oboist NU va remarca ca este aceeasi companie si vac rede ca schimbati des locul de munca. Cumulate-le in aceeasi experienta. Titulatura experientei este cea pe care o aveti in present. Exemplu:
2010 – present, CTO, LIA
2018 – present – CTO – puneti aici responsabilitati, proiecte etc, conform sugestiilor de mai jos
2015-2018 – department manager (mobile division)
2012 – 2015 – mobile (React native) team leader
2010 – 2012 – react Native (mobile) developer
5. Proiectele
· NU le mai puneti la final de CV. Nu aveti idee cat de putina lume chiar citeste CVul pana la capat. Dar cam toata lumea citeste experienta. Prin urmare, puneti proiectele la jobul la care le-ati facut.
· Daca aveti proiecte personale, creati-le ca experienta de sine statatoare de munca, NU le puneti la sectiunea de proiecte, nici in CV, nici pe LI. Din nou, nu se uita nimeni din pacate sau extrem de putina lume. Creati o sectiune in CV, ca o experienta de munca, care sa se numeasca, Personal Projects, si faceti descrierea proiectelor conform sugestiilor de mai sus.
6. Daca aveti joburi irelevante (pentru ca aveti alta directie de cariera) in trecut
Other jobs and activities: sept 2000 - May 2004 · 3 yrs 9 mos iasi, romania
o 2008-12 <> 2010-04, Polirom Publishing House, Iasi, Romania, Translator2003-09 <> 2003-12, SC Forum Intermed SRL, real estate company in Iasi, Romania, Site managereal estate agent2003-02 <> 2003-09, Polirom Publishing House, Iasi, Romania, Proofreader2002-09 <> 2003-01, SC Univers’all SRL, supermarket, Suceava, Romania, Department manager
A le pastra in CV il lungeste degeaba si il incarca cu informatii irelevante
7. Educatie
Invers chronologic pusa
Puneti si liceul
Chiar daca nu ati terminat facultatea puneti facultatea inceputa. Puneti anul de incepere – present. BTW, Cei care nu aveti nicio diploma – faceti ceva facultate no name, la ID, luati hartia. Nu va ajuta cu nimic, dar va poate incurca daca nu o aveti.
Cei care nu ati dat lucrarea de licenta, dar sunteti absolventi. Faceti un proiect de 2 bani, dar functional, si dati licenta. Nu intereseaza pe nimeni ce ati facut la licenta sau la scoala oricum, ci ce stiti.
Da, diploma asta nu ne ajuta cu nimic, dar ne incurca daca nu o avem. As fi vrut sa imi spuna cineva asta cand ma agitam ca sprayul sa fac o lucrare de licenta interesanta cu care nici la fund nu s-a sters comisia. M-au scos din sala in 7 min, dupa un an de munca.
Profilul de linkedin
Sfaturile legate de profilul de LI provin din experienta de utilizare – in 2023 am facut 18 ani de cand sunt membru in retea si am avut la un moment dat un premiu pentru 1% cei mai frecventi utiliatori de LI la nivel global. Deci suntem prieteni vechi.
Cand un recrutor cauta candidati pe linkedin – asa numitul headhunting – foloseste ceva cuvinte cheie si dupa aceste cautari I se afiseaza o lista de profiluri care sunt puchinoase si una sub alta, cu informatiile esentiale despre persoana returnata – nume, poza, titulatura si titulatura jobului actual. Modulul de search de la LI s-a dus naibii odata cu Microsoft asa ca, majoritatea recrutorilor folosesc 1, max 2 cuvinte cheie in aceste cautari pentru ca altfel LI se zapaceste si returneaza porcarii sau prea putine profiluri. De asemenea, majoritatea candidatilor au informatii insuficiente sau vagi in profil, asa ca folosirea de cuvinte cheie prea specifice iti poate scoate din cautare persoane cu care ai vrea sa stai de vorba.
LI functioneaza ca orice alta aplicatie web, are SEO organic, adica returneaza cu prioritate profilurile care au cuvantul cheie present de cel mai multe ori.
In acest context sugestiile mele sunt urmatoarele:
  1. Completati sectiunile de skills de peste tot, de la LI – la summary, fiecare experienta, scolarizare. Puneti java, de exemplu, si adaugati la profilul vostru tot ce vi se potriveste din sugestiile oferite de aplicatie
Va atrag atentia ca la export LI NU exporta si aceste skilluri pt ca este un tampit, prin urmare le completati doar ca sa iesiti printre rpimii la cautari dupa cuvinte cheie. Este chestiune de clickuri, deci nu e bataie de cap
  1. La Summary, fiecare experienta profesionala, fiecare proiect si educatie introduceti o sectiune de skills, dedicata, de tools and technologies ca parte a descrierii jobului, in aceeasi sectiune cu responsabilitatile. Acestea vor fi exportate, in caz ca trimiteti CVul asa sau decide recrutorul sa faca export.
  2. CVul si LI trebuie sa fie in oglinda. Majoritatea recrutorilor tehnici fac aceasta comparatie si se uita si pe githubul vostru sau ce alte informatii mai oferiti in CV. Asa ca alegeti intelept ce informatii treceti aici, adica sa fie ceva ce chiar ati facut si stiti sa raspundeti la intrebari despre X sau Y din CV.
In final, desi vi se pare redundant, treceti TOATE detaliile tehnice.
De exemplu, multa lume scoate din CV, LI informatii banale, de gen HTML/CSS, pentru ca sunt by default. Asa este, dar sunt o gramada de recrutori non tehnici acre lucreaza in IT de putin timp, asa cum exista un numar tot mai mare de companii care faca analiza profiluriloCVurilor folosind tooluri de analiza de CV – nu intotdeauna performante. Aceste tooluri primesc niste cuvinte cheie si, daca nu le gasesc, nu treceti de selectie. Asa ca mai bine safe than sorry, mai ales in vremurile astea.
Criza de acum este la pitici fata de cea din 2008. Si atunci s-au facut disponibilizari, dar nu ca acum. Ca si context piata salariala romaneasca era MULT MULT mai competitiva decat acum (romanii cereau salarii mici si erau foarte buni), si erau MULT MULT mai putini oameni pe piata decat acum, mai ales in IT. Si atunci am avut guvern cretin, dar parca nu totalmente brainless ca acum si nu atat de obraznic, sa ne badjocoreasca pe fata si cu zambetul pe buze.
Asa ca cei care sunt in situatia de a isi cauta loc de munca, mai ales dintr-o tara cu zero protectie sociala, trebuie sa straluceasca. Si primul pas sunt CVul si profilul de LI.
Alte sfaturi
CV-ul format European
CV tabel
CVuri foarte colorate
CVuri cu mult text
CVuri de o pagina
CV in Engleza
Titlul CVului ca fisier
Tineti CVul si LI actualizate, constant
Persoana non-IT
Interviu HR
Cum verificati daca firma este ok?
o Analizati angajatii actuali – de cat timp sunt in firma? Ideal este sa vedeti cat mai multe profiluri mai vechi de 2 ani in firma respectiva
o Analizati angajatii care au plecat – cat timp au stat cu firma? Daca majoritatea au stat sub 2 ani e posibil sa fie o problema
o Abordati unul din fostii angajati, care a lucrat in acelasi department si rugati persoana sa va dea feedback. Fostii angajati au tendinta de a fi mai liberi in exprimare si mai onesti decat oricine altcineva care are de-a face cu firma.
o Daca vedeti reviewuri negative aveti de ales – riscati pt ca va arde somajul si tineti cu dintii de jobul asta pana gasiti altul sau trece criza SAU ziceti pas. Voi stiti care va sunt posibilitatile.
In final, dar nu in ultimul rand, tineti minte – interviul de angajare este reciproc. Atitudinea cu care mergeti la interviu este de egal cu egal, nu disperat si stapan. Chiar daca angajatorul are tendinta de a se comporta ca un stapan tratati-l ca pe un egal. Macar in interiorul vostru.
Si ultimul lucru – angajatorii care se comporta acum ok cu candidatii si angajatii sunt si cei de calitate. Este o perioada de putere pentru angajatori – ce fac cu ea spune multe despre caracterul liderilor si implicit a angajatorului. Sa ii tineti minte pe cei buni.
Link catre modele de CV cu care am avut rezultate foarte bune (aka oferte de munca/interviu):
https://www.dropbox.com/scl/fo/tpiytp30khm462n7ubr3o/h?rlkey=ib8sdeo783j4sk0vcqctrtl2d&dl=0
submitted by LIA_dating to CasualRO [link] [comments]


2024.02.17 10:16 LIA_dating Sfaturi legate de CV si interviuri

Salutare,
Fac aceasta postare proactiva ca forma de ajutor pentru cei care isi cauta loc de munca, dar nu numai.
Context – lucrez ca HR, in IT, de 20 de ani, cu focus majoritar pe recrutare. In toti acesti ani am oferit feed-back pe CV, solicitat sau nu 😊 (eu dau sfaturi nesolicitate, ca si cele de acum), multor mii de persoane. De cele mai multe ori, cei care mi-au ascultat indrumarile si-au gasit repede loc de munca si au avut oferte mai bune. In ultimele luni am dat cateza zeci de feed-backuri pe CV si nu mai fac fata, dar vreau sa ajut. Asa ca las acest text aici pentru cei care au nevoie de ajutor.
Bon, iata sugestiile mele legate de CV si profilul de linkedin.
CVul
  1. Poza – NU mai puneti poza de la chefuri, de pe munte etc. Nu sunt deal breaker, dar, pe o piata inundata de profesionisti cu experienta, o poza profi, din fata, fara fundal de mare, munte etc in spate etc. va crea impresie mai buna.
Uitati-va in camera cand faceti poza, asigurati-va ca aveti lumina pe fata si ca zambiti putin.
O camasa sau un tricou uniforme la culoare sunt suficiente.
2. Titulatura
Titulatura voastra trebuie sa fie relevanta pentru ceea ce stiti si ce cautati. Practic ii spuneti in cateva cuvinte cheie recrutorului cam care e treaba cu voi.
NU software developer, ci .net developer, java developer.
Daca sunteti seniori (in teorie 5 ani+ experienta), puneti si asta – Senior java developer etc.
Testerii – daca sunteti manual tester asta e titulatura voastra – manual software tester (puneti software, ca sa faceti diferenta de games). Automation tester, games etc. pueti chiar sa punel toolul pe care il stiti cel mai bine – de exemplu, Selenium automation software tester.
Devops/ SRE – puneti si cloud-ul pe care il stiti, AWS, Azure, Google. Exemplu, Senior devops (AWS).
Customer support – pe ce anume faceti suport. Exemple, Microsoft Office technical support; networking customer support; infrastructure customer support; invoices customer support; first level subscription customer support. Ati prins idea.
HR – IT recruiter; HR admin; Conflicts management HR; retention HR; training HR etc.
De ce sa faceti efortul?
Ca sa fiti mai smecheri ca altii. Ca sa faceti recrutorul sa ia o decizie usoara de a va selecta din marea de CVuri pe care o are de analizat acum, cand multa lume isi cauta.
Va place sau nu, hateriti sau nu, trebuie sa treceti de recrutor ca sa ajungeti la interviu.
3. Summary
Scurta prezentare de la inceput, daca alegeti sa o faceti (va recomand sa da), trebuie sa includa:
· date de contact (daca e pentru Linkedin, daca nu, aveti in CV datele de contact, ca sectiune separata). Mail e suficient, daca nu vreti sa va expuneti prea mult. Va va pune in legatura si cu recrutorii din firmele bogate care nu dau tooluri de recrutare echipei de HR, adica majoritatea 😊. Mai exact sunt o gramada de firme care fac o gramada de bani, dar nu cumpara pt HR abonamente la LI care sa le permita sa va contacteze direct. Asa ca trebuie sa treaca prin procesul de a va adauga in reteaua proprie, sa astepte sa ziceti da si apoi sa va scrie. Daca puneti mail/telefon la summary le faceti viata mai usoara si deja va simpatizeaza.
· Puneti datele de la contact in primul rand. La fel si interesul vostru – exemplu: interested only in full remote, B2B, min 20 euros/h. Ati prins ideea.
· Daca sunteti deja disponibilizati, sau junior la primul loc de munca, ori nu va pasa – puneti – open for work si apoi datele de contact. Exemplu – Senior IT Recruiter Open for Work; full remote/hybrid/office; [lia@lia.best.com](mailto:lia@lia.best.com)
· Precizati ce fel de colaborare acceptati, asa cum am aratat in exemplu - full remote/hybrid/office
· Pe randul 2 puneti ce stiti – tooluri si tehnologii sau ce inseamna puncte forte in meseria voastra (vanzari, recrutari tehnice, support, etc). Le puneti primele pe cele pe care le stiti cel mai bine si care sunt relevante pentru postul pe care il doriti. Dar e musai sa le scrieti. Dati informatie mura in gura cat mai multa.
· Abia apoi puneti detalii despre personalitatea voastra minunata.
4. Experienta:
· Nu imi vine sa cred ca trebuie sa spun asta in 2024, dar experienta si educatia se pun invers cronologic, intotdeauna. De la cel mai recent job avut pana la primul, de la cel mai recent curs pana la liceu, maxim.
· Structura de prezentare a fiecarui job in parte, pe care o recomand, este cea de mai jos:
Name and town of the employer: exemplu, LIA, Brasov, Romania
Company’s description: exemplu – dating platform, start-up
Position: NU mai scrieti ce titulatura interna ati avut acolo. Sunt prea multe companii care au tot felul de cucuri de denumiri interne care inseamna fix pix in ochii cuiva care nu lucreaza acolo. Developer 4 inseamna nimic pentru cineva care nu lucreaza pentru Amazon. Banuie ca esti smecher, dar nu stie CAT de smecher esti.
Cand va puneti titulatura alegeti denumiri relevante, ca in vazul variabilelor in cod. Trebuie sa aiba sens pentru toata lumea, nu doar pentru voi si inca cativa oameni.
Titlul postului avut trebuie sa vorbeasca de la sine legat de ce anume ati facut in firma respectiva ; - .net developer; java developer etc. exact ca mai sus, da.
Responsibilities
NU le mai scrieti text, bulk. Ne omorati ochii.
Puneti-le una sub alta, cu bulinuta.
Accesati acest site:
https://resources.workable.com/java-developer-job-description
Cautati fisa postului pentru ce faceti voi. Copy-paste. NU este necesar sa reinventati roata, nici sa fiti mega originali. JD-urile de aici sunt scurte, sintetice, super bine facute. Doar daca ati avut responsabilitati mai deosebite completati fata de ce gasiti aici.
Used Tools and technologies:
Puneti aici TOT ce ati folosit in firma respectiva, like TOT. Ganditi-va ca aveti de-a face cu un tool de analiza de profil/CV care NU stie ca React e javascript by default, nici ca spring e java, etc. Dati mura in gura, TOT.
Mentionati inclusiv ca ati folosit git, confluence, jira, whatever. Nu stiti niciodata ce pitici are managerul care recruteaza.
Ce va pot spune este ca exista o gama extraordinar de variata de pitici activi in recrutorii si managerii care au decizia finala pe o candidatura. Sugestia mea este sa acoperiti cat mai multi.
Indraznesc sa va sugerez sa puneti si versiunile cu care ati lucrat, mai ales in cazul programatorilor, dar nu numai. Eu m-am lovit de intrebari sceptice din partea celor de la tehnic – “daca nu a lucrat cu react 17? Intreaba inainte de il programa la tehnic”.
Developed projects:
Ce trebuie sa includeti aici:
- Scurta descriere functionala a proiectului – complex dating platform 😊
- Durata, daca o aveti. Nu e musai
- Ce ati facut voi din acel proiect
- Daca era proiect de la zero sau cu legacy code. Ambele experiente sunt extrem de bine cotate in ochii recrutorilor. Daca ati facut de amandoua deja aveti puncte in plus.
- Ce tooluri si tehnologii ati folosit pentru acel proiect
Cu ce va ajuta descrieri atat de detaliate?
- Indica munca, care va fi apreciata, de a va prezenta complet experienta voastra, fara ghicit
- Proiectele la care ati lucrat, cu tot cu industrie, sunt indicator foarte bun al experientei acumulate. O eventuala compatibilitate de industrie va poate scoate in fata comparative cu alti candidati cu experienta similara pentru ca ati inteles deja cum functioneaza industria. De exemplu, daca ati lucrat deja la un tool bancar va va fi mai usor sa mai dezvoltati unul.
- Tools si technologies la fiecare proiect pentru ca sunt multe persoane, mai ales cei din outsourcing care au lucrat cu tooluri si tehnologii diferite pe proiecte diferite. Daca acestea au fost uniforme, atunci faceti descrierea, spuneti ce ati facut pe proiect si la finalul descrierii proiectelor puneti toolurile si tehnologiile folosite. DAR, in cazul profilului de LI repetarea lor ajuta enorm pentru ca va creste SEO pe profil.
- Daca ati lucrat in firme de outsourcing si ati trecut prin proiecte cu diverse tehnologii, dar voi vreti sa va specializati pe una anume, treceti in CV doar proiectele in care ati lucrat cu ce vreti sa continuati. La interviu puteti povesti si despre altele.
- Daca ati lucrat la multe proiecte in aceeasi firma alegeti-le doar pe cele complexe, grele, din care ati invatat mult, de care sunteti mandri, la care ati avut contributia cea mai mare. Cele care va vor vinde, mai pe romaneste
Foarte important
Daca ati lucrat la aceeasi companie si ati avut diverse pozitii acolo NU le puneti ac experiente separate. Daca recrutorul este neatent sau oboist NU va remarca ca este aceeasi companie si vac rede ca schimbati des locul de munca. Cumulate-le in aceeasi experienta. Titulatura experientei este cea pe care o aveti in present. Exemplu:
2010 – present, CTO, LIA
2018 – present – CTO – puneti aici responsabilitati, proiecte etc, conform sugestiilor de mai jos
2015-2018 – department manager (mobile division)
2012 – 2015 – mobile (React native) team leader
2010 – 2012 – react Native (mobile) developer
5. Proiectele
· NU le mai puneti la final de CV. Nu aveti idee cat de putina lume chiar citeste CVul pana la capat. Dar cam toata lumea citeste experienta. Prin urmare, puneti proiectele la jobul la care le-ati facut.
· Daca aveti proiecte personale, creati-le ca experienta de sine statatoare de munca, NU le puneti la sectiunea de proiecte, nici in CV, nici pe LI. Din nou, nu se uita nimeni din pacate sau extrem de putina lume. Creati o sectiune in CV, ca o experienta de munca, care sa se numeasca, Personal Projects, si faceti descrierea proiectelor conform sugestiilor de mai sus.
6. Daca aveti joburi irelevante (pentru ca aveti alta directie de cariera) in trecut
- Nu le stergeti. Va aparea perioada lipsa in evolutia voastra profesionala si se gandeste lumea la prostii. Adunati-le intr-o singura experienta. Va dau exemplul meu:
Other jobs and activities: sept 2000 - May 2004 · 3 yrs 9 mos iasi, romania
o 2008-12 <> 2010-04, Polirom Publishing House, Iasi, Romania, Translator 2003-09 <> 2003-12, SC Forum Intermed SRL, real estate company in Iasi, Romania, Site managereal estate agent 2003-02 <> 2003-09, Polirom Publishing House, Iasi, Romania, Proofreader 2002-09 <> 2003-01, SC Univers’all SRL, supermarket, Suceava, Romania, Department manager
A le pastra in CV il lungeste degeaba si il incarca cu informatii irelevante
7. Educatie
Invers chronologic pusa
Puneti si liceul
Chiar daca nu ati terminat facultatea puneti facultatea inceputa. Puneti anul de incepere – present. BTW, Cei care nu aveti nicio diploma – faceti ceva facultate no name, la ID, luati hartia. Nu va ajuta cu nimic, dar va poate incurca daca nu o aveti.
Cei care nu ati dat lucrarea de licenta, dar sunteti absolventi. Faceti un proiect de 2 bani, dar functional, si dati licenta. Nu intereseaza pe nimeni ce ati facut la licenta sau la scoala oricum, ci ce stiti.
Da, diploma asta nu ne ajuta cu nimic, dar ne incurca daca nu o avem. As fi vrut sa imi spuna cineva asta cand ma agitam ca sprayul sa fac o lucrare de licenta interesanta cu care nici la fund nu s-a sters comisia. M-au scos din sala in 7 min, dupa un an de munca.
Profilul de linkedin
Sfaturile legate de profilul de LI provin din experienta de utilizare – in 2023 am facut 18 ani de cand sunt membru in retea si am avut la un moment dat un premiu pentru 1% cei mai frecventi utiliatori de LI la nivel global. Deci suntem prieteni vechi.
Cand un recrutor cauta candidati pe linkedin – asa numitul headhunting – foloseste ceva cuvinte cheie si dupa aceste cautari I se afiseaza o lista de profiluri care sunt puchinoase si una sub alta, cu informatiile esentiale despre persoana returnata – nume, poza, titulatura si titulatura jobului actual. Modulul de search de la LI s-a dus naibii odata cu Microsoft asa ca, majoritatea recrutorilor folosesc 1, max 2 cuvinte cheie in aceste cautari pentru ca altfel LI se zapaceste si returneaza porcarii sau prea putine profiluri. De asemenea, majoritatea candidatilor au informatii insuficiente sau vagi in profil, asa ca folosirea de cuvinte cheie prea specifice iti poate scoate din cautare persoane cu care ai vrea sa stai de vorba.
LI functioneaza ca orice alta aplicatie web, are SEO organic, adica returneaza cu prioritate profilurile care au cuvantul cheie present de cel mai multe ori.
In acest context sugestiile mele sunt urmatoarele:
  1. Completati sectiunile de skills de peste tot, de la LI – la summary, fiecare experienta, scolarizare. Puneti java, de exemplu, si adaugati la profilul vostru tot ce vi se potriveste din sugestiile oferite de aplicatie
Va atrag atentia ca la export LI NU exporta si aceste skilluri pt ca este un tampit, prin urmare le completati doar ca sa iesiti printre rpimii la cautari dupa cuvinte cheie. Este chestiune de clickuri, deci nu e bataie de cap
  1. La Summary, fiecare experienta profesionala, fiecare proiect si educatie introduceti o sectiune de skills, dedicata, de tools and technologies ca parte a descrierii jobului, in aceeasi sectiune cu responsabilitatile. Acestea vor fi exportate, in caz ca trimiteti CVul asa sau decide recrutorul sa faca export.
  2. CVul si LI trebuie sa fie in oglinda. Majoritatea recrutorilor tehnici fac aceasta comparatie si se uita si pe githubul vostru sau ce alte informatii mai oferiti in CV. Asa ca alegeti intelept ce informatii treceti aici, adica sa fie ceva ce chiar ati facut si stiti sa raspundeti la intrebari despre X sau Y din CV.
In final, desi vi se pare redundant, treceti TOATE detaliile tehnice.
De exemplu, multa lume scoate din CV, LI informatii banale, de gen HTML/CSS, pentru ca sunt by default. Asa este, dar sunt o gramada de recrutori non tehnici acre lucreaza in IT de putin timp, asa cum exista un numar tot mai mare de companii care faca analiza profiluriloCVurilor folosind tooluri de analiza de CV – nu intotdeauna performante. Aceste tooluri primesc niste cuvinte cheie si, daca nu le gasesc, nu treceti de selectie. Asa ca mai bine safe than sorry, mai ales in vremurile astea.
Criza de acum este la pitici fata de cea din 2008. Si atunci s-au facut disponibilizari, dar nu ca acum. Ca si context piata salariala romaneasca era MULT MULT mai competitiva decat acum (romanii cereau salarii mici si erau foarte buni), si erau MULT MULT mai putini oameni pe piata decat acum, mai ales in IT. Si atunci am avut guvern cretin, dar parca nu totalmente brainless ca acum si nu atat de obraznic, sa ne badjocoreasca pe fata si cu zambetul pe buze.
Asa ca cei care sunt in situatia de a isi cauta loc de munca, mai ales dintr-o tara cu zero protectie sociala, trebuie sa straluceasca. Si primul pas sunt CVul si profilul de LI.
Alte sfaturi
CV-ul format European
- Cine a factu acest format de CV este o persoana cu un singur neuron care nu a vazut vreodata un CV. Est incredibil de enervant pt recrutor. Exceptand situatia in care aplicati pe EU sau vi se cere specific format European evitati-l.
CV tabel
- Ma refer la cel care are informatii pe 2 coloane. Nu stiu cine a venit cu moda asta, dar NU e una buna. Senzatia este de inghesuit, de aglomerat. Obligati recrutorul, care citeste sute de profiluri, sa caute pe pagina informatile ca sa vada daca va potriviti sau nu. Il iritati. Este si el/ea om, obosit, stresat. Va reamintesc – daca ii dai mura in gura ii faceti viata usoara si treceti de selectia CVuurilor.
CVuri foarte colorate
- No no, nici daca esti designer. Intrati pe profilul meu de LI, am facut o postare dedicata pentru designeri, ca majoritatea candidaturilor sunt praf pur si simplu.
- Alegeti o singura culoare, de preferat un albastru elegant, si o folositi DOAR pentru a marca sectiuni MARI din CV – titulatura si nume, experienta, educatie, hobbyuri. In rest alb si negri
CVuri cu mult text
- No no. Nu citeste nimeni. De aceea v-am sugerat sa cautati JD pe workable, sunt puse frumos responsabilitatile, cu bulinuta, unele sub altele. Sunt usor de citit si de inteles. Folositi principiul KISS aici.
CVuri de o pagina
- Pot sa inteleg temerea asta. Cine pune presiune pe un CV de o pagina angajeaza doar juniori sau este o persoana care nu respecta munca celorlalti. DAR, pentru ca stiu ca se cere asta, am creat o struto-camila de format care impaca si capra, si varza. Pe prima pagina faci sinteza experientei si apoi detaliezi experienta si proiectele fara stresul ca e prea lung CVul.
- Am pus in linkul de la final modele de CV pe care le-am create/salvat pentru ca erau foarte bine facute si au trecut de selectia tehnica cu succes.
CV in Engleza
- Faceti CVul in enegleza by default. Aproape toate firmele din Romania lucreaza, intr-un fel sau altul, cu firme din strainatate, engleza e ca a doua limba nationala.
- Daca totusi vreti sa aveti ambele variante creati-le si trimiteti-le pe amandoua, daca se poate. Mai bine au de ales decat sa fie insuficient
Titlul CVului ca fisier
- Prenume, nume, post
- Multa lume denumeste CVul aiurea si, daca avem o scapare ca recrutori, si uitam sa il redenumit cand il salvam ne ia gaia pana il gasim.
Tineti CVul si LI actualizate, constant
- Uitam chestii pe care le facem, chiar daca ni se pare ca nu
- Asa ca este o practica iteleapta sa tinem CVul la zi. Am facut un proiect, pun in CV, am mai invatat sa fac ceva – pun in CV. Este o practica care va va si ajuta sa puteti trimite CVul instant la cerere.
Persoana non-IT
- Formatul sugerat este acelasi, eliminati parte de proiecte daca este cazul
Interviu HR
- Dozati sinceritatea. Este impotriva principiilor mele de viata sa sugerez asta, dar parerea mea este ca trebuie. Lasati la o parte sefii si kkturile pe care le fac. Motive care au sens intotdeauna pentru cei de la HR – inchiderea firmei (aveti grija ca asta se poate verifica); dorinta de a lucra pe proiect intern vs outsourcing; dorinta de a lucra pe alt proiect; nevoia de a invata lucruri noi, de a testa alte industrii si stiluri de lucru, oportunitatile de promovare. Sugestia mea este sa va abtineti de la a spune mai multe de atat.
- Zambiti cat mai mult, chiar daca interviul este telefonic – conteaza mult si se vede/simte.
- Ca si in cazul pozei, un tricou simplu/camasa simpla, blugi intregi si drepti; o rochita simpla, pana la genunchi, cu machiaj discret sunt suficiente pentru interviu. Daca va place sa purtati haine colorate, cele pastelate transmit cel mai bun mesaj (sociabilitate, comunicare).
- Raspundeti la subiect, incercati sa nu va pierdeti in detalii.
- Daca nu stiti sa raspundeti la intrebare spuneti fix asta “nu stiu”, dar profitati de ocazie sa cereti raspunsul corect.
- NU mentionati ca ati facut freelancing si job in paralel – indica lipsa de loialitate si focus. Majoritatea dintre noi facem asta, dar, cumva, asta a ajuns sa fie motiv de isterie in randul managerilor spalati pe creier, prin urmare se cere dedicare 100% pentru companie. Daca va ajuta experienta de freelancer facuta in paralel cu jobul precizati ca vreti sa aveti un worklife balance mai bun si doriti ca la urmatorul loc de munca sa fiti 100% dedicati. Ulterior, dupa ce luati jobul NU va laudati cu proiectele de freelancing.
- Creati o lista detaliata si clara de intrebari pentru interviu – administrativ si tehnic. Majoritatea candidatilor se lasa furati de interviu si omit sa puna intrebari. Ceea ce va face sa va lamuriti care e treaba cu firma dupa ce ati inceput sa lucrati acolo. O decizie informata este una asumata. Asa ca anuntati intervievatorul ca aveti o lista de intrebari, inca de la inceputul interviului, ca sa isi aloce timp pentru voi. Daca nu vi se raspudne la intrebari sau primiti raspunsuri vagi aveti semnale de alarma vizavi de firma
Cum verificati daca firma este ok?
- Undelucram.com – aveti grija CINE a scris reviewul. In general departamentele de support – HR, legal, conta, support si IT sunt caii de bataie ale companiilor, asa ca au tendinta de a fi mai putini fericiti in evaluare. Incercati sa gasiti o evaluare facuta de cineva cu aceasi functie.
- Glasdoor.com
- Linkedin:
o Analizati angajatii actuali – de cat timp sunt in firma? Ideal este sa vedeti cat mai multe profiluri mai vechi de 2 ani in firma respectiva
o Analizati angajatii care au plecat – cat timp au stat cu firma? Daca majoritatea au stat sub 2 ani e posibil sa fie o problema
o Abordati unul din fostii angajati, care a lucrat in acelasi department si rugati persoana sa va dea feed-back. Fostii angajati au tendinta de a fi mai liberi in exprimare si mai onesti decat oricine altcineva care are de-a face cu firma.
o Daca vedeti reviewuri negative aveti de ales – riscati pt ca va arde somajul si tineti cu dintii de jobul asta pana gasiti altul sau trece criza SAU ziceti pas. Voi stiti care va sunt posibilitatile.
In final, dar nu in ultimul rand, tineti minte – interviul de angajare este reciproc. Atitudinea cu care mergeti la interviu este de egal cu egal, nu disperat si stapan. Chiar daca angajatorul are tendinta de a se comporta ca un stapan tratati-l ca pe un egal. Macar in interiorul vostru.
Si ultimul lucru – angajatorii care se comporta acum ok cu candidatii si angajatii sunt si cei de calitate. Este o perioada de putere pentru angajatori – ce fac cu ea spune multe despre caracterul liderilor si implicit a angajatorului. Sa ii tineti minte pe cei buni.
Link catre modele de CV cu care am avut rezultate foarte bune (aka oferte de munca/interviu):
https://www.dropbox.com/scl/fo/tpiytp30khm462n7ubr3o/h?rlkey=ib8sdeo783j4sk0vcqctrtl2d&dl=0
submitted by LIA_dating to programare [link] [comments]


2024.02.17 08:58 prakash_jpn Hardware requirement for Selenium

I wanted to use the python script using selenium which automate my chrome driver. For that I created a script and I have tested the automation via my local machine everything works fine and now I want to use it on the production environment. I tried to change the .py file to .exe and it was converted however I cannot run the program successfully because of the several module dependency. Can anybody suggest me on below topics:
  1. Best Hardware requirements to run python with selenium?
  2. To run python 24x7 365 days is visual studio code is good or the python IDE is good?
  3. Is there any other tool to convert in to exe?
  4. Is there any effects that may be faced if I run using VS Code or Python IDE 24x7 365 days?
(Note: the code will automatically clear the terminal every 90 seconds)

submitted by prakash_jpn to sysadmin [link] [comments]


http://rodzice.org/