Working as a developer requires very specific qualifications—a set of norms, priorities, and even languages that are often foreign to non-developers.
As a result, working with a developer can also call for a particular set of skills. But the key to building great relationships and easing tension between developers and non-developers is simple: it all starts with communication.
If you work with developers, whether you're in marketing, editorial, ops, or another department, chances are you've experienced the disconnect between these siloed fields first hand. Maybe not in a full-on interdepartmental feud, but what about a missed deadline caused by lack of communication? A terse email that could've easily been avoided? Experiences like these are not uncommon.
"Include [developers] in the planning process." If a product or feature is going to need a developer down the line, it's best to include them from the beginning. They don't need to have creative input, but their technical expertise will help keep the plan on the right track and avoid delays in the future.
"Don't make assumptions." Only a developer can know how technically complicated something is going to be. Don't assume that any request will be quick or easy. Coordinate with your developers to "evaluate the complexity of a task," says Dmitry, "before [establishing] a hard deadline."
In the end, a successful relationship with your developers is all about communication. Effectively communicating across departments isn't easy, but it starts with recognizing your pain points and improving from there. "Talk to your developers about your projects, don't just hand them assignments," Dmitry suggests. "Remember: You're all in this together."
I have a friend whose discerning toddler refuses to eat her preschool lunch unless it's in a bento box. I get it; baby carrots are much more appealing when stacked in their little compartment than not. That made me think: when did adult lunchtime stop being fun? When did a soggy sandwich brought from home or a $12 bowl of greens, scarfed down in 10 minutes while scrolling through emails, come to define midday sustenance? Enter adult lunchables.
A Q&A with Netskope's Senior Engineering Manager May Yan
May Yan has spent most of her impressive decades-long engineering career in California, but I asked her to take me back to the beginning — to when she first moved to the Golden State from China to get her Master's Degree in Computer Engineering at Santa Clara University. Were there any challenges, I wondered, as she adjusted to life and corporate culture in the U.S.?
It's pretty common in your 20s and 30s to feel like you're treading water financially – dealing with the immediate bills and expenses and not thinking too far beyond the next year or two. But this is the ideal time to think about the financial objectives you want to achieve. The best rewards don't come without risks, and there's no better time to start setting goals and taking chances.
In an interview, it's hard to anticipate what questions an interviewer will ask, but there is one that they are guaranteed to ask every single time (and it may be the most important question of the interview): "Do you have any questions for me?"