93 subscribers
Go offline with the Player FM app!
Podcasts Worth a Listen
SPONSORED


1 Understanding Taxes as a Newly Formed Small Business - Part 2 of the Small Business Starter Kit 28:24
Episode 444: Surrounded by apathetic coworkers and put it on my resume?
Manage episode 462176091 series 1314025
In this episode, Dave and Jamison answer these questions:
After a decade as a Senior front-end engineer in companies stuck in legacy ways of working—paying lip service to true agility while clinging to control-heavy, waterfall practices—I’m frustrated and exhausted by meetings and largely apathetic, outsourced teams who don’t match my enthusiasm for product-thinking or improving things. It seems allowed and normalised everywhere I go.
How can I escape this cycle of big tech, unfulfilled as an engineer, and find a team with a strong product engineering culture where I can do high-impact work with similarly empowered teams? Thank you, and sorry if this is a bit verbose! Thanks guys. Martin
How do you judge your competency in a technical skill and when should you include it on your resume? Should you include a skills that you haven’t used in a while, skills you’ve only used in personal projects, or skills that you feel you only have a basic understanding of?
I’m a frontend developer and I’ve seen some job descriptions include requirements (not nice-to-haves) like backend experience, Java, CI/CD, and UI/UX design using tools like Figma and Photoshop. I could make designs or write the backend code for a basic CRUD app, but it would take me some time, especially if I’m building things from scratch. I’ve seen some resumes where the writer lists a bunch of programming languages and technical skills, and I often wonder if they truly are competent in all of those skills.
454 episodes
Manage episode 462176091 series 1314025
In this episode, Dave and Jamison answer these questions:
After a decade as a Senior front-end engineer in companies stuck in legacy ways of working—paying lip service to true agility while clinging to control-heavy, waterfall practices—I’m frustrated and exhausted by meetings and largely apathetic, outsourced teams who don’t match my enthusiasm for product-thinking or improving things. It seems allowed and normalised everywhere I go.
How can I escape this cycle of big tech, unfulfilled as an engineer, and find a team with a strong product engineering culture where I can do high-impact work with similarly empowered teams? Thank you, and sorry if this is a bit verbose! Thanks guys. Martin
How do you judge your competency in a technical skill and when should you include it on your resume? Should you include a skills that you haven’t used in a while, skills you’ve only used in personal projects, or skills that you feel you only have a basic understanding of?
I’m a frontend developer and I’ve seen some job descriptions include requirements (not nice-to-haves) like backend experience, Java, CI/CD, and UI/UX design using tools like Figma and Photoshop. I could make designs or write the backend code for a basic CRUD app, but it would take me some time, especially if I’m building things from scratch. I’ve seen some resumes where the writer lists a bunch of programming languages and technical skills, and I often wonder if they truly are competent in all of those skills.
454 episodes
All episodes
×
1 Episode 453: Why did my company build an internal LinkedIn and how do I not get stagnant in my skills? 31:34

1 Episode 452: Consulting refactor and extra work, extra scrutiny 25:12

1 Episode 451: Un-collaborative architect and who is my boss? 32:47

1 Episode 450: I'm terrible at behavioral interviews and time zonessssssss 34:04

1 Episode 449: My tech lead ignored my warnings and I don't know what my leadership style is 29:54

1 Episode 448: Title over salary and from figure skater to software developer 28:01

1 Episode 447: Overleveled at FAANG and accidental draft feedback 30:11

1 Episode 446: Wading through AI slop and they don't get git 33:19

1 Episode 445: Staying at my first job and my coworker is insulting other departments 26:23

1 Episode 444: Surrounded by apathetic coworkers and put it on my resume? 31:10

1 Episode 443: Does my PM hate me? and My coworker has anxiety when I help 36:26

1 Episode 442: Improving communication skills and how to break my job hopping habit 31:45

1 Episode 441: Will working in healthcare hurt my reputation and precious wisdom 22:53

1 Episode 440: How do I help my boss not burn out and should I tell people I'm older than I am? 37:24

1 Episode 439: Harried VP of Eng and first startup job 23:20

1 Episode 438: Software job after prison and working 60 hours per week at age 20 and feeling unfulfilled 42:25

1 Episode 437: My company canceled all one-on-ones and moving to a single backlog 30:29

1 Episode 436: Paralyzed by checkboxes and I'm on a "must keep happy" list 33:34

1 Episode 435: How to make my boss actually do something and kindly shooting down 32:40

1 Episode 434: Forgetful boss and nothing to say 33:49

1 Episode 433: My teammate pretends we decided, but we didn't and my team is getting worse and worse 31:29

1 Episode 432: As an LLM, how can I be more emotionally smart and when to use I vs we? 35:23

1 Episode 431: Stinky.js and power hungry friend 34:49

1 Episode 430: Should I quit this job I'm underqualified for and honestly torpedoed my promo chances 30:46

1 Episode 429: Should I quit my job for free hoodies and manager to IC 29:20

1 Episode 428: Interim tech lead and asking for a raise when a peer leaves 27:32

1 Episode 427: Under to over-employed and wibbly wobbly timey wimey 30:16

1 Episode 426: I got too many promotions and I have anxiety about getting fired 32:10

1 Episode 425: Org chart bait and switch and ole' reliable 26:29

1 Episode 424: Bragging without ego and how to predict layoffs 29:32
Welcome to Player FM!
Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.