|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Reverse Interview||25,553||3 months ago||26||other|
|Questions to ask the company during your interview|
|Guide on how to prepare for quant trading roles out of college|
|Company Questions||11||8 years ago|
|Technical Interview Study Guide||9||8 years ago|
|An overview of the responsibilities of different web engineering roles. Intended as a study guide for tehcnical interviews.|
|Interview||8||2 years ago||1||other||Python|
|Ciso Interview Questions||7||2 years ago||cc0-1.0|
|Questions to ask about the team and company when you're interviewing for a CISO position|
|Templates for structured interviews|
|WebRTC based video interview practice.|
|Tex Resume||3||3 months ago||mit||TeX|
|Compilation and source of a XeLaTeX implementation of my CV. The CV is built according to the currently considered best practices by the majority of US companies for Software Development roles.|
|Devrel Interviews||3||3 years ago||unlicense|
|Reverse Interview Questions for Developer Advocate/Technical Evangelist roles|
WARNING, this repo has been deprecated.
Updates to this study guide are being made at it's new location:https://github.com/gSchool/outcomes-curriculum/blob/master/Unit-1/10-roles-study-guide.md. Several forks of this markdown file have already been made so we're leaving this repository here for posterity. However, if you have suggestions or edits please make them at the updated location in the outcomes-curriculum.
Web Engineering Roles all require composing smaller programs into larger programs using:
Common titles are front end / client side engineer, back end / server side engineer, or full stack engineer which is a blend of both. Different businesses have different neads, so roles will focus on different technologies and techniques.
Back end positions are focused on the operation of webservers. Back end technologies involve more machine to machine communication than human interaction. Perfect webservers would run constantly, never turning off. All webservers will use some of these technologoies and techniques:
Web Servers * MVC design pattern, using * A Server Framework (Express.js, Rails, ...) * An HTML templating language (ejs, Jade, Haml, ...) * The delivery of JS, CSS, HTML assets to the client * Build Tools (Gulp, Grunt, npm, linux/command prompt)
Database connections and data modeling, * A SQL langauge (postgres, MySQL ...), * Non-relational datastores (Mongo, redis ...) * ORM / ODBM (Knex, Mongoose, Active Record ... )
Business logic both in both the client and server.
* Authentication flows (Passport, OAuth),
* Object Oriented Programming (inheretence with
* Data Modeling (data structures, hashmap / hashtable, linked list),
* Data processing (HTTP routing, Controller in MVC, algorithms)
Front end positions are focused on writing code that runs in a web browser like Chrome, FireFox, or heaven forbid IE8. Front end positions tend towards creating interfaces that humans use then interpreting that input for the computer. All front end positions will use some of these technologies and techniques:
Communication with web servers and APIs over HTTP
* REST pattern (HTTP methods and routing, data modeling),
* Browser requests (HTTP methods and routing, HTML forms, AJAX),
* Asset delivery (HTML especially
* User Input (
<input>, event bindings, selectors),
* Through the use of a frontend framework or library (Angular, JQuery ...)
Then you'll be responsible for some blending of both the front and back end. You'll have to be a jack of all trades; a flexible generalist.