1. you don't have to tell people you were fired in interviews, and it won't show up in background checks. you'll be fine.

  2. ...I'm not exactly sure what you're asking, but it sounds like "would a sales job or a helpdesk job better develop psychological tricks for security testing". Both are really not great for that, and those really aren't the type of skills you should be targeting to start out as a pentester.

  3. being reasonably resourceful/persistent is most of it, on top of generally solid collaboration/soft skills. most of the job is researching problems and synthesizing a solution. the people who suck at their jobs are the people who give up/can't figure out the answer to basic problems without handholding, the people doing well are the ones that can research the answer to most questions without much outside assistance.

  4. most school and local government roles are more or less identical, same pros (stable, easy) and cons (lower avg comp, bad places to learn/advance), so shouldn't be a huge jump in that respect. if you want growth, you might be better off getting out of anything government-adjacent.

  5. googling "Go Cloud Career reddit ban" reveals this:

  6. JDs are usually not comprehensive - you're meant to find out more about the specifics of the job in the interview.

  7. depends on employer/skills. no real consistent answer. employers are often fine with some skill gaps - they're looking for the whole package, so somebody who is personable/has a good attitude but works with a different tech stack is going to be more attractive than somebody who has a shit attitude but is 100% flush with the company's existing tech.

  8. yep. good certs are good, a ccna is a good cert for a ton of different things.

  9. sure sounds like you have a performance review coming up and don't expect any increase in comp. not sure what you are looking for.

  10. if you try to find a job outside current company and you can't make the jump to net admin, then jumping to t2 is a good thing to do. so I'd just make the t2 jump then try and find a net admin role later.

  11. Working on a team with other developers on an existing codebase is usually the definition of professional software development.

  12. yep, can also make friends with the devs you work with and get referrals/learn from them which can range from "pretty helpful" to "accelerates career progression by years".

  13. Depends on locale, but unless you've taken on a lot of duties outside your original role, I don't think so. Basically, unless you were underpaid to start, which it doesn't sound like, just getting better at your job isn't what gets you raises; you're supposed to get way better at your job in the first 6 months. If you did something like take on new work building out cloud infrastructure, yeah, maybe there's a conversation to be had.

  14. If you're serious about your career you should probably get out of a solo-IT situation and avoid them categorically. MSPs are going to be hectic/crazy, generally, and you'll deal with a lot of the same bullshit, but you'll get massive upside too of the challenge + fast learning pace.

  15. doesn't build professional connections, near-impossible to find an in-field mentor to help you grow, work-complexity levels are generally very low are the big reasons

  16. Not sure where you work, but this is exactly how it works everywhere I’ve worked. If you waste the time of hiring managers and interviewers, you will have some questions to answer

  17. Yeah, eventually somebody is going to notice that you're throwing shit at the board to see what sticks, and just stop interviewing your referrals.

  18. Nothing to do really except move on. Often, the reasons you're going to get aren't even the actual reason; there's a lot of stuff going on behind the scenes that you aren't privy to.

  19. I said that thing in the first interview, and still made 2 interviews and assessment after that so still not that.

  20. No idea what their reasoning was for continuing to interview and there's no real way to know, it could be a ton of things.

  21. If they give you work above support at your current job, and you can see a path to higher-level disciplines, then honestly I'd target that over a short-term pay raise.

  22. there are a lot of IT career paths besides helpdesk. check out wiki/do some research, find one that interests you, then figure out what skills those folks tend to have and get certs that validate these skills/try to move into roles that use these skills in your current company.

  23. Counter point: cover letters are not necessary and I don't think anyone should bother unless you are making a massive career shift and want to explain it.

  24. I'm with you, they're never going to save a bad resume and they at-best quintuple the time spent applying per-job. If you're getting absolutely no bites and you've already done the best you can with your resume, sure, maybe spend the extra time. But if you're going to pick between always writing cover letters and never writing them, I think the case is waaaaaay stronger for never writing them.

  25. 1 page is plenty unless you're dumping everything you've ever done onto it, using very loose formatting that wastes a ton of space, or including useless filler like a bloated skills section or an objective/professional summary. Lots of people want to include everything they've done since the dawn of time, which pushes them to 2 pages, but once you have more experience you should be trimming down things you've done to only include the things directly relevant to the job.

  26. Even scripting pulling data from an email could be difficult if there is non-standard formatting, but pulling data from a phone call automatically is not realistically possible in your position.

  27. Yeah this is standard for government, it's very stable/easy/good benefits but also a very bad place to learn + cash comp isn't great. That combination of positives also tends to attract people who aren't especially good engineers, which makes it an even worse learning environment. Stability is also somewhat overrated; if you're a somewhat-experienced halfway-decent sysadmin/cloud admin/dev, you can find a job in five minutes, so getting laid off isn't a major risk.

  28. Too many certs would be stacking entry-level certs across a bunch of different functional areas, which makes you look like you have no idea what you want to do.

  29. Differences between SQL dialects are not very substantial, usually just comes down to syntax/different function names. Only think that is awkward when swapping between DBMSes is the actual database configuration differences, but those also aren't that difficult to pick up.

  30. It's used fairly broadly, but it's one of those things that isn't really a differentiator - anybody can learn what they need to know about MS Project in a couple of weeks.

  31. I don't know where you got that idea, people doing the hiring look at githubs all the time...

  32. Whoever said that is very wrong. Every middling-or-better CS hopeful has their github linked in their resume for a reason.

  33. almost definitely no. check out the wiki.

Leave a Reply

Your email address will not be published. Required fields are marked *

News Reporter