Keiran Kozlowski

Public Service Announcements to recruiters. If you have the same job post you re-publish every day for many weeks, we notice. This gives hesitation to apply as we have no idea why you rejected the dozens of other candidates that commented "Interested" on your previous posts. Please provide more details about the position so that it's easier for candidates to know if they are a fit or not. If your intent is to build a pool of candidates, please be candid about it and openly say "Need iOS developer to build a pool of candidates". Believe me, they will still apply.

81

8 Comments

🎥 Coding interview grind update! 🚀 I've been putting in the work, and while some interviews have been great, others not so much. It's all part of the process, and practice makes perfect! 💪 Today, I had a really good interview, and I'm excited to see where it leads. Hoping this opportunity bears fruit! 🌟 Big shoutout to @AlgoExpert for keeping me motivated and sharp during this journey. Looking forward to what's ahead! 🙌 #CodingLife #TechInterviews #StayMotivated #AlgoExpert #KeepGrinding

7

Something I've learned as an educator, leader, and learner: people love rules but say they hate them and want to be mavericks. For example (hot take incoming), in development there are strictly and dynamically typed languages. People LOVE the freedom of coding for the ability to create literally anything, but HATE how JavaScript is dynamically typed (if they're coming from a strictly typed one). This is because they can't imagine people putting data in the right way (they lack trust in users) or don't want to read/write sensible documentation. I agree that a strictly typed language is great for libraries and distributed packages / software. It's built-in documentation, inline. However, TypeScript does NOT make JavaScript readable. It even has extensions to the language that the original writers regret putting in there. What it boils down to is that humans are actually quite good at following rules, but are not so great at following principles. However, principles are far more powerful and flexible than rules. They are evergreen and timeless, whereas rules generally expire with progress or conceptual flexion. We should (not just developers, but all people) focus more on the principles, for more unity and peace in our lives and as a group, and less on ridged, inflexible, rules. Maybe hiring will improve too - after all, no one has experience in Cobol, Fortran, JS, React, Angular, Vue, Linux, and Windows, PowerShell, Bash/ZSH, plus a Sec+ cert, and chops in finance, a minor in data science, has a masters and 3+ years experience for an "entry level" job.

5

Most jobs have an easy-to-understand title you can quickly mention and move on from with no risk of confusion, and most job titles don't require lengthy explanations. I'm a photographer. I'm a teacher. I'm a zoologist. People nod, say something polite like "That must be interesting!", take a sip of their drink and continue the conversation. "I am a Software Engineer ," however, almost always results in raised eyebrows followed by a rambling monologue where I try to explain the complexity, expansiveness, and evolving nature of the field. #gratitude #career #tech #leadership

11

This job market is a dumpster fire. Hot, flaming garbage all around. I've read your stories. So many brilliant, talented and dedicated people are caught in the lurch. So many tragic stories of application purgatory (I'm looking at you, Workday and ATS systems) constant customization of resumes, CVs and cover letters... and more cover letters. (I got so sick of writing cover letters that I actually just sent a chili recipe as a cover letter - don't tell anybody) My point is this: You're valuable. Getting laid off is not your fault. Please don't feel like a victim - a big ask, I know. You've honed your craft and your skills absolutely have value. This too shall pass and I want you to know that I'm cheering for you. Simple as that. I'm cheering for you to get a better gig than you had, to get the remote or in-office situation that suits you best, a competitive market-value salary (no low-ball offers), and a chance to work within a team that values your contribution and makes it known. You deserve every bit of it. EVERY BIT. A colleague had a brilliant quote: "Your network is your net worth." Work those contacts, use this platform to connect in positive ways. I'm cheering for you.

14

How do Software Engineers get promoted? Technical ability + soft skills +strategic moves Here's how to stand out 🤝 Master your craft 🔊 Dive deep into your technical skills. Always be learning, whether it's new programming languages, frameworks, or tools. Your commitment to excellence sets you apart. Solve the right problems 🔊 Look for opportunities to solve problems that align with your team's goals and your company's mission. It's not just about fixing bugs; it's about identifying and solving high-impact problems. Communicate with impact 🔊 Whether it's through code comments, documentation, or presentations, your ability to clearly communicate complex ideas is crucial. Remember, your code isn't just for machines; it's for people too. Take initiative 🔊 Don't wait for opportunities to come to you. Propose new projects, improvements, or innovations that can drive value for your team and company. Show that you're thinking ahead. Seek feedback 🔊 Regular feedback is your growth catalyst. Embrace constructive criticism and use it to refine your skills and approach. Remember, feedback is a gift that helps you grow. Network internally 🔊 Build relationships outside your immediate team. Understand the broader business context and how your work fits into it. These connections can provide valuable insights and opportunities. Demonstrate leadership 🔊 Leadership isn't just for managers. Mentor juniors, lead by example, and contribute to a positive, inclusive team culture. Show that you're someone others can look up to. Align your goals with your manager's 🔊 Understand your manager's priorities and how you can contribute. Regular check-ins to align your goals can pave a clear path to your promotion. We are djr 🔵 ⚪

3

🚨 Hiring a Junior Developer in 2024 🚨 Over the past 2 months I onboarded 8 bootcamp grads. Let me tell you, the job market is flooded with bootcamp grads, but there’s a big issue: many stop coding until they land a job, and their portfolios are often clones of the same bootcamp projects. What are companies really looking for? 🔍 Self-taught problem solvers who can adapt on the fly. A modern, self-built portfolio showcasing real-world solutions, not just coursework. Demonstrated experience with client projects or unique challenges they’ve overcome. It’s not about how many years you claim—it's about showing how you’ve applied your skills. Your portfolio should speak volumes about your creativity and drive.  If you’re on the job hunt, keep coding, keep learning, and build projects that make you stand out!

264

37 Comments

What is the best combination of references for a job application? Curious to hear thoughts on this, and again especially from people involved in the hiring process. I had a conversation with a student recently who felt it would be best to have recommendations from three professors, and particularly ones who knew the student from very recent classes. I wasn’t as sure that this was necessary or even necessarily beneficial. But I don’t know. What factors make a good reference portfolio? Do people expect an undergraduate student to have three solid references from school who can speak directly to their expertise in their field? Should a student specifically look for more diversity, like two professors and a head counselor from the camp where they had their most recent summer job? A successful aunt or uncle who’s known them their whole life and will speak on their behalf? Is a professor from an advanced class more valuable than one from an introductory class? A current one more valuable than a previous one? Etc., etc. What makes one reference better or worse than another, and what’s a good combination?

2

I'm certainly not the most neurodivergent person out there, but I have my quirks. As I've been interviewing, I've noticed a lot of stumbling blocks for people who are neurodivergent. Recently while prepping for a HackerRank challenge, I read one of the agreements they ask you to sign and it occurred to me: if the hiring team focuses on the wrong metrics I'm screwed. During some proctored tests you may get dinged for some out-of-the-ordinary behaviors. Here's some of my [mostly subconscious] fidget behaviors to help illustrate what I'm talking about: * Randomly highlighting or clicking things while reading or just wiggling the mouse cursor a bunch; depending on the platform, you might get dinged for [possibly] trying to copy text or using automation * Repetitively alt-tabbing -- again, depending on the platform they may think you're cheating * Typing & deleting a single character repeatedly -- I doubt an automated system would notice this, but I've noticed it bugs some people a lot, so could create bias if the interviewer notices * Although less likely to be an issue: long pauses with no activity while in deep thought -- this could look like cheating as well * Excessively using shortcuts can signal the use of automation -- I hate using the mouse; I grew up trying to do everything with a keyboard. Unfortunately, I guess that can make it look like automation. * When I'm trying to figure out a "real" problem mentally, I have a tendency to make "nitpicky" code changes; this can signal I'm "focused on the wrong thing", when in reality it's just busy work to keep my subconscious busy while I'm mentally focused on "the right thing" What quirky behaviors do you have OR have you observed in others that could be an issue during an interview?

18

5 Comments

Doctors hate charting. I built a tool to automatically generate structured clinical notes from an audio memo - or a recording of the entire appointment. A workflow for many independent clinicians making house calls is to do an audio memo, send this to someone for transcription, get the drafted note back a day or so later later, and then make final edits, sign, and upload to a secure database. This cuts the process down considerably: go from audio memo / appointment recording to structured SOAP note in about a minute. Review and sign. It works surprisingly well! I was even able to tuck in an additional feature: the app automatically generates a "second opinion" for the clinician to consider. Potentially decreases the possibility of clinician error or oversight. Built with Replicate and Supabase. Deployed with Vercel. Currently doing evals with models from Anthropic, OpenAI, and Gemini AI #medtech #healthtech #healthcare #ai

16

5 Comments

When I built Learn WCs, I disabled animations on Firefox because the frame rate was so bad. Turns out it was due to 2 CSS properties 👀 I wrote up how I diagnosed the problem and what I did to fix it #webdevelopment #webperformance #frontend #css https://lnkd.in/eCQ3e_eD

2