r/Backend • • 6h ago

AI agents sound exciting, but would you actually trust one with your daily work? Spoiler

0 Upvotes

I've been exploring AI agents lately, and the idea is pretty interesting.

Instead of just asking AI questions and getting answers, you can give an AI agent a task and let it work through multiple steps. For example, researching a topic, organizing information, managing emails, or helping with repetitive work.

It sounds like a huge time-saver, especially for students, developers, and people working in different industries.

But I also wonder how reliable these agents are when things don't go as planned.

Imagine giving an AI agent a task and coming back an hour later. Would you trust the result without checking everything?

A few things I'm curious about:

  1. Have you actually used an AI agent for something useful in your daily life or work?
  2. What task would you happily let an AI agent handle for you?
  3. What's the biggest problem you've faced while using AI agents?
  4. Do you think AI agents will become a normal part of everyday work in the next few years?

I'd love to hear real experiences, not just what these tools promise to do.


r/Backend • • 10h ago

Go Lang or any other backend tech(expect java)

6 Upvotes

Hi everyone, I'm a Frontend Developer, and I'm noticing that there aren't many frontend-only opportunities in the market. Most companies seem to be looking for Full Stack Developers.

I'm planning to expand my skill set beyond frontend development. Which backend language would you recommend learning apart from Java? I'm considering Go or other languages.

Would love to hear your suggestions based on the current job market and future opportunities.


r/Backend • • 9h ago

Que se necesita para ser analista de datos Junior?

2 Upvotes

Tengo una oferta de analista de datos Junior es mañana la entrevista, y no sé si tengo lo necesario, se sql lo básico, se inglés y otros lenguaje pero ninguno es python, que necesito practicar para ir bien a la entrevista?


r/Backend • • 6h ago

Looking for a dependable email verification API that can handle a high volume of requests

4 Upvotes

We use SES for transactional emails, but after launching a new partnership, we're now seeing around 40k new signups daily across several apps. Our bounce rate is currently about 4.6%.

I'd like to check email addresses before sending out the welcome email. The service needs to handle that kind of volume and integrate with Lambda. What are you using for something like this?


r/Backend • • 18h ago

Looking for a Study Partner – .NET Developer

1 Upvotes

Hey everyone!
I’m a recent Computer Science graduate and a Junior .NET Developer. I’ve worked on several backend projects using C# and ASP.NET Core.
I’m looking for a study partner or a small group of people who are also into software development and want to keep learning and improving their skills.
We can study together, work on projects, discuss technical topics, share resources, and keep each other motivated and accountable.
I’m open to learning different things related to .NET, backend development, software engineering, or even exploring new technologies.
Ideally, I’d love to connect with 1–3 people who are serious about learning and growing together.
If you’re interested, feel free to comment or DM me. Let’s grow together


r/Backend • • 19h ago

How do you find good engineering problems to build projects around, especially for systems/backend roles?

14 Upvotes

I've been running into a bit of a creative block lately, and I'd genuinely appreciate some advice from people who review resumes or have experience hiring for backend and systems engineering roles.

I keep hearing people say that finding real-world problems to solve is easy. Just look around, identify something inefficient in your day-to-day life, and build a solution. But I've been struggling with this.

Almost every problem I've come up with already has an established solution, sometimes even an entire product built around it. I've spent the last week hunting for project ideas, and I keep running into the same wall.

For some context, I've primarily built projects as a hobby, focusing entirely on backend engineering without relying on AI APIs.

A couple of things I've built:

1. File Management System for Educational Enterprises

A tool designed to organize large amounts of educational material, particularly in environments where files are poorly named using generic identifiers like dates, subject codes, etc.

It parses documents, extracts relevant information, identifies document types, renames files accordingly, and provides features for modular organization and arrangement.

2. Repository Change Visualization Tool

A developer-focused tool that visualizes changes within a Git repository. This goes beyond conventional diffs by tracking changes to JSON variables, mapping classes, and providing a more structured understanding of how a codebase evolves.

Both projects were built using my own understanding of backend technologies. No AI APIs or external AI-powered services involved.

Now, I feel like it's time to move towards building projects that actually align with the domain I want to pursue after graduation.

I'm interested in backend engineering, systems engineering, distributed systems, and related fields. I haven't settled on a particular specialization yet.

Here's where my dilemma begins.

When hunting for projects, I find myself stuck between two approaches:

Approach 1: Build something that already exists, but engineer it myself**.**

For example, something like a data recovery system or a recovery tool verifier. These are problems that already have enterprise-level solutions, but building a prototype myself could involve interesting engineering challenges, concurrency, fault tolerance, recovery mechanisms, etc.

Another example could be a ledger system for tracking natural resources at a municipal/local government level.

I feel like I have 1000 more ideas which I feel like with a little bit of dedication I can do it right and impressive.

Approach 2: Find a problem that hasn't been properly solved yet.

Instead of recreating something that already exists, I could hunt for a relatively unexplored problem and build a solution around it, even if the engineering complexity is comparatively average. Again is this the necessity right now given the job market?

My question is: Which of these approaches actually carries more weight when you're evaluating a candidate's resume?

Would you rather see a student build a technically complex prototype of an existing enterprise solution, or a relatively unexplored solution to a problem that hasn't received much attention?

I'm also curious about something a senior once told me:

Why are we always chasing solutions for individual users when we could be building solutions for enterprises?

The idea was that instead of building another consumer-facing application, perhaps I should look at smaller, overlooked enterprise problems and build tools that solve them.

I found that perspective interesting, but I'm still trying to understand how to approach it.

One last thing: I'm currently studying at a college I'd consider well below the 2.5-tier category. I know that puts me at a disadvantage when applying for internships, so I want my projects to genuinely stand out and demonstrate engineering ability rather than just add another CRUD application to my resume.

I'd especially appreciate perspectives from people who have reviewed technical resumes, interviewed candidates, or work in backend/systems engineering.

TL;DR: I'm a student interested in backend, systems engineering and distributed systems, trying to build projects that genuinely strengthen my resume for internships.

I've built two backend-focused projects without AI APIs, but I'm struggling to find what to build next.

My dilemma is whether I should:

- Build technically complex prototypes of problems that already have established enterprise solutions.

- Hunt for relatively unexplored problems and build solutions that don't already exist, even if the technical complexity is lower.

- Focus on overlooked enterprise problems rather than consumer-facing applications.

As someone reviewing a resume, what would impress you more: engineering depth, originality of the problem, or the practical value of the solution?

Coming from a lower-tier college, I want my projects to compensate for the lack of institutional advantage and actually demonstrate that I can engineer systems.

I am really sorry for the extremely long rant and ofc generated ai content.