{"id":999882139,"date":"2024-07-12T18:30:00","date_gmt":"2024-07-12T18:30:00","guid":{"rendered":"https:\/\/www.dice.com\/?p=521026725"},"modified":"2024-07-12T18:30:00","modified_gmt":"2024-07-12T18:30:00","slug":"back-end-engineer","status":"publish","type":"post","link":"https:\/\/www.dice.com\/hiring\/recruitment\/back-end-engineer","title":{"rendered":"Tech Hiring Guide: Back-End Engineer"},"content":{"rendered":"

Return to Technical Hiring Guide<\/span><\/a><\/p>\n

Back-End Engineer<\/span><\/strong><\/u><\/h2>\n

While the word \u201cback-end\u201d is certainly amusing in a job title, it describes the role well. These engineers typically work in what might be the back room of a store, but for software. The work they do (namely, the code they write) doesn\u2019t touch the users or customers; it isn\u2019t the user interface or part of the software you can see. More often, back-end engineers are writing code in the form of APIs or interfaces that then get consumed by others (such as middle or front-end engineers). These engineers typically interface with the data (stored in files or in databases) or APIs to transform it and make it usable by other parts of the system. These engineers are often closest to the systems, web services (such as in the cloud), or hardware.<\/p>\n

Questions for Back-End Engineers<\/span><\/strong><\/u><\/h2>\n