i am windows system-level developer. programming in both kernel and user mode. i have very deep knowledge about windows architecture, internals and undocumented features - what is "under the hood" and ability correct to use this. this knowledge gives me very great freedom of action. windows for me is not a black box. i can finding creative, effective and nice solutions. i have very deep knowledge and huge experience in asynchronous programming, multithreading, synchronization, manage objects lifetime and access (reference counting and rundown protection)

in kernel mode i write generic/separate (non Pnp) drivers, WDM (Pnp) drivers (virtual bus driver (FDO) and filter drivers (FiDO) ) primary in storage, filesystem and input (keyboard/mouse) stack. legacy filters and minifilters. filtering registry

calls and objects operations. process, threads, images notifications. in depth knowledge kernel development specific, kernel <-> user mode communication, all aspects of IRP processing, kernel objects, memory dump analyze and remote/live debugging, kernel networking(over TDI interface), DPC, APC and many etc..

in user mode excellent knowledge of WIN API (including so called 'native' API), process and threads, DLLs, synchronization (of course this and many another related and to kernel mode too), IPC, windows services, boot execute apps, registry, filesystems (especially NTFS(streams, EA, internal structures)), memory management, cryptography, authentication and authorizations, security (tokens, security descriptors, labels, integrity levels), networking - write code and for client and for higly loaded servers too(based on IOCP (KQUEUE object in kernel)), client <-> server communications, COM, RPC, windows shell, GUI, exception handling (SEH/VEX), api and interface hooking, perfect knowledge of PE format,and many many etc..

i have especially huge experience in debugging (have own toolkits for this including own private debugger, one of the best from existing), experience in reverse engineering (however i prefer debugging and analyze code under debugger than under static code analyzer like IDA). ability research why some api "not worked", effective debug cross-process calls, system processes, including protected (yes! my debugger can do this), view kernel memory and object in run-time, many many etc

my main working language - c++ (c++03, CL.EXE compiler(in MSVS)). use x86/x64 assembler when need - perfectly know both. deep knowledge of compiling/linking process and resolve related issuer like undefined/unresolved symbol, name mangle, calling conversion, etc. SDK and WDK. use IDL when need for RPC and COM interfaces or for communications with js script from c++ code (implement IDispatch by typelib help) - have great experience in this. have some basic knowledge in js script and HTML, but not deep.

my Environment - Windows xp-10(32 64), Ms Visual Studio (2005+), SDK+WDK, my own Debugger and tools + MSVS integrated + WinDbg. VmVare.

i always focused on code quality and effective, have very high motivation.

some my libraries code - https://github.com/rbmm/LIB (for demo only, something i cut here)

winZ - my windows class library (like MFC - ~ in 100 times smaller, but not less functional and more

effective)

asio - user mode library for asynchronous I/O, classes for pipes and sockets(tcp/udp/icmp), SSL, thread pools

kasio - kernel mode library for asynchronous I/O, classes for pipes and sockets (tcp/udp) based on TDI (despite it marked as deprecated yet begin from vista - it great worked and in latest win 10 builds)

inc - some general util code, including my own rundown protection implementation

from summer 2016 i have account on stackoverflow.com forum (posting basically in [winapi] tag) - http://stackoverflow.