2. Guest Talk 1 #
Created Thu May 23, 2024 at 7:28 PM
-
Improve AI usage thinking: AI wise, it’s ok to think how to use current AI APIs to solve software problems/enhance current-products. You don’t have to learn ML from scratch, unless you’re deeply interested it in specifically.
-
Proof-of-practice is an important sort of evidence for a job
- Projects should be deep or be end-to-end. They shouldn’t be a weekend project.
-
Q: Can you plz talk about how you managed to revise all the things before any interview, which things you prepared well and which you left behind, also can you share about your resume that how you mentioned your scaler curriculum there ?
- Revision strategies.
- Making notes
- Leetcode 75, 150 is good
- Revision strategies.
Articulate about soft skills in your resume
- Learnship skills
- Stakeholder management
ATS scorer:
- gowtham
- resumeworded
Principal engineer #
Q: As principal software engineer, what kind of work have you done in past 6 months in Oracle? What are you upcoming goals?
A: Day starts with standup (last 24h and what today). Bugs and features.
Quitting a job and study #
This should be last resort. Because there’s:
- Anxiety
- Hurts confidence
- my_point: Likeliness for wasted time and low-end jobs
Kshitij, Bhalla, Anshuman (HLD)
Resume is a single thing recruiter cares about #
So keep resume effective:
- Use numbers
- Add transition
Stop making identity based on stack #
All software is mostly design, programming, testing. Tools don’t matter that much.
What you want exists, look for it #
I have wasted a lot of peace, time thinking I’m whiny, unrealistic which made me miss even common and known info, that was helpful to my goal, almost exactly.
So prioritize:
- Find, reinterpret, create artifacts
- as a last resort, assume you’re wrong, and accept whiny