|
This thread is getting programming jobs, especially for newbies. That can be lifelong math nerds with CS degrees looking to snag a position with Big Tech, people with no coding experience looking to self-teach, or desperate humanities majors trying to pivot careers into something that pays well. All are welcome under this roof. Personally, I'm of the CS degree/BigTechCo variety of coding goon, so some of what I write here may be biased towards that experience. A few definitions that help make the rest of this OP make sense: Programming: Wikipedia posted:Computer programming (often shortened to programming or coding) is the process of designing, writing, testing, debugging / troubleshooting, and maintaining the source code of computer programs. Computer Science: Wikipedia posted:Computer science or computing science (sometimes abbreviated CS) is the study of the theoretical foundations of information and computation and of practical techniques for their implementation and application in computer systems Note that computer science != programming. College computer science programs invariably teach you to code at some level along the way, but the focus is on more abstract concepts like data structures, algorithms and discrete math, and this is more true the more prestigious the college is. Since CS programs can vary wildly school to school, if you want to know how much of it is applicable to industry, ask someone who goes there, or better yet, someone who used to go there and now works as a programmer. That said, getting a CS degree is the safest path to becoming a professional software engineer. It provides the most structure and support to learning, and just having a CS degree on your resume is a big boost when you're just entering the work force. Programmer vs Software Engineer: The distinction here isn't always black and white, but generally the job title of programmer denotes just basic programming duties, whereas the title of software engineer denotes a "higher rank" and being responsible for higher-level aspects of software design. Job postings for software engineers nearly always require a degree in CS (or something related, like CompE or Math), although some companies may waive this requirement if you have sufficient experience. Along the same lines, software architect implies that you're working at an even higher level and are responsible for the overall design, or architecture, of an entire program (or perhaps a very large section of a program if your program is something enormous like, say, Windows). Other job titles include software developer (dev), which is kind of a catch-all for "writes software" and is often interchangeable with software engineer, and principal engineer, which basically just means EXTRA senior engineer. I want to work in software development. Should I get a degree in Computer Science? Quite possibly! This seems to be the most common route into software engineering, but there are a few things to consider: 1. Computer Science degrees can be very difficult (depends on school). They're usually similar to engineering degrees in drop-out rates (many drop-outs seem to go to MIS, which is sort of a hybrid business/CS degree). If you go to a school with a rigorous program, expect to spend long hours studying various algorithms or implementing them. 2. Computer Science involves a lot of math and math-ish concepts. You don't have to be amazing at math, but you have to be at least halfway decent, in college-level terms. For example, you'll probably have to take classes in at least differential/integral calculus, linear algebra, and discrete math (often called discrete structures). Many other classes will involve math-ish concepts like understanding Big-O, which is a measure of how algorithms' running time responds to changes in the size of their inputs. 3. As noted above, there is no guarantee that getting your degree in and of itself will adequately prepare you for real-world programming. Stories abound of CS seniors or even grads that had decent enough GPAs but couldn't code their way out of a wet paper sack (or couldn't code their way through FizzBuzz, an extremely simple but well-known programming test). Even if your school does a good job of this, however, you'll still want outside experience. If I get a degree in CS, how's the job market? Will I make big bucks? Yes. Well, maybe. The job market right now for devs is excellent overall, but companies often play the hiring game very safe, by preferring to not hire at all than to hire someone that seems iffy, as bad engineers can cause negative productivity. That said, overall jobs are abundant and salaries are high, as demonstrated by the following large numbers: code:
So according to NACE, CS is in the #4 spot now for new grad starting salaries. Compare that $64,700 to a reported average of $36,553 for humanities majors. Ouch! Now anecdotally, it seems like there are simply more jobs about in CS than in other engineering fields (software engineering is definitely growing more). But that's not all! http://www.drdobbs.com/architecture-and-design/2013-developer-salary-survey/240163580?pgno=1 In addition, the Bureau of Labor Statistics expects strong growth: quote:Overall, employment of computer software engineers and computer programmers is projected to increase much faster than the average for all occupations. Job prospects should be best for those with a bachelor's degree and relevant experience. And in even more good news, CareerCast rated software engineer as the third-best job to have overall, beating out, well, everyone except for actuaries and biomedical engineers. Woo! Ok, I've decided to become/I am a CS major. What do I do now to get one of those sweet, high-paying gigs I've heard so much about? To maximize your odds of entering the ranks of the good-jobbed, you'll want as many of the following as possible: 1. A good GPA. You want to at least have a 3.0, and 3.5+ is generally seen as very good. Besides demonstrating some level of competence in the art of Computer Science, companies want to know that you aren't lazy, and that even if some classes are boring, you are willing and able to suffer through boring things. Many big companies seem to have a cutoff around 3.0. As you progress in your career, a high GPA's relevance rapidly declines, but early on it's an excellent thing to have on your resume. 2. Outside experience. Companies want to know that you can take initiative and can code without the rigid structure of a class holding your hand the entire way. There are basically five forms this can take:
3. Technical Interviewing Skills: At the very least, you need to know how to code on the fly on a white board/piece of paper, as well as the most common data structures and algorithms, along with their running times for different operations. You should also understand complexity/Big-O in general so that you can analyze whatever algorithm/data structure an interviewer asks you to write. A whole book could be written about interviews; in fact, there has!
Here's an actual question taken from an interview I did with Microsoft: quote:Parameters: array of objects, an integer 'n'. Randomly select 'n' objects from the array to return. No repeats. You can assume 'n' is a valid number. 4. "Soft" Interview Skills: Unfortunately, this has nothing to do with having a round, squishy belly, and everything to do with people/social skills. Companies don't want a hardcore neckbeard who can't communicate or get along with others. You don't have to be incredibly charming either, but there's a baseline of stuff you should do like smile, act confident without sounding arrogant, speak clearly and coherently, etc. Many software companies are ok with dressing casually in interviews, but keep in mind there's a difference between dressing casually and dressing like a slob. Wearing jeans is fine at many companies, as long as said jeans do not have cheetos stains all over them. Check with [the recruiter/someone who works there/someone who works in a similar company] about expected dress. A safe rule of thumb is go a half-step or step above whatever people normally wear to work there. For example, interviewing at Google where people usually wear jeans and a t-shirt, I wore nice jeans, a t-shirt, and a nice collared sweater. Another part of this are behavioral questions. Most companies will have questions like, "Tell me about a time where you had a deadline that you didn't think you'd be able to meet, and how you dealt with it," and "Tell me about a time you had a problem with a teammate, and how you resolved it." Questions about a particularly nasty bug that you fixed also seem to be common. For more examples of both behavioral and technical interview questions, go to glassdoor.com and search for well-known software companies, then go to the Interviews section for them, like so: http://www.glassdoor.com/Interview/Microsoft-Interview-Questions-E1651.htm How do I apply for internships/jobs? Probably the best way through recruiting events at your school. My college does technical career fairs in fall and winter semesters where only smarty-pants math/science companies and majors are allowed. Handing out your resume at these and asking them about procedure (these days they usually ask you to also apply online, but maybe through a different website than the general public one) is a good idea. For companies that don't recruit at your school, go to their website, they usually have a section specifically for university recruiting; you can try googling "[Company name] internships" or "[Company name] university recruiting" or something along those lines if their main website is proving difficult to navigate. You won't get responses from the majority of these unless you're super-amazing, but it's worth a shot; in fact, the offer I accepted my senior year was from a company that wasn't recruiting at my school, I just applied online. These job requirements are intense! Guess I'm not good enough... Skandranon posted:All job requirements are 'wish lists', very similar to the ones children make for Christmas. When should I start applying for jobs? If you're graduating at the normal time in late spring/early summer (May/June), you can start applying to large companies (especially large tech companies) in the preceding fall semester. These companies generally want to pick off promising new college grads earlier so that their competitors can't get them, as there's a perpetual bidding war for the most talented new developers. Generally, smaller companies won't hire that far ahead of time, but it obviously depends on the specific company. Try calling and asking around your area for local companies, I guarantee no one will bite your head off. Definitely want to start trying at least a few months before graduation. IF YOU WAIT UNTIL YOU GRADUATE TO LOOK FOR JOBS YOU'RE AN IDIOT! DO NOT DO THIS. Exactly how much money we talking about here? Glassdoor.com is awesome for this. Starting salaries for the big-names seem to mostly be in the 80s through the low 100s, although keep in mind that we're talking the most prestigious companies in high cost-of-living areas. It's also possible you'll get some sort of signing bonus in cash, and some stock; these will have time restrictions attached to them. For smaller places, it's going to be more random, and probably less (with some exceptions; if you get hired at some boutique hedge fund you may be making bigtime money), although the bidding wars at the big names have a pulling effect on everyone else too, so be thankful Facebook gives out 100k signing bonuses to former interns who sign with them. I got an offer what do I dewwwww?? Congrats, you've escaped the Gen Y Curse. You should try negotiating, although as a new college grad your leverage is small (some would say nonexistent). Still, it's probably worth a shot, especially if you have multiple offers. If you're still waiting on other companies for interviews/offers, try to play for time. Most companies should be understanding. Here's a good guide to negotiating for engineer-types: http://www.kalzumeus.com/2012/01/23/salary-negotiation/ Wait so do I have to actually know about Big-O and algorithms or can I toss that knowledge in the trash bin once I'm done with classes? Otto Skorzeny posted:This varies so much from company to company that it's difficult or impossible to generalize like this. Companies that work in middleware may have the luxury to be able to take anyone who can coax eclipse into compiling their code, whereas companies working on eg. high-performance databases need people with solid CS fundamentals, even especially if the company is small and there's no where for a coder to hide, so to speak. Jobs writing firmware or whatever will have their own set of fundamentals with regards to concurrency hazards and intimate hardware knowledge that they need to interview somewhat rigorously for, people working on game engines need to know a fair amount about efficiency all the way up and down the stack, and so on and so forth. But what if I'm not a sheeple and don't want to/didn't follow the standard CS degree path right out of high school? Is there hope for me? Yes! There are many paths to salvation, my son. They fall into a few different categories (see the Appendix for more links): Degrees: If you already have a bachelor's degree in something else, you can get often still get a master's in CS. This usually requires you to take some preliminary classes before you can start the grad program proper; for example, BYU's program says this: quote:Provisionally admitted students must either take or have taken the equivalent of CS 124, 142, 235, 236, 240, 252, any three CS courses beyond the 200-level (except 404), any two math courses beyond Math 113, and either an additional CS course beyond the 200-level (except 404) or an additional math course beyond Math 113. A forewarning, though: to some, these types of degrees have a stigma precisely because they are most often used by programmers who come 'late to the game', so to speak. Bootcamps: These are intensive programming courses that usually last somewhere in the 2-3 month range, and the bootcamp will be pretty much your entire life during that time. The most well-known ones have gotten some positive press, and some even guarantee a job or your money back, but as a whole they're relatively new and it's hard to say anything concrete about them. Personally I think there's a lot of potential here, but I'd also be very careful about researching them if you're interested in participating in one. Self-teaching: Online tutorials, books, reading forums and stackoverflow, and the newest addition to this area, free online classes ala Coursera or Udacity. These things take the least upfront investment, especially in terms of money, but can still lead to developing marketable skills, and the sheer amount of resources you can draw from to learn programming is immense. The main drawback is that you need to be very self-motivated; in practice, most people who go this route don't make it very far (e.g. the average completion rate for MOOCs is tiny). Turns out learning a difficult subject without real live humans to get help from is hard! Those who go this route will also really need to go out of their way to prove they actually learned enough to be useful. A portfolio of sorts is pretty much required. Reading Hacker News is a good idea for all types of developers, as it's basically the news site for programmers, but it's particularly necessary for people who are self-teaching since you won't have IRL contacts telling you about cool new stuff. Of course you can't read every single article that pops up there, but keeping tabs on it and doing a fair amount of reading about different languages, technologies, ways to prep for interviews, etc. is an excellent idea. Oh, and remember: down with slavery posted:The idea of holding a "career" where you get raises that will compete with what you can get shopping around is long gone. They'd rather pay you poo poo for as long as possible and get their moneys worth than invest in to you long term. Cicero fucked around with this message at 21:08 on Sep 21, 2015 |
# ¿ Dec 24, 2010 20:04 |
|
|
# ¿ Apr 29, 2024 02:57 |
|
- APPENDIX - Useful Resources (includes inline links from above)
Practice practice practice Example Resumes (Disclaimer: these resumes are decent or better, but not perfect. You can ask about resume help in this thread, but you may also want to consider consulting an expert like that resume guy) USSMICHELLEBACHMAN: PDF Cicero: PDF, DOCX (note that Dropbox's doc viewer doesn't handle docx too well) Someone's fiance: PDF, DOCX astr0man: PDF, LaTeX aBagorn: PDF Random Resume Tips
*** Goon Mentors *** Helpful goons that can help you out, because let's face it Timmy, you're desperate. PM them to seek their guidance (click the usernames). listed in thread postcount descending order "Ithaqua posted:Experience: .NET/C# development, all things ALM (SCM, Agile, DevOps), TDD, unit testing, former interviewer "Cicero posted:Experience: Google, Amazon, Goldman Sachs (internship), Java, Android "shrughes posted:Experience: LaTeX, C, C++ (NOT C/C++, that's not a language!), LaTeX "Strong Sauce posted:Experience: Worked at a big corporation and two startups. Javascript, Ruby, Backend Web Development "bonds0097 posted:Experience: Automation, Security, Java, Android "pr0zac posted:Experience: Facebook, Y-Combinator, Apple, Python, C++, C, Ruby You can also access LIVE synchronous gooncoder chat right here. Data structures and algorithms for interviews You should know the basics of: linked lists in their various forms (singly-linked, doubly-linked, stacks, queues, deques), arrays and array-based lists, trees (particularly binary search trees), graphs, sets, maps/hashes/dictionaries (these all mean the same thing), and hashtables. As far as algorithms you should know offhand, sorts are the most common one. You should know a couple simple O(n^2) sorts like bubble/insertion/selection, and the major average-case O(nlogn) sorts: heapsort, mergesort, quicksort. ESPECIALLY quicksort. How can you come to know these things? Implement them all in your language of choice. Then google around for problems that use them, and code up solutions. Look at the Big O Cheat Sheet when you need a bit of review. Cicero fucked around with this message at 07:18 on Jan 13, 2016 |
# ¿ Dec 24, 2010 20:13 |
|
Lumpy posted:An addition to your "Outside Experience" list: Contribute to (or start) an open source project. I considered adding stuff for a couple other posts to the OP, but it seems like if I just added every single piece of posted good advice to it that'd be kind of silly. I dunno, maybe I'll change my mind. If anyone thinks I should add something to the OP and says so specifically though I'll probably do it. Grey_Area posted:Math PhD stuff
|
# ¿ Dec 30, 2010 20:16 |
|
Grey_Area posted:Ok, thanks. I'm not sure I'm being particularly naive. The one job I applied for seemed ideal, but like I said I failed the technical tests. I put it down to excessive stress, but even if it was incompetence or stupidity I got to the last round of interviews so at least had a reasonable shot at getting the job. And that started you on £30k with really good benefits and required no experience at all. And IBM also require no experience for software development jobs, while paying a bonus to people with PhDs in any mathsy/engineering subject. I was hoping there might be other companies with similar starting positions. Grey_Area posted:Yeah, that's fair enough. The "technical tests" assumed no specific knowledge of anything related to computers, so that's not why I failed them. I intend to learn more, but I'm not going to be able to learn a massive amount in three months while simultaneously writing up a PhD. I'm not that bothered about getting paid a lot, but I assumed low paying jobs would involve lots of drone work and little development. I'd be happy to be proved wrong, though. I guess "nah, you're hosed" might be good advice, but I'll keep looking for now. EDIT: Since you're a math PhD, You might also want to ask around about jobs in the grad school megathread in SAP.
|
# ¿ Dec 31, 2010 06:16 |
|
tef posted:I've seen graduate jobs as low as £15k. 30k is a pretty good starting salary. Grey_Area, ever considered moving to the states?
|
# ¿ Dec 31, 2010 07:56 |
|
Jick Magger posted:This thread could not have come at a better time. I just graduated with a CS degree, and I'm going through the process of getting me resume spruced up. I'm absolutely terrified, but excited because I'll (hopefully) get to do something besides IT crap now. quote:And, how important is it really to an interview? (I guess that depends on the company) code:
Explanation of answer: The outer loop obviously executes 'n' times. For each time the outer loop executes, the inner loop ALSO executes 'n' times. So if 'n' was 5, when i = 0 in the outer loop, the inner loop will execute with j = 0, j = 1, j = 2, j = 3, and j = 4. Then when i = 1 in the outer loop, the inner loop will again execute 5 times. And so on for i = 2, i = 3, and i = 4. So total running time with 'n' = 5 is (5 * 5). As 'n', the length of the array, gets larger, the running time of the method will increase quadratically. If the size of the array doubles, the running time will increase fourfold. If it triples, the running time will increase ninefold. tef posted:Might be things like universal healthcare and different taxation wolffenstein posted:Are MS interviews as bad as the rumors say? frightened goat posted:Also, are there any good books/textbooks/resources out there that I can read up on to fill in the gaps in my CS knowledge, plus not come off as a relative schmuck in interviews? Cicero fucked around with this message at 00:41 on Jan 1, 2011 |
# ¿ Jan 1, 2011 00:35 |
|
shrughes posted:It's O(n^3), right?
|
# ¿ Jan 1, 2011 02:18 |
|
shrughes posted:Because there exists a number x such for n > 0, for all inputs of length n, the running time is less than or equal to x*n^3?
|
# ¿ Jan 1, 2011 02:56 |
|
shrughes posted:I am simply sperging about the meaning of big O notation. Any function that is O(n^2) is also O(n^3).
|
# ¿ Jan 1, 2011 03:04 |
|
Sefar posted:MS Interview Stuff
|
# ¿ Jan 4, 2011 06:32 |
|
Enderzero posted:So to sum up: you're a glorified factory worker here for one task, please be passionate about the limited area we have slotted you into until we outsource the technical side because it's a commodity
|
# ¿ Jan 6, 2011 01:07 |
|
Enderzero posted:I guess my point is you are starting to sound like a boss and not a worker - and part of being a boss nowadays is finding ways to undifferentiate workers. Who cares about your soft skills when the eventual goal is make you replaceable? It's probably because this is a thread about getting a job and interviewing, but the onus here is placed completely on tech workers to improve their skills to work around others' failings. I don't see anyone (not just in this thread) saying companies should eliminate waste and inefficiency, organize a company better, or cut executive pay. The narrative is all "how to make yourself attractive to companies" and no "how do we change society to make businesses work better and more fairly". "Build your brand!" will only work for so long when there are no jobs because everyone caved to corporate culture.
|
# ¿ Jan 6, 2011 23:38 |
|
Enderzero posted:Yeah, thanks, I did think about it, that's why I wrote this: quote:If you'd actually stop and read, it would have been obvious. quote:You are correct, though, the biggest part of changing those situations can mostly be done by bigshots, but not even discussing it in the general society is one way to ensure nothing will change. If the news does a story about job retraining, have some balance mentioning that jobs wouldn't need to be cut in the first if companies were organized better; Build support for limiting executive pay instead of allowing republican focus group language to convince everyone that if we do that, then you won't ever get rich! (you won't get rich anyway) Stuff like that.
|
# ¿ Jan 7, 2011 00:15 |
|
tef posted:this is good advice.
|
# ¿ Jan 7, 2011 06:03 |
|
Good news, everyone!quote:CareerCast rated 200 jobs based on income, working environment, stress, physical demands and job outlook, based on data from the Labor Dept. and U.S. Census and researchers' own expertise.
|
# ¿ Jan 9, 2011 03:12 |
|
Kilauea posted:Do I need to be concerned that my computer science program at my university is not ABET accredited? Should I transfer to a different university?
|
# ¿ Jan 14, 2011 02:07 |
|
Cyrik posted:Has anyone taken the Berger Aptitude for Programming Test? Any advice?
|
# ¿ Feb 19, 2011 17:37 |
|
2banks1swap.avi posted:Posted at the request of the OP: But the thing is, locking yourself down right now probably isn't the best idea, as you may not really know what you want. So I'd just pick whatever language suits your fancy, practice doing something useful in it, do well in your classes and try to do some internships or part-time work. I don't imagine your age will be a big deal, but then again I'm not a recruiter. EDIT: There is also more good news for us CS folk, as average starting salaries have gone up to 63k! quote:Curriculum
|
# ¿ Apr 13, 2011 00:30 |
|
2banks1swap.avi posted:Well well, talk about motivation! It's quite a stark contrast to most other majors right now where most people are still desperately applying for a job, any job. I mean, I don't even have any real work experience (depending on whether you count the internship). If the job market is this good right now, I can't imagine what it will be like in a few years when the unemployment rate isn't some horrible number.
|
# ¿ Apr 16, 2011 01:26 |
|
2banks1swap.avi posted:To be brutally honest the stability and vibrancy of the job market is the biggest motivator ever. It's not that I wouldn't enjoy it, but the fact that I know I could get paid well enough to retire young, have hobbies before I retire, and a good life as opposed to instability and being stressed is very, very positive.
|
# ¿ Apr 16, 2011 02:20 |
|
I don't know much about security, but check out this post: http://forums.somethingawful.com/showthread.php?threadid=3303022&pagenumber=10#post390112048
|
# ¿ Apr 16, 2011 05:27 |
|
Melted_Igloo posted:Average starting salary is an incredibly bad measure, careerwise
|
# ¿ Apr 26, 2011 19:30 |
|
Melted_Igloo posted:More demand for a specific type of skill (say COBOL), does not equate to more jobs
|
# ¿ Apr 27, 2011 21:28 |
|
Piss Man 94 posted:2banks1swap.avi you're being a big old nerd about this. Starting salary means gently caress all. The Reaganomicon posted:Connections determine where you get a job. The job you get there determines the amount of cashmoney you will acquire. Unless you're an autistic shutin or a poor that went to a degree mill, your connections will matter more than your Hot poo poo Quotient.
|
# ¿ Apr 28, 2011 22:23 |
|
Shitpost Gaze posted:2banks1swap.avi, are you Flux_core? Because you act almost exactly like him. quote:2b1s you seem like a huge annoying dick and i would never want to work with you Personally I think this debate is silly because both sides are right: nearly everyone in a field is affected by general trends, and being exceptionally skilled can help you rise above the fray. It might be worth it to discuss this sort of thing more in BFC or D&D, but CS as a field is strong enough to where anyone competent, hard-working, and reasonably socially-skilled doesn't have much to worry about if they're just concerned with financial stability. Melted_Igloo posted:Er what? where the heck do you live? Google, of course, announced across-the-board raises back in November. Obviously that's just two companies, but they're big enough to where this will probably put pressure on other companies to match or at least get somewhat closer. They wouldn't be increasing pay if getting good talent was easy, that's for sure. Cicero fucked around with this message at 08:39 on May 9, 2011 |
# ¿ May 9, 2011 08:33 |
|
Ithaqua posted:The technical assessment part of the interview was equally unimpressive. I was asked 3 things:
|
# ¿ May 27, 2011 03:52 |
|
Theler posted:When is the right time for a future CS grad to start sending out resumes? For example if I was graduating in December and looking to start a job in January would applying for jobs during August/September be considered too early? Edit: As in, the September before graduation. Cicero fucked around with this message at 16:58 on May 27, 2011 |
# ¿ May 27, 2011 06:54 |
|
Theler posted:When is the right time for a future CS grad to start sending out resumes? For example if I was graduating in December and looking to start a job in January would applying for jobs during August/September be considered too early? Also keep in mind that since the majority of people graduate around May/June, the big companies that hire new college grads in waves will be oriented around that schedule.
|
# ¿ May 27, 2011 17:44 |
|
His Neutralness posted:I just graduated and I made the mistake of going to college in a city that has somewhere in there range of 2-3 software companies, and also I don't really want to live here regardless. Are many companies, besides extremely large one's like Google, willing to fly people out for interviews? I can't imagine many would for entry level positions. Would I be better off just moving to somewhere with jobs and then looking?
|
# ¿ Jun 1, 2011 02:17 |
|
HondaCivet posted:From what I've been reading, in this economy, companies generally aren't going to bend over backwards for you unless you have a lot of experience/skills that they need. Unless you are really something special, why would they fly you in when they've likely got tens, maybe hundreds of local grads with about the same experience as you who can show up for an interview next week for free? It sucks but it makes sense. If I were you I'd just save up 6-12 months' living expenses and move first.
|
# ¿ Jun 1, 2011 03:09 |
|
His Neutralness posted:I'm not opposed to it, I just figured that they're very competitive and I shouldn't depend on getting a job at MS or Google.
|
# ¿ Jun 2, 2011 06:54 |
|
Pram posted:Yes I realize programming certs are useless but I was mostly curious if it has any value as resume fodder. Probably not though I'm guessing.
|
# ¿ Jun 15, 2011 00:59 |
|
Has anyone heard about this? Excerpt:quote:Launched less than a year ago, GILD is a site for computer programmers and other tech professionals that combines social gaming with job search and career advancement. Programmers from around the world can see where they stack up against each other in skills like Java, HTML, C++. They can enter free contests for prizes like iPads, or take free certification tests and amass medals that showcase their skills to colleagues and potential employers.
|
# ¿ Jun 21, 2011 01:18 |
|
Joking is good if you can pull it off and your interviewers appear to be normal humans. Just don't overdo it, and if a joke falls flat, don't look all embarassed; pretend it never happened and keep on truckin'.
|
# ¿ Jun 23, 2011 22:53 |
|
Pweller posted:^^^ Pweller posted:Okay. I'm getting super uncomfortable since they're grooming me for stuff... this would be so much easier if everyone had agents or whatever as mediators. Also, it sounds like maybe you're not putting your skills to the best use there? If the type of work you're doing won't look good on a resume, that's another factor to consider.
|
# ¿ Jul 14, 2011 23:19 |
|
TasteMyHouse posted:Quicksort isn't O(n*log n). It's O(n2) edit: Wikipedia confirms. Also in order to get the worst-case scenario you either have to have data explicitly designed to screw with quicksort or have astronomically terrible luck. Cicero fucked around with this message at 16:59 on Aug 21, 2011 |
# ¿ Aug 21, 2011 16:57 |
|
iam posted:I'm soon to be applying for developer roles after finishing a one year MSc in CompSci, and whilst we covered sorts etc in algorithms, all this talk of algorithms is making me
|
# ¿ Aug 22, 2011 23:05 |
|
No Safe Word posted:Like 95% of other job titles with Engineer in them have some sort of certification that they have to achieve. Cicero fucked around with this message at 22:24 on Aug 23, 2011 |
# ¿ Aug 23, 2011 22:20 |
|
The number of data structures and algorithms you're expected to have memorized isn't really huge; let's see for data strucutres, I'd guess there's arrays, linked lists, hash tables, array-based lists, maps, binary search trees, heaps. More difficult and important is knowing the how and why behind those data structures and algorithms.
|
# ¿ Sep 15, 2011 20:50 |
|
|
# ¿ Apr 29, 2024 02:57 |
|
Sab669 posted:I think the big reason why it's unnpaid is because it's a small startup company that hasn't actually rolled out its first product commercially. They're in the final stages of development, they say, and are looking to hire on a few more hands for when it goes live basically. Pweller posted:Does the US not have some sort of subsidy for hiring students/new grads in tech roles? I would think there'd be all kinds of grants with all the 'omg we need STEM students' I've been reading about... quote:e: US dept of labour says unpaid internship is legal only if a for-profit employer isn't getting work of any immediate benefit to them (ie. a waste of both your time)
|
# ¿ Sep 17, 2011 05:03 |