|
Honest Thief posted:Is it me or these take home assignments are getting more demanding with each year? Seems like the only constant is me sucking at being ready and organized for them, well at least now I got a bunch of code for various poo poo, some of this will be useful, right? I think they're pretty pointless. If you want to use it as a fizzbuzz then go and have them come in an hour early give them a desktop on a VLAN that logs all network traffic and have them work on something then and there. Also watch the 'some of this will be useful' portion, I bet most of them are covered under NDA.
|
#
?
Mar 27, 2017 19:08
|
|
|
|
| # ? May 17, 2024 21:23 |
|
|
Shirec posted:Is there ever a chance that these recruitment things are stealing those solutions and using them? I had a friend that got very far into a recruitment process at a company and did a lot of work into a presentation that was requested, and they ghosted him as well. I don't think it's prolific or anything, but I wonder if it's possible. That was a respectable company so in that case I would say no. However, I did have an interview at a startup where the challenge they proposed to me was a current issue they couldn't figure out and I wouldn't be surprised if they used my suggestion.
|
|
#
?
Mar 27, 2017 19:11
|
|
|
huhu posted:That was a respectable company so in that case I would say no. However, I did have an interview at a startup where the challenge they proposed to me was a current issue they couldn't figure out and I wouldn't be surprised if they used my suggestion. I've often given interviews where I talk about a problem we haven't solved as the "here's some things you might do in your first month on the job" portion of the interview. A few times, the candidate's said something interesting about the problem and I haven't felt bad about using their idea even if we don't hire them. (In all of these cases, we didn't hire them because they got a much better offer somewhere else.) However, there's a big difference between doing engineer-chat with some real-world examples and you give me a good idea, versus asking you to code up something I can't figure out. In the first case, I could probably have gotten the same thing by asking for help on a forum or in-person at a meet-up. Plenty of experienced engineers are happy to spend 10 minutes telling me a better solution to my problem. In the latter case, I'm not going to get anyone to write me an hour+ of code without paying them.
|
|
#
?
Mar 27, 2017 19:51
|
|
|
fantastic in plastic posted:Candidates continue to not object to them or push back, of course they're going to get more onerous over time. I never do any test implementation though, that's what kills most of my applications. Honest Thief fucked around with this message at 11:02 on Mar 28, 2017 |
|
#
?
Mar 28, 2017 10:52
|
|
|
Had a recruiter call me and when asked for it, so I named some rudely high number to get him off my back. He said "we can work with that." Appears I could have asked for more? Tempting still, it is 20 minutes bicycle ride from my house and would give me anice shitload of money. Let's see how far I can get before they reject me with an insultingly low offer.
|
|
#
?
Mar 28, 2017 12:15
|
|
|
Keetron posted:Had a recruiter call me and when asked for it, so I named some rudely high number to get him off my back. He said "we can work with that." Appears I could have asked for more? Recruiters make more if you make more, unless he's actually from the company.
|
|
#
?
Mar 28, 2017 14:02
|
|
|
huhu posted:Recruiters make more if you make more, unless he's actually from the company. This is true, but incentives still aren't aligned. On homework, I say no unless it's under a couple of hours as I then feel it's similar to a phone interview. You have enough options to not red to put up with it, at least in the Bay Area.
|
|
#
?
Mar 28, 2017 15:32
|
|
|
huhu posted:Recruiters make more if you make more, unless he's actually from the company. Yeah but it's a small difference so closing two deals low is better than one high.
|
|
#
?
Mar 28, 2017 22:40
|
|
|
Hey thread, I posted here a week ago asking for resume help and got a lot of good feedback, and I have a new version here. Once again, any suggestions or criticism would be great. I tried to add a lot of detail to my current job and a little more to the one before it, hopefully I didn't go overboard. I tried to focus on what little actual programming I've done in this job, since most of my time has always been manual testing. Especially since it feels like when 2017 started, 90% of my job became "go to work and poke at this Android target in whatever random way the SECRET PROJECT team needs". e: The only real thing on my Github is my senior project and I don't know if having it there is a good idea or not, since when I wrote it both my partner and I had very little C++ experience and were in a serious rush. If anyone is willing to take 10 minutes to look it over and tell me if it makes me look worse than not having it at all, I'd appreciate that. Yaoi Gagarin fucked around with this message at 03:20 on Mar 29, 2017 |
|
#
?
Mar 29, 2017 03:05
|
|
|
VostokProgram posted:Hey thread, I posted here a week ago asking for resume help and got a lot of good feedback, and I have a new version here. Once again, any suggestions or criticism would be great. Your resume is impossible to skim and that's bad for people who are only spending 30 seconds on it. You need some kind of dividers, bold text, something. After making all my additional comments below, I think this is your resume's greatest weakness. It currently looks like a blob of text. A random Google search suggests this might be helpful - https://www.themuse.com/advice/12-tiny-changes-that-make-your-resume-easy-for-recruiters-to-skim Format your dates somehow, add bullet points, etc. Lines shouldn't consist of a single word (i.e. "RTOS') Pick different verbs. (i.e. you use "wrote" one line and then again on the next) "Responsibilities included" does not flow with all of the other lines. Consider that the person reading your resume is either in HR, has no idea about industry specific vocabulary, or both. "Maintained a logistics software application for use at freight depots." ... I don't really get what you did.
|
|
#
?
Mar 29, 2017 05:07
|
|
|
VostokProgram posted:Hey thread, I posted here a week ago asking for resume help and got a lot of good feedback, and I have a new version here. Once again, any suggestions or criticism would be great. It's getting better. I agree with the above poster about formatting and the heavy use of jargon. Something you might do to improve it further is to make your positions bold and use bullet points to mark each accomplishment. That would help visually break it up and guide the reader through it. I don't think the current/past projects subheadings that you've used are necessary. On my own resume I do something like: quote:Company - Location - Role That way, if someone who isn't familiar with the tech reads the resume, they can see how my key accomplishments represent things they do understand (money, that I've led a team, how big the team was), while if someone technical reads my resume, they can see that I've got experience with bandersnatch frumiosity, vorpal swords and MIMSY. As an example of something on your resume that works: quote:Wrote C and C++ programs and Python scripts to test new features added to the RTOS, clearing three years of backlogged new features. I don't know what RTOS is (you defined it above, but I already had forgotten by the time I read this line), but I certainly understand "cleared three years of backlog". If you wanted to rewrite it, "Wrote programs and scripts to test new features added to a critical system, clearing 3 years of backlogged new features." is a way to cut down the jargon but say the same thing. If people want to know the details, they'll ask in an interview. As an example of something that doesn't work so well for me: quote:Writing a Python program that uses pexpect to control the Android instance over ADB and the hypervisor through the Company A debugger, and will be able to store the results of benchmarks in a database. I'm not an expert in your domain and so maybe the buzzwords are things that anyone in your area would know. But as a developer outside of your field, what I take away from that sentence is "is writing a Python program that will be able to store something in a database". (As I wrote this sentence, I further guessed that the buzzwords might have to do with running some kind of automated benchmarking test, but I only came to that conclusion because I'm lingering over what you wrote so that I can critique it.) edit: I've been taking a screenwriting course for fun and the two critical writing principles I've learned from it are "Don't confuse the audience" and "Don't tell the audience something they already know" -- I think those are useful heuristics for resumes, too. fantastic in plastic fucked around with this message at 11:22 on Mar 29, 2017 |
|
#
?
Mar 29, 2017 11:18
|
|
|
On the topic of resumes, one thing I constantly question is whether I should provide context for experience and projects, especially as someone still in school. I've tried to pare down the walls of text while trying to convey that "hey, I'm still in college but I'm familiar with buzzword," but I can't help feeling like I'm making people's eyes glaze over or giving them the impression that I have a lot more experience with buzzword I've worked with than I really do. For example, during my internship, the team I was on was developing a RESTful API to spin up a containerized <microservice technology> cluster for our cloud customers. We were "agile", with lazy daily standups and a JIRA board we rarely updated, but we also practiced CI/CD, pushing code often with tests we wrote ourselves, which were then ran by a Jenkins server. My bullet points, however, describe what I actually did for those 3 months: Configured our containers for monitoring, wrote tests to ensure monitoring availability, wrote some simple input validation for the API, and spent a lot of time having code reviewed and refactoring it (thus learning to write better Python). I can't really boil anything down to quantifiable accomplishments, but I learned a ton about writing clean code, not writing slow & lovely tests, and was exposed to a ton of different technologies. So I have three lines providing the context of the team, and 4 bullet points for what I did. On one hand, I've had recruiters are career fairs say "Wow, you have a lot of different experiences than the usual C++/Java other students have," and tell me they wanted to pass my resume on to someone working on <microservice technology> (I'd love to work with it again, but strictly speaking, I didn't work a ton with the functionality of it). On the the other, I've had folks ask me whether I configured the Jenkins server (no, I just had to unfuck it when my code broke it), or how much of the REST API I had written (not much, but I had to learn what the hell one was while I was there). Basically, I've touched on a variety of things which give my experience more breadth than many college students, but depth will obviously be lacking. I can't decide whether I'd be better off losing the contextual stuff and just sharpening the bullet points for what I did, or finding a better way of conveying breadth (or whether I should at all for some of this stuff).
|
|
#
?
Mar 29, 2017 14:13
|
|
|
I'm of the opinion that your resume exists to get you an interview, and it's up to you to get yourself a job. That means, buzzwords go on the resume, details happen in the interview. You should absolutely talk about the things you have experience with, even if you don't think it's "much." Your resume shouldn't have, you know, lies on it, so don't say "I'm SUPER experienced with Java*!!!" because a job posting says they want 5 years of experience in Java and you have done a single tutorial on Java on, like, Codecademy because you're gonna waste everyone's time and piss people off. But for the most part, you should let your interviewer determine whether or not your depth is appropriate. Like, you mentioned you didn't learn much in terms of REST. Whatever you learned I can pretty much assure you it's more than enough for day-to-day. If they want you to be, like, I dunno, Head Guy In Charge Of The RESTful API, then they'll determine that it's insufficient when they interview you because you have no way of knowing that Head Guy In Charge Of The Restful API is even a position that can or should exist. Let your interviewer decide whether or not your skills are deep enough, and use the breadth to your advantage. Vincent Valentine fucked around with this message at 04:51 on Mar 30, 2017 |
|
#
?
Mar 30, 2017 04:48
|
|
|
Smugworth posted:For example, during my internship, the team I was on was developing a RESTful API to spin up a containerized <microservice technology> cluster for our cloud customers. We were "agile", with lazy daily standups and a JIRA board we rarely updated, but we also practiced CI/CD, pushing code often with tests we wrote ourselves, which were then ran by a Jenkins server. ... I can't really boil anything down to quantifiable accomplishments,
|
|
#
?
Mar 30, 2017 16:53
|
|
|
That actually helps a lot, and I'll try and apply that kind of concision to the rest of my resume experience and let the interviewers make their own judgement about my experience before I dismiss it myself. Thanks!
|
|
#
?
Mar 30, 2017 18:42
|
|
|
quote:You’re receiving this email because you’ve shown interest in Amazon in the past and I wanted to loop you in on an event we’re having. On April 28th we’re conducting interviews to build out our Amazon Business - Software Engineering team in Seattle. I'm not sure if this is an open invite, but I can forward on a resume, or even better forward the contact details of the internal recruiters to someone if they're interested (I'm not at the moment).
|
|
#
?
Mar 30, 2017 23:45
|
|
|
Modest Mouse cover band posted:I'm not sure if this is an open invite, but I can forward on a resume, or even better forward the contact details of the internal recruiters to someone if they're interested (I'm not at the moment). PM'd!
|
|
#
?
Mar 31, 2017 19:13
|
|
|
So, uh, does doing excel report writing (formulas out the rear end) and SQL DBA/development stuff count for this thread? Because I just realized that after trying to get into a programming job for 3.5 years now, I lucked into one that wasn't even described as one when the recruiter contacted me. Yesterday I spent 6 hours working on a report and when the day was done it didn't even feel like I had been working. This is the best feeling ever.
|
|
#
?
Apr 1, 2017 18:52
|
|
|
I'm essentially finished with CS50, and am starting to try to create some personal projects. I've decided to focus on Python and Flask for the time being, but would eventually like to get into C# or Swift to do app development. CS50 did a great job giving me a strong programming foundation to build on, but I'm having trouble figuring out to do stuff outside the CS50 Cloud 9 IDE interface. Cloud 9 uses Linux or Ubuntu I think, so those are the terminal commands I am comfortable with, but my home computer is Windows. I also have an OSX laptop that I could use, potentially hooking it up to my desktop monitor. So basically, I found out today that I still need some training wheels. I spent half of today trying to figure out how to import a third party library into PyCharm using pip but gave up and just went and did it on Cloud 9. Cloud 9 is expensive and seems to be pretty buggy (especially the free version). Should I figure out how to develop on Windows, use my OSX laptop, or put a ubuntu virtual machine on my computer. I'm learning that this is a very important part of the development process that isn't really covered in depth with in the books and classes I've taken. Also, should I stick with PyCharm work in something that is a little easier to grasp?
|
|
#
?
Apr 1, 2017 23:32
|
|
|
laxbro posted:I'm essentially finished with CS50, and am starting to try to create some personal projects. I've decided to focus on Python and Flask for the time being, but would eventually like to get into C# or Swift to do app development. CS50 did a great job giving me a strong programming foundation to build on, but I'm having trouble figuring out to do stuff outside the CS50 Cloud 9 IDE interface. Cloud 9 uses Linux or Ubuntu I think, so those are the terminal commands I am comfortable with, but my home computer is Windows. I also have an OSX laptop that I could use, potentially hooking it up to my desktop monitor. I find Pycharm to be a bit overwhelming even with several years of experience. I would suggest something like Sublime Text. I think you should start developing on whichever system you're most comfortable with and worry about that later. Things like git will have the exact same commands on all the operating systems. If you're comfortable with Linux, I'd suggest that because most likely your server will be running on Linux.
|
|
#
?
Apr 1, 2017 23:42
|
|
|
If you're writing Python I think you are definitely going to want to be on something UNIX-like, either OSX or Ubuntu would be good. If you're installing using pip and don't have a virtual environment, the package is likely installed globally on the system, so no need to do anything fancy with importing into pycharm or anything. I'm not sure what Cloud9 is, but yeah you are going to want to know how to develop outside of it.
|
|
#
?
Apr 1, 2017 23:45
|
|
|
laxbro posted:I'm essentially finished with CS50, and am starting to try to create some personal projects. I've decided to focus on Python and Flask for the time being, but would eventually like to get into C# or Swift to do app development. CS50 did a great job giving me a strong programming foundation to build on, but I'm having trouble figuring out to do stuff outside the CS50 Cloud 9 IDE interface. Cloud 9 uses Linux or Ubuntu I think, so those are the terminal commands I am comfortable with, but my home computer is Windows. I also have an OSX laptop that I could use, potentially hooking it up to my desktop monitor. What version of Windows are you using? If you're on Windows 10, you can run Bash on Ubuntu on Windows to get access to the same commands that you're used to on Cloud 9. I was in a similar boat to you. I finished CS50 about 2ish months ago. Afterwards, I bought a cheap SSD off newegg and threw a copy of Ubuntu on it, and I have to say, it's helped make me infinitely more comfortable with the terminal. Things feel much more intuitive and customizable, so if you have the extra hard drive space/money to spare, I'd personally recommend you give some sort of Linux distro a look!
|
|
#
?
Apr 1, 2017 23:49
|
|
|
The Dark Wind posted:if you have the extra hard drive space/money to spare, I'd personally recommend you give some sort of Linux distro a look! It's 2017 man, use a virtual machine. They're very good.
|
|
#
?
Apr 1, 2017 23:50
|
|
|
Nippashish posted:It's 2017 man, use a virtual machine. They're very good. I've been using an Ubuntu VMWare machine for development on a Windows host for years. It's great.
|
|
#
?
Apr 2, 2017 00:22
|
|
|
Thank you everyone for the feedback. I will focus on implementing vmware unbuntu and sublime in some personal projects while I wrap up CS50.
|
|
#
?
Apr 2, 2017 01:42
|
|
|
laxbro posted:So basically, I found out today that I still need some training wheels. I spent half of today trying to figure out how to import a third party library into PyCharm using pip but gave up and just went and did it on Cloud 9. Cloud 9 is expensive and seems to be pretty buggy (especially the free version). Should I figure out how to develop on Windows, use my OSX laptop, or put a ubuntu virtual machine on my computer. I'm learning that this is a very important part of the development process that isn't really covered in depth with in the books and classes I've taken. Also, should I stick with PyCharm work in something that is a little easier to grasp? Don't feel bad. I've been programming for a couple decades, but every time I have to pick up a new IDE or package manager or some "new easy toolchain" I feel like a blubbering idiot again.
|
|
#
?
Apr 2, 2017 02:19
|
|
|
lifg posted:Don't feel bad. I've been programming for a couple decades, but every time I have to pick up a new IDE or package manager or some "new easy toolchain" I feel like a blubbering idiot again. Thank you.
|
|
#
?
Apr 2, 2017 10:13
|
|
|
Was wondering if I could get some critiques on my resume as well. I just cleaned it up with some new skills and fixed my experience. https://drive.google.com/file/d/0Bzk6dpbjvYzBN041NVp1ZWhmbnM/view?usp=sharing
|
|
#
?
Apr 4, 2017 05:55
|
|
|
Here is the third version of mine. I tried to reduce the details and jargon and just have stuff that makes me sound useful on it. Some specific questions: - I'm considering adding another entry in the skills where I'd put frameworks and other "buzzwords" that I've used that aren't programming languages, is that a good idea? - I have very little to say about my oldest job, I was a college sophomore so I was assigned very simple tasks. I tried to emphasize that other people had more time to focus on important stuff because of me but I don't know if that really works. Should I just remove that job completely? If I was actually asked about it in an interview I'd have at least one interesting story I could talk about, but as far as the resume is concerned I feel like all I can say is "this job taught me how to debug code". Other than that I'd still appreciate critiques on anything at all. Thanks!
|
|
#
?
Apr 4, 2017 07:37
|
|
|
Grump posted:Was wondering if I could get some critiques on my resume as well. Put specific technologies into each bullet point. You mention HTML and PHP and MySQL in your skills section, which are skills that employees want, but did you use them for on your job? Show me where. What kind of jobs are you looking for? Frontend, backend, QA, other?
|
|
#
?
Apr 4, 2017 15:55
|
|
|
VostokProgram posted:Here is the third version of mine. I tried to reduce the details and jargon and just have stuff that makes me sound useful on it. Add horizontal breaks. Grump posted:Was wondering if I could get some critiques on my resume as well. Several of your skills have the wrong uppercase letters, for example, it's WordPress not Wordpress.
|
|
#
?
Apr 4, 2017 17:25
|
|
|
lifg posted:Put specific technologies into each bullet point. You mention HTML and PHP and MySQL in your skills section, which are skills that employees want, but did you use them for on your job? Show me where. Front end. Almost all of my skills are showcased in my job or projects sections, except for stuff like React, where I only have small hobby projects, not large enough to put on a resume. huhu posted:Add horizontal breaks. Thanks. I'll match the formatting.
|
|
#
?
Apr 4, 2017 18:04
|
|
|
Grump posted:Front end. Almost all of my skills are showcased in my job or projects sections, except for stuff like React, where I only have small hobby projects, not large enough to put on a resume. Put a frontend skill into every bullet point in your job. You didn't install an app, you installed an HTML/CS+JavaScript app. Get those important keywords into the experience section.
|
|
#
?
Apr 4, 2017 18:20
|
|
|
huhu posted:Add horizontal breaks. What do you mean?
|
|
#
?
Apr 4, 2017 19:54
|
|
|
VostokProgram posted:What do you mean? <hr>
|
|
#
?
Apr 4, 2017 22:34
|
|
|
I'm thinking of taking a programming course or two and I was wondering how to choose what to focus on. I've moved from Calgary to Vancouver so actually having a choice outside of oil and gas related industries is unusual to me, plus I did an EE degree and focused on stuff related to that (eg lots of C with lots of pointers, Assembly and MATLAB. Less of C++/python, no web/db stuff) Like, what are the broad categories of dev work out there? I kind of have an idea that I dislike db stuff, but that might be because everytime I've worked with a db its under someone who hasn't learned a new technology since 1976 (which I know isn't uncommon) or have worked at a church for 15 years with no industry experience. I liked web stuff when I did it as a kid in grade school, but I haven't really touched it since 2009. I have Lynda.com through the local library so I can always go through those, are those worth a drat?
|
|
#
?
Apr 5, 2017 19:58
|
|
|
With EE you can get into embed, if that stuff interests you. Especially if you don't mind filling the world with more IoT I don't know for sure, but I'm under the impression that most people start off with webdev jobs now. Just off the top of my head: DBA, Embed, Web Development (Front, Back, Full stack), Video Games (no don't). From my few months interviewing, I felt more interested in what the business was doing rather than what their development area was. mekkanare fucked around with this message at 00:59 on Apr 6, 2017 |
|
#
?
Apr 6, 2017 00:53
|
|
|
I'm starting a 6 month contract position tomorrow that may turn in to a full time position if the company receives FDA approval. How should I best plan my next 6 months in the case they can't bring me on full time?
|
|
#
?
Apr 11, 2017 01:12
|
|
|
huhu posted:I'm starting a 6 month contract position tomorrow that may turn in to a full time position if the company receives FDA approval. How should I best plan my next 6 months in the case they can't bring me on full time? Get some nice, new keywords for your resume. Like Python, Big Data, ML, etc. Make your boss love you enough to give a great reference, by doing good work and making his or her life easier. Don't buy a new car.
|
|
#
?
Apr 11, 2017 04:00
|
|
|
|
| # ? May 17, 2024 21:23 |
|
|
lifg posted:Get some nice, new keywords for your resume. Like Python, Big Data, ML, etc. Yeah, buying a new car is stupid in any scenario. Always buy used.
|
|
#
?
Apr 11, 2017 05:36
|
|