First 30 Days at Eventcore

New city. New office. New team. New desk.
I nodded through most of it. I also Googled through most of it.

Week one hit differently than I expected. There's a particular kind of sensory overload that comes with starting a role like this. New tools, new processes, new faces, new acronyms. Week one was less about performing and more about absorbing. Every meeting was a data point. Every conversation was a clue. I was building a mental map of how things worked, who cared about what, and where the interesting problems lived.

By week two, I stopped watching and started contributing. The frameworks I'd picked up at university started showing up in real conversations. I was asking questions, not because I was lost, but because I genuinely wanted to understand. There's a difference between those two things. One comes from feeling behind. The other comes from actually wanting to understand how something works. It took me about ten days to realise I'd crossed from one to the other.

Imposter syndrome doesn't disappear the moment you start adding value. But it does get quieter. For me it started fading when I stopped waiting to feel ready and just did things that made me uncomfortable. I kept a daily log of my tasks, nothing fancy, just a record of what I was doing and why. It sounds small but seeing your own progress written down does something to your confidence. Setting clear goals with my supervisors helped too. Suddenly there was a target, and hitting it meant something real.

My role as a Digital Analyst doesn't come with a tightly scripted job description. Nobody handed me a task list. What I got instead was autonomy. The expectation was that I'd find where I could add value and go do it.

At first that felt like standing in a room with no furniture. What do I do? How can I help? I didn't want to overstep but I also didn't want to disappear. It was exactly what I signed up for, and it was terrifying. The thing about having no roadmap is that there's no one else to point at when something goes wrong. That realization hits differently when you're new.

So I made my own structure. I started mapping out where the gaps were, asking questions, and slowly trusting my own judgment. It helped that my colleagues and managers weren't just watching from a distance. They were in it with me, which made the autonomy feel less like being thrown in the deep end and more like being trusted to figure it out.

Week three was where that became real. I started working on content strategy and social media, thinking about what the brand needed to say, to whom, and why. I also connected with the reporting team to find where I could help technically. Turns out, there were a few spots.

By week four, I was building. I'm developing an internal tool to simplify a process that had been eating up time. It's gone through a few rounds of feedback and is still being refined. Turns out they let interns do real work here.

The culture around that process stood out to me. Standards are high, feedback is fast, and people care about doing things properly. I was treated as a contributor, someone whose work mattered and was worth improving. When you feel seen, heard and taken care of, growth isn't something you have to chase. It just happens.

By the end of week four, I started to feel like part of the team. Not because I was included in meetings, but because I'd built something with people and cared about how it landed.

Yes, The Coffee Is Actually That Good

 On a completely separate note, the coffee deserves its own mention. Strong, consistent, and dangerously easy to refill. I'd like to formally credit it for at least part of my output. 

Thirty days in, I'm more confident, more capable, and significantly more caffeinated. I came in trying to look like I knew what was going on. Somewhere along the way, I actually started to.