It's been a pretty long time since I've updated this, but to me that's better for you, the reader, because I can give you so much more information at a time about my experiences.
It's been over a month since I started at Treevah, a startup focused on providing job-seekers with an organizational system to make the application process easier, and I think I've seen big parts of how the workflow at startups works.
Firstly, the pace should be discussed. It's a job that really keeps you moving throughout the day and the week, but none of that work has really felt unsatisfactory. Tiring, yes, but not useless. The amount of work that has to be put in by all team members to get an alpha product, let alone a beta or prod scale, speaks to how much workload you get at a startup.
It's not something that I've hated; in fact, it's been some of the most fulfilling work I've done. I've gone from public speaking clubs to hackathons to semester-long projects, and the opportunities I've had this summer, progressing my skills in web development, are second to none.
I want to speak to some of the frustrations that have come with the job as well. A lot of the bugs I've worked on are bugs that don't exist because of any singular failure in logic. More often, they exist because of things like multiple definitions of the same CSS rule, or defining elements outside of the div that give them certain properties.
Some of these bugs have taken me multiple weeks to track down and fix, but that's what makes it so fulfilling to me. Working at a startup, where the pace is constant and the bugs even more so, has taught me that there'
s always a solution to be found, but it's never the first thing you think of.
Top comments (0)