A ping and notification bounce from Slack. A heated discussions in the backend channel about efficiently resolving production errors. Static typing? More integrations test? Ideas being tossed around. All in a day’s work at Credy. So here is my story.
Journey Before Credy
My previous gig Enguru – an English learning application which helped users learn the language through carefully designed adaptive games, had been the steepest learning curve in my career so far.
Despite being a niche market, with several other competitors, the app had taken off pretty well with over 2 million users. With over 20K daily active users, we had our hands full with implementing new features, while handling the scaling issues and other woes that came along with it.
Challenges never ceased to sprout at Enguru, all the way from internal dashboards for Corporate Analytics, EnguruTalk – an online tutoring platform, right down to Chatbots that interacted with users; keeping me always on my feet.
Thoughts of changing
After a while, when things started to settle down at Enguru, and every day seemed to be another Déja Vú (refer Urban Dictionary), I decided that it was time to seek out another adventure, and a different scene.
How did Credy happen?
I had applied to two dozen other Fintech and SaaS startups over few days on Angellist. After weeks of gruelling interviews (several good, some bad and few really horrific ones), I came across Credy – an online lending startup that was still less than a year old then, Y Combinator-backed, and working on automating almost the entire banking process. Sweet!… I knocked.
After several rounds of really long interviews, spread over a couple of weeks, I strolled into the office, on a hot August afternoon, in khaki shorts and a worn-out t-shirt, and signed my contract. I was officially, a part of the team.
Me as a part of Credy
“Welcome to Credy! We are happy to have you as a part of our team”, said Pratish.
First day on the job, I dove right into understanding the levers and gears of Credy, or more specifically – the backend service. Though it reflected a custom banking service, I was fascinated by the automation that was built/ being built into it, all the way from processing a loan application, to transferring money between virtual bank accounts mapped to individual customers.
Challenges at Credy
Over six months aboard the ship, we surge forward through harsh waters, with no sign of slowing down. We quarrel, criticise, build and improve. Given a free reign to work on side projects within the company, I treated myself to a slice of everything – from tinkering with the frontend web-app, designing posters for sales, all the way to securing the infrastructure for the servers.
The main projects were never a drag either, with all sorts of new challenges that came along.
I found myself building tools to help our men on the field, algorithms to manage auto debits from user accounts, managing documents uploaded by users, helping out with integrating with lending partners, and many more.
Since GOT is a pretty big deal at Credy: When you play the game of clones, you merge or you reset – hard.
What’s a usual day at work at Credy?
Every morning, I open up the Google Sheet with the list of tasks assigned to everyone (Yes, Sheets seem to beat every other Project management tool out here!), only to be greeted by a long pipeline of tasks, stretching towards the end of May.
Things to improve, new technologies to try out, more code to refactor, more users to handle, servers to scale, security to patch up and plenty of data to crunch. And I know, “Today is gonna be a good day!”