Fernando is a Front-End Web Developer currently based in the miracle city of Santo Domingo. He has been working in the Web industry for 5 years now, mostly in agencies but he has also done freelance gigs. He is currently looking for a role that really encourages him to think outside the box and to use his best skill: his never-ending curiosity. He tends to do his best work when he is around a team with strong communication and pushes him to find creative solutions to the problems. He prefers to work remotely but relocation could be an option if it makes sense.
Stack:
Responsibilities:
by brokers to serve thousands of clients alongside a cross-disciplinary
team.
shared modules.
Stack:
Responsibilities:
web apps using the Jamstack architecture for renowned companies.
Stack:
Responsibilities:
Stack:
Responsibilities:
Description: The Accounts project was envisioned to replace several parts of the legacy system which was very convoluted and hard to use with a modern and fast app that streamlines the account management workflow while also being able to connect with other tools & services.
The Accounts app has been instrumental for hundreds of brokers to manage thousands of clients through the whole acquisition process. Brokers can now manage new accounts and their coverage opportunities in a more intuitive interface.
Role: Our small team of engineers has full ownership of the project across the whole stack from backend to frontend. Since the project first started, I’ve been tasked with building the frontend interfaces in conjunction with building tooling and abstractions for the data layer and the shared UI library. More recently we’ve been porting legacy features from the old service into this new one, removing technical debt.
Technologies used: The app is built with Next.js & Typescript and leverages Next.js’ built-in serverless functions as a BFF layer to interface with a Nest backend. We use XState in some workflows for managing state and we’ve built extensive tooling around SWR for data fetching from multiple services. Tests are done with React Testing Library.
Description: Website redesign & rearchitecture of the member’s dashboard where users can access exclusive information and documentation, as well as a public microsite with general info.
Role: I was part of a small team as a Front-End Developer and was tasked with several aspects of the project. I ended up implementing a bunch of layouts and components that were reused across the whole project, some with design variations.
Technologies used: Content was managed and served through Contentful via an Apollo client to a Next.js + Typescript frontend app. Styles were done with Tailwind.CSS.
Description: Briefly contributed to the ongoing development of an internal researcher’s dashboard project.
Role: I was tasked with implementing a table list view of survey contacts that had been contacted for previous studies and assigning them to either a blacklist or a whitelist.
Technologies used: A pure React and Redux app using Typescript with Sass styling and and as the design system.
Description: My first project at Bejamas, I got to work on a mobile PWA with a strong focus on i18n and custom native-like animations/transitions. The app was intended for guests to have easy access to key information about the hotel they were staying in. Hotel rooms would be equipped with tablets preloaded with the app.
Role: As a Front-End Developer, I contributed to a big chunk of the project, implemented the information screen where most of the user interaction happened and where it was most critical to have performant animations.
Technologies used: Next.js PWA in tandem with Typescript, with Storyblok.js for multi-language content management. Emotion is used for authoring styles, alongside Tailwind.css and react-spring for custom animations/transitions.