What Truly Defines a Senior Engineer? Insights from Etsy’s CTO

Gen‑X engineers often expect rapid career advancement, but becoming a senior engineer in five years is rarely realistic; true seniority comes from sustained growth and maturity.

The author, reflecting on years of hiring and mentoring senior engineers, argues that seniority is not a title that appears overnight but a set of evolving standards that go beyond technical knowledge.

To avoid conflating titles with vague expectations, the author references engineering maturity, emphasizing that a senior engineer should be a mature engineer.

Essence of a Mature Engineer

Mature engineers constantly seek constructive criticism of their designs and ask their peers questions such as:

"What might I have missed?"

"Why doesn’t this work?"

"Can you critique my approach as thoroughly as possible?"

"Is the solution understandable and maintainable for the rest of the organization?"

They understand that good peer review leads to better decisions and that engineering success depends on collaboration, not on solitary brilliance.

Mature engineers recognize that technical prowess alone (e.g., writing Bloom filters in Erlang or multithreaded C) is insufficient; without teammates willing to work with them, expertise is meaningless.

They practice humility, avoid arrogance, and value the joy of building alongside supportive colleagues.

Communication awareness is another hallmark: they know their strengths and weaknesses, solicit feedback, and strive to express ideas confidently without being aggressive.

As an industry, we must avoid personal criticism while embracing critique of work products; code has no feelings, and blaming the code rather than the coder fosters healthier collaboration.

Mature engineers do not shy away from estimation. They view commitments, timelines, and estimates as essential tools for predictable delivery and take responsibility for them rather than deflecting.

“Commitments, schedules, and estimates are indispensable in orderly business; no engineer should hide behind vague excuses.”

They accept uncertainty, understand trade‑offs (e.g., the ETTO principle), and are comfortable working within risk boundaries while maintaining foresight.

Ten Commandments of Selfless Programming

Accept that you will make mistakes and discover them early before production.

Remember you are not your code; code reviews aim to find problems, not assign blame.

Seek advice from those who know more, even when you think you don’t need it.

Never rewrite code without consultation; distinguish between fixing and rewriting.

Treat less‑knowledgeable people with respect, patience, and humility.

Embrace change as the only constant and view each change as a new challenge.

Authority stems from knowledge, not position; cultivate expertise to earn respect.

Fight for your beliefs gracefully and accept failure without retaliation.

Avoid becoming the “corner programmer” who hides away; engage actively in the community.

Critique the code, not the person; keep feedback constructive and improvement‑focused.

Novice vs. Expert: The Dreyfus Model

The Dreyfus model outlines five stages of skill acquisition:

Novice : follows strict rules, limited situational awareness, little discretion.

Advanced Beginner : uses multiple guidelines, still limited context.

Competent : engages in conscious, deliberate planning and follows standard procedures.

Proficient : sees problems holistically, perceives deviations from normal patterns, applies maxims contextually.

Expert : operates intuitively without reliance on rules, acts swiftly based on deep experience.

While the boundaries are not absolute, recognizing these stages helps engineers understand their growth path.

Ultimately, a mature engineer balances technical skill with empathy, communication, and a willingness to share knowledge, fostering an environment where the team’s success outweighs individual accolades.