|
Unsuccessful endeavors are just as worthy, if not more, to me. Especially if you can pinpoint where things didn't go well and how you'd correct them moving forward.
|
#
¿
Oct 23, 2014 15:33
|
|
|
|
| # ¿ Apr 27, 2024 19:45 |
|
|
Good Will Hrunting posted:Has anyone used those hiring websites like Hired and poo poo? Before I start an aggressive search I kinda want to exhaust my options there since it's the summer and I'm lazy. I got to my current job through Hired. Had to go through a second "marketplace" in order to not get crappy companies reaching out. But the experience was pretty easy as they're in desperate need of competent engineers going onto the platform. I'm in NYC and have 4 years of professional experience FWIW.
|
|
#
¿
Jul 2, 2015 20:41
|
|
|
Agreed, leave it out completely.
|
|
#
¿
Aug 6, 2015 16:56
|
|
|
kitten smoothie posted:Yeah, I had a similar job, except working on a rule engine. My project manager actually took me aside and told me to work more slowly and maybe surf the internet or something. I was knocking stuff out in one hour that unbeknownst to me was previously estimated to take 8, and we were billing the customer by the hour. Definitely one of the worst things I've ever been told in my career was just that. Nothing more frustrating when you want to do the work and someone actively tells you not to. I like building poo poo damnit 
|
|
#
¿
Sep 18, 2015 18:02
|
|
|
The moment the senior engineers find out the new guy is making more after having "put in" less time is when they become even more disgruntled. While I don't like co-workers discussing salaries, it does happen with some regularity.
|
|
#
¿
Sep 25, 2015 12:54
|
|
|
Pollyanna posted:I've spent a lot of time being loudly wrong at this soon-to-end job, and it has actually helped me learn quite a bit - unfortunately, it had the side effect of making my manager go "I've received complaints about you asking people too many questions" and poo poo like that, sooooooo Seconding what sink said. If I'm mentoring a younger engineer, I want them to ask tons of questions. I don't want them to be loud and obnoxious while doing it. Nuance is key here and will get you a hell of a lot further than anything else (sadly or not).
|
|
#
¿
Oct 5, 2015 20:06
|
|
|
minato posted:In my experience, a good presentation can take days to prepare, even if the author is an expert. And rehearsal time alone will take at least an hour or two. I think maybe a 5 minute presentation would be a reasonable ask to test someone's communication skills, but 30 is excessive. I'd expect the presentation aspect for a higher level position, not just an engineer. Is this a leadership/managerial role Cryolite?
|
|
#
¿
Dec 16, 2015 18:55
|
|
|
I've been out in the professional field for 5 years now and am primarily focused on iOS development. I was just promoted to a engineering lead role and we're starting to build out our team. This is my first leadership role (outside of running a summer internship program) and I'm looking to hit the ground running. Any advice for folks who've made the jump?
|
|
#
¿
Feb 13, 2016 20:59
|
|
|
Good Will Hrunting posted:Thanks for the suggestions, everyone, I appreciate it. I'm away next week and my bonus (+ raise with retroactive comp for 4 paychecks) lands on 3/15 but basically as soon as that paycheck is in my account I'm going to start aggressively looking. I'll follow up with how the search is going in a few weeks. Echoing what Chutwig said, try out Hired. Got my current job through them. Also come with with me at Plated.
|
|
#
¿
Feb 20, 2016 23:26
|
|
|
chutwig posted:Haha, Plated. Has the SVP of Eng tried to jam Hadoop into everything yet? That was his parting gift when I worked with him before. Nope! No Hadoop!
|
|
#
¿
Feb 21, 2016 16:55
|
|
|
Hired worked for me last year. PM me and I can send you my profile (that seems to have worked) if you'd like an example.
|
|
#
¿
Jun 3, 2016 18:07
|
|
|
Munkeymon posted:Also Objective C. Everyone has to have a dang app. You mean Swift? 
|
|
#
¿
Aug 3, 2016 16:18
|
|
|
Pollyanna posted:Yeah, I don't think I'm going to be able to predict lifespan/health in any intelligent way. I'm just going to focus on the poo poo that matters to me, and if my parents start giving me poo poo for working at a startup then gently caress em. You're an adult, this shouldn't matter.
|
|
#
¿
Oct 11, 2017 12:32
|
|
|
Good Soldier Svejk posted:I joined a small dev team a little over a year ago as a straight-up developer. Since then I've taken on essentially a second-in-command developer/back-end designer role under our Senior Architect. I've asked to have my title and salary adjusted given the new responsibilities and while I realize the title doesn't necessarily correlate to any real standards across the industry - having the right words on a resume can make all the difference so I was wondering what I should shoot for. I am inclined to think "Technical/Team Lead" or "Senior Software Developer" since my role has expanded beyond coding to being the direct technical contact for our clients and being the sort of "on-call" guy to put out fires. Be careful trying to jump titles too early. I don't know how long you've been working professionally, and while years of experience isn't the only qualification for seniority, but having too big of a title can screw you when you try to go elsewhere that has very different standards for the same title. Instead, I'd approach the conversation with your manager about what a growth path looks like for you at your company. What's the next tier that you're working towards? What are the competencies of being in that tier?
|
|
#
¿
Oct 14, 2017 13:18
|
|
|
Blinkz0rz posted:Confirmed yesterday that this next sprint will be my last with my current team. On 11/1 I'm moving to manage my own engineering team. 1. Get really comfortable giving and receiving feedback. Figuring this out on the job has been rough. 2. Resisting the temptation to jump into code too quickly - let folks hash it out and ask more guiding questions. Find ways to prevent yourself from being the defacto say in every conversation and having people just defer to you. (still getting the hang of it here)
|
|
#
¿
Oct 19, 2017 14:44
|
|
|
Good Will Hrunting posted:From my understanding, yes, I was told that this is how it works on other teams, but generally there's a pretty strict vetting process. Supremely fucc'd indeed. We definitely do not allow hiring managers to get referral bonuses here as that's a big no no.
|
|
#
¿
Dec 19, 2017 19:46
|
|
|
Professional goals for 2018: Double the size of our engineering guild, successfully navigate managing 2x the number of people I did last year. Personal goals: Redo my website in one of the newer front end web frameworks as I've been out of webdev for 5+ years. Need to keep my knowledge about these systems more up to date than just cursory reading. Keep doing freelance native iOS work as it allows me to keep working in the platform I love while working on features completely outside of my day to day.
|
|
#
¿
Jan 2, 2018 13:32
|
|
|
CPColin posted:At the end of last week, my new boss sent out an email introducing me to the boss of another department. The latter boss turned me down for a job something like two years ago. I wonder if she remembers me! Definitely not. Pollyanna posted:Hm. I got CTCI years ago when I was first trying to get a job, but ended up forgetting about it when it turned out that most of the stuff in it didn't really apply to what I'd be doing (and still hasn't). Given what I'm hearing, I don't think I'm prepared for this screening - is it still worth a try? Just loving do it https://www.youtube.com/watch?v=ZXsQAXx_ao0
|
|
#
¿
Jan 16, 2018 12:31
|
|
|
Whoa hey, this thread just got really serious. Software engineering generally occurs in a a physically cushy environment while having a high level of mental pressure, similar to any other office based skilled labor. We just happen to be in an excellent (bubble?) market right now so we have more leverage than others. Doesn't mean that lasts forever and it doesn't mean everyone is exactly in that same position. Finding that proper work-life balance has been key for me in order to not burn out. Do the work that enables the life that you want to live. If that's working 9-5 (let's be real, you know it's 10-6) then do it. If it's working remotely from your home, freelancing on contracts or bootstrapping your own site/app/business, cool. Programming enables all of that quite easily.
|
|
#
¿
Jan 31, 2018 13:46
|
|
|
Jaded Burnout posted:I did look at them but they're just SOOO expensive that if you even a little bit stack it up against a giant pile of top quality notebooks and pens it can't compete unless you are truly hardcore about your usage. They're very good for having all of your notes in one location and easily sharable with teammates. They're great for follow ups to meetings with said notes and annotations, and even diagrams. That said, you can also just whiteboard + write on a piece of paper and use Microsoft Lens (or I think the default camera on iOS) to "documentize" an image to a PDF. They do a pretty good job fixing lighting and aspects nowadays with that all. I don't have one here at work but I too have been thinking about it.
|
|
#
¿
May 2, 2018 16:58
|
|
|
The Fool posted:I disagree. .NET does historically trend towards enterprise, so you never see it in "trendy" startup environments. But .NET's foothold appears to be expanding with Microsoft's commitment to open source over the last couple of years. If they can keep up the momentum, .NET will absolutely gain wider usage. Agreed. Microsoft is killing it lately with its open sourcing work. .NET Core Typescript VS Code WSL All of that is dope and good.
|
|
#
¿
May 23, 2018 04:17
|
|
|
Titles mean absolute dick. Been hiring engineering teams for quite some time now, no one cares about previous titles or what you think they meant - it's the experiences, how well you can speak to them and what you're looking for next. If someone is reaching out to you for a senior title, and you even think for a second that you can't do it because you're not "senior" enough, throw out the thought completely. They looked at your resume and deemed you worthy of a contact. As long as it's something you're interested in, go for it.
|
|
#
¿
May 29, 2018 23:47
|
|
|
BurntCornMuffin posted:That said, they can be useful as a quick and dirty way to establish expectations and BATNAs for salary when it comes to negotiating and salary research. Please negotiate. 100% this. Particularly in our field as for the past 8 (more?) years, we have had much more leverage than the employers.
|
|
#
¿
May 30, 2018 11:48
|
|
|
comedyblissoption posted:an industry that has one of the highest profit margins is a weird way to phrase "much more leverage than the employers" Are those mutually exclusive?
|
|
#
¿
May 30, 2018 14:08
|
|
|
Yeah, not too sure where you're going with this.
|
|
#
¿
May 30, 2018 14:31
|
|
|
Zaphod42 posted:Hiring is also a soul crushing experience where you have to deal with hundreds of applicants not remotely qualified lying about their experience thinking they can just pick up engineering on the job just in order to find a couple people who truly understand how to program a Hello, World. I find recruiting to be one of the most rewarding parts of my job.
|
|
#
¿
Jun 27, 2018 12:22
|
|
|
Sign posted:How are you doing this so it isn't terrible? Work with recruitment and engineering leads to create a process you actually like. Move the hell away from algorithm whiteboarding. Focus on actually providing a good candidate experience. Make sure you have clearly laid out scorecards for each rec that layout outcomes as well as qualifications for the candidates. Make sure your hiring team knows which areas to focus on for their respective interviews. Know that hiring is the most important thing you can be doing, particularly as an engineering leader.
|
|
#
¿
Jun 28, 2018 15:49
|
|
|
Eggnogium posted:Am I crazy for thinking that is a wrong answer? Given only the facts of 500s I would definitely first go digging for more info before making any assumptions about the root cause. Like maybe after working on a product for several months you could have developed a sane heuristic of “500s => very likely resource exhaustion” but it would be only for that service and the wrong approach without the experience to back it up. Minato's point is it's more nuanced than just a solution and lays out a plan to find the root of the problem. Interview answers don't *need* to be technically correct as long as you explain your thought process and back it up sufficiently.
|
|
#
¿
Jun 29, 2018 12:17
|
|
|
Munkeymon posted:I think that when I approach a novel troubleshooting problem with preconceived notions of what probably went wrong that I often end up wasting time disproving my guesswork before making real progress on the problem, but that could be faulty/biased memory - certainly haven't been rigorously keeping track. I think that's a really important thing to consider (not letting your biases force you into tunnel vision) - but I expect an experienced engineer to use their previous experiences to inform their thought processes moving forward. That said, I also expect people to begin answering those types of questions by gathering more information and requirements up front (it'll almost never hurt to ask more questions).
|
|
#
¿
Jun 29, 2018 14:48
|
|
|
I joined, I am now in.
|
|
#
¿
Jul 14, 2018 02:16
|
|
|
Hey, what do people do for technical reading/resources today? We're contemplating starting a technical-book Library, but it's 2018 and there's gotta be alternatives out there. We've used Safarionline in the past but found their collection to be somewhat wanting (although we could try it again). Does anyone else have any recommendations? I want folks to be able to have a digital version, on top of a physical one, should they want it.
|
|
#
¿
Aug 2, 2018 16:16
|
|
|
Handsome Wife posted:So I'm pretty happy in my current job, feel well paid, etc., and have been there about 10 months. It's an established and growing company of about 150 people. Several things here: 1. *knocks on wood* Software engineering as a core business competency isn't disappearing anytime soon, and experienced engineers will be needed EVEN more so IF there was a downturn in the market. 2. Boomerangs are definitely a thing. Don't burn any bridges with your current employer. If/when the startup putters out, you have an easy in back with the company. 3. If/when the startup putters out, having an early stage startup under your belt like that (even if failed) will look great on the resume and you'll learn a TON. 4. You will be wearing ALL of the hats, and be on call most of the time. I don't mean production support on call, I mean chatting/answering questions and being the tech-guy on calls/presentations/pitches. It won't just be "throw Handsome Wife into the corner to let them code 100% of the time". tl;dr go for it if you're willing to put the work in.
|
|
#
¿
Sep 4, 2018 00:27
|
|
|
asur posted:The only definition for senior that is remotely consistent is being able to work with minimal oversight. At over six years experience I would definitely be applying to senior positions. Anyway you're bored and that only is a good reason to move on as when you're bored you aren't learning and improving. Agreed. You're still early on enough in your career to where (it sounds like) you still enjoy the type of work you're doing, just not the work you're able to do at your job. Stagnation now will have a much larger impact down the road.
|
|
#
¿
Sep 8, 2018 13:27
|
|
|
LLSix posted:Looking for some feedback on my resume. I tried to inline my language and technical skills with their relevant tasks and job experience to make space for more work experience examples. 1. Order your professional experience newest to oldest. 2. Kill the associations 3. Highlight your personal projects more than just saying you did them and not even specify/link to them 4. Format your sections like you would code (indentation can be your friend here) 5. Try to cut down on the amount of text for each of your lines. Indenting above will mean you'll have less space to fit things in which will help you out in the long run.
|
|
#
¿
Oct 11, 2018 00:16
|
|
|
leper khan posted:Depends if you’re trying to leave as means of promotion or not. Always shoot for 25%+ raise + any potential signing bonus to offset lost yearly bonuses.
|
|
#
¿
Dec 11, 2018 00:19
|
|
|
rt4 posted:If this company doesn't use version control properly and wants to poo poo on you for broken links in an internal site, those are two good indicators (three if we count not using git) that it's time to leave anyway This is correct.
|
|
#
¿
Jan 2, 2019 21:58
|
|
|
I feel like a lot of my initial git problems were just because of how poorly I was trained on SVN originally. Now I couldn't imagine living without it.
|
|
#
¿
Jan 4, 2019 04:18
|
|
|
Sab669 posted:It's literally just a static page full of links to different resources. This sounds like the biggest non-issue I've come across in quite some time. And I work very closely with marketers.
|
|
#
¿
Jan 9, 2019 16:57
|
|
|
Sab669 posted:I exaggerate a little bit, the exact request was: Yeah, they're testing out if you know how to write a client that interacts with a RESTful API.
|
|
#
¿
Jan 9, 2019 21:19
|
|
|
|
| # ¿ Apr 27, 2024 19:45 |
|
|
rt4 posted:Other companies are totally gormless and you'll eat dinner alone and go to bed at 9pm. And at that point it's time to find a new place to work.
|
|
#
¿
Jan 11, 2019 16:10
|
|