Architecture: Quality Attributes First, Trade-offs Later

Daniil Kuleshov has worked in technology for twenty years and combines Staff engineering with an architecture role at T-Bank. In Architecture Research and Transformation he advances the 100M program and reviews critical services with security, infrastructure, and reliability experts.

Daniil discovered computing at school in a military town and spent extra time in its computer lab. At Lobachevsky University he chose information systems, then sold PCs with friends, built Flash sites, and ran a web studio. A fifty-city directory delivered early lessons in SEO, high load, and product mistakes.

After building government systems, Daniil moved to Moscow for deeper engineering challenges and joined a real-time bidding startup. He learned SSPs, DSPs, and DMPs, introduced delivery and management practices, and joined Tinkoff after a company crisis. At the bank he revived an advertising platform and managed its sociotechnical system.

A new authorization program shows his architecture method: classify stakeholders, collect requirements, quality attributes, and constraints, then compare options against relevant criteria. An experiment can stop while preserving contracts and knowledge; a sustainable career also needs clear boundaries among work, family, and continuous learning.