Hello! My name is Arjan Jassal.
I’m a frontend developer based in London. I build (and sometimes design) simple, fast, useful, websites and apps.
An app to keep track of feedback, schedule 1-on-1 meetings, and keep your team happy.
A flexible camera component for React DOM. Take photos using the latest WebRTC API's.
- Media Stream
- Styled Components
Browse Reddit without visual noise. Built with React + Flux.
- Reddit API
Sr. Frontend Engineer
- Shipped themeable dashboard built with React, TypeScript and Styled Components
- Used gRPC for client-server communication and type safe APIs
- Used Node.js to build a Slack a integration for real-time alerts
- Unit and integration testing with Jest
- Collaborating with amazing backend engineers and product designers
I joined Taloflow's tight-knit team as their first frontend engineer. Part of my role was to decide what tech to use, how to structure things, and to get an MVP up and running a.s.a.p. Like most startups, trade-offs and prioritization were key when it came to shipping on time.
With that in mind, I choose to use tech I was very familiar with like React, Styled Components, and Firebase, and some tech I'd never used but wanted to, like TypeScript. This way I could still progress quickly and keep things interesting by learning something new.
Sr. Frontend Engineer, Team Lead
- Architected and shipped modular white-labeled UI (with React, Redux) which other developers used to quickly build new product workflows.
- Designed and built UIs used by Canada's largest banks and credit unions
- Worked with backend engineers to design REST APIs
- Mentored junior team members through code reviews
- Interviewed Frontend Engineers and refined interview process
- Spoke about how we use React at Vancouver Startup Week
I joined Grow's team of 4 engineers while the company was still focused on a direct-to-consumer model. At the time, Grow's competition was banks and credit unions across Canada. Shortly after joining, Grow pivoted to a SaaS model, and now their competition were customers. This brought a slew of challenges to the engineering team, like making our existing product white-labeled and modular so that it could be highly scalable across all customers. As you could imagine, a lot of discussions around what to refactor to fit this new business model were had, along with what to rewrite from a blank slate and the pros and cons of each option.
Grow also didn't have any product designers, so myself and another frontend engineer designed all products and old marketing websites. This was a fun but challenging responsibilty because we had to thinking about the UX, UI, as well as code, so there was a lot of context switching, but also a lot of valuable experience wearing those different hats.
- Used Jekyll to build static websites
- Promoted brand through CodePen experiments and articles
- Someone showed me how to use Git properly
- Worked remotely and communicated through Slack
Ettrics was my first real taste of being a frontend developer on a team with backend engineers and product designers. It was at Ettrics that I started as Web Designer and ended as a Frontend Developer. The key moment during this evolution was when I picked up Angular.js and started to intract with RESTful APIs that the backend devs were building. This way of working on the frontend was totally different than the static websites I was used to building, and I loved it.
- Created new themes for in-house CMS to replace old outdated themes
- Taught co-workers modern tools (at the time) like Gulp, SCSS, etc...
PerfectMind offered me my first real job in the industry as a Web Designer, but it wasn't quite what I had imagined. I was part of a small web team that pumped out websites from a few depressing templates that looked like they were designed in 1999. Along with outdated designs, the tech being used to build the websites was just as old. To sum it up, it was just plain old HTML and CSS.