|
Unsinkabear posted:Managed to keep the text at size 12 by making some small tweaks to other content. Still interested to hear what you guys think about min text size though. I'm far from an expert, but I would organize your skills into grouped bullet points. Maybe organized into more technical tools, social media platforms, something else? Things like 'Python' seem really good to highlight, but at the moment it's a bit hard for any individual one to stand out.
|
#
¿
Oct 4, 2018 03:31
|
|
RIP ZEEZ 
|
|
| # ¿ May 3, 2024 02:12 |
|
|
Cross-posting from the Newbie programming/interview thread: Would y'all be up for giving some feedback on my resume? This version is specifically for new grad data science jobs, but I also use a version with some skills/projects swapped around for data engineer positions too. There's a couple things in particular I'm not sure on: 1) I started my current internship a week ago, so I have no accomplishments, but it will use skills from coursework that don't come up elsewhere (esp on the data engineering/infrastructure side of things), and has a lot more name recognition than other places I've worked. Basically I want enough there that I can chat with an interviewer re: what I'm doing without misrepresenting my experience. Tbh I'm still kind of baffled they hired me for the role at all. 2) The most recent completed internship (second in list) specifically wasn't focused on business outcomes, but instead on making design decisions - which I loved - but that doesn't translate as well to clear numbers/impact. Are these bullets alright, or should I try and cut/quantify more? 3) At the bottom, I just added a section with two research projects I completed for classes, with links to the Github and paper. They're also on my portfolio site, but the basic idea is to get across the idea that I've completed substantial ML projects (which aren't under NDA or otherwise disallowed from being put on Github) and can do that kind of work despite not having a grad degree. Not sure if the section is getting that across as-is though - maybe I should be more specific re: the techniques/tools used, or just cut it and leave them on the portfolio site only? The 'impacts' are also strictly 'here is some small contribution to the field', and idk if that really comes across as substantial. I could also cut it and replace it with something else, or increase the font size or what have you if it's too dense. 3.5 - I left out my other experience during college, since some of it was social science research, and the rest was product management at a start-up and neither felt as relevant. It does mean I have a gap for 2019/2020 though, not sure if that matters  I'll also go over it at my uni's career center when I can get an appointment, and ask some other folks to look at it elsewhere ofc. Basically, I'm applying to FAANG/big tech companies for the first time, and would like to be a competitive candidate/get a gut check re: if my resume's in an alright spot. On a related note, if anyone has good resources they'd point to slash tips for negotiating offers I'd appreciate it (reading through the one from the OP). The place I was at over the summer should be sending me a full-time offer in the next few weeks, and is pretty great in terms of work-life balance, has a uniquely interesting career progression, and is at a v specific intersection of a lot of my interests - I loved working there. The one issue is, from looking on Glassdoor/h1b sites, salaries there average ~80k, whereas it looks like equivalent roles in the Bay Area are more like 110-130k (the place I'm furthest along with in the interview process apparently has like 140k total comp for the Cloud SWE III role I'm for some reason being considered for). I honestly didn't realize that new grad salaries were that high here, but that's a pretty tough salary difference to overlook, and I'm worried about anchoring salary expectations for my career going forward. It does feel kind of absurd when compared to the non-profit stuff I'd done before going back to school, but hey. e: Ok, I found a typo/some inconsistent capitalization looking back at it, will fix that foutre fucked around with this message at 03:14 on Sep 30, 2021 |
|
#
¿
Sep 30, 2021 03:11
|
|
|
downout posted:Negotiation thread is pretty helpful on that part https://forums.somethingawful.com/showthread.php?noseen=0&threadid=3768531 Ah, missed that one, thanks!
|
|
#
¿
Sep 30, 2021 06:49
|
|
|
CarForumPoster posted:Hey, though we're not hiring right now I hire people like you. In fact you'd be just about my ideal intern engineer 1 hire based on resume. This would easily put you in the top 15% of applicants. This was all very helpful, I appreciate it. I'm coming from a social science background, so it's v encouraging to hear that I've gotten to a decent spot as a technical candidate too. I'll go ctrl+f for your post in the YOSPOS thread (and yeah just lol at intern salaries; I know a lot of folks in the grad programs who basically fund their academic year lives off those kind of internships - which is maybe more of an indictment of grad student stipends than anything else, but hey), and take a look at the negotiating one as well. I'll spend the weekend making a few toy examples of things I've done elsewhere; I have most of a web app in Dash already done so I can 100% just deploy it quickly and make a serial numbers filed off/generic version of what I worked on. I also have a super basic 'social network' in React that I made for a class that I can probably make a generic version of as well. I've been putting off making the toy versions of a couple of notebooks, thinking like, ah, will people even look at it? But it sounds like they absolutely would, good motivation to go get that done. I'll go through and do some cutting in general, and add back in some of the other experience -- very good point re: keeping one bullet from 3 years ago vs. demonstrating a long work history. I'll look at YC/start-ups as well, getting competitive offers is one of my goals for sure. I'm also not necc. opposed to that genre of company, it's just that in my last position I was basically the most technical person as an intern and didn't really have anyone to mentor me/learn from, which I realize is almost certainly not representative, but I do want to make sure that I go somewhere with a good support structure for my first role. VelociBacon posted:Rip Zeez RIP ^ . Ty, will fix that real quick! foutre fucked around with this message at 22:21 on Sep 30, 2021 |
|
#
¿
Sep 30, 2021 22:17
|
|
|
I'm not actively looking or anything, but I try to update my resume occasionally as I do stuff. Hearing those X times salary guidelines made me think of one bullet point I've been struggling with. An AB test I ran on a feature I've worked on for 1 1/2 years went really well (i.e., a some % bump in weekly retention, with about as solid of an experimental protocol as you could realistically have) and ended up being deployed to production. That should translate to at least a $10 million dollar increase in yearly revenue (this is pretty conservative and assumes a v significant drop-off in the initial effect). To me, that seems like a more impressive number to share than the retention bump, but I worry it's 1) so large it sounds like nonsense (it's like 75 times my salary...) 2) it's making some (reasonable, imo) assumptions about the rest of the year post-test (which, again, seem to be correct but it's ofc hard to perfectly track the continuing impact of a specific change once you've rolled it out everywhere). Alternatively, I could just list the retention bump, but I think if you don't know the size of our user base or how hard it is for any one change to shift retention, then it's not really clear how impactful it is. What would y'all put down? One issue is that I can't share stats that would let people calculate either 1) total users or 2) total revenue, so I have to work within those restrictions. I think this might be my statistics brain that always wants to qualify everything shooting me in the foot, but I wanted to get y'all's thoughts. Hopefully, this won't actually be relevant for a while since I'm not looking to move, but I wanted to get it squared away.
|
|
#
¿
Jan 3, 2024 22:30
|
|
|
CarForumPoster posted:Share both thats a killer metric. The revenue is the more important one. Not unreasonable to create a 100x value, that's the magic of software. Its why you can get paid figgies. Sweet, will do. I appreciate the template sentence too!
|
|
#
¿
Jan 3, 2024 23:00
|
|
|
Lieutenant Dan posted:I mostly do systems design & narrative design for single player games, but I got my start in QA analysis and am super happy to do that too. I realize I'm trying to get back into the industry in the WORST POSSIBLE TIME IMAGINABLE, but it's literally the only thing I've done professionally besides freelancing comics since 2009 and I love this industry to death, so - please help me take a scythe to this resume and get it 2024-ready? As a qualifier, I've got much less experience but for game dev some scattershot thoughts on cuts/consolidation, I guess take them with a grain of salt! I think you have more than enough impressive experience/skills/accomplishments, imo I'd focus on choosing which to highlight. I think the solo dev, the two full-time roles, and the full-time cartoon work are the things to lead with and to make sure you keep. Everything else imo is bonus, just if you have extra space. I think priority is keeping it lean enough that people read through the good stuff! 1. Cut out the music and submissions editor 2. Cut print specialist, medical bias reviewer and design jntern; reduce the diversity consultant and authenticity reader to 2 bullet points, one describing what you did, one the companies 3. Try to remove bullets that are repeated - i.e., either include the nyt bestsellers in awards or the comic work experience but probably not both (def include though, of course - maybe notable enough to double up, but be v v succinct in at least one section). 4. Cut the teaching to one or two bullets: just courses and positions at most, maybe either just cut the life drawing or cut it to like 3 words. 5. Maybe move the teaching artist in residence from cartoonist to teaching, and cut down length. 6. Remove the HS diploma 7. Could move the portfolio link to the same line as contact info, maybe have it on the left bolded? If not don't and center enough that way them nevermind! 8. For the solo dev section consolidate the "Featured" bullets, and consolidate the various review bullets. 9. Try and cut down the bullets in each experience section, and include specific technical skills you used in each (i.e., did you use Unity? Add that to a sentence, so they don't have to wait until the technical skills section). Basically try and have the bullets highlight an accomplishment and the skills if reasonable. 10. I don't think MS Office suite needs its own line, paper prototyping could maybe also get cut or consolidated. Similarly, probably cut the big bullet of cool skills down to like a line; it's sick but probably not all relevant enough to give it so many inches! 11. Each games internship should probably just have one bullet at most, if included 12. Should the shipped games be enumerated separately, or part of the relevant roles? I've seen the latter, plus maybe "x shipped games" earlier on. That said the games resumes I see are all data science/analytics, so I'm sure conventions are different. Also on PTO but I can see if we have anything relevant and PM if so - imo try the game jobs thread as well of you haven't. E2: potentially also cut down some of the extra experience that's less related to specific roles after those cuts, I think you'd prolly be better serves with multiple resumes for diff roles. foutre fucked around with this message at 21:43 on Jan 6, 2024 |
|
#
¿
Jan 6, 2024 21:27
|
|
|
Organic Lube User posted:I'm constantly on the fence about whether or not to check the disability box for my ADHD. I usually don't, and just figure I'd just magically "discover" I have ADHD after starting the new job and then have them do accommodations. I think one case it could help is for government jobs, they'll often have Schedule A quotas and can fast-track candidates with disabilities. You'll need documentation as well; outside of that context I don't disclose it, and don't really touch on it beyond that. Could v well depend on the agency, so could be hard to know if it'll help or not. foutre fucked around with this message at 01:35 on Jan 20, 2024 |
|
#
¿
Jan 20, 2024 01:33
|
|
|
I'd just write your graduation date, that's what I do with a more substantial gap than that and it's worked just fine. I guess maybe there's an argument if you're trying to make it clear why there's employment gaps, but I think if you're largely applying for new grad roles I don't think that's an issue.
|
|
#
¿
Jan 29, 2024 23:07
|
|
|
Probably will cross-post this to the Data Science thread, but I've got some internal interviews coming up and would love some advice re: what to prep. There's a couple Senior data science roles that have opened up, that'd be a v good fit for me (they're down to downgrade them to regular DS, which would be a better level for me). I'm currently a 'senior data analyst', a role I've been in for 2 years post-graduation, and have been considering swapping, but wasn't going to do so just yet, so I've got some review to do. Talking to coworkers, it looks like there's 5 parts: 1. Behavioral 2. A ML case study (i.e., talk through some common models, discuss the decision-making process around it, implementation, pros/cons etc) 3. Python coding 3a. Pytorch coding 4. 'Product' interview - i.e., working with stakeholders, calculating ROI, etc 5. Another behavioral with your would-be manager I've got like a week to review (wasn't planning on moving just yet!). The Python coding and working with stakeholders are 90% of my job, so I feel pretty good about those. In school, I did a decent amount of stats/ML coursework, and a good bit of NLP (mostly transformers). However, the most complex model I use regularly at work is a logistic regression - part of the reason I want to move is that a good % of my work is just graphing - and I've only touched Pytorch once in the last few years. I think that I should definitely review common machine learning models, and go back and refresh on Pytorch. However, I'm not sure what to focus on/what resources to look at (esp since I've got a bit of a time crunch). Do y'all have suggestions for how to prep, what to make sure that I know, etc? I realize this is a bit field-specific vOv I was originally going to go back over my ML and DL coursework, but I think I've gotta be a little more targeted than that to make this work.
|
|
#
¿
Feb 7, 2024 01:08
|
|
|
Hey y'all! I'm trying to update my resume for an internal Data Scientist role, and would love help cutting it down/improving my resume - I wasn't planning on moving before this, so I'm a little underprepared. I basically specifically just want to target it for this role, and would appreciate any help/advice/criticism!quote:Main job responsibilities: A little added context - there's another role not posted yet that I'm also interested in, which is basically an NLP data scientist doing a lot of work in Pytorch. Both are listed as Senior, but they'd be open to down-leveling to a regular one for me. The specific role I'm interested in is the matchmaking one, I don't actually want the forecasting one and I'm a bit ambivalent about the recommendation one. I've worked with people on both of the teams, who are actually part of the interview process which is a bit weird but probably good, given they also framed it as "you should apply, we'd like you on the team". My resume is: (for whatever reason the formatting got messed up, the actual, non-anonymous one is a single page, albeit with similarly small margins) https://docs.google.com/document/d/1pWpbSnJuGa4DZhXGWstUmnIB0PI8YbziAsDqoB6Q9YA/edit?usp=sharing Some questions: - Are there things that I should cut (esp. in the 2 internships) or highlight more/less? In particular, are there any things from the JD that seem weak? Aside from Hive/Hadoop, I do have other things I could highlight for all of them - I wasn't prepped for this, so the bullets under my current role aren't the best - please lmk where/what I should improve! - My trajectory at the current place has been-- internship, return full-time, got promoted -- is that fine just lumped? Is there a good way to cut that down? - I've built a recommendation system before for a class - chatbot that recc'd movies using collaborative filtering - but it's been a while. Worth adding as a project? - Is there anything that I'm missing from the job description, looking at this? - I've sometimes included this section of personal games: quote:Selected Games: Game1 (bit.ly/d2020 - platformer in Unity, won Industry Awards from Niantic and Improbable.io for Best in Show at 2017 University Game Design Showcase, start of University Game Design Club), Game 2 (bit.ly/ritd - visual novel with procedural character relationships, in Unity), Game 3 (bit.ly/st - MatchX game built in Phaser) but cut -- it's a pretty short timeline, but maybe it's worth just putting together a quick portfolio site to host them instead? I wouldn't actually be making games in this role tho vOv. I also have one more internship in between these, which was just a month working with the NASA Ames High Performance Computing group, but all I did was spec out an internal on-prem system using AWS to swap over some of the supercomputers from simulations to modeling. I got sick and had to leave early so I didn't actually like, execute on the plan, and I figured a 1 month stint would raise more questions than it's worth. Does that make sense? Idk, the value I could see is just 'this group at NASA thought I'd be a good fit for their data engineering work, let me signal that I can do this', but the experience itself is not much. I think this is something I'm pretty specifically qualified for, and I do think I'd do well in a Data Science role, I was just originally intending to take longer to prep before moving.
|
|
#
¿
Feb 9, 2024 22:06
|
|
|
Lockback posted:I got access denied trying to access your resume. Ope, fixed, ty for the heads up!
|
|
#
¿
Feb 10, 2024 00:25
|
|
|
Lockback posted:Am I reading it right that this is an internal role? Yup, this is an internal role! Thank you, this is very helpful. Great call-outs on what to emphasize/how it comes off. I think I probably over-emphasized the data janitoring, I've been hunting down bugs in our ETL lately so its top of mind, but % wise it's pretty low. Wanted to make it clear I could do it, but it sounds like I overcorrected! 99% of my data work actually comes up when I'm working to build a model from particularly messy data and realize there's a better way we could be ingesting or surfacing it (or that theres a table I need thst doesn't exist). My role is basically a mix of running & analyzing AB tests (plus setting up KPIs & dashboards), ad-hoc data analysis & storytelling (90% data viz), and building models/simulations (usually designed to be interpretable by non-technical stakeholders, so it'll be a lot of translating design problems to data ones, data processing, then like a logistic regression with gradient descent). Sounds like I should definitely emphasize the last part (maybe last two parts?) more. Is there anything else in that that you feel doesn't come across? Sounds like I should for sure add that stuff in to set up those convos. The plan is for a decent amount of my prep to be making sure I can talk about the decision making around this stuff. Really appreciate the feedback! Arquinsiel posted:Did the plan get executed on? If so you have a really impressive project to brag about. Bonus points if it was executed smoothly based on your plan. Maybe reach out to former colleagues to find out? Yeah, good call! I think they may have ended up using a parallel system that looked /very/ similar to what I laid out, but may have just been developed elsewhere in the org. I'll double check though! foutre fucked around with this message at 01:02 on Feb 10, 2024 |
|
#
¿
Feb 10, 2024 00:59
|
|
|
E: Submitted, fingers crossed. Ty for the help!
foutre fucked around with this message at 23:45 on Feb 15, 2024 |
|
#
¿
Feb 13, 2024 22:04
|
|
|
|
| # ¿ May 3, 2024 02:12 |
|
|
Just got the (verbal) offer for my internal transfer! I was a bit worried about the timing, since I was going to get promoted to lead next month in my current role, but it sounds like my current & soon-to-be bosses both advocated v hard for that to be taken into account. It’s a 25% increase in pay, and a role I’m very excited about - data science, but entirely focused on game design, truly so specifically targeted towards me & my skill set. I think I’m technically on the low end of the salary band for the role, but to be fair this is the end of my 2nd year working after going back to school so I mean I’m not mad! This is also a role that usually requires a MS/PhD on top of 2-5 YoE so truly it does make sense, I think I’ll just have to make sure my salary doesn’t get too anchored by this. A very common move is to go to FAANG for a few years and then boomerang back here, but hopefully won’t be necessary. I also get to keep my years at the company for accruing more annual weeks of PTO, which is great - I think I’m a year off 3 weeks, and then two more after that for 4? Thanks to everyone in the thread for the resume help and interview tips, it’s very very appreciated.
|
|
#
¿
Apr 18, 2024 21:48
|
|