The one about my new job

Search for a command to run...

No comments yet. Be the first to comment.
A while ago I wrote a post about automatically adding my latest blog posts to my GitHub profile. The idea was simple: a GitHub Action would query Hashnode's public GraphQL API, grab my most recent pos

In the previous post I talked about how to override htmx's default behavior on failure. The proposed solution relied on events to handle any server-side error directly from the view. Although I recomm

The project that I have been working on for the past few months is coming to an end. A few days ago, we even presented a demo of the new UI to the stakeholders, who have already started using it in pr

In a previous post I talked about the internal design system I have been working on recently, consisting of server-rendered UI components, using Ruby and ERB templates. Most of these components are si

In a previous post I mentioned I had been working on replicating some functionality for collecting beneficiaries data in an old SPA. The code in that application was quite legacy and highly coupled to

David Montesdeoca
43 posts
Passionate software engineer and continuous learner
After I left Domestika last year, I decided to take some time off. After a few weeks I started taking lots of courses mainly related to clean code, DDD, software architecture, TypeScript and other similar stuff.
I spent a lot of time putting those learnings into practice completing challenges from real companies that I found on the internet, so until March 2024 I didn't start looking for a new job.
As you can imagine, one of the first questions every HR person always asked me was what I had been doing all that time.
In the past, I always found a new job within a month, so I hoped it would be the same this time. Little did I know how hard is to find a good job these days.
Usually I only apply to companies that I'm insterested in and for roles where I consider I could be a good fit. Even so, I have failed a lot during these last few months. I made some mistakes but I definitely think I am better prepared to get a good job than I was before.
In any case, I too think that some of those mistakes are the result of hiring and interviewing processes that I consider to be broken. But that is an story for another time.
Dealing with failure is not an easy task. As time went on and failures piled up, at some point I even doubted whether I would ever be able to get a new job. If you are in the exact same situation, my advice is not to give up. Look at what you can do better and keep trying.
I'm not going to lie to you. You probably need to adjust your expectations as well. And that's exactly what I did.
After three hard months, I am really excited to tell you that I finally landed a new job at SNGULAR last month.
Working for a consulting firm was not in my plans, but I liked the proposal of SNGULAR to work exclusively for an American fintech company developing their own product. Among other benefits, I will have the possibility to continue working remotely.
During this first month and as part of my onboarding, I have been teaching Ruby to some colleagues in the company. Next month I will start the onboarding with the fintech company and, at some point, I would like to share some of my experiences working for an American company.
Thank you for reading and see you in the next one!