#Looking for mid level SWE backend or backend data positions

30 messages · Page 1 of 1 (latest)

queen drift
#

My ideal position would be in the following priority -> only backend > backend for data > data engineering. Targeting mid level and SSE if I'm a bit ambitious/if possible.

Backend - I would like positions which focus on building services for the end user. Ideally this would be B2C but I'm ok with B2B as well.

Backend for data - I would like these positions to focus on creating libraries and frameworks which can be used by other teams in the company. My end user here would most probably be other teams inside the same company.

Data engineering - I would like to avoid roles which do ETL/SQL only work. I would rather build pipelines connecting different tools and streamline data for consumption. I do not want to mung data. I'd rather focus on challenges involved in getting/storing data as necessary.

Here's is my updated resume. I'm open to any feedback.

  1. Is it realistic to be considered for SWE backend roles given my profile?
  2. What kind of positions do you think I'd be best suited for given my experience and what can I do to improve myself to showcase I'm a good candidate for SWE backend roles?
  3. Any other feedback?
resume_descriptive-1.png
#

I'm a bit unsure about the format, whether the one above is good or this current one is good. The content is almost the same, format varies very slightly where I'm more descriptive above but here it's more like direct bullet points. Please let me know. This image is not the updated resume content wise as shared above.

resume_bulleted-1.png
midnight shale
#

i like 2nd resume better personally

#

“Deceloped caching mechanisms for multiple APIs using Redis . This reduced the data, reducing data warehouse load by 60%.

#

same thing with 2nd and 3rd bullet of top experience

queen drift
midnight shale
#

resume looks less cramped in the 2nd one

#

1st one the project names aren’t necessary IMO and then u have like 2nd level bullets

#

and just a bit too cramped looking

queen drift
queen drift
queen drift
midnight shale
#

ur still using “This does XYZ”, just say what u did

#

be more concise

#

Big Pharma :

Developed web service using … reducing turnaround time from 5 days to 1.

#

Developed SparkSQL… improving data quality by 5x

#

would drop last sentence in 1st bullet of 2nd position

queen drift
midnight shale
#

1st bullet is really long and idk if all that specific information is needed imo

#

Designed and implemented API gateway to aggregate APIs from microservices using OpenAPI 3.0

queen drift
#

Is there a better way to word that? It technically doesn't have an impact... we had to implement that service since we're moving away from a monolith

midnight shale
queen drift
#

Got it thanks.

queen drift
midnight shale
#

“Developed a module concerting ETL jobs…” -> this bullet has a period instead of a comma

midnight shale
#

the last sentence of the 1st bullet aka “This library handles data sources…”

queen drift
#

Ah that. Okie. My bad, second position I was looking top down... 😅

queen drift
weak karma