Mauricio G.

giving support / adding new features to consumer platform and internal platform for agents Tasks and commitments: * full-stack software development focused on the front-end side * development of features and improvements, at least 70% code coverage for unit testing. * formal documentation in confluence pages * updating schemas for formik, updating typescript interfaces * using jsonet for configuration in order to trigger pdf when we reach the effective dates * bi-weekly status reporting for sprints reviews * github actions (for CI) * Jira (for project management) * for development testing, we have different - local - ephemeral (here we should test our changes before merge our PR's) - staging - UAT (this is the last stage before production envs, we usually have an scheduled open window we all the team coordinate, integrate our changes, and run common scenarios) * scrum ceremonies (we have daily, sprint reviews, retrospectives, planning, refinements, post-mortem) - we have an estimation for all the tickets, where we have: - 1 point is generally considered around 1-2 hour task, - 2 points - half a day - day, - 3 points, 1-2 days - 5 points - up to one week - 8 points - 1 and a half weeks up to a sprint - 13 points - would be a great candidate for a breakdown tech stack: react v16.8, react router v6, tailwindcss, storybook, github, github actions, terminal commands,

development for human resources app, focused on the payroll module. * authentication and authorization implementation relying on oAuth, using google and facebook strategies. Using jwt for getting grants for logged user * using figma for getting mock-up and build new react screens based on this prototype, really focused on details * big fixing from previous sprint * using ant design framework for building function react components * scrum ceremonies and rituals * Reaching out to other team for clarification on some tickets, so autonomy it's quite important in sprint