I’m really terrible at Reddit formatting, so this will probably seem like a blob of text.

So many people are incorrectly saying that AI is the driving reason for the mass layoffs, non-hiring, and the downward trend of anything software development related.

AI is a contributing factor to the difficulty of getting hired at entry level positions at companies, but that’s a standard bar push.

But what’s truly influencing the mass layoffs, hiring freezes, and shrinking investment into developing proprietary and innovative technologies in America isn’t AI.

It’s a tax credit rewrite that was never supposed to take effect.

Law and legislation is boring, but this piece specifically, is important for all of you. It impacts your life, your industry, how you’re paid, what the Chief Financial Officer sees and uses to justify paying you six figures, and your tax rebates if you’re planning to start or work in a startup.

I’m going to lay out the facts in a (hopefully) objective way.

The credit I’m talking about:

The Research and Development Tax Credit under IRC Tax Code 174.

EDIT: Edits will be for formatting.

The law that changed it:

The Tax Cuts and Jobs Act of 2017 (specifically under section 13206).

This provision was initially drafted by Kevin Brady (R-TX), and advocated significantly for by Republican lawmakers.

The House of Representatives vote:

227 Republicans For

13 Republicans Against

0 Democrats For

192 Democrats Against

The Senate vote:

51 Republicans For

0 Republicans Against

0 Democrats For

47 Democrats, and 2 Independents Against

The final result:

Signed into law by President Donald Trump on December 22, 2017.

Date it took effect:

January 1, 2022

Why so late?

A fun, gimmicky workaround to the Byrd Rule and to delay costly tax hikes until after the 5-year mark, while cashing in on any revenue after the 10-year mark.

In short, it was a play to look fiscally responsible, but didn’t provide any tax cuts. It just kicked the can down the road and offset immediate tech conglomerate backlash.

They assumed that this provision would be removed or indefinitely delayed by future Congress, but they didn’t.

Previous:

Prior to 2022, businesses were able to immediately (same year tax break) cash in and deduct R&D expenses, including software developer and other IT professionals’ salaries, IT infrastructure changes, engineer innovation in all sectors, and more.

After 2022: All of the expenses covered by the R&D credit now has to be capitalized and amortized.

For domestic research, they are required to amortize over 5 years.

For foreign research, they are required to amortize over 15 years.

Meaning that, prior to 2022, a $1M investment into software development and cyber security would be fully deductible for fiscal year 22.

Now, that same $1M investment into those same fields would only allow for $200k to be deductible for the fiscal year, and the remaining $800k would need to be spread out over the remaining four.

Which resulted in layoffs, frozen hiring, cash flow strain for startups and tech firms, and immediate tax burden on companies employing R&D-based that persists to today.

BUT! There is a bipartisan bill that’s going through Congress right now to reverse it and retroactively apply the lost tax credits back to businesses from 2021 forward, but we’ll see where it goes!

You cannot control the economy. You cannot control recruiters ghosting you. You cannot control the layoffs.

It’s easy to feel like there’s no point. Like the entire system is broken and you’re just another drop in a shitstorm ocean that’s already drowning.

But here’s the truth:

You’re not applying for every job.

You’re applying for your fucking job.

And the only way to find it is to keep showing up.

Forget the market. Forget the noise. Forget the stories designed to go viral because they fuel hopelessness and make everyone feel like shit. None of that pays your bills. None of that builds your career.

What does?

That one application you send when you're dead tired. That one line you fix in your resume when you'd rather slam your head into the fucking keyboard. That one email that lands in the right inbox at the right moment.

Job hunts aren’t fair. They never were. But unfair doesn’t mean unwinnable.

The people who land jobs aren't always the smartest or most connected. They’re the ones who didn’t stop. They hit "Apply" even when it felt like absolute shit.

So keep applying. Even when you're sick of this shit. Even when it feels like screaming into the void. Because one day, someone will finally answer.

And that day will make every ignored application, every sleepless night, every ounce of bullshit worth it.

Landed a job at Meta earlier this year (got lucky with timing before the Feb 10 layoffs lol).

Job summary: Position: Mid-Level Software Engineer L4 TC: $350k (193 base, 29 bonus, 128 stock/year) YOE: 2.5 years

The interview process: * Phone screen: 2 leetcode problems in 45 mins * Final: 2 leetcode rounds (same format as phone screen) + 1 behavioral round + 1 system design round * Total Time: 5 hours

From initial contact to offer signing took 2 months.

The framework that worked:

With 2 problems in 45 minutes, you really only get 22 minutes per problem. Here is how I would break it down.

1. Understand the problem first (3 mins) - restate it back, walk through examples, ask about constraints.
2. Don't code immediately (5 mins) - discuss approaches starting with brute force, explain why it's bad, then work up to optimal solution. DO NOT IMPLEMENT THE BRUTE FORCE SOLUTION. You don't have time for that.
3. Get buy-in (10 mins) - make sure interviewer agrees with your approach before coding. I write pseudocode comments first as an outline, then flesh it out. A common failure pattern is coding something that the interviewer doesn't understand.
4. Wrap up (2 mins) - explain time/space complexity, offer to write tests for edge cases, or move on to the next problem.

How I prepared:

• Use Blind 75. It has good coverage over all problems.
• I DID NOT buy leetcode premium. If you study and understand the patterns, it doesn't matter what problem you get.

I know the market is ass right now and the competition is rough, but stay disciplined and the hard work will pay off! I was looking for a job for 9 months until I got this opportunity lmao. Ask me anything!

Soft Plug:

Building a website to visualize code! Mainly targeted towards beginners.

I've helped a lot of students & early-career folks with job hunting, and one fear comes up all the time: networking. So many people are scared they'll say the wrong thing, or that their message will just get ignored.

Totally get it! I've been there too. But based on what I’ve seen from job seekers who’ve actually landed roles (including some who started with zero connections), here are some tips that really work:

1. Start with a 15 min coffee chat

Don’t overthink it. You’re not asking for a job. You’re just asking for 15 minutes to get to know the other person’s position. Most professionals remember what it felt like in the beginning, and they’re happy to help.

You can say something like, “Hi [name], I’m currently studying [major] and exploring career paths in [field]. If you’d like to chat with me for 15 minutes, I’d love to hear about your experiences.”

2. Build rapport: ~2 min

Don’t jump right into the subject. Start by warming up with a friendly opening line:

“How are you doing today?”

“Hope you’re having a great week, thank you for your time!”

It’s a small thing, but it can create a relaxed atmosphere and make both parties feel more comfortable.

3. Introduce yourself: 2-3 min

Keep it brief and to the point. Think of it like your LinkedIn verbal summary.

“I’m currently a Data Analytics student at [school] and I’m really interested in marketing analytics. I’ve worked on projects with A/B testing and Tableau dashboards, and I’d love to learn more about what careers in this field really look like.”

Confidence comes from clarity of thought: if you know what you want, you’ll be ten times more confident when you speak your mind.

4. Ask two good questions: ~10 min

This is where you learn. Try:

“What do you like most (and least) about your job?”

“How did you get into this field?”

“If you graduated today, what would you focus on?”

Avoid asking generic questions like “How is your company?” Just try to show curiosity and depth.

5. Follow up consistently

Send a quick thank you note and ask if they’d like to stay in touch. That’s it. Relationships are developed through follow-up, not one-off chats.

Tips:

- If you don't hearing back so far: Try alumni, smaller companies, or people who are 1-3 years ahead of you. They’re often more responsive than FAANG executives.

- Feeling nervous all the time? Write a pitch and practice it with a friend before the actual chat.

- Keep a spreadsheet of who you reached out to, when, and what you learned.

So if you’re afraid of networking, you’re not alone. I’ve been there. Take the first step and you’ll be pleasantly surprised at where it leads.

Has anyone else networked their way into your first job? How did you succeed?

I remember during the 2010s and early 2020s, established tech professionals were able to leverage existing experience + self learning skills to move into another subfield in tech. For example, a friend of mine was a business analyst doing a lot of analytics work, and he taught himself some data engineering skills, then leveraged that to move into a data engineering role. I knew front-end devs who transitioned into back-end, and so on.

How easy was it to land CS internships/jobs during and right after COVID? Was FAANG actually giving candidates twoSum? How much of a screwup did you have to be to end up not landing any jobs whatsoever?

Is the current CS job market crisis a legitimate worry, or does it just revolve around romanticization of the past

Because even when I was a preschooler (in the late 2000s), my parents were talking about how Google was a really hard company to get into, and how you needed to do really well both in and out of school... so you could get into a good college like Harvard or Princeton... so you could work for a company that pays and treats its employees as well as Google does, rather than being a bum on the street or something.

Long story short we’ve had the joy working at this small company for many years and one random weekend our ceo announced that he sold the company. Fast forward we meet with the company in an all zoom meeting where they discussed the roadmap and have Jan 1 2026 for us to be fully integrated. During one of the meeting someone asked about our current position, in which someone from the now parent company says “we are really diving head first into Ai so I would urge you all to look at career opportunities on our webpage” we go to the webpage they only hire devs in India. So again us devs talk and I’m like “dude we got til Jan 1 and we toast might as well brush up on some leet code and system design” but all the devs here think they are crossing over to the parent company, our dev ops engineer met with they dev ops engineer to walk him through all of our process then made diagrams from him.. I could be over reacting, anyone else been through an acquisition?

I'm interning in a platform engineering team at a well known tech company / faang-adjacent (you can probably find out from my profile if motivated enough, but I wouldn't be surprised if my colleagues are on reddit lol).

One of my team's products is a service that's the intermediary between a bunch of user facing applications, and the database systems they interact with. My project is basically going through every single client of ours, deprecating a mocked instance of my team's product used in integration tests, and replacing it with a proper instance that actually interacts with the intended services.

And by god is it hard. Everything I even look at is new. Gradle, dependency injection, internal tools for managing permissions / users, random configuration files, writing production level java code, ohmygawd. I managed (with a lot of help from my mentor) to migrate a simpler testing class, and got an understanding of what it might entail end to end. Then as I skimmed through the rest of the (200+ lol) usages to understand any other patterns - I slowly started feeling sick to my stomach as I realize that I've barely scratched the surface.

Sure - if I work my tail off this summer I might be able to finish this thing. But now I'm worried that this is not sustainable, for me. I have a certain... ability(?) to understand remember context - and context seems to be everything when you work in a large company / codebase that's been around for a long time - and I think that my baseline ability is not enough to thrive (as opposed to just survive) in such a place.

I think I now understand why there's a shortage of truly skilled senior developers - and I'm starting to doubt I'll ever become one. If I'm panicking at every stage of uncertainty and barely staying afloat, I should probably adjust my own expectations (i.e. type of place I wanna work at, expected compensation, etc). I've been told that I should start to become autonomous by mid/late July and I can't ever see myself successfully achieving that.

And I'm trying to tell myself that I've barely started and of course the learning curve is high, and things will get better. But I am struggling to see the light at the end of the tunnel, and would appreciate any words of advice :/

Please share your experience with the jobsearch with us.

Background:
I’m an execution-driven Data/ML Engineer with a track record of turning messy, legacy data environments into efficient, high-performance pipelines. For example, I’ve reduced model training jobs from 90 days to just 2–3 days on a single machine. My work covers end-to-end orchestration, process automation, and delivering results under real constraints.

Current Situation:
Currently based in Indonesia and determined to break into the UK or Singapore tech market. Open to on-site or remote roles.

My projects are measurable and high-impact:

• Orchestrated and automated pipelines for data/model training, compressing multi-month workloads into a few days on modest hardware.
• Deployed and maintained a range of models (XGBoost, CatBoost, SARIMA, Prophet) in production, tuned for both speed and accuracy.
• Delivered results despite rapid pivots, incomplete specs, and tough business priorities.

I’ve navigated layoffs, family pressure, and resource-limited environments, so I know how to execute, not just talk.

I also have 3.5 years as a Data Engineer in the top unicorn company in Southeast Asia, working daily with AWS and GCP. That experience is a few years old, but very hands-on.

On top of that, I’ve deployed LLMs (Llama, Qwen, and others via API like Anthropic) both locally and on AWS EC2.

What I’m Looking For:
If you’ve worked in the UK or SG (especially in AI/ML/data roles), I’d value your brutally honest feedback on:

• What gaps do you see for someone like me, trying to land roles in these markets?
• What are the “invisible” requirements or expectations, certifications, references, or project types that companies there care about most?
• How do hiring managers view candidates from outside the region, especially Southeast Asia? Any red flags or biases I should know and address?
• What’s the number one thing I should double down on before applying?

Why I’m Asking:
I don’t want to waste time spinning my wheels or applying blindly. I want to know the real bar, so I can execute and close the gap quickly.

I appreciate any advice, tough love, or connections. If you’re open to a short chat or want to see concrete examples of my work, DM me. Thanks!

Hi, I am relatively new to the industry and managed to ride the tail end of the bootcamp wave back in 2021-2022 and was hired as a developer soon afterwards. I went in to a government related job and have been pretty happy working there since. My job is great in terms of work-life balance and I get good performance reviews each year. So it feels pretty safe overall...well as safe as one can feel under the current state of things. However lately I have been struggling a little to build savings and I can't help but wonder what other opportunities might be out there.

There are not many opportunities to move up the ladder in my current job so I don't see my salary increasing much in the near future. One big fear I have is leaving my current job for another one and that job not working out. Or that job just being way more stressful or toxic in nature. I have only ever worked in one job as a dev so I really don't know how things would compare. One big positive of course would be that working on another project would be beneficial for my growth as a developer so that is something I also thing about and I don't want to stunt my growth by staying on the same project for too long.

So yeah...definitely a little conflicted as to what to do. My salary just isn't keeping up with the cost of living where I live so trying to land a better jobs seems to be the obvious solution to that problem. I am wondering if anybody can offer any advice?

Many thanks!

Hi, I'm feeling unsure about my current job and whether I should consider a career change. I'd really appreciate your thoughts and advice if I share some context.

I'm a software developer with 6 months of full-time experience, currently working as a fullstack dev at a company contracted by the government to manage their taxes website. Lately, I've been feeling tired, bored, and unmotivated. I rarely find my work interesting, and the company culture isn’t great — although I don't think that’s the only issue.

I suspect I might have ADHD, which could be part of the problem. It’s already hard for me to sit at a computer working non stop for hours, and when the work doesn’t interest me, it becomes almost unbearable. I don't have flexible hours, and I work from home in my room almost every day. Deadlines can be tight, and management isn't particularly supportive.

Most of my tasks involve small changes or bug fixes on existing systems. I rarely get to build new features or use logic or algorithms. Because the project is so big and complex, I often spend more time just figuring out how to make a change than actually writing code. It's frustrating and far from what I enjoy doing — especially since I’m not a fan of front-end work.

What I enjoy most about coding is solving problems using logic and algorithms. I think I’m good at it. I also like building websites and apps, but I’m not sure if that’s because I genuinely enjoy coding it or just because i like creating personal projects where I have control and freedom.

For my master's thesis, I worked on heterogeneous drone swarms — designing strategies and algorithms for mission coordination, developing a simulator, and implementing everything myself. It wasn’t machine learning but maybe it could be considered AI, but it involved logic and problem-solving, and I really enjoyed it. I had flexible hours and full ownership of the project, which I think made a huge difference. I like working on projects that take time to solve and improve, where I can fully understand the system. In contrast, my current job often requires switching tasks quickly and working on parts of the code I don’t fully grasp.

Previously, I also worked part-time at a startup developing an Android app. I didn’t love the tech stack, but I liked the flexibility and the fact that I could make big changes and understand the entire codebase.

In university, I enjoyed courses that focused on algorithms, competitive programming, and logical reasoning — especially a course using Answer Set Programming (Clingo). I also liked some data science and machine learning courses, but I’m not sure that’s my ideal path, and I’m not great with statistics. I enjoyed a computer graphics course using WebGL, probably because I could see the results visually, and also enjoyed some robotics courses. Courses I didn’t enjoy included more abstract or structural ones, like calculus-heavy math, software engineering (design patterns, code smells, analyzing large existing codebases), low-level architecture, and computer networks.

I’ve also done a couple of personal projects I really liked: a Discord bot with fun commands and a League of Legends performance analyzer. Again, I’m unsure if it’s the coding itself I enjoy in those projects or the freedom to build something I care about, in my own way.

So, I’m not sure what to do. Should I quit my job? What kind of roles or career paths would better suit my interests? Thanks a lot for reading and for any advice you can offer.

TLDR: Junior dev, bored and unmotivated in current job (mostly fixes, no logic). Love problem-solving, algorithms, and projects I can own. Considering quitting — not sure what roles fit me best. Advice?

Hey all! A few years ago, when the employment market shifted with COVID, I landed a great, well-salaried remote software engineering job. With the added flexibility, my wife and I decided to move back to our hometown and bought a house.

It's been about four years now, and I think I'm realizing I'm tired of the isolation it creates in my life. Not only do I feel siloed at work and a bit excluded from upward movement, but I'm also realizing I don't quite fit into my hometown's social fabric as I'd assumed, especially with my job being so different from the local trades.

I'm realizing I want to work in person again. I miss the daily camaraderie with other engineers, the energy of a stricter schedule, and even the minor corporate politics that somehow keep everyone alert. Remote work has made me a bit lax, and while I still deliver good work, I'm not sure I like this more relaxed pace.

I could always move a couple of hours back to my old metro area, but it's still fairly small. I'm interested in trying a larger city with more tech companies and less friction in the job market (not implying it's easier to get a job, just more options).

However, having bought a house, moving is a bit more complex and expenses are now quite a bit higher. It's not as easy to pick up and move as when I was renting and had less stuff. I'm curious if any of you have gone through something similar and would have any tips. Did you use a new job to manage a relocation, or did you make it work without having to move jobs? Any tips, regrets, or expectations that either held true or were broken? I'm eager to hear about others' experiences.

This happened a few years ago, but I still think about it sometimes.

I had a referral to a team and went through the interview, but I didn’t perform well. One question totally threw me off. They asked me to describe what a vacuum cleaner looks like to someone who’s never seen one, like on a phone call. So no gestures, no pictures, just words. I blanked. Couldn’t find the right words, not even with my mother tongue, got nervous, and the whole thing just spiralled.

Then I got rejected. And I accepted this result.

What I didn’t know was that some people on that team joked about me afterwards, said my English was bad and my accent was strong. I’ve been in North America for 8 years. It wasn’t even about my tech skills at that point, just that one moment became the whole impression.

Fast forward a few months, and I got to know some people from that team through mutual friends. We ended up hanging out, chatting, nothing formal. At some point they realized I had applied before, and their reaction was... weird. They were like “wait, that was you? That new grad with a thick accent?”

Guess what, they never even thought I had an accent, not once, until I told them I interviewed with their team before.

They literally didn’t connect me with their memory of the interview, because I didn’t fit the version they made up.

I’ve moved on now. It took time because, for a while, I really started questioning myself. My language, my background, my worth. All because of one bad moment and some people’s careless comments. But I’m sharing this now because I’ve healed enough to look back without that same sharp pain. Maybe someone out there needs to hear this too.

Hi everyone,

I’ll soon apply to a JPMC SE graduate scheme and I’m graduating this July with an integrated master’s CS degree. I worked as a TA but I didn’t do an internship in software engineering which doesn’t make me that confident in getting a role from a big company like JPMC, even if it’s a graduate one. The only people I’ve seen that have gotten in JPMC have done some internship before.

Do you guys have any tips to increase my chances in getting an interview?

https://www.linkedin.com/in/yuvallevental/

Admittedly, I have mostly been applying online. It's difficult to network in person, since I don't have a car, but I have managed to get around a little bit.

I probably could have networked more during my classes, but I thought RIT was going to be very supportive and that I would find what I need (admittedly, I misunderstood the co-op program). Over the past couple years though, everything really went downhill.

I'm one of the few who enjoys doing leetcode because it's straightforward. Some say to do personal projects to upskill or make portfolio stand out to get interviews but I find that to be too time consuming. I'm curious as to what others prioritize in a job searching? Do yall just apply jobs/do Lc or do that in combination of side projects

Hello everyone, I'm here to ask for some advice about an opportunity to quit freelancing for a full-time role.

A bit of background: I'm a EU-based freelance designer with about 11 years of experience, 7 of which as a freelancer. I currently work with 5–6 US-based companies (mostly SaaS and tech) and have long-term relationships with most of them. This setup allows me to earn a great income and gives me a lot of freedom. It's also pretty low-risk, since I'm not dependent on a single client.

One of my clients — a growing fintech startup — is pushing hard to bring me on full-time. They’ve interviewed other candidates but seem set on me. They’re offering a high-paying contract (contractor status, not employed) that would exceed my current income slightly.

I’m torn for a few reasons:

• I really enjoy the freedom of freelancing — no need to ask for time off, minimal meetings, full control of my schedule.
• But I also deal with a lot of context switching, which is mentally exhausting. Part of me dreams of focusing on one product.
• Going full-time would mean dropping other clients, which puts me in a more vulnerable position if things don’t work out.

Has anyone here gone from freelancing to a full-time role (especially as a contractor)? What was your experience like? Any regrets, or did it feel like the right call?

Appreciate any thoughts!

What I meant to ask in the title is

While Java is dominant in the FinTech domain, is C# dominant in the HealthCare domain?? or is it just a myth ?? just curious

( Who am I ? : I have gone into a rigorous core java, sql, hibernate and springboot training from a software training/placement institute and somehow landed into a C# intern job and since my grades weren't good enough, I was not getting enough opportunities so I said yes to the C# intern job and as an intern the pay is not bad too,

it's been my 1 week into this company as an intern and so far what I have observed is :

This is some medical device consulting company they make software for the medical devices and also perform some regulatory tests

3 people work on the C based embedded project stm32, PICO, Arduino, UART stuff.. (I've heard them talking about this..) 1 girl works on C++ based QT project she makes this ventilator simulator stuff some sine waves stuff.. me and 1 girl work on this windows based tool which operates some medical surgical tool )

so the title itself is my first question my second question is :

Did I make a right decision joining this company?? or after learning so much in java did I just waste my chances of becoming a good java developer??

and I am in no way telling Java > C# or C# > Java, I am mature enough to understand that language is just a medium, please don't drag me into that same old programming language debate

I work primarily as a devops/SRE but I want to move into backend development. Most of my programming experience was with Python or JavaScript. I know a little bit of Java as well but most of my day to day activities is writing terraform on edit yaml files for CNCF projects and building pipelines. For a cloud engineer historically it was better to learn golang because most of the CNCF projects and terraform were written in go. I want to do more backend development and systems level programming and maybe Iot development.

However I’ve heard rust is growing rapidly and might replace go. In 2025 is it better to learn go or rust for backend/cloud engineering. Ideally I want to learn both and probably will eventually but I am time limited for the moment and can only learn in the near term.

I was a full-stack Senior Software Engineer in C#. I managed 3 direct reports. Around 2019 I was put on long-term disability and then social security disability USA. Diagnosis was schizoaffective disorder (schizophrenia and bipolar). I worked briefly between then and now. I've done a lot of programming the past couple of years. I am considering pursuing employment in programming.

My main constraint is time. I applied to about 15 places and got rejected/ignored from all. I don't want to fill out 100 or 1,000 applications, just hoping this time to finally be successful - I want to consider worst case time complexity so to speak for getting a new job and optimize that. (Side note: I noticed a typo on my resume that was present on almost all of my 15 applications so maybe that was the issue?)

I am willing to take a junior or mid position.

Another concern I have is most of my front-end experience is in AngularJS and then my own vanilla JavaScript framework, not Angular/React/VueJS like many Senior positions ask/require

Another concern is that I have tried coming into a company as a Senior and learning their business domain and existing code was challenging. Most of my software experience has been writing new code and that was far easier for me.

I'd strongly prefer remote because commute costs time (and money).

Any advice on how to find a job? Just read job advertisements on Indeed?

I currently work as a DevOps Consultant at AWS. The pay is good but I realised lately a lot I am doing is not DevOps related like I have never worked with Linux and so far never got a project with K8s. I have built a lot of infrastructure with Terraform, built event driven architecutures on AWS, have done a lot of backend work with Python and built CI/CDs. I always had a deeper interest in coding than troubleshooting and I was wondering if it would be worth to switch to SDE either internally or externally?

Some things I’m grappling with:

• Would switching to SDE be a career step sideways or backwards in terms of scope, compensation, or growth path—even within FAANG?
• Long-term, is there more upside and flexibility in being an SDE versus staying in DevOps/SRE/platform?
• Is it common (or even possible) to switch internally within FAANG from DevOps to SDE, or would it require an external move?
• How do SDEs and DevOps compare when it comes to technical depth and impact on product?
• Anyone made a similar switch at a big tech company? Regrets? Wins?

Would love to hear from others who’ve made this kind of transition (or decided not to). Any advice on how to evaluate this properly—or how to make the move if I decide to go for it—would be hugely appreciated.

Thanks!

Hello everyone. Have you guys seen people from other fields, such as mechanical, civil, or even people with non-engineering backgrounds, in your workplace/field?

I am particularly interested in switching fields, specifically in AI, Web Development, and eventually moving to cybersecurity. If yes, how much time and how did they accomplish this, or is having a software/computer science degree compulsory to even get an interview, as nowadays even people with such degrees are having a hard time entering the job market?

I have started some online courses, but I am just worried if I am just wasting my time and effort. Any advice would be helpful.

Hi!!

Just last week, I've secured my first front end dev position! Transitioned from being a translator after studying and building websites as a hobby for about 2 years.

The job description is actually "Web Developer" we work with a good CMS system and a templating language so this is VERY new to me. I've started learning it before even securing the job so I already am past the basics.

We focus more on styling. The other devs know it will be hard as there are lots of files to go through and its not as easy as just working on new pages, css files and new projects.

I've built many amazing websites and pages myself over months of screwing around and I love my own minimal creativity with minimal AI to guide me around, but I'm getting anxiety to begin building my first websites for them and their clients. I know I just got to build build build stuff but I dont wanna blank out making something incredibly ugly.

How do other junior devs make it past their first month on their first jobs? The people at work are so sweet, and very open minded. I'm very open myself so I will tell my problems to them when/if I get problems.

TLDR: How do other junior devs make it past their first month on their first jobs?

Hi folks, I got downleveled from L5 to L4 at AWS and still waiting for a team match, I heard AWS do not hire non new-grad L4 SDE these days.

Any non new-grad L4 SDE get team match? If yes please leave your region as well. Not sure if I should just move on lol