A job posting, careers page and internet research can only go so far in providing a preview of what it would be like for a prospective employee to join an organization. So it’s not uncommon that initial enthusiasm to subside during the hiring process.
People might not click. Challenges that might come off as enticing on paper might lose their sparkle when expounded upon in conversation. There could be a misalignment in philosophies between interviewee and interviewer.
The fit might just not be there.
And in the world of software engineers, for whom the hiring process is a common experience (the U.S. Bureau of Labor Statistics projects a 26 percent growth in the hiring of software engineers between 2021 and 2031), this scenario is likely familiar.
Fortunately, for Brian Cameros, a software engineering opening at Grammarly that he said “checked all my boxes” didn’t just remain an aspiration — but materialized into the hiring experience he had hoped for.
Cameros explained that throughout the virtual interview he was able to get authentically acquainted with his future engineering counterparts. “It felt like I was genuinely able to get to know the team — and vice versa.”
Ultimately, Cameros joined the writing and grammar support tool company midway through 2022. Continue on to learn more about his experience, along with what interested talent should keep in mind if they, too, want to join Grammarly.
What initially drew you to apply for an engineering role at your current employer?
When searching for a new opportunity, it was important to me that the company was clearly succeeding and growing like a weed. I also found myself attracted to companies with a strong machine learning or natural language processing focus. Previously, I’d worked in an NLP group at Amazon and found the field full of interesting concepts.
When I saw the job posting at Grammarly and began learning more about the company, I realized it checked all my boxes. Meeting the team and hearing about the innovation happening with the ML and NLP teams, along with continued business strength, I was excited to interview.
What was the hiring process like, and how was it different from other experiences you’ve had?
With Grammarly’s remote-first hybrid working model, my interview process was virtual. Throughout the process, it felt like I was genuinely able to get to know the team — and vice versa. I had casual “coffee chats” with engineers as if we were actually going out to get a coffee, and I was able to share with leaders about my past experiences and how what I’d learned at each company helped me progress in my career.
Another interview that stood out to me during the hiring process was the system design question. During this interview, we touched on core concepts in distributed data, which I saw as a good sign for a team I considered joining.
During the system design interview, we touched on core concepts in distributed data, which I saw as a good sign for a team I considered joining.”
What advice would you give to fellow engineers thinking about applying for one of your team's open roles?
For engineers interested in the Grammarly for Developers team, I’d recommend they familiarize themselves with the various APIs and ecosystems that companies have built for developers. Our team is in a unique position where our customers are actually other engineers, so it’s helpful to understand the common issues and patterns that recur.