Auto Apply to hundreds of jobs in a few hours

Español

日本語

Back end developer skills: what to learn first, and what can wait

Frameworks come and go, but a slow query is a slow query in every language. Learn SQL, HTTP and one server framework properly before you touch Kubernetes or event sourcing. The fancy architecture work pays off only after that.

177 open jobs

Step one

Gets you the interview

SQL beyond SELECT starYou should be able to write a join across a few tables, group and filter with HAVING, and read an EXPLAIN plan in Postgres or MySQL. Screeners notice when you've never looked at the SQL your ORM generates.

One framework, known deeplyPick Spring Boot, Django, Express with TypeScript, or ASP.NET Core and learn how it handles routing, middleware, validation and database sessions. Hiring managers would rather see real depth in one stack than a résumé listing five you've barely opened.

REST API designKnow which status code a failed validation gets, why a POST that creates an order should be safe to retry, and how to page through a long list without offsets that drift. A clean OpenAPI spec in your portfolio repo helps too.

Git and a working CI pipelineSmall commits, a branch that rebases cleanly, and a GitHub Actions workflow that runs your tests on every push. It's basic, and reviewers still check it first.

Step two

Gets you the offer

Indexes and query tuningThe system design round often turns into a question about why an endpoint got slow. Explaining a composite index, why column order matters, and how you'd spot the ORM firing one query per row inside a loop is what moves you from maybe to yes.

Caching with RedisAnyone can put a cache in front of a database. The offer comes from explaining what happens when the data changes: cache invalidation, time-to-live choices, and what stops a flood of requests from all rebuilding the same expired key at once.

Auth done properlyHashing passwords with bcrypt or Argon, handling OAuth flows, and knowing what a JWT can and can't safely carry. Interviewers probe here because a mistake in auth is the kind that ends up in a breach notice.

Integration tests against a real databaseTests that spin up Postgres with Testcontainers catch the bugs mocks hide, like a unique constraint or a timezone that the ORM quietly converts. Knowing which tests to skip convinces people too.

Step three

Gets you promoted

Queues and async workSenior back end developers know when a job belongs on Kafka, RabbitMQ or SQS instead of inside a request. They also plan for the message that arrives twice or out of order, which is where most of the real bugs live.

Zero-downtime schema migrationsAdding a column is easy. Renaming one on a busy table without locking it means expanding first, backfilling in batches, switching reads, then dropping the old column in a later release. People who can plan that get trusted with the scary changes.

Observability you can act onStructured logs, metrics in Prometheus or Datadog, and traces through OpenTelemetry that follow one request across services. When you can find the cause of an incident from a trace instead of a guess, you become the person leadership wants in the room.

Writing design docsThe promotion case usually rests on a system you designed, not the tickets you closed. A short doc that lays out the options, the tradeoffs and why you rejected the obvious answer is how that design gets approved and remembered.

Certificates worth your time

Certificate	Best for	Effort	Worth it?
AWS Certified Developer - Associate	Developers on teams that run on AWS and use Lambda, DynamoDB, SQS and IAM daily	a few weekends of study plus hands-on practice	Worth it if your target companies run on AWS. It won't replace a project, but it helps a résumé get past a filter that asks for cloud experience.
Microsoft Certified: Azure Developer Associate	Developers working in C# and ASP.NET Core at companies built on Azure	a few weekends, more if you haven't used Azure before	Useful in Microsoft-heavy shops, especially consulting firms that need certified staff on client bids. Skip it if you're not aiming at the .NET world.
Certified Kubernetes Application Developer (CKAD)	Developers who deploy their own services to Kubernetes clusters	several weeks of hands-on practice, since the exam is timed tasks in a live terminal	Respected because you can't pass it by memorizing answers. Save it for after you've shipped a few services, since it's a promotion-tier skill, not an interview one.

Exam formats, prices and renewal rules change, so check the provider's own certification page before you book.

Put it on your résumé like this

Weak

Worked on backend APIs and improved database performance.

Strong

Cut p95 latency on the order history API from 1.8s to 240ms by adding a composite index and a Redis cache, handling 40k requests per hour at peak.

Questions people ask

Which back end language should I learn first?

Pick the one most local postings ask for, which is usually Java, Python, C# or TypeScript on Node. Go is a strong choice if you're aiming at infrastructure-heavy teams. The language matters less than you'd think, because SQL, HTTP and caching carry over to all of them.

Do I need to know Kubernetes to get hired?

Not for a first role. Knowing how to write a Dockerfile and run your app with Docker Compose is enough to start. Kubernetes shows up more in senior postings, and most teams have a platform group that owns the cluster.

Should I learn GraphQL or stick with REST?

Learn REST first, since nearly every back end touches it. GraphQL is worth picking up once you're on a team that uses it, and you'll get far more from learning it against a real schema than from a tutorial.

How much front end do back end developers need?

Enough to read the network tab in browser dev tools and understand what the client sends you. You don't need to write React, but you should know why the mobile team is annoyed when your API changes a field name without warning.

Got step one? Start applying. HeroApply matches you to roles that fit.

Start your trial