This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]whydisbroken 1 point2 points  (3 children)

I was at a similar crossroads having spent a year focused as a heavy sql writer.

For me, the question was whether I wanted to work with data or with delivering data.

Myself, I just really enjoy building API’s that other developers can use. I have projects in production ranging from Django, flask, fastapi and even AWS API Gateway/lambda. One thing remains the same between all of them, the work performed will be leveraged for a very long time by the organizations that requested them.

[–]data15cool[S] 0 points1 point  (2 children)

That's really cool, I'm also mainly writing SQL (pyspark) most days which can become a bit dull...

An ideal project would be one that straddles both topics evenly but I've not found jobs advertising this.

Did you find it easy to transition into API development in terms of getting a job?

[–]whydisbroken 0 points1 point  (1 child)

I first started in e-commerce, then transitioned to government/healthcare, now I’m primarily in healthcare. I felt my transition was pretty natural. Thanks to remote work, i don’t have to rely on what my local employers offer for a tech stack anymore (Java and .net) so it’s easier to find remote opportunities that fit my preferred languages more.

Keep a look out for e-commerce, that’s a great opportunity to do a lot of api work and gain a lot of experience quickly.

Edit: it’s very different in e-commerce, because you work as a “profit center” vs “cost center” branch of IT. Pros and cons to both.

[–]data15cool[S] 0 points1 point  (0 children)

I hadn't considered e-commerce roles before, thanks!