Skip to main content

FAQ

Frequently asked questions about me, my work, and my technical preferences. Get to know me better through these common questions.

Technical Preferences

On the backend: Golang, Python, and Rust. On the frontend: TypeScript. That's my preferred combo for building reliable, performant systems end-to-end.

Both — I'm truly full‑stack and also comfortable with DevOps. I like to take things from idea to production: frontend, backend, infra, CI/CD — the whole thing.

It depends on the project's specifics and constraints — I pick tools to fit the problem. The good news: with me, you have it covered broadly, from frontend and backend to infrastructure.

No strong preference — the team should decide. Consistency is what matters.

JetBrains suite: IntelliJ IDEA for miscellaneous/monorepos, GoLand for Go, PyCharm for Python, WebStorm for frontend, DataGrip for databases, and so on. For COBOL, I use VS Code.

Absolutely — I try to learn daily. I explore broadly across mobile, web, DevOps, and machine learning, keeping my toolkit sharp without fixating on course counts.

Solid experience with AWS and GCP, plus Kubernetes and Docker. I handle the full DevOps cycle — infrastructure as code, CI/CD pipelines, container orchestration. I can take projects from local development to production-ready cloud deployments.

From the heart — React. I have 5+ years of experience with both React and Angular.

Work & Experience

Projects that solve real problems and have a meaningful impact. I particularly enjoy building scalable distributed systems, real-time applications, and IoT solutions. My Planning Poker project and various IoT experiments reflect this passion for practical, interactive systems.

I'm always open to interesting opportunities! Feel free to reach out via email or LinkedIn to discuss potential collaborations. I'm particularly interested in modern web technologies and system architecture — anything non‑trivial.

Remote for the win — only remote, and I love it.

Over 12 years in software development, starting from 2013. I've worked across various domains including fintech, healthcare/IoT, and retail, gaining experience with diverse tech stacks and architectural patterns.

Building distributed IoT systems with real-time data processing. Coordinating sensors, edge computing, and cloud infrastructure while maintaining reliability and performance taught me a lot about system resilience and scalability.

Absolutely. Architecture reviews, code audits, tech stack evaluations, and performance optimization — I'm happy to lend my expertise. Sometimes a second set of experienced eyes is all you need.

At least 3 months. Reach out early if you have specific timelines so we can plan accordingly.

Personal

Simple and professional - it's my surname (Janiec) with a 'k' for Krzysztof, plus .dev because... well, I'm a developer! It's easy to remember and clearly communicates what I do.

Playing games on various platforms — PlayStation, Nintendo, Xbox, and PC. I'm a big fan of Souls and souls‑like games.

Definitely coffee — black, without milk.

Curiosity and the desire to create things. I've always been fascinated by how software can solve problems and automate tasks. The ability to turn ideas into working applications is incredibly rewarding.

Contact & Collaboration

Preferably via email at contact@kjaniec.dev. LinkedIn is also okay, though some days I may not have time to check it.

Absolutely! Whether it's open-source projects, technical writing, speaking opportunities, or consulting - I'm always interested in connecting with fellow developers and exploring new collaborations.

Central European Time (CET/CEST) — Poland. I'm flexible with meeting times for collaboration with other timezones, especially for kickoffs and important discussions.