|
shrughes posted:More like, rolleyes-vomiting-rolleyes.gif
|
#
¿
May 19, 2011 17:47
|
|
|
|
| # ¿ Apr 28, 2024 22:19 |
|
|
kimbo305 posted:How is this set up? Do the candidates have to provide their own camera? You can go to places like Kinko's/FedexOffice for rented videoconference rooms.
|
|
#
¿
May 19, 2011 19:47
|
|
|
Why would you use LINQ to answer that question? Usually the point is "without <language>'s built-in method for reversing things what would be a simple way of doing this task?"
|
|
#
¿
May 27, 2011 03:06
|
|
|
Ithaqua posted:- design patterns (know at least 2 or 3 and be able to explain what they are and when they're applicable) And don't be surprised if you hear "except singleton" for the design patterns question
|
|
#
¿
Jun 9, 2011 04:25
|
|
|
Ithaqua posted:It depends on the level of cert. Microsoft's certs are pretty good, especially as you get higher up. Basically, a guy who's an MCPD is probably pretty good, or at the very least, not a total moron. Or can afford the tests and knows how to use google to find the answers.
|
|
#
¿
Jun 15, 2011 01:53
|
|
|
Orzo posted:...or they just want a few months off. There's nothing wrong with taking time off for personal reasons, travel, leisure, etc. You don't need to be 'retarded' to want to have a summer off after working hard for a few years. Maybe it's just my experience but most places (I've seen) will let you take a leave of absence to do this, you don't have to straight up quit. We've had several folks do this.
|
|
#
¿
Aug 11, 2011 20:04
|
|
|
baquerd posted:On a strictly financial level, don't take a break. Yes, but on a strictly financial level, always take the job with higher pay and less vacation and more total compensation and also work multiple jobs and live in the cheapest housing possible and ...
|
|
#
¿
Aug 11, 2011 21:14
|
|
|
Any answer other than Timsort is an automatic reject, handshake, here's the door.
|
|
#
¿
Aug 19, 2011 16:35
|
|
|
Dire Penguin posted:It probably varies too much by the company for this question to be worth much, but I'll ask anyway. For a first job, assuming two roughly equal positions, would I be better off looking at a small company or a large one? Depends on what you're looking for. A larger company will typically be more stable and might be able to provide you more flexibility in where you go after that initial position. A smaller company might be a little riskier but it might allow you to stand out more amongst your peers and get noticed. Just "size" (whether it be headcount or revenue) doesn't really say much about a company that makes it a better place to work than another company.
|
|
#
¿
Aug 23, 2011 21:09
|
|
|
The thing is, "Engineer" in a job title is a thing that usually comes with a certification from the NCEES and you get to be considered a certified PE (Professional Engineer). Like 95% of other job titles with Engineer in them have some sort of certification that they have to achieve. Software guys don't, and just kind of started attributing themselves the title of Engineers. The NCEES just recently started licensing Software Engineers, though I don't know how good this is or if it's useful or meaningful, it's just "something" right now.
|
|
#
¿
Aug 23, 2011 22:15
|
|
|
If anyone is 10 years out of college and still lists their GPA on their resume, I'd ask why the hell they're doing so.
|
|
#
¿
Nov 10, 2011 17:03
|
|
|
To me it'd be like putting down what clubs you were in during college. While it's nice when you're just getting out of school to show your involvement, it's largely irrelevant once you reach a certain point. Your actual work in the industry at that point is a better indicator of what you are capable of. If you're including it and it's good I'd wonder if it's because you're trying to cover for a shortcoming somewhere else. If you're including it and it's bad well then you're stupid.
|
|
#
¿
Nov 10, 2011 17:57
|
|
|
Orzo posted:Just because you say this, or want this to be true, doesn't make it so. I mean, are you really trying to speak for every company here? Why do you think someone's ability to do college-level work 10-13 years ago is relevant to someone who would be looking for a non-junior level position? Even if it's at an elite school, I still don't see it being nearly as relevant as your professional experience (then combined with any screening you'd have to do as part of the interview process).
|
|
#
¿
Nov 11, 2011 18:52
|
|
|
Fiend posted:I had a phone interview with a hiring manager for a job that required C# experience, but they weren't aware of the subtle differences between C and C#. They sent me an example in C to talk about, became annoyed when I told them they sent me a sample in C and not C#, told me to 'just pretend the code sample is in C#', then became irate when I asked what 'stdout' meant. "Okay, sorry for the confusion, thanks for your time." You're done there, do not pursue.
|
|
#
¿
Jan 4, 2012 17:30
|
|
|
shrughes posted:SMTP. with failover to POTS
|
|
#
¿
Jan 10, 2012 21:13
|
|
|
Roloc posted:Ok well after applying to 3 different companies and getting 3 offers I finally decided on one yesterday. Even though I was lurking a bit this thread really motivated me so first off thank you. The reason you have candidates write code in front of you is not (just) to make you perform under pressure, it's to see your thought process. It's okay if you're questioning yourself as you're doing stuff, and in fact, it's often a good thing. The problem with your proposed solution (overnight coding problem followed by code review) is that you miss this process, and of course the more obvious problem that folks can "game it" to an extent, by having outside help and coaching. To address the things you say live coding tests accomplish: quote:It tests how nervous the person gets when asked to “perform” on the spot for a total stranger. quote:It shows you if they have good hand writing. quote:Generally shows the person knows what the structure of one simple function looks like and if they can write a loop. quote:Are they good at writing code on the whiteboard/napkin/paper. That said, I don't think there's any reason to not do the code review idea you've presented. But I would still contend that there is value in the live coding test as well.
|
|
#
¿
Mar 30, 2012 17:38
|
|
|
Cicero posted:Gonna have to disagree here. I would say "I don't know", and then go on with whatever you DO know on the subject, even if it's not a lot, and also say how you would go about figuring it out. Yeah always say how you would figure it out, since most employers don't want folks who will just throw their hands up when faced with a new problem they don't know the answer to. Even if that amounts to "I'd search for resources on <topic>" though it's preferable if you have something more specific and technical.
|
|
#
¿
May 3, 2012 18:59
|
|
|
NotHet posted:I've done a first phone interview with a company and I'm feeling extremely stressed about the process. I'd like to both vent and compare experiences with people.
|
|
#
¿
May 3, 2012 20:58
|
|
|
Strong Sauce posted:The HR person should ever only be in 2 interviews. The first one to make sure you're not a putz and the first or last person to interview you onsite to try and get you to take $20k for the job. Yup. They're not expected to make technical talent evaluations for the most part so them being involved in them is pretty stupid.
|
|
#
¿
Jun 21, 2012 20:14
|
|
|
Strong Sauce posted:From my experience, if they don't get back to you with ~1 week or so it's because you're not their first choice and they're waiting on their first choice to decide before moving on to the next candidate. Then again, Ithaqua posted:I've never once gotten a call back from a place that didn't like me to say "we didn't like you". we've sometimes passed off candidates that we didn't use to other partners who may not be as choosy. Though I don't know that it's ever actually resulted in a hire or not to be honest.
|
|
#
¿
Jul 24, 2012 10:28
|
|
|
Ironsights posted:Craigslist is a wonderful place to look for jobs sometimes I would apply to that just to find out what they actually need.
|
|
#
¿
Aug 2, 2012 17:57
|
|
|
Star War Sex Parrot posted:Holy poo poo maybe I don't want to go into software development. On the flipside, I live in a very cheap market and we hire folks out of college making well over twice what the folks above were talking about. Granted, we're fairly picky but it's not impossible.
|
|
#
¿
Sep 28, 2012 23:20
|
|
|
Cicero posted:Personally, I don't think it counts as very good experience, because dealing with bad code is not a very useful skill in real work environments. In the real world, all code is designed as part of a brilliantly elegant architecture, with sensible, consistently-followed style guidelines. Code cruft and technical debt are non-existent, and everyone in the office gets along spendidly and sings Kumbaya every morning at stand up. I almost kneejerk responded to this post after the first sentence. Thankfully I kept reading. 
|
|
#
¿
Oct 23, 2012 14:39
|
|
|
Lenin Stimpy posted:If you're applying for a company like apple or microsoft, an open source resume can hurt you quite a bit. They're really picky about hiring people that contribute to GPL'd code (due to legal fears). Uhhh, where did you hear this? Sounds incredibly bogus considering both companies do contribute to open source projects.
|
|
#
¿
Nov 9, 2012 15:38
|
|
|
how!! posted:I solve complex problems by finding an already existing solution, and leveraging that. If a company wants to call that "plagiarism", then gently caress 'em. Congratulations, you can almost compete with every offshore outsourced resource out there. There's money to be made doing this, but don't expect it to be lucrative. Also if your business isn't solving any new problems at all, chances are they aren't a great business.
|
|
#
¿
Dec 7, 2012 22:26
|
|
|
To be honest it sounded like other than a bit of bitterness toward the process, you did fine. If he was insisting that you get the "right" answer, then that's stupid, but pushing for optimizations or alternate implementations is not uncommon and the motivating factor is to see how you can adapt to try and see your critical thinking process. The naive solution at first is fine, and if you suggested it immediately that's fine. Then adapting using the sorted list is good as well, shows that you realize that you don't want to have to check everything every time. You aren't expected to really be able to fully write algorithms over the phone. Just display critical thinking about the relevant properties of a problem given a set of requirements. You did do a fair amount of that quite successfully. And yes, the problems are fabricated and generic for a reason and there's often better knobs to turn than the arbitrary ones you're constrained by, but for the sake of simplicity and to probe for problem solving approaches they're what you have to deal with.
|
|
#
¿
Dec 13, 2012 21:45
|
|
|
Pweller posted:The whole point is that the solution itself doesn't even matter at all so long as you explain what you're thinking along the way and don't give up until the interviewer is satisfied. Though of note: sometimes interviewers intentionally say inaccurate things and want you to catch them. I don't love it when they do it, and I don't do it personally in my interviews, but it is A Thing, and I've had to deal with it myself.
|
|
#
¿
Dec 13, 2012 23:51
|
|
|
how!! posted:I was once asked in another interview how database indexes work. I answered "thats how you speed up queries. You add an index to a column that you query against and it makes selecting against that column much faster. The trade-off is that is slows down writes". The interviewer then asked me how they are implemented. I said "low level computer sciency stuff, linked lists and big O trees and crap, idk" (in other words, "don't know don't care"). He then proceeded to practically lecture me (in a respectful way) on how important it is to understand stuff from a low level. I fundamentally disagree with this sentiment. Well this isn't going to win you any favor with interviewers (nor will it help your career). Nobody's expecting you to write your own database, but understanding the mechanics behind them and the consequences of your actions allows you to make better decisions. Willful ignorance isn't a sought-after quality. how!! posted:Why does that matter? How does "showing your thinking process" solve business problems? In the real world, solutions matter, not thinking processes.
|
|
#
¿
Dec 14, 2012 00:10
|
|
|
how!! posted:Developer A know the ins and outs of Django's ORM. If Django's ORM can do it, he knows how. Developer A has absolutely no idea how the internals of Django's ORM works. All he knows is you construct the query object, cast it to a list, and then magic happens. If Developer A continues to refuse to look under the hood of any other technology, then Developer B. Disclosure: I do consulting work, so "knows the specific topic inside and out" is naturally not a hard requirement to me while "can quickly learn things" is far more desirable.
|
|
#
¿
Dec 14, 2012 00:30
|
|
|
Yeah we've straight up declined candidates who while they had the right technical chops, were very laissez-faire about the whole thing. So, in addition to the formalities like shaking hands and dressing nicely, if you're being asked to present something on a whiteboard, don't sit in a chair and kick back and just motion in the general direction of the board. Stand up and talk to your audience as if you were, you know, doing it for a job.
|
|
#
¿
Dec 18, 2012 00:47
|
|
|
gucci void main posted:Offer in My god, that's terrible even in the cheapest of living environments. It's borderline insulting.
|
|
#
¿
Dec 19, 2012 01:26
|
|
|
Sutureself posted:I know the "how much are you looking to make" question has been covered, but what about the "what did you make at your last job?" part?
|
|
#
¿
Dec 19, 2012 08:34
|
|
|
wide stance posted:It's a C# position for an enterprise firm in a semi-ideal location. I don't think I want to go down the Microsoft path. Ideally I'd like to work at a small tech company in a major city (Chicago for instance). However, You're not locked into one technology stack even if you're only professionally doing that one. It does make it more difficult to find things that have requirements of "N years experience in <other stack>" later on, but there you go. 2. What do you have a degree in? MIS? 3. Is it a change in that it's now development where you weren't doing development before? Is that the path you want to take? 4. How littered? If it's more than 2 or 3, that could start to look a little dicey but I don't know that it really gets all that much attention. If it were 3-6 month stints or less, that'd be a different story. 5. This won't necessarily be a barrier to hiring, if you're worried about that. The latter point may be true, though if you want to work in a different technology than your job allows, this is a good way to do so. There is a bit of "I already do this all day professionally" that can make side-development a turnoff, but if you find an itch you really want to scratch you'll do it  It kind of all hinges on what you've done and where you want to go. If this is your first development gig and it'd be an entry-level role then don't sweat too much about being locked in. It'll either pan out to be awesome or it can be a stepping stone to a better role (you get experience to build your resume, you learn some things, you meet people in the dev community, etc.)
|
|
#
¿
Jan 7, 2013 19:27
|
|
|
meatier shower posted:I just graduated last month from a tiny private liberal arts school in Texas with a BA in Computer Science and moved back to the Baltimore area to live at home and save some money. I just got my first offer back and I told them that I needed a few weeks to consider it before I come onboard. It's a mobile development position with a small virtual company, so I'd be exclusively telecommuting. They offered me 52K with two weeks paid vacation and health benefits, as well as a signing bonus so I can buy a new laptop. I mentioned that I was interested in trying coworking and they mentioned being able to pay for that as well. Am I getting a bad deal? People are mentioning much higher starting salaries in the thread, but Baltimore isn't exactly NYC or the Bay Area, and I really like the idea of working for a smaller company, particularly after a bad internship experience with a well-known consulting firm in DC. It's certainly on the low end, though what kind of mobile development are you talking about? That's a pretty non-specific job description. Also it depends on what other benefits and such make up your total compensation (you mentioned health and vacation, but are there other bonuses/profit sharing/retirement matches/etc.). I imagine they can get away with paying a little less by offering positions that are exclusively telecommute. I also graduated with a Comp Sci degree from a tiny private liberal arts school in Texas, and my entry-level salary over half a decade ago was about 20% higher than that in Houston, which isn't a very expensive place to live either (it appears to be cheaper by the online things I've checked). But it was also not telecommute (and in fact, involved a non-zero percentage of travel), so that factored in.
|
|
#
¿
Jan 11, 2013 21:39
|
|
|
Che Delilas posted:If you ask about 401k contributions, make sure you find out how long it takes them to vest. If it's like 5 years it doesn't really count as a benefit. The gently caress? There are companies that put vesting schedules on 401(k) matches? That sounds questionable at best.
|
|
#
¿
Jan 16, 2013 20:26
|
|
|
Che Delilas posted:The example I used was from personal experience. And yeah, it's bullshit and just another way for a company to screw over employees. Sab669 posted:I haven't asked my boss how long it takes to be fully vested, but after three months of employment my discussion when like this: I can understand a waiting period before matches start if turnover is a concern, but starting a match that you have to vest into over a period of years is stupid as hell.
|
|
#
¿
Jan 16, 2013 22:51
|
|
|
lmao zebong posted:stuff Depends on your personal needs, but Company A sounds good to me. Though I've been annoyed in the past with teams I didn't work well with, so similarly compensated I would choose the better workmates almost always. Though you can't really know that from an onsite visit or two, so consider that. Other things to consider which you didn't list are things like performance management (how do they do employee evaluations, what's the career path like, will I be stuck in a position forever), and the fiscal footings of the companies themselves. Are the companies growing steadily? Are they startups that only have funding through a specific amount? Are there things like profit sharing? Other things that can add up and can tip the balances one way or another. You do seem to have done a fair bit of homework (especially for a fresh graduate), so even without these I'd say you've done pretty well at narrowing your choices. lmao zebong posted:Another issue I'm struggling with is telling a company that I want to turn down their offer. I do understand this is a business and a huge career decision, but I felt like I got along so well with both companies it is going to be hard or awkward calling and saying I don't want to accept. Any advice on how to effectively phrase it so that I don't burn any bridges? It's still rough to tell them "thanks but no thanks", but as long as you're not combative about it, nothing should be held against you. As you said, it is business after all.
|
|
#
¿
Jan 30, 2013 19:23
|
|
|
2banks1swap.avi posted:Honestly, anything. As far as a I know ASP.net isn't used a lot, so I'm thinking I should expand into something else.
|
|
#
¿
Feb 6, 2013 20:33
|
|
|
Rello posted:Did you even read his post? WARNING: THE PROGRAMMING INTERVIEW ADVICE CONTAINED HEREIN WILL NOT LIKELY GET YOU HIRED
|
|
#
¿
Mar 6, 2013 01:46
|
|
|
|
| # ¿ Apr 28, 2024 22:19 |
|
|
how!! posted:The first sentence reads like he is interviewing people, and has never interviewed a developer before. So no.
|
|
#
¿
Mar 6, 2013 03:15
|
|