Position: CTO / Head of Engineering / Solutions Architect / Principal Software Engineer
Category: Lead
Experience: 11 years | English: fluent

- Was able to solve non-trivial technical challenges with minimal or no prior experience in the corresponding platform, technology or framework
- Successfully started a number of projects by initially leading a pre-study phase and then taking the project from there
- Was able to quickly learn new technology and deliver on business-critical projects
- Helped to win strategic customers by gathering business requirements, drafting user flows, writing solution descriptions, designing the system architecture, and calculated AWS infrastructure cost projections
- Spoke at STHLM Tech Fest with presentations on managing technical debt at a startup
- Introduced a structured software project estimation approach, including guidelines, Excel templates, and training sessions
More than 15 years of experience on technical leadership positions as a development lead / architect / CTO. Full-stack expertise, primarily with .NET / .NET Core / NodeJS on the back-end side, and React on the front-end. On top of that, I have Python expertise under my belt, primarily for automated data collection and aggregation.

To summarize my responsibilities, they were mainly about staring projects from ground zero or saving a "sinking" project in a SWAT fashion (that sometimes included gradually transforming a legacy codebase). Also, consulting and coaching on the software development process and engineering excellence.

For the next step in my career, I am looking for a technical leadership position at a software product development company or at a startup that has reached at least Series A funding. An ability to solve technical problems and to contribute to the software solution hands-on is essential: I love to code and to create software, so it's unlikely I would consider a purely managerial position. What would also matter is the ability to communicate directly with product management and/or sales in order to have full understanding of how the product is positioned on the market, and what are they key selling points / pains of the existing userbase.
- Ideally, a small to mid-size software product house or a well-funded startup (preferably Seed A round or beyond).
- Remote strongly preferred till we are through these pandemic times
- New product development or adding a substantial amount of new functionality to an existing product. Some fraction of supporting legacy solutions is acceptable, but I am certainly NOT looking for projects where the majority of work is supporting and maintaining existing legacy solutions.
- Would be willing to learn new or expand my knowledge of the existing skills
- Not afraid of technical challenge
- Ideally, an one or two pizzas team, though it's rather a "nice to have" preference. 
- Lack of bureaucracy and of inflexible rules with no apparent purpose. Reasonably justified rules e.g. ones related to information security, regulatory compliance or GDPR, are perfectly acceptable, though.
- Pragmatic (rather than hype-driven) approach to choosing architecture and technology would be nice, too
- Would NOT consider projects with apparently outdated technology
- Critical situations do happen, but I would definitely NOT work at a company where overtimes / crunch are *the norm*.