{"id":18443,"date":"2016-10-31T10:00:20","date_gmt":"2016-10-31T14:00:20","guid":{"rendered":"https:\/\/simpleprogrammer.com\/?p=18443"},"modified":"2017-10-24T15:40:23","modified_gmt":"2017-10-24T19:40:23","slug":"going-from-qa-to-software-developer","status":"publish","type":"post","link":"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/","title":{"rendered":"Going from QA (or Another Technical Role) to Software Developer"},"content":{"rendered":"

I decided to dedicate a whole chapter to this topic because it\u2019s one of the most common questions I get asked. Making the transition from QA or some other technical role to being a software developer<\/a> can be extremely difficult.<\/strong>\\\\n\\\\nI made the transition myself\u2014in fact, I had to do it twice.\\\\n\\\\nThe first time I made the transition was when I had just started out in my career.\\\\n\\\\nI had been a self-taught programmer and had taken a year of college in a computer science program, but I couldn\u2019t find a job as a programmer<\/strong>, so I started a job doing QA as a contractor for HP.\\\\n\\\\nInitially, my job was brainlessly simple.\"Software\\\\n\\\\nI\u2019d go through stacks of printed tests, which were compared to a \u201cmaster\u201d printout that had already been flagged, and I\u2019d look at the differences to see if they were known issues or new bugs that had been introduced in the latest printing firmware.\\\\n\\\\nThe job was pretty boring.\\\\n\\\\nWe were just supposed to look at flagged differences and decide if they were a big deal or not.\\\\n\\\\nI wasn\u2019t happy with that. I wanted to know what caused the differences, so I started digging a little deeper.\\\\n\\\\nI asked to have access to the actual print instructions which were sent to the printer for each test.\\\\n\\\\nThe print instructions were either in PCL or PostScript, two popular printing languages.\\\\n\\\\nI spent my own time and any downtime to learn both PCL and PostScript<\/strong>.\\\\n\\\\nI became an expert in both.\\\\n\\\\nThen when I looked at errors, I would go through the printer test and modify them, using my understanding of the printer languages to test my theories about why specific printer language commands were causing the problems.\\\\n\\\\nPretty soon I was filing detailed bug reports with snippets of printer code, indicating exactly what printer language commands were likely to be behaving wrong and causing the errors.\\\\n\\\\nIt didn\u2019t take long before the software development team became interested in pulling me in as a resource to show them how and what I was doing and for me to do more of it.\\\\n\\\\nI was eventually asked to write printer tests, and thus I officially became a programmer and got an actual programmer title.\\\\n\\\\nLater in my career, I went through a similar experience when I couldn\u2019t find a software development job and again found myself at HP, this time in the role of a QA test lead.\\\\n\\\\nThis time, I was sitting next to a fairly new software developer who didn\u2019t have too good of a grasp of C++.\\\\n\\\\nWhen we\u2019d chat about some of the problems he was facing, I\u2019d come over to his cubicle and give him some tips and help to get his tasks done.\\\\n\\\\nI didn\u2019t take any credit and only tried to make him look as good as possible.<\/strong>\\\\n\\\\nAfter a few weeks of this, he started telling his boss how much I knew about C++ and how it seemed like a ridiculous waste to have someone who knew this much about software development writing test cases.\\\\n\\\\nWhen a big deadline came up, the software development team asked to borrow me as a resource to help meet the deadline.\\\\n\\\\nOnce I was working with the development team, they didn\u2019t want to give me back<\/a>. Thus my role was switched to software developer once again.\\\\n\\\\n<\/p>\n

The Biggest Hurdle You\u2019ll Face<\/h2>\n

\\\\n\\\\n\\\\n\\\\nPerhaps the biggest hurdle you will face in switching from QA or some other technical role into software development is the perceptions people have of you.\\\\n\\\\nOnce you have a role within a company, people tend to always see you as that particular role, regardless of your skill set or how you grow.<\/strong>\\\\n\\\\nIn the software development world, in particular, there is usually a sharp distinction between software developers and testers (or QA).\\\\n\\\\nBecause of this bias, coming into a new company as a software developer is often easier than transitioning to a software development role from being a tester or other position.\\\\n\\\\nThis can be extremely frustrating\u2014especially if you\u2019ve outgrown your previous role.\\\\n\\\\nYou will have to be patient, and realize that although it will take time for perceptions to change<\/strong>, they eventually will.\\\\n\\\\nThe more you can involve yourself in the software development side of the organization and take on more programming tasks, the more that other people in the organization will start to see you in the new role.\\\\n\\\\nSometimes, though, you may have to move to a completely different company to escape the box you\u2019ve been put into.\\\\n\\\\nLet\u2019s talk now about some strategies other software developers and I have used in the past to make the transition from a non-developer technical role to software developer.\\\\n\\\\n<\/p>\n

Make Your Goal Known<\/h2>\n

\\\\n\\\\nMy first piece of advice for you would be to go ahead and make your goal known as widely as possible.<\/a>\\\\n\\\\nLet your coworkers know that you are aspiring to move into development.<\/strong>\\\\n\\\\nAsk for a meeting with your boss or manager, and frankly tell them that you\u2019d like to move into a software development role and that you are willing to do whatever it takes to get there.<\/strong>\\\\n\\\\nWhen you talk about this goal with your boss, make sure you discuss how your testing background will benefit the company when you eventually move into a programmer role.\\\\n\\\\nTalk about the benefits your company will gain from you making the transition.<\/strong>\\\\n\\\\nThe more it is known that you want to move into a software development role, the more you\u2019ll start to chip away at the bias people might have about keeping you in your current role, so don\u2019t be afraid to openly talk about it.\\\\n\\\\nBut talk is cheap.\\\\n\\\\nIf you keep saying that someday you want to become a software developer and you aren\u2019t doing anything about it or learning programming, you are going to sound like a hopeless dreamer.\\\\n\\\\nMake sure you back up your talk with action<\/a>.<\/strong>\\\\n\\\\nWhen you do have this conversation with your boss, see if you can get a list of requirements or a course you can take that will move you from your current role to one working as a software developer.<\/strong>\\\\n\\\\nIf you can nail down a list of things you need to learn or milestones you need to achieve, you can create a much more solid case for making the transition, when you are ready.\\\\n\\\\nI\u2019ve used this exact technique to not only switch into new roles but also to get promotions.\\\\n\\\\nI\u2019ve simply asked what I would need to accomplish or what skills I would need to improve to get a promotion, then I\u2019ve gone and done all of those things and asked for the promotion.\\\\n\\\\nIt\u2019s not foolproof\u2014you could still be denied your request\u2014but if you\u2019ve got a list of what you need to do and you\u2019ve done it all, then it\u2019s pretty difficult to form a case against your advancement.\\\\n\\\\n<\/p>\n

Ask for Opportunities<\/h2>\n

\\\\n\\\\n\\\\n\\\\nIf you really want to move into software development, don\u2019t wait for someone to hand you the title and assign you work. Instead, ask for opportunities to do some programming even while you are in your current role.\\\\n\\\\nAsk your boss for one or two simple assignments.<\/strong>\\\\n\\\\nAsk if there are any bugs you can fix.\\\\n\\\\nAnd keep asking.\\\\n\\\\nYou may be refused the first few times or it may seem like too much of a hassle to assign you a task that someone is going to have to explain to you how to do, but if you are the squeaky wheel and you keep asking, there is a good chance you\u2019ll eventually get something thrown your way<\/strong>\u2014even if it’s only to shut you up.\\\\n\\\\n<\/p>\n

Make Your Own Opportunities<\/h2>\n

\\\\n\\\\nSometimes, though\u2014quite often, actually\u2014you are not going to get opportunities to do software development, even if you ask.\\\\n\\\\nLike I said, it might be because explaining a task to you would take more time than it\u2019s worth, and most projects are always behind.\\\\n\\\\nIt might be because, frankly, your boss or coworkers don\u2019t believe you have the technical chops to take on software development work because they see you as \u201cjust a tester\u201d or \u201cLinux admin\u201d or \u201ctechnical support person,\u201d or whatever it might be.\\\\n\\\\nYou might have to make your own opportunities<\/strong>.\\\\n\\\\nYou might have to take it upon yourself to look for areas where you can help out and contribute without getting in anyone\u2019s way or taking up their time asking questions.\\\\n\\\\nOften these opportunities lie in what I call the \u201cdirty work<\/a>.\u201d\\\\n\\\\nThat is the stuff that no one wants to do.\\\\n\\\\nIt\u2019s the coding equivalent of cleaning the toilet.<\/strong>\\\\n\\\\nPerhaps it\u2019s debugging this really nasty bug that no one has been able to figure out.\\\\n\\\\nPerhaps it\u2019s writing up documentation for an API or building a tool to make things easier for everyone else.\\\\n\\\\nIt\u2019s probably going to be the boring work that is difficult, but if you want to find a project that no one will fight you for, it\u2019s likely to be \u201cdirty work.\u201d\\\\n\\\\nBe ready to roll up your sleeves and dig in.<\/strong>\\\\n\\\\n<\/p>\n

Use Your Own Time<\/h2>\n

\\\\n\\\\nSome bosses might assign you some small programming tasks you can do as part of your regular workload.\\\\n\\\\nSome bosses might be ok with you spending some of your time picking up the \u201cdirty work\u201d kind of projects I mentioned above.\\\\n\\\\nHowever, that will not always be the case.\\\\n\\\\nIn fact, in many work environments, you are likely to get a slap on the wrist if you start doing software development work when you are supposed to be doing your regular job.<\/strong>\\\\n\\\\nIn those cases, if you really want to get your shot at software development, you are going to have to be willing to give a little\u2014or a lot\u2014of your own unpaid time to further your mission.<\/strong>\\\\n\\\\nEven if you are given some work time to work on software development tasks in your current role, it\u2019s still a good idea to devote some extra, unpaid hours to those tasks, so that you can move the needle much further, much faster.\\\\n\\\\nBe willing to get in early or to stay after work to get extra projects done.<\/strong>\\\\n\\\\nIf you are having a difficult time finding anyone who will let you work on tasks involving software development, you will probably have much more success if you are willing to do the work on your own time.\\\\n\\\\nIt\u2019s an offer that most companies would find difficult to refuse.\\\\n\\\\n<\/p>\n

Look for Bridges<\/h2>\n

\\\\n\\\\n\\\\n\\\\nOne really good way to make the transition from a job like QA to software development is to find a bridge job that will put you between the two roles<\/strong>.\\\\n\\\\nFor many testers, automation is a great bridge<\/a><\/strong>.\\\\n\\\\nIf you can start taking on test automation tasks, you\u2019ll get a chance to write code to automate manual tests.\\\\n\\\\nConvincing your boss to let you do test automation<\/a> is usually going to be an easier sell than convincing him to let you become a junior developer without any real experience.<\/strong>\\\\n\\\\nIt\u2019s a win-win situation because you gain valuable, real programming experience, and your company gains the benefit of automated tests, which make the entire organization more efficient.\\\\n\\\\nOnce you have the title of test automation engineer or software developer in test, it\u2019s going to be extremely easy to move into a regular software development role at any company because now you have real experience being paid to write code.<\/strong>\\\\n\\\\nIn fact, you might find that test automation is more fun and rewarding than doing testing alone or<\/strong> regular software development.\\\\n\\\\n(I love designing automated testing frameworks<\/a>. It\u2019s one of my favorite technology areas, which I find extremely rewarding and challenging.<\/em>)\\\\n\\\\nThere are bridge opportunities to software development from many other technical jobs as well..\\\\n\\\\nFor instance, Linux administrators can become tool developers <\/strong>or easily move into devops positions<\/strong> where they can use their Linux administration skills, scripting, and programming to automate tasks and build tools that benefit everyone.\\\\n\\\\nTechnical support people can move into roles where they do technical support for developers or even become higher-tiered support technicians who dive into the code to try and solve customer problems<\/strong> or gather information to send to developers.<\/strong>\\\\n\\\\nLook for ways you can leverage your existing skills and responsibilities in some kind of development capacity, and you can create your own bridge job.\\\\n\\\\n<\/p>\n

Moving to a New Company\"Paper<\/h2>\n

\\\\n\\\\nMost of what I\u2019ve talked about in this chapter has assumed that you\u2019d be making the transition from QA or some other technical role to software developer within the same company, but that is not always possible or desirable.\\\\n\\\\nHow, then, do you go from a tester at one company to a developer at another company?<\/strong>\\\\n\\\\nActually, most of the same advice I\u2019ve given you in this chapter still applies; it\u2019s just that your job title doesn\u2019t change until you switch companies.\\\\n\\\\nWhat I mean by this is that you should be trying to get some kind of development experience at your current job\u2014even if you can\u2019t move into a software development role\u2014simply so that you can put that experience on your resume when you apply for a software development role in another company.\\\\n\\\\nEven if you built some tools that helped you do your job, that no one blessed, and you did on your own time, you have the opportunity to put that on your resume as real development work, which is going to greatly help you get your first development job.\\\\n\\\\nBridge jobs are also going to be extremely useful here, especially if you can get your title to have developer or engineer in it.\\\\n\\\\n<\/p>\n

My Last Piece of Advice<\/h2>\n

\\\\n\\\\nDon\u2019t get discouraged.\\\\n\\\\nIt\u2019s often more difficult to transition from another technical role into software development, simply because of the bias I talked about before, where people tend to see you as \u201cjust a tester\u201d or \u201cjust a server admin,\u201d etc.\\\\n\\\\nHowever, if you are willing to do the extra work and be \u201cso good they can\u2019t ignore you<\/a>,\u201d as Cal Newport says in his book of the same title<\/a>, you are eventually going to hit success.<\/strong>\\\\n\\\\nKeep learning, keep improving your skills, keep looking for opportunities and making your own, and you\u2019ll get what you are after.\\\\n\\\\nPatience and perseverance are key.\\\\n\\\\n<\/p>\n

\n

\\\\n\\\\n<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

I decided to dedicate a whole chapter to this topic because it\u2019s one of the most common questions I get asked. Making the transition from QA or some other technical role to being a software developer can be extremely difficult.\\\\n\\\\nI made the transition myself\u2014in fact, I had to do it twice.\\\\n\\\\nThe first time I made…<\/p>\n","protected":false},"author":2,"featured_media":18454,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","footnotes":""},"categories":[162229812,14560,162228966,162229782,5895,162229840],"tags":[],"class_list":["post-18443","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-advice","category-career","category-education-2","category-goals","category-self-improvement","category-skills"],"yoast_head":"\nGoing from QA (or Another Technical Role) to Software Developer - Simple Programmer<\/title>\n<meta name=\"description\" content=\"Making the transition from QA or some other technical role to being a software developer can be extremely difficult, but it's not impossible. Here's how.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Going from QA (or Another Technical Role) to Software Developer - Simple Programmer\" \/>\n<meta property=\"og:description\" content=\"Making the transition from QA or some other technical role to being a software developer can be extremely difficult, but it's not impossible. Here's how.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/\" \/>\n<meta property=\"og:site_name\" content=\"Simple Programmer\" \/>\n<meta property=\"article:published_time\" content=\"2016-10-31T14:00:20+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2017-10-24T19:40:23+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/simpleprogrammer.com\/wp-content\/uploads\/2016\/10\/Moving-From-QA-To-Another-Role-In-Software-Development.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1280\" \/>\n\t<meta property=\"og:image:height\" content=\"720\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"John Sonmez\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"John Sonmez\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"13 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/simpleprogrammer.com\\\/going-from-qa-to-software-developer\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/simpleprogrammer.com\\\/going-from-qa-to-software-developer\\\/\"},\"author\":{\"name\":\"John Sonmez\",\"@id\":\"https:\\\/\\\/simpleprogrammer.com\\\/#\\\/schema\\\/person\\\/1abc70edfb189184827740310672de67\"},\"headline\":\"Going from QA (or Another Technical Role) to Software Developer\",\"datePublished\":\"2016-10-31T14:00:20+00:00\",\"dateModified\":\"2017-10-24T19:40:23+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/simpleprogrammer.com\\\/going-from-qa-to-software-developer\\\/\"},\"wordCount\":2567,\"commentCount\":2,\"image\":{\"@id\":\"https:\\\/\\\/simpleprogrammer.com\\\/going-from-qa-to-software-developer\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/simpleprogrammer.com\\\/wp-content\\\/uploads\\\/2016\\\/10\\\/Moving-From-QA-To-Another-Role-In-Software-Development.png\",\"articleSection\":[\"Advice\",\"Career\",\"Education\",\"Goals\",\"Self Improvement\",\"Skills\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/simpleprogrammer.com\\\/going-from-qa-to-software-developer\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/simpleprogrammer.com\\\/going-from-qa-to-software-developer\\\/\",\"url\":\"https:\\\/\\\/simpleprogrammer.com\\\/going-from-qa-to-software-developer\\\/\",\"name\":\"Going from QA (or Another Technical Role) to Software Developer - Simple Programmer\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/simpleprogrammer.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/simpleprogrammer.com\\\/going-from-qa-to-software-developer\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/simpleprogrammer.com\\\/going-from-qa-to-software-developer\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/simpleprogrammer.com\\\/wp-content\\\/uploads\\\/2016\\\/10\\\/Moving-From-QA-To-Another-Role-In-Software-Development.png\",\"datePublished\":\"2016-10-31T14:00:20+00:00\",\"dateModified\":\"2017-10-24T19:40:23+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/simpleprogrammer.com\\\/#\\\/schema\\\/person\\\/1abc70edfb189184827740310672de67\"},\"description\":\"Making the transition from QA or some other technical role to being a software developer can be extremely difficult, but it's not impossible. Here's how.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/simpleprogrammer.com\\\/going-from-qa-to-software-developer\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/simpleprogrammer.com\\\/going-from-qa-to-software-developer\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/simpleprogrammer.com\\\/going-from-qa-to-software-developer\\\/#primaryimage\",\"url\":\"https:\\\/\\\/simpleprogrammer.com\\\/wp-content\\\/uploads\\\/2016\\\/10\\\/Moving-From-QA-To-Another-Role-In-Software-Development.png\",\"contentUrl\":\"https:\\\/\\\/simpleprogrammer.com\\\/wp-content\\\/uploads\\\/2016\\\/10\\\/Moving-From-QA-To-Another-Role-In-Software-Development.png\",\"width\":1280,\"height\":720},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/simpleprogrammer.com\\\/going-from-qa-to-software-developer\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/simpleprogrammer.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Going from QA (or Another Technical Role) to Software Developer\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/simpleprogrammer.com\\\/#website\",\"url\":\"https:\\\/\\\/simpleprogrammer.com\\\/\",\"name\":\"Simple Programmer\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/simpleprogrammer.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/simpleprogrammer.com\\\/#\\\/schema\\\/person\\\/1abc70edfb189184827740310672de67\",\"name\":\"John Sonmez\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/dc2f18dfa76e017566ce607de002d7abe4acfd5ec19a6db82c180b00867b8d94?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/dc2f18dfa76e017566ce607de002d7abe4acfd5ec19a6db82c180b00867b8d94?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/dc2f18dfa76e017566ce607de002d7abe4acfd5ec19a6db82c180b00867b8d94?s=96&d=mm&r=g\",\"caption\":\"John Sonmez\"},\"url\":\"https:\\\/\\\/simpleprogrammer.com\\\/author\\\/jsonmez\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Going from QA (or Another Technical Role) to Software Developer - Simple Programmer","description":"Making the transition from QA or some other technical role to being a software developer can be extremely difficult, but it's not impossible. Here's how.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/","og_locale":"en_US","og_type":"article","og_title":"Going from QA (or Another Technical Role) to Software Developer - Simple Programmer","og_description":"Making the transition from QA or some other technical role to being a software developer can be extremely difficult, but it's not impossible. Here's how.","og_url":"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/","og_site_name":"Simple Programmer","article_published_time":"2016-10-31T14:00:20+00:00","article_modified_time":"2017-10-24T19:40:23+00:00","og_image":[{"width":1280,"height":720,"url":"https:\/\/simpleprogrammer.com\/wp-content\/uploads\/2016\/10\/Moving-From-QA-To-Another-Role-In-Software-Development.png","type":"image\/png"}],"author":"John Sonmez","twitter_card":"summary_large_image","twitter_misc":{"Written by":"John Sonmez","Est. reading time":"13 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/#article","isPartOf":{"@id":"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/"},"author":{"name":"John Sonmez","@id":"https:\/\/simpleprogrammer.com\/#\/schema\/person\/1abc70edfb189184827740310672de67"},"headline":"Going from QA (or Another Technical Role) to Software Developer","datePublished":"2016-10-31T14:00:20+00:00","dateModified":"2017-10-24T19:40:23+00:00","mainEntityOfPage":{"@id":"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/"},"wordCount":2567,"commentCount":2,"image":{"@id":"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/#primaryimage"},"thumbnailUrl":"https:\/\/simpleprogrammer.com\/wp-content\/uploads\/2016\/10\/Moving-From-QA-To-Another-Role-In-Software-Development.png","articleSection":["Advice","Career","Education","Goals","Self Improvement","Skills"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/","url":"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/","name":"Going from QA (or Another Technical Role) to Software Developer - Simple Programmer","isPartOf":{"@id":"https:\/\/simpleprogrammer.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/#primaryimage"},"image":{"@id":"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/#primaryimage"},"thumbnailUrl":"https:\/\/simpleprogrammer.com\/wp-content\/uploads\/2016\/10\/Moving-From-QA-To-Another-Role-In-Software-Development.png","datePublished":"2016-10-31T14:00:20+00:00","dateModified":"2017-10-24T19:40:23+00:00","author":{"@id":"https:\/\/simpleprogrammer.com\/#\/schema\/person\/1abc70edfb189184827740310672de67"},"description":"Making the transition from QA or some other technical role to being a software developer can be extremely difficult, but it's not impossible. Here's how.","breadcrumb":{"@id":"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/#primaryimage","url":"https:\/\/simpleprogrammer.com\/wp-content\/uploads\/2016\/10\/Moving-From-QA-To-Another-Role-In-Software-Development.png","contentUrl":"https:\/\/simpleprogrammer.com\/wp-content\/uploads\/2016\/10\/Moving-From-QA-To-Another-Role-In-Software-Development.png","width":1280,"height":720},{"@type":"BreadcrumbList","@id":"https:\/\/simpleprogrammer.com\/going-from-qa-to-software-developer\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/simpleprogrammer.com\/"},{"@type":"ListItem","position":2,"name":"Going from QA (or Another Technical Role) to Software Developer"}]},{"@type":"WebSite","@id":"https:\/\/simpleprogrammer.com\/#website","url":"https:\/\/simpleprogrammer.com\/","name":"Simple Programmer","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/simpleprogrammer.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/simpleprogrammer.com\/#\/schema\/person\/1abc70edfb189184827740310672de67","name":"John Sonmez","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/dc2f18dfa76e017566ce607de002d7abe4acfd5ec19a6db82c180b00867b8d94?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/dc2f18dfa76e017566ce607de002d7abe4acfd5ec19a6db82c180b00867b8d94?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/dc2f18dfa76e017566ce607de002d7abe4acfd5ec19a6db82c180b00867b8d94?s=96&d=mm&r=g","caption":"John Sonmez"},"url":"https:\/\/simpleprogrammer.com\/author\/jsonmez\/"}]}},"_links":{"self":[{"href":"https:\/\/simpleprogrammer.com\/wp-json\/wp\/v2\/posts\/18443","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/simpleprogrammer.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/simpleprogrammer.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/simpleprogrammer.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/simpleprogrammer.com\/wp-json\/wp\/v2\/comments?post=18443"}],"version-history":[{"count":0,"href":"https:\/\/simpleprogrammer.com\/wp-json\/wp\/v2\/posts\/18443\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/simpleprogrammer.com\/wp-json\/wp\/v2\/media\/18454"}],"wp:attachment":[{"href":"https:\/\/simpleprogrammer.com\/wp-json\/wp\/v2\/media?parent=18443"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/simpleprogrammer.com\/wp-json\/wp\/v2\/categories?post=18443"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/simpleprogrammer.com\/wp-json\/wp\/v2\/tags?post=18443"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}