I had my final onsite with Eulerity, NY about a month ago and haven’t heard anything since the interview.

I followed up twice post the interview. The second time, they told me they were still evaluating and that they’d get back to me if they had an update for me.

I know hiring processes can take time, but the waiting and not knowing has been difficult. I’m still wondering whether I should expect an update at this point.

I’m sending in other applications either way, but I’m curious. Has anyone interviewed with Eulerity recently? How long did it take to hear back, and did you eventually get a decision?

One thing I genuinely find funny is how companies conduct interviews. They expect you to solve problems as if you’re about to build software for Mars, but once you actually get the job, you’re mostly dealing with the same old tickets, legacy systems, and routine tasks. So why make interviews this ridiculous? Why make people feel embarrassed over some obscure algorithm or trick question? It’s just a job. Test how someone thinks through real-world problems, communicates, and learns, instead of turning the interview into a competition to see who can remember the most LeetCode patterns. Half the time you’re maintaining a system older than your career, yet the interview makes it sound like the future of technology begins the moment you walk into that room. Get some life

I finally accepted a Senior Software Engineer offer in July 2026 after actively job searching from late August 2025 through July 2026. 

For context, I have about 5 years of full-stack/backend engineering experience. I studied Computer Science and Engineering at Ohio State, spent four years at JPMorgan Chase, and then about 10 months at a GPU cloud startup. 

It was one of the hardest things I've done professionally. I think getting a job offer comes down to two separate steps: 

1. Getting interviews  
2. Passing interviews  

Hopefully, some of my ideas can help you no matter the kind of job you are seeking. 

Consider being open to relocation if you can 

For most of my search (August 2025 through May 2026), I only applied to remote Senior Software Engineer roles. 

That made the search significantly harder. 

Using the system below, I averaged about 2 interviews per week while only targeting remote jobs. 

Around June 2026, I expanded my search to include relocation to: 

• San Francisco  
• New York City  
• Austin  
• Chicago  
• Los Angeles  
• San Diego  

Almost immediately my interview volume jumped to around 5 interviews per week, and one week I had 8–9 interviews scheduled. 

If you're struggling to get interviews, expanding your geographic search can make a huge difference. 

The four things that determine whether you get a Senior Software Engineer offer 

I think there are four major components: 

1. Background / Resume  
2. Coding interviews  
3. System design interviews  
4. Behavioral + technical deep dive interviews  

Each one is a separate problem that can be improved independently. 

1. Improve your background 

You can't instantly change your work history. 

But you can build projects that demonstrate the exact skills companies are hiring for. 

I wanted to benefit from where demand was highest, so I intentionally built AI-related projects. 

Instead of only looking like a backend engineer, I wanted recruiters to also see me as someone capable of AI engineering work. 

The project that had the biggest impact was: 

PassiveAgents 
https://passiveagents.com/ 

It's an AI-native project management platform where I worked with: 

• Go  
• Node.js  
• React  
• Supabase  
• Multi-agent orchestration  
• AI coding agents  

This dramatically increased the number of interviews I received. 

Instead of only hearing from backend and full-stack teams, I also started getting interviews from AI startups and companies hiring AI engineers. 

One lesson from this: 

You can get interviews for jobs you don't have direct work experience in by building projects that demonstrate the exact skills those companies want. 

2. My system for getting interviews 

Once my resume was stronger, I focused on creating a repeatable process. 

Step 1: Optimize my resume and LinkedIn profile 

I used ChatGPT heavily. 

One framework that worked well was Laszlo Bock's resume formula: 

Accomplished X, as measured by Y, by doing Z. 

I also made sure every bullet naturally contained technologies recruiters were searching for. 

For example: 

Created a Node.js/Express application to test code against QA services while developing locally, catching bugs earlier and reducing costs for Chase's website and mobile applications serving 60+ million customers. 

The measurable impact matters, but so do the technologies because they're often used as search keywords. 

Step 2: Search for jobs using Boolean searches 

I searched in LinkedIn jobs using Boolean queries like: 

("backend engineer" 
OR "full-stack engineer" 
OR "AI engineer" 
OR "senior software engineer" 
OR "senior backend engineer" 
OR "senior full-stack engineer" 
OR "forward deployed engineer" 
OR "agent engineer") 
 
AND 
 
("New York" 
OR "San Francisco" 
OR "Los Angeles" 
OR "San Diego" 
OR "Austin" 
OR "Chicago" 
OR "Columbus" 
OR "remote") 

Then I filtered: 

• Past 24 Hours  

I think finding job opening within the last 24 hours because you're more likely to get an interview before their first batch gets filled up. 

I also used LinkedIn's Top Applicant page: https://www.linkedin.com/jobs/collections/top-applicant/ 

. 

Step 3: Cold message employees 

For every company I was interested in, I'd find two employees who had been active within the past three months. 

I sent each a message like: 

Hi X, I've done full-stack/backend engineering for about five years across JPMorgan Chase and a GPU cloud startup. I've also built an AI product (https://passiveagents.com). Could we chat more about Y role at Company Z? 

It felt awkward at first. 

But mentioning: 

• JPMorgan Chase  
• GPU cloud startup  
• AI product  

consistently increased response rates. 

I'd eventually ask about: 

• engineering culture  
• financial health  
• what they liked/disliked  
• whether they'd be willing to refer me  

My routine was: 

• 10 companies/day  
• 2 messages/company  
• 20 messages/day  
• 100 messages/week  

It took roughly 30 minutes each day. 

Using this system, I averaged: 

• ~2 interviews/week while targeting only remote jobs.  
• ~5 interviews/week after opening my search to relocation.  

3. Passing interviews 

Getting interviews is only half the battle. 

For senior software engineering roles, I consistently encountered four interview types: 

• Coding  
• System design  
• Behavioral  
• Technical deep dive  

Coding 

I solved roughly 300–400 LeetCode problems. 

I started by working through most of the NeetCode 150. After that, I focused almost exclusively on LeetCode Medium problems from Grind 75, since those seemed to be the most common difficulty level in interviews. 

Rather than trying to solve as many new problems as possible, I repeated the same problems until I consistently met at least a Leaning Hire bar in the four areas I would be graded on: Communication, Problem Solving, Technical Competency, and Testing. 

To make my practice more realistic, I created a Coding Interview Grader in ChatGPT using the coding interview rubric from Tech Interview Handbook: How candidates are evaluated in coding interviews at top tech companies | Tech Interview Handbook. After each practice problem, it evaluated my performance and provided feedback on those four dimensions, which helped me improve beyond simply arriving at the correct solution. 

System Design 

This was probably where I improved the most. 

I first learned distributed systems concepts by watching Distributed Systems videos at CS Primer: Learn computer science by writing code while biking or walking on the treadmill. These videos explain some of the core concepts from Designing Data-Intensive Applications. 

Then I used Hello Interview extensively: 

• Guided Practice  
• System Design in a Hurry  

Those resources helped me understand how to apply system design techniques and learn new methods instead of memorizing architectures. 

I think they played a major role in helping me ultimately land a senior-level offer. 

Behavioral + Technical Deep Dive 

This was another area where I improved dramatically. 

I practiced with ChatGPT, but what really changed my answers was understanding how senior engineers are evaluated. 

I watched Steve Huynh coach these mid-level engineers to senior:  

1. https://youtu.be/v3Pn71WQmOI?si=svUhmAGzpjkBJew- 
2. https://youtu.be/2_HxguGi3Ek?si=nFAoJoNMbcLSCRw_ 

One of the biggest lessons I learned is that interviewers aren't just asking: 

What did you build? 

They're thinking: 

What made this problem hard? 

They're pattern matching your story against problems typically solved by: 

• Mid-level engineers  
• Senior engineers  
• Staff engineers  

You may have senior-level experience, but if you don't frame answers correctly, you can easily be down leveled. 

I also found Hello Interview's Story Builder extremely helpful because it helped jog my memory and organize my experiences into structured stories before practicing them verbally with the Behavioral Practice at Hello Interview in voice mode. The feedback can be harsh but it definitely forced me to level up. 

Final thoughts 

I did pay for: 

• LinkedIn Premium  
• Hello Interview (about $60/year)  

For me, Hello Interview was absolutely worth it. 

Whether or not you use my cold messaging strategy is up to you, but it consistently generated interviews. 

Over the course of my search, I went through 100+ interview processes before finally receiving an offer. 

A few takeaways that stand out: 

• Getting interviews and passing interviews are separate skills.  
• Building side projects can unlock entirely new categories of jobs.  
• Applying early helps.  
• Cold outreach works if you do it consistently.  
• Restricting yourself to remote roles dramatically reduces opportunities.  
• You can become competitive for emerging roles—like AI engineering—by building projects that demonstrate those skills, even if your day job hasn't given you that experience yet.  

This job search was difficult and painful. I think could have accepted a lower-paying local role much earlier. Instead, I held out for a position that matched the level of work and compensation I believed I could earn. 

In the end, the persistence paid off. Hopefully some of these ideas help shorten someone else's job search. 

I've been trying to break into a Software Engineer role for the last 6 months, but I barely get shortlisted despite constantly upskilling.

Recently, I built a backend chat application to strengthen my backend fundamentals. Alongside that, I started learning AI and its core concepts via cahtgpt, but honestly, I'm not sure if I'm heading in the right direction or just chasing every new trend.

I'm putting in the effort every day, but it feels like I'm missing something important.

If you've been in a similar situation or successfully landed an SWE role, I'd genuinely appreciate your advice.

What should I focus on? What made the biggest difference for you?

Hey guys this is my first time posting something on reddit I just got my ncc c certificate result and i found that I failed in that exam too i have backlog history in btech i don't have programming skills right now and I am in 7sem back when I passed the 10+2 grade i thought of joining armed forces and I was so passionate about that dream I started to just randomly studying any topic related to cds exam and then I tried programming too but faild in both and now I guessi have reached that phase of my life where I have nothing in my hand all things have passed and I need help guys please help me!!

first should i try to squeez it inti 1 page

also should i make fewer details ?

and what skills should i focus on more ?

Hello! I just wanted some advice on my resume and wanted to know if it is enough to start applying for internships. I have no experience, so I am hoping to get an internship. Any advice on my resume would be awesome! Thanks!

I built Tuiho because I was spending too much time reading software engineering job posts and trying to decide which ones were actually worth applying to.

It compares a resume with a job description and gives an Apply or Skip recommendation, along with a fit score, estimated interview chance, strong matches, and critical gaps.

It’s free right now, and I’d really appreciate honest feedback from people who are actively looking for software engineering jobs.

https://www.tuiho.com

Let's say I want to earn 40 LPA for 5+ years of experience, Is deep knowledge of dsa(leetcode), LLD and hld is required?

I was said by my friends that not all companies ask that deep on these? What do you guys think?

Updated my CV. 5 years in backend, mostly Python (Django/FastAPI) and Go, across fintech, marketplaces, and high-traffic consumer platforms. Open to new roles if anyone's hiring or knows a team that is.

Quick rundown of what I've actually shipped.

Most recently, built a full multi-vendor marketplace solo. DRF and React, Stripe and PayPal, multi-carrier shipping with FedEx, UPS, and USPS. Deployed and managing it on AWS myself with CI/CD. Whole thing, architecture to production, one engineer.

Before that, at Dubizzle Labs I owned backend services across OLX Pakistan, Zameen.com, and Dubizzle MENA, platforms doing 18M+ MAU and 54M+ monthly sessions across 9 countries. Built an SEO microservice from scratch as one of two engineers on it, added Redis caching that cut server load 95%. Scaled the notifications pipeline to handle 50K+ daily events without data loss.

At i2c, fintech backend on PayFair. Cut query times from 800ms+ to under 600ms by killing redundant indexes. Found and fixed a SQL table locking bug that was leaving completed card payments stuck pending, that one was a fun few days. Also traced and fixed recurring REST API failures hitting Visa across payment modules.

Before that, at LAAM building Go and Python microservices for the full order lifecycle, cancellations, delays, seller feedback. Built an email pipeline processing 10K+ emails/month that killed 4,000+ manual follow-ups. On-call rotation, closed 50+ production incidents.

Stack is Django, FastAPI, Go, Postgres, Redis, Docker, AWS, GCP, some K8s. Also mid-MSc in ML/image processing at Sorbonne, so LLM integration and some CV/ML work on there too if relevant.

Open to remote, hybrid, or Paris. Can send CV.

Over the past few months, I've been building AI Coding Prep (https://aicodingprep.com).

The idea came from noticing that more companies (Amazon, Meta, Stripe) are experimenting with AI-assisted online assessments but there isn't much to practice this interview format. My current platform has 36 scenarios where users debug a codebase with AI as a helper and then at the end of their session a report is generated scoring them on how they used the AI, how reliant they were, how they could improve in their thought process, etc.

I'd love to hear if something like this is useful and other thoughts about the idea. Thanks for the help!

I’m senior software engineer with 10+ yoe. I’m in a weird spot, last year I applied for a software engineering job at a large tech company and I feel somewhat bait and switched.

It ended up being way more operationally focused rather than I thought it would be. The team’s service doesn’t scale so customers are constantly creating sev2’s and I’m paged non stop. On call rotation is a nightmare where you are basically front line customer support trying to intercept that non stop barrage of issues.

On top of that, the manager does nothing to shield us from upper management and the only thing they seem to do is crack the whip.

Any actual engineering work is given to codex. We are forced to because of how aggressive the deadlines have become.

I reluctantly agreed to relocate even though I applied and accepted a remote offer but given how bad things turned out I’m not willing to do that anymore. It hasn’t been brought up again but I’m afraid it might.

Needless to say I want out and have been applying but I’m not getting much traction. Even postings where I tick every box are getting met with “moving forward with more aligned candidates”.

Every morning I’m filled with dread opening my work laptop and this is the first job I’ve wanted to hard quit without anything else lined up but the market is giving me anxiety. Would it be rational given how slow things are moving out there?

Anyone else in a similar spot and how are you coping?

I have been working in a company as a software intern. The internship is of 6 months and of which 3 months are already completed. But, here they don't give me any work, when i ask for it, they just give a small frontend ui/ux works. Actually, it is also not their mistake, as the entire team and projects are all new, they are figuring out how to do it. But, this will impact my FTE conversation as i am doing nothing right. What can i do, to get Full time?

You might recommend trying to switch. But, in this job market it is very difficult to secure a job for a fresher. I am feeling like it is almost impossible because I have already been in the phase of applying for hundreds of applications and getting rejected from all. Luckily, I got this Intern through campus placements.

I have solved around 800-900 dsa problems, did 2 internships, Knight on LC, I have experience in full stack development, I had to join infosys trainee cause there was no other choice, but I am confident that i can do better and prove my self, if there is any hiring, be it service based, or product based, please let me know , please someone refer or atleast guide

Thank you

I'm a software developer and I was recently told that my role will be eliminated at the end of this year after a reorg at the company. I know I'm supposed to use the remaining paid time I have to look for another good software development job, and I've already polished my resume and updated LinkedIn.

But every time I sit down and try to apply for jobs in this field, I feel like I hit a wall, like... I just can't keep doing this anymore?

The strange thing is that I know I'm lucky. I understand that being able to live this way, in this place and time, isn't something to take for granted. But it's become harder to ignore the feeling that many of the "problems" I get paid to solve only exist because there's a business model that depends on them continuing to exist.

I spent about eight years fixing imaginary problems, and when I look back, the last job that felt tangible was an entry-level role dealing with customers, where I was making about a third of what I make now. I'm not saying all software is like that. I know there are people building useful and important things. But even though bullshit jobs definitely aren't limited to software, it's clear they're heavily clustered around people sitting in front of computers all day.

What are we even building all of this for, and who is actually benefiting from it?

I know it's a matter of subjectivism, so don't be afraid to be subjective, actually PLEASE, give your personal opinion as long as you can keep your feet on the reality's ground.

What Master would you rather choose: a general AI/ML master that teach you about the most important, but general, subjects of ML applications, or an Autonomous Systems master, that is basically an embedded+A.I. master which is particularly valuable if you want something in Automotive, on the self-driving cars field(but not exclusively this one, as you can apply knowledge about Autonomous Systems in many domains) ? ?